Don't just hold the keys — build the locks

Every device on the guide page was designed by a small group of people who decided not to wait for permission. This page is the ladder from user to producer: open hardware, open firmware, open silicon — and a proving ground unlike anywhere else on earth. The creators of the next thousand years start as students with a $50 kit.

127 cells — the bComb's own geometry from rung 4, wearing festival colors: every smaller hexagon a kernel of truth, every pulse a photon the rig could really send. The decor here is the doctrine with the lights on.

The builder's ladder

1
Build one — the build party.

A SeedSigner or Krux assembles in an afternoon from ~$50 of commodity parts. You leave holding a signer you built with your own hands and can verify to the last line. This is the ceremony that converts belief into capability.

2
Read one — firmware literacy.

Open the source of the device in your pocket. Trace one flow end to end: seed words in → key derived → transaction displayed → signature out. You now know more about your own custody than 99% of holders.

3
Change one — your first patch.

Fork, change a screen, tighten a check, add a language. Flash it. The moment your own build boots is the moment vendors become optional. (This is exactly how bSAFE 7 began: a fork that restored what upstream dropped.)

4
Speak light — the optical layer.

Screens and cameras are radios that can't be jammed silently. Study fountain-coded QR (BC-UR), then the bComb beam — 127 hexagonal cells, no_std, honest CRCs — and make two devices talk with photons alone.

5
Wear it — the open wearable gap.

Watches and rings that sense heartbeat and presence are mostly closed today. That's not a wall, it's an opening: open-firmware wearables that attest liveness to a sovereign identity barely exist. First movers get to define the category.

6
Silicon — the thousand-year layer.

Auditable secure elements (TROPIC01), open microkernels (Xous/KeyOS-class), reference designs anyone can manufacture. The generation that treats chips the way this one treats code will build devices no empire can discontinue.

The proving ground: the massive festival

A giant EDM festival is a city that exists for three days: hundreds of thousands of people, dense radio spectrum, patchy backhaul, real money moving fast, and everyone wearing something on their wrist. It is the hardest honest test environment sovereign tech can ask for — a temporary micro-economy where the whole loop (identity → payment → access → data) runs at maximum pressure and then resets. What survives a festival scales to a city.

Case study A — EDC Las Vegas.

On the order of half a million attendances across three nights in a speedway. Today it runs on closed RFID wristbands and centralized cashless systems: one vendor, one database, one point of failure — and the attendee owns none of it. Study questions: map the payment + access flows; where does the system fail when backhaul drops? What would the same loops look like on optical + mesh with self-custodied identity? What does the attendee get back when they own their own data?

Case study B — Tomorrowland, Belgium.

Roughly four hundred thousand people across two weekends, with one of the most sophisticated closed wristband ecosystems in the world (payments, social features, access tiers). The most polished version of the centralized model — which makes it the best benchmark to surpass. Study questions: what UX standard must a sovereign wristband meet to feel this smooth? Which features exist only because the data is centralized — and which get better when it isn't?

The sandbox study: a socioeconomic wellness experiment.

Run the sovereign stack at festival scale and the byproduct is a research dataset that exists nowhere else: a complete, consented picture of a temporary economy — spending, movement, mesh connectivity (bMeshAi), and Lane-C wellness telemetry from wearables — in a population of hundreds of thousands, with a natural control (the same festival on the closed stack).

The data law is inherited, not invented: per-study opt-in bound to a persona nullifier, never the root identity; raw data sealed to the participant; only aggregates leave; participants are paid from the proceeds in the same economy they generated. Monetizing raw data means monetizing consented, participant-owned data — the study inherits the custody-disclosure law wholesale, and a study that can't recruit under those terms doesn't run.

The multi-dApp front end. One surface, many dApps: wallet, access, marketplace, dispute, wellness — each an app holding a child seed, none holding the root, all riding the same mesh (bMeshAi) when the towers choke. The festival build IS the city build at 1:100 scale; cross-pollination is the point. Students who ship a stage-scale deployment have shipped the architecture of the macro economy.

Where to start this week

Get the parts list from the guide page. Host a build party — six people, one afternoon, six signers. Then pick your rung on the ladder above and climb one step. The onboarding surface will enroll your bzDiD when you're ready; the same identity follows you from your first $50 build to whatever you ship at festival scale.