Blockula v1.0.10

Upgrade: blockula release install v1.0.10 --provenance. It checks checksums.txt (its first line
names v1.0.10) against the offline signature checksums.txt.sig by the Blockula release key
(ML-DSA-65) whose key id you pinned at your first install, then the archive's SHA-256,
provenance and the binary's version, and never runs this release's install.sh. A first
install checks the archive against the SHA-256 announced in the operators' channel first:
docs/OPERATIONS.md "A first install". Take the release key id from SECURITY.md, the website
and the operators' channel, never from this page. Every file also has SLSA build provenance
(gh attestation verify <file> --repo jackdishman/blockula --source-ref refs/tags/v1.0.10), which a
compromised GitHub account or workflow could produce as well. The Linux archives rebuild bit
for bit with COMMIT=<commit> scripts/reproduce-release.sh v1.0.10, which first rebuilds
the wallet they embed (blockula-wallet.tar.gz).

Developers: curl -fsSL https://github.com/jackdishman/blockula/releases/download/v1.0.10/install.sh | BLOCKULA_VERSION=v1.0.10 sh
(the release's own script: it checks what it can, but it's only as trustworthy as this release).

What's Changed

• Name sites: .blockula.app for .boo owners; only the project's own hosts marked as its by @jackdishman-blockula-release[bot] in #173
• Hosting scripts: find the volume they already have (no new volume on every upgrade) by @jackdishman-blockula-release[bot] in #180
• Release v1.0.10: only the project's own hosts are marked as its; hosting scripts reuse their volume; npm 1.0.10 by @jackdishman-blockula-release[bot] in #184
• feat(cli): open the local wallet with dev --open by @darkoheth in #153
• Example: a club that votes, open proposals shown from their bound content by @ndihokubway in #183
• Randomness for programs: host ABI, guest helpers, and dice by @blockula-bat in #182
• FAQ: what Soul is, and a Soul section for agents by @jackdishman-blockula-release[bot] in #186
• Blackjack: a program on protocol v2, its dealer daemon, a table page and an X bot in dry run (stacked on #182) by @blockula-bat in #185
• Example: a bounty board, a repo's open Hunts as a Markdown table by @ndihokubway in #187
• Séance juries in the wallet: seal and reveal a juror's ballot with a passkey by @janvierhumura in #181
• Blackjack: security review, and a bet in two transactions (commit the seed's hash, then reveal it) by @blockula-bat in #188

New Contributors

• @ndihokubway made their first contribution in #183

Full Changelog: v1.0.9...v1.0.10

Blockula v1.0.9

Blockula v1.0.9: profiles at /boo/<name>, and an X proof post that links them. UNSIGNED, like every release so far.

This release is not signed. The offline ML-DSA-65 release key doesn't exist yet, so there's no
checksums.txt.sig and no release key id to pin. blockula release install refuses to install without one.

The one-line install.sh and the MCP's install_node check each archive's SHA-256 against checksums.txt,
whose first line is # blockula-release v1.0.9. With a logged-in gh, they also check its SLSA build
provenance (gh attestation verify <file> --repo jackdishman/blockula --source-ref refs/tags/v1.0.9), and
they report which checks ran. A compromised GitHub account or release workflow could produce both. The
stronger check is a bit-for-bit rebuild of the Linux archives:
COMMIT=3ccf255d6f2f46f386e0c091524179d1c28f617d scripts/reproduce-release.sh v1.0.9.

Blockula is for education and research only. Each chain's coins have no value: nobody sells them, buys them or gets paid in them.

What's new

• Profiles at /boo/<name> (#178): a boo's public page on its chain. It shows the name, the GitHub and X handles the account links (each with how far it's been checked), Soul, hunts won, contributions claimed and its other names. Balances, keys and activity stay on the account's page. Every node answers https://<node>/boo/<name> and sends it on to the profile in the wallet it serves, so it's the link to share. Named boos in the directory, the guestbook and the leaderboards open their profile.
• The X proof post links the profile, never a .boo name (#177): .boo is also a web domain, so X turned you.boo in a post into a link to an unrelated website. The post now carries https://<node>/boo/<name>, or blockula.app for an account without a name or a node that isn't on https. Posts already made stay valid: only the code is checked.
• SDK: booProfileUrl(node, name) is new, and xProofPost(code, profile?) takes the profile link where it took a label.
• npm: @blockula/sdk and @blockula/mcp are 1.0.9.

No protocol change: v1 blocks replay exactly as before.

Blockula v1.0.8

Blockula v1.0.8: one bar across the site, the explorer and the wallet; calling a program from the wallet. UNSIGNED, like every release so far.

This release is not signed. The offline ML-DSA-65 release key doesn't exist yet, so there's no
checksums.txt.sig and no release key id to pin. blockula release install refuses to install without one.

The one-line install.sh and the MCP's install_node check each archive's SHA-256 against checksums.txt,
whose first line is # blockula-release v1.0.8. With a logged-in gh, they also check its SLSA build
provenance (gh attestation verify <file> --repo jackdishman/blockula --source-ref refs/tags/v1.0.8), and
they report which checks ran. A compromised GitHub account or release workflow could produce both. The
stronger check is a bit-for-bit rebuild of the Linux archives:
COMMIT=0b635e78f19f948586d32c49b9ea71235554c245 scripts/reproduce-release.sh v1.0.8.

Blockula is for education and research only. Each chain's coins have no value: nobody sells them, buys them or gets paid in them.

What's new

• One bar across blockula.app, a chain's explorer and its wallet (#172): every node's explorer and the wallet it serves carry a slim bar above the masthead that leads to each other and back to blockula.app, with the page you're on marked. On a node built without the wallet, the explorer hides its wallet links.
• Call a deployed program from the wallet (#174): a program's page (/program/{address}) runs its views and builds its calls, with a typed field for each argument. The review shows the exact transaction and the program's full version digest before the passkey signs it. Only an owner key of a personal account calls.
• The SDK's program ABI codec (#174): encodeProgramInput, encodeProgramValue, decodeProgramValue, decodeProgramInput, sameProgramValue and ProgramValueError, held to the node's own encoding by shared test vectors.
• Wallet checklist: later stages open for a look (#170): the stages after the current one are buttons that show their tasks early.
• npm: @blockula/sdk and @blockula/mcp are 1.0.8.

No protocol change: v1 blocks replay exactly as before.

Blockula v1.0.7

Blockula v1.0.7: a validator at home in one command, shared accounts, linking an X account, the pulse. UNSIGNED, like every release so far.

This release is not signed. The offline ML-DSA-65 release key doesn't exist yet, so there's no
checksums.txt.sig and no release key id to pin. blockula release install refuses to install without one.

The one-line install.sh and the MCP's install_node check each archive's SHA-256 against checksums.txt,
whose first line is # blockula-release v1.0.7. With a logged-in gh, they also check its SLSA build
provenance (gh attestation verify <file> --repo jackdishman/blockula --source-ref refs/tags/v1.0.7), and
they report which checks ran. A compromised GitHub account or release workflow could produce both. The
stronger check is a bit-for-bit rebuild of the Linux archives:
COMMIT=20745cb98512ff5a37af2e21e488a01d65bf0e34 scripts/reproduce-release.sh v1.0.7.

Blockula is for education and research only. Each chain's coins have no value: nobody sells them, buys them or gets paid in them.

What's new

• blockula validator setup (#158): a validator at home in one command. It checks the genesis hash, works out how the chain's validators reach each other, makes the key once, takes the bond from the faucet, runs the node as a launchd agent or systemd service, waits for sync and registers, then prints the message to send the chain's owner. --dry-run shows the plan first.
• Shared accounts (#169): the chain's M-of-N multisig in the wallet (/shared) and the MCP. People and agents co-own an account; owners propose and approve, and the review page renders each action itself and signs its digest, never the node's summary.
• Link an X account (#166, #168): show which X handle belongs to an account, verifiable by anyone with the SDK (verifyXLink) and no X API key, at /wallet/x/ on every node. No protocol change.
• The pulse (#165): accounts active this week, counted as people (validators, programs, system accounts and named bots left out), on /metrics (blockula_accounts_active), /api/status (pulse) and both explorers' front pages. --pulse-exclude <address|name> leaves out bots.
• Contributor docs point at the demo chain (#163): Blockula's own Hunts and contribution pool run on blockula-demo-2.
• npm: @blockula/sdk and @blockula/mcp are 1.0.7.

No protocol change: v1 blocks replay exactly as before.

Blockula v1.0.6

Blockula v1.0.6: the balance chart, the SDK's demo network, the wallet in Docker images, the invite QR. UNSIGNED, like every release so far.

This release is not signed. The offline ML-DSA-65 release key doesn't exist yet, so there's no
checksums.txt.sig and no release key id to pin. blockula release install refuses to install without one.

The one-line install.sh and the MCP's install_node check each archive's SHA-256 against checksums.txt,
whose first line is # blockula-release v1.0.6. With a logged-in gh, they also check its SLSA build
provenance (gh attestation verify <file> --repo jackdishman/blockula --source-ref refs/tags/v1.0.6), and
they report which checks ran. A compromised GitHub account or release workflow could produce both. The
stronger check is a bit-for-bit rebuild of the Linux archives:
COMMIT=66d7d1c78a50f3d20640a6fdb1e7a0bf889e35a2 scripts/reproduce-release.sh v1.0.6.

Blockula is for education and research only. Each chain's coins have no value: nobody sells them, buys them or gets paid in them.

What's new

• An account's balance over time on the wallet (#150).
• Explorer front-page news (#149): open proposals and large movements.
• The SDK knows the demo chain (#151): new Client({ network: "demo" }) and Client.demo(), pinned to its chain id, genesis hash and clock like the MCP's --network demo; the examples take --network demo.
• The playground's house bots (#151): deploy/host-bots.sh runs the trick-or-treat house and the guestbook on Fly next to a hosted chain. Docs on watching for payments sent to a name (match to.address, not action.to). The 1.0.4 install workaround is gone.
• The wallet in Docker images (#155, thanks @darkoheth): deploy/Dockerfile builds the served wallet in, so a Docker-built node serves /wallet/.
• A QR code for the wallet on the invite page (#154, thanks @darkoheth), drawn by the wallet's own encoder inside the explorer's one script.
• A shared-tab example (#143, thanks @janvierhumura): a tab split among friends and settled by .boo name.
• npm: @blockula/sdk and @blockula/mcp are 1.0.6.

No protocol change: v1 blocks replay exactly as before.

Blockula v1.0.5

Blockula v1.0.5: every deployed program on the Programs page; agents first. UNSIGNED, like every release so far.

This release is not signed. The offline ML-DSA-65 release key doesn't exist yet, so there's no
checksums.txt.sig and no release key id to pin. blockula release install refuses to install without one.

The one-line install.sh and the MCP's install_node check each archive's SHA-256 against checksums.txt,
whose first line is # blockula-release v1.0.5. With a logged-in gh, they also check its SLSA build
provenance (gh attestation verify <file> --repo jackdishman/blockula --source-ref refs/tags/v1.0.5), and
they report which checks ran. A compromised GitHub account or release workflow could produce both. The
stronger check is a bit-for-bit rebuild of the Linux archives:
COMMIT=8320a955fbe74efd65bc17ebd13ba9fd1d0688d0 scripts/reproduce-release.sh v1.0.5.

Blockula is for education and research only. Each chain's coins have no value: nobody sells them, buys them or gets paid in them.

What's new

• Every deployed program on the Programs page (#141, #139).
  • The node serves GET /api/programs?after=&limit=: every program, newest first, a page at a time.
  • The wallet's Programs page lists from it, with featured programs pinned for a chain on top.
  • Against an older node, the page falls back to the creates in recent blocks, and says so.
• Agents first (#140): blockula create --fast, the MCP's call_program from an agent's own account, a leaderboard, and a front page that leads with agents.
• The playground (#138): agents join the demo chain in one line, sign a guestbook and play trick or treat.
• Boos (#136): the chain's people are called boos.
• Site (#132, #133, #134): a comparison with Solana and Ethereum's Layer 2s, a form to ask to join the demo chain's validators, and four ways to help build Blockula.
• npm: @blockula/sdk and @blockula/mcp are 1.0.5.

No protocol change: v1 blocks replay exactly as before.

Blockula v1.0.4

Blockula v1.0.4: Terms of Use and a Privacy Policy, agreed before any wallet; Face ID before every spend. UNSIGNED, like every release so far.

This release is not signed. The offline ML-DSA-65 release key doesn't exist yet, so there's no
checksums.txt.sig and no release key id to pin. blockula release install refuses to install without one.

The one-line install.sh and the MCP's install_node check each archive's SHA-256 against checksums.txt,
whose first line is # blockula-release v1.0.4. With a logged-in gh, they also check its SLSA build
provenance (gh attestation verify <file> --repo jackdishman/blockula --source-ref refs/tags/v1.0.4), and
they report which checks ran. A compromised GitHub account or release workflow could produce both. The
stronger check is a bit-for-bit rebuild of the Linux archives:
COMMIT=fb9f287d3755da90c94a5955dab398f6ddb9d846 scripts/reproduce-release.sh v1.0.4.

Blockula is for education and research only. Each chain's coins have no value: nobody sells them, buys them or gets paid in them.

What's new

• Terms of Use and a Privacy Policy (#124). Before it makes, restores, links or unlocks a wallet, the wallet asks you to agree. The agreement is remembered per device, and asked again when the terms change. Both pages are served at /terms and /privacy by blockula.app and by every node's wallet, and the explorer's footer links them. The terms say it plainly: for education and research only, the coins have no value, experimental and unaudited, self-custody, public and permanent.
• Face ID, fingerprint or PIN before every spend (#126). This covers Send and payment links, the explorer's action forms, claiming a name, staking, and adding a key that can spend. The wallet asks the passkey again even while it's unlocked, and checks that the answer derives the same key. Nothing is signed before the check, and a cancel signs and sends nothing.
• ML-DSA 0.1.2 and ML-KEM 0.3.4 (#125). These are constant-time hardening and zeroization updates. ML-DSA-65 signatures are byte-identical, and every v1 block replays as before. Commonware stays on 2026.9.0.
• Hosting:
  • deploy/host-validator.sh runs a validator for an existing chain on Fly, with a beginner's guide in docs/BECOME-A-VALIDATOR.md (#121).
  • deploy/host-chain.sh takes PEER_HTTP, so a restarted validator of a two-validator chain can sign again (#123).
• Tokenomics (#124). A value-bearing mainnet's genesis builder now has no founder allocation and no distribution bucket. Nothing in this release makes such a chain. docs/PUBLIC-CHAIN.md says what the permanent demo chain promises.
• npm: @blockula/sdk and @blockula/mcp are 1.0.4.

No protocol change: v1 blocks replay exactly as before.

Blockula v1.0.3

Blockula v1.0.3: blockula create, a People directory, Request links, and the wallet on your Home Screen. UNSIGNED, like every release so far.

This release is not signed. The offline ML-DSA-65 release key doesn't exist yet, so there's no
checksums.txt.sig and no release key id to pin. blockula release install refuses to install without one.

The one-line install.sh and the MCP's install_node check each archive's SHA-256 against checksums.txt,
whose first line is # blockula-release v1.0.3. With a logged-in gh, they also check its SLSA build
provenance (gh attestation verify <file> --repo jackdishman/blockula --source-ref refs/tags/v1.0.3), and
they report which checks ran. A compromised GitHub account or release workflow could produce both. The
stronger check is a bit-for-bit rebuild of the Linux archives:
COMMIT=8afc4327603ec85d9544e0b731e102e1e90f10b4 scripts/reproduce-release.sh v1.0.3.

Each chain's coins have no value: nobody sells them, buys them or gets paid in them.

What's new

• blockula create (#111) is the new name for blockula launch. launch still works as an alias.
  • The chain's guide is now README.md in its home.
  • The internet-reach hint now points at the right Tailscale setting.
  • docs/CREATE.md
• People (#113): the wallet and explorer list a chain's accounts and .boo names, with balances.
  • The node adds GET /api/accounts and GET /api/names.
  • The SDK adds client.accounts() and client.names().
• Request (#113): your profile makes a payment-request link with a QR code. Opening the link fills in the
  Send form.
• Add to Home Screen (#113): the wallet a node serves has a web app manifest named after the chain, and
  icons. On iOS it explains how to add it to the Home Screen.
• A minimal Python client (#56, thanks @darkoheth): sdk-py reads the chain and signs transfers.
• Hosting a chain on Fly (#111): deploy/host-chain.sh runs one verified release binary behind HTTPS.
  This is how the demo chain at https://demo.blockula.app runs.
• npm: @blockula/sdk and @blockula/mcp are 1.0.3.

No protocol change: v1 blocks replay exactly as before.

Blockula v1.0.2

Blockula v1.0.2: launch your own chain, and every node serves its own passkey wallet. UNSIGNED, like every release so far.

This release is not signed. The offline ML-DSA-65 release key doesn't exist yet, so there is no
checksums.txt.sig and no release key id to pin, and blockula release install refuses to install without one.

The one-line install.sh and the MCP's install_node check each archive's SHA-256 against checksums.txt
(first line # blockula-release v1.0.2). With a logged-in gh, they also check its SLSA build provenance
(gh attestation verify <file> --repo jackdishman/blockula --source-ref refs/tags/v1.0.2), and they report
which checks ran. A compromised GitHub account or release workflow could produce both. The stronger check is
a bit-for-bit rebuild of the Linux archives:
COMMIT=e3b5f95c24303d02729c0746b6bbc7851aeef906 scripts/reproduce-release.sh v1.0.2.

Each chain's coins have no value: nobody sells them, buys them or gets paid in them.

What's new

• blockula launch (#97, #98) makes and starts a chain of your own in about a minute. It asks four
  questions:

  • a name and a ticker, both bound by the genesis hash;
  • who can reach it (this machine, Tailscale, a home network or the internet);
  • a block time and a faucet;
  • whether to serve it over HTTPS on your tailnet.

  It prints the one command friends run to join, and keeps it all in ~/.blockula/<chain id>/LAUNCH.md.
  docs/LAUNCH.md

• Every node serves the passkey wallet at /wallet/ (#100), so a friend needs only the node's link.

  • The wallet uses the node it comes from, is titled with the chain's name, and shows amounts in the chain's
    ticker.
  • /api/status gains "wallet": "/wallet/".
  • Each page's CSP allows only 'self' and a hash of each of its inline scripts.
  • The wallet is built once, reproducibly, as blockula-wallet.tar.gz, which is listed in checksums.txt.
    Every binary embeds that archive.

• The explorer's Start page (#100) walks through:

  • making a wallet and a first payment;
  • programs, on chains that have them;
  • inviting friends and validators;
  • changing the apps with Claude Code and deploying them.

  It also has a live tokenomics graphic, an invite page, and a prompt that connects a coding agent to the chain.

• The CLI shows amounts in the chain's own ticker (#100). Tailscale addresses (100.64.0.0/10, *.ts.net)
  count as private for plain http in the CLI and MCP.

• The public testnet is retired (#96). There's no built-in testnet RPC, and the CLI, SDK and MCP default to
  a local chain. Releases still ship blockula-testnet-2's genesis and checkpoints for its archive.

Upgrading

• Node/CLI: a drop-in replacement for v1.0.1. The protocol versions are the same, and nothing changes in
  state, consensus or the wire format. Every PR replays the recorded v1 history. The binary grows by about
  1.6 MiB, for the wallet.
• SDK and MCP: @blockula/sdk and @blockula/mcp go to 1.0.2, matching the tag. summon_chain takes
  name and token.

Commit: e3b5f95c24303d02729c0746b6bbc7851aeef906 (PR #101 merge).

• Built by release.yml. CI rebuilt the wallet archive and the x86_64 Linux archive bit for bit on second
  runners.
• Also rebuilt outside GitHub. The wallet archive and the aarch64 Linux archive were rebuilt bit for bit on the maintainer's machine, in the pinned build images. scripts/check-release-files.sh accepts this release against the reviewed commit.
• Every file's build provenance verifies against release.yml at refs/tags/v1.0.2, and every file matches
  checksums.txt.

Blockula v1.0.1: a jailed validator that stays online keeps following the chain

Blockula v1.0.1: a jailed validator that stays online keeps following the chain. UNSIGNED, like every release so far.

This release is not signed. The offline ML-DSA-65 release key doesn't exist yet, so there is no
checksums.txt.sig and no release key id to pin. blockula release install refuses to install without
one. The one-line install.sh and the MCP's install_node check each archive's SHA-256 against
checksums.txt (first line # blockula-release v1.0.1) and, with a logged-in gh, its SLSA build
provenance (gh attestation verify <file> --repo jackdishman/blockula --source-ref refs/tags/v1.0.1), and
report which checks ran. A compromised GitHub account or release workflow could produce both, so the
stronger check is a bit-for-bit rebuild of the Linux archives:
COMMIT=1e90cc20b82c10115641512f7cf3951942c7a457 scripts/reproduce-release.sh v1.0.1.
Each chain's FANG, the testnet's included, has no value: nobody sells it, buys it or gets paid in it.

What's fixed (#95)

• A validator jailed for downtime whose node stays online now keeps following the chain.
  • Before: every node let connect only the active set and the likeliest next validators, and a jailed
    validator is neither. About two epochs after it left the set, no other node accepted its connections. Its
    node then froze until it was restarted, and an Unjail sent through it never left its own mempool.
  • Now: nodes keep jailed validators (not tombstoned or removed ones) as secondary peers until they
    unjail, in the slots the likely next validators leave. So blockula validator unjail --rpc can point at
    the validator's own node.
  • Scope: this changes only which peers a node accepts. Nothing changes in blocks, state, consensus or
    the wire format.
  • Tests: a new simulator test at the production setting (two tracked peer sets) fails on v1.0.0 and
    passes now.
• On v1.0.0 and earlier: a jailed validator that stopped following comes back when it's restarted, or
  once an Unjail sent through another node lands.

The testnet (unchanged): chain blockula-testnet-2, address prefix tboo, genesis hash
b004e2f91b63429fc009088b16ec02b6d5388a03642699ae3dc6e325939f19b2, public node
https://blockula-testnet.fly.dev. The checkpoints are v1.0.0's, unchanged: the newest is block #1115999 of
2026-10-31 12:14 UTC.

Upgrading

• Node/CLI: a drop-in replacement for v1.0.0, with the same protocol versions and no state, consensus or
  wire-format change. Every PR replays the recorded v1 history, and this release's tree replays the
  testnet's own history to block 173,082 unchanged. Validators should upgrade; restart them one at a time.
• Joining the testnet: blockula join --genesis https://blockula-testnet.fly.dev --home <dir> uses the
  compiled-in checkpoint until about 2026-11-04 00:14 UTC (the testnet's 3.5-day weak-subjectivity period).
  After that, take a recent one with blockula checkpoint --peer https://blockula-testnet.fly.dev and pass
  it as --checkpoint.
• SDK and MCP: unchanged. @blockula/sdk and @blockula/mcp stay at 1.0.0.

Commit: 1e90cc20b82c10115641512f7cf3951942c7a457 (PR #95 merge). Built by release.yml; CI rebuilt the x86_64 Linux archive bit for bit on a second runner, and the aarch64 Linux archive was also rebuilt bit for bit outside GitHub, on the maintainer's machine in the pinned build image (rust:1.98.1-bookworm@sha256:93ce27a8…). scripts/check-release-files.sh accepts this release against the reviewed commit, and every file's build provenance verifies against release.yml at refs/tags/v1.0.1.