what is proven, and what is not
Most projects show you the first half. This page is the second half too — the unstarted work, the test that refuses to pass, the repo missing its licence. Every claim below comes with the command to check it, because a front door that overstates is worse than no front door.
what this is
Beehive Nature is a coordination kernel written in Rust — a small core that knows almost nothing on purpose: identity, settlement, escrow, disputes, reputation, and one canonical event log. Everything specific plugs in around it, so chains enter as adapters and applications as dApps, and swapping the settlement chain underneath does not change the heart.
Its first target is private commerce between two strangers who trust neither each other nor a middleman: the payment waits in a Zano escrow that only a Trezor can co-sign to release, disputes settle on evidence, and standing is earned by acting well rather than bought.
proven — and you don't have to take our word
Host-side Zano derivation is proven against stock Zano. Not asserted: reproducible, on your machine, from nothing:
git clone https://github.com/beehive-nature/beehive-nature.git
cd beehive-nature
cargo test -p chain-zanocrates/chain-zano hashes identical at both points (tree 6a56c1ba) and compiles the same 20 dependencies, so the code being timed never changed. The 14s was one un-repeated run. Three runs and a median replaced it. Stamped: measured 2026-08-24 against chain-zano tree 6a56c1ba, and e2e/dock-claims.mjs fails the build if that tree moves without a fresh measurement.
Before you commit anything: git config core.hooksPath .githooks — one command per clone, and it turns on the secret scan that CI re-runs on every push.
not proven — and the code says so out loud
Four tests are held shut across the workspace, and every one states why in its own #[ignore] reason — none is skipped quietly:
chain-zano/slip0010.rs waits on a verified end-to-end (seed → view_public) vector, and no tool currently produces one because that derivation is Trezor/Beehive-specific. adapter-lti waits on a real LTI 1.3 AGS capture. mastery-ledger waits on the L2 commons ledger. watchpay/tests/ledger_contention.rs is the child arm of the cross-process lock proof — it exists to be spawned by its own parent test, never to run alone. A green test on a fabricated vector would be worse than a held one, so they stay held.
The wire contract sits at proto v0.3 — and the file itself reads AUTHORITATIVE DRAFT, not "frozen". This page quotes the artifact rather than the README, because the artifact is the receipt.
unbuilt — named, never omitted
Firmware and legal review are unstarted. Not this pages framing — the ledgers: STATUS.md names both as "the unstarted work between here and anything a user touches", and the README repeats it. They are the entire distance between this repository and anything an end users money touches. No amount of green tests shortens it. The self-service contributor wizard does not exist. A form that builds your roster entry and opens the pull request for you was designed and never written. You contribute the ordinary way: open an issue, or open a PR. There is no queue you are waiting in. One public repo has no licence file. b-domain carriesSPDX-License-Identifier: MIT inside its contract sources, but GitHub reports no licence for the repository, which defaults to all rights reserved. If you mean to contribute there, ask first — the terms are not yet stated where they need to be.
the repos
beehive-nature/beehive-natureAGPL-3.0-onlyThe kernel workspace and the static surfaces. Start with README, then STATUS.md — the ledger that never rounds up — then the constitution. skaists/LOVErnment-DAOAGPL-3.0-onlyThe first community built on the kernel. It consumes this repo as a pinned dependency, never a fork —escrow-core at tag kernel-v0.1.0 — which is the property that makes the kernel a kernel rather than a template.
beehive-nature/b-domainno repo LICENSEThe .b name registry contract, deployed at kingbeelovis on Vaulta mainnet. See the licence gap named above.
if you contribute
Signed off, not signed away. Contributions need a DCO sign-off — git commit -s — certifying the Developer Certificate of Origin. There is no CLA: you keep your own copyright, nothing is assigned to any steward, and the consequence is the point — the licence can never be changed without the consent of every copyright holder, including yours. The reasoning is written down in docs/LICENSING.md.
Credited in the commit itself, with Co-authored-by: trailers — so credit travels with the history rather than with a page someone can edit later. Every machine seat working in this tree is credited the same way.
Ask anywhere here: Discussions for "why is it built this way" and "is this real yet"; Issues when something is broken. Both are open today. There is no mailing list and no support address — saying otherwise would be inventing one. The house rules are in CONTRIBUTING.md.
what this looks like when it works
Open recover.html and watch your network tab. It rebuilds keys from a recovery phrase and loads nothing at all — no scripts, no fonts, no analytics. It used to load a shared navigation script, which quietly pulled in three more; the sentence claiming otherwise was not deleted, the four loads were. Save that file to a USB stick and it still works in ten years.