Status

Where the proof of concept has got to — what has been proven, and what has not.

Implementation plan

What this page is. A proof of concept measured against reality rather than asserted — and the most useful thing it has produced is a correction. The light client, the one component we believed finished, was built on a difficulty rule that does not exist: BSV does not retarget every 2016 blocks, it recalculates every block, so the client would have rejected its first real header. It was found by replaying 324 real mainnet headers against the implementation, and it is now correct on all 324.

Below, "Done" means done and tested; everything described as designed is a specification. The vault is now built — every mint lands in a program-owned account, is released only after a 144-block (~24 hour) maturity window, and release_mint and burn_staged are permissionless. The federation registry is built and peg-out is built; what is still specified is custody. The registry records members, bonds and thresholds, and holds no key material at all, so nothing about the reserve is operational yet. Peg-out can verify a payout but cannot make one, so it cannot run end to end until a member set actually holds the reserve and pays.

What changed since this page was last accurate. The design moved from an operator-less model to a bonded federation following the architecture of RenVM — the bridge that issued wrapped ZEC — with a second quorum of trusted third parties that must co-sign every reserve movement. What we add to that reference is reorg protection it does not have: our host chain verifies BSV rather than trusting a committee to report it.

Phase 0 · Environment Complete
Phase 1A · Peg-in, BSV side Complete
Phase 1B · Against a real SV Node Complete
Phase 2 · Solana token and light client In progress
Phase 3 · Peg-out Built, with one dependency
Phase 4 · The federation Registry built, no custody
Phase 5 · Public monitoring Built

How a parameter change is gated. Every number the program turns on is projected from one sheet, config/params.json, by config/gen.py. Before a change is committed, config/check.sh regenerates the projections and — when a value differs from the committed sheet — runs the suite, because checking the projections against each other can never check them against the compiled program. It is a maintainer script and this repository has no CI, so it is a convention a maintainer follows rather than a control that can fail a build. The same script takes --profile testnet, which projects a small testnet overlay into config/out/testnet/; that profile is not compiled and nothing reads it until it is copied into the program by hand.

What is proven so far

27 instructions built 82 on-chain tests 4 of 4 peg-out steps 21 live SV Node checks all passing

What is not proven

This page is temporary. It exists so a small group can see exactly what is real — every claim above is a test you can run yourself from the repository. It will be removed before any wider release.

← Back to SOLBEAM