Claim SonicBOOM (riscv-boom)

Prove you control https://github.com/riscv-boom/riscv-boom by committing a libfpga.yaml file to its default branch. That file then becomes your listing: edit it, and the registry re-syncs. No account required.

Add this file to your repository

Create libfpga.yaml in the repository root on your default branch (main or master) with your verification token and your listing metadata:

libfpga.yaml
# --- your one-time verification token (keep this line) ---
libfpga_claim: lfpga-verify-e4677b711ff1d615411312047fe526d4

# --- your listing (all fields optional; edit freely later) ---
name: SonicBOOM (riscv-boom)
tagline: The Berkeley out-of-order RISC-V machine.
category: cpu
license: BSD-3-Clause
languages: [chisel]
interfaces: []
targets: [device-agnostic]
maturity: stable
tags: [risc-v, cpu, out-of-order, superscalar, chisel]
top: rtl/top.v            # optional: lets us run synthesis checks
testbench: tb/tb_top.v    # optional: lets us run your testbench
description: >
  A longer description of what your core does.

Your token is unique to this claim and unguessable. Anyone who can push to the repo can add it, which is exactly the proof we need. The verification badges cannot be set from the manifest: those are earned only by our toolchain actually running your code.

Verify

Once libfpga.yaml is committed and visible on your default branch, verify the claim:

After you claim

Your listing is marked claimed by you, and its metadata comes from your manifest from then on. Change a field, we pick it up on the next sync. A later phase runs our open toolchain against the top and testbench you declared and turns the pending markers into earned badges. Questions or trouble? Get in touch.