Singular documentation and on-chain release 0.11.0

0.11.0 (2026-10-16)

Features

• 491: fold, reject and reclaim prepare a funding output when none suits (8090b5c)
• 491: insert and terminate prepare a funding output when none suits (d3c330b)
• 491: plan one preparation transaction that funds the wallet (758eaf2)
• 491: plan the funding preparation for a preview without submitting it (ad93787)
• 518: reconciliation reads every transition of a fold (c54f040)
• 518: the capacity bound of a fold is nine (aca4ee4)
• 518: the Demo 1 journey settles two actors in one fold (52d64bb)
• 518: the fold settles every selected request in one transaction (0058081)
• 518: the fold's journal line lists its transitions (bd46de2)
• 518: the fold's result lists its settled requests (9bc8f72)
• 528: keri-stub convict books a termination and folds it terminal, with the journey to Terminal and its hosted job (52d3b41)
• 528: keri-stub register books an insertion and folds it, with its journey and the script serving mint and spend (18d07de)
• 528: the keri stub, a second application against the registry library (6d2de3a)
• 528: the keri-stub package: value, script pin, and a parser on the shared flag group (93aa8d5)
• 528: the separation check covers the keri stub and naming-onchain (ff4dae3)
• add the wallet verbs that keep a signing key in an encrypted vault (72f8fd1)
• decode, check and witness a bundle of unsigned transactions (db2c2ab)
• model: admit a fold only inside every request's processing window (#519) (55a64aa)
• model: admit a fold only inside every request's processing window (#519) (83f9574)
• model: refuse a batch that terminates a key it just registered (#519) (d4f8d94)
• model: refuse a batch that terminates a key it just registered (#519) (7cd2b53)
• negative-host: a mutant of the registry's occupied-key defence (8c2d555)
• negative-host: a mutant of the registry's occupied-key rule (#559) (3bff7e6)
• negative-host: add the closed-update-accepted mutant and its self-check (#661) (8924a0b)
• negative-host: follow a registry's mode and add the closed-update part (#661) (e312a64)
• negative-host: the owner reclaims the booking a refused insertion strands (84396b3)
• onchain: add the closed-datum entry point to the open-datum application (#651) (edfe6ef)
• open-datum: create a closed-datum registry and follow its mode (#654) (4e750d3)
• registry: refuse a fold outside its window and name it not-phase1 (#519) (0a9d7c3)
• registry: refuse a fold outside its window and name it not-phase1 (#519) (c720537)
• seal and open the encrypted wallet vault, from the wallet loader's own parts (8de599b)
• sign a bundle of unsigned transactions from the wallet vault (9a8014e)
• the owner's reclaim after a refused insertion and the page that shows what the chain refuses (#358, part B2) (1d9f8b0)

Fixes

• 518: the capacity bound of one gives recovery as its reason (1879f9f)
• 518: the deployment identity check waits for its devnet before removing the directory (30b76f5)
• 518: the readers of the settled list hold at bound nine (3d303c8)
• 518: the two-actor journey reads the settled list of the fold receipt (2235491)
• 526: judge the wallet on the operation's measured cost, not a fixed floor (533d554)
• 526: refuse an empty wallet with the faucet step and judge it the same on the devnet (303123c)
• 528: the keri stub reads the settled list of the fold receipt (e4f47da)
• 528: the keri stub's flake declares only what a hosted job runs (59ab5f4)
• conformance: keep validity intervals open until the row submits (bad168e)
• conformance: keep validity intervals open until the row submits (914ccf9)
• rebase: adapt ownership data to #526 wallet-floor on rebased main (5895bd5)
• rebase: bind the two #518 fold-harness sites on rebased main (da62196)
• rebase: census counts for #503 page modules on final main (15cb3a9)
• recovery: pair each forged block with its own adoption in the rollback controls (12cb5b2)
• recovery: pair each forged block with its own adoption in the rollback controls (34449db)
• registry: keep the snapshot refusal for an undecodable edge before the edge guard (#519) (9bdc4eb)

Documentation

• 491: narrate the funding paragraph and the module extent (913c5eb)
• **4...

Singular documentation and on-chain release 0.10.1

0.10.1 (2026-10-11)

Fixes

• journal rollback through an owned inspect and count every adoption (ce1dd84)

Singular is a registry of unique names on Cardano that applications can use
with their own rules. This archive includes the compiled smart contracts and
runnable examples: claim a name, change its payment destination, recover
control after losing a key, and retire it permanently so it cannot be reused.
Run the naming application on a local devnet or against your own test-network
node.

Use it

1. Download the singular-onchain-<version>.tar.gz archive and SHA256SUMS
   from this release. The checksum file also covers the documentation archive;
   download that too to check every listed file.
2. Run sha256sum --check SHA256SUMS, extract the on-chain archive, then run
   bash verify-identities.sh inside it to check the compiled validators.
3. For a local devnet, follow README.md in the archive. The runners use
   Nix. That README separates the commands verified against this release's
   source — the bounded registry journey and the identity and fixture
   checks — from the retained legacy row commands, which are not currently
   buildable or verified and must not be relied on. Release instructions
   are corrected forward; already published archives are never rewritten.
4. To use your own node and wallet, follow the
   onboarding runbook.
5. For the shared registry on preprod, follow docs/preprod.md once that
   deployment guide is published.

Singular documentation and on-chain release 0.10.0

0.10.0 (2026-10-11)

Features

• 381: control a faulted replay to RootDoesNotChain through the actor command (7702511)
• 381: fold each insertion by the other actor (f610234)
• 381: fold each termination by the other actor (2c6cbed)
• 381: fold the altered edge in the journey for the exit-zero aggregate (d737c71)
• 381: hold the computed report to receipt removal and the size cap (f26ede8)
• 381: inspect the fold root by both actors after every fold (440568f)
• 381: list harness evidence as a marked appendix after the rows (215c539)
• 381: reclaim the request inside its window by its owner (58ed2de)
• 381: refuse a withheld fold history through the actor command (53c3f0e)
• 381: refuse foreign update and terminate by controller (3f0f3c7)
• 381: refuse the wrong owner's reclaim by name (d138e8c)
• 381: reject the expired request by the other actor (54dddb7)
• 381: run token-only actors that insert and fold from the state token (4d2fd54)
• 381: wrap the foreign-open control with its stand-in proof (4ed2c47)
• 518: build the fold over a chosen pending request (c0582ea)
• 518: command-line rules for a fold that takes a selection (a2ea682)
• 518: pure fold selection judges every pending request alone (62e843f)
• 518: read the selection's inputs from pending outputs (67ed812)
• 518: the fold judges each pending request alone and settles the first that passes (9d5f4c7)
• 518: the fold takes the selection and prints the receipt lists (11c4d60)
• 528: refuse bookings the key's current entry rules out, before signing (70baaa2)
• 528: the open datum is an executable of its own, built from its own tree (6a4e0cb)
• 528: the open datum's validators move to their own Aiken project (60acd6f)
• 528: the Singular command line is the registry; the open datum is an executable of its own (c674895)
• add fixed two-edge permanent registry contract (#505) (7accc40)
• add the registry pairs and the connected short fold to the singular-negative host (d8bc7db)
• add the singular-negative host and its first forbidden and accepting pair (f733a04)
• add the tamper, termination and release pairs to the singular-negative host (7d76efb)
• carry the datum in the request and fold from the chain alone (#419) (9eaf50e)
• carry the request's datum in the model and build folds from public inputs (#419) (31ab236)
• cli: manage registry state for independent participants (75f0708)
• cli: registry create takes the processing and retract windows (2c4fa13)
• cli: registry create takes the processing and retract windows (33a01c1)
• cli: resolve managed state per network, token and wallet (#485) (32f7c9f)
• cli: run every registry command on the state token (bdbf42b)
• conformance: bind raced seed spend to winning boot (#485) (9a14be1)
• conformance: retire the saved application selector promise (e611e9f)
• conformance: run the CLI controls on the state token (da5bbea)
• demo: every actor names the registry by its state token (a28e079)
• every trie refusal names its registry, its transaction and its cause (f2784e2)
• join a registry from its state token alone (32b05d3)
• local ledger evaluation and validated network time (Part of #383) (5e6cf20)
• make registration and termination the single active registry law (e3c9ab0)
• mutant validators and stable check names for the singular-negative pairs (#358, part B1) (403b480)
• narrate on standard error or a file, as text or JSON lines (#416) (336f317)
• narrate registry, request, edge and transaction events from every command (#416) (913b147)
• negative-host: a mutant validator runs the pair against the archive's own build (fd2c279)
• negative-host: add host apps, pair arrangement, workflow and proof (6608fa9)
• negative-host: add singular-negative package on shared sources (32f1c39)
• negative-host: book an insertion for any signer and fold it (fc4153b)
• negative-host: book termination for any signer; tamper names another controller (a2b1af6)
• negative-host: fold pending requests without local evaluation (4d39b4c)
• negative-host: map the host sources in the file inventory (7f31dd4)
• negative-host: mutants for the termination booking and the additive release rules (7abde46)
• negative-host: mutants for the update signature and the escape rules...

Singular documentation and on-chain release 0.9.0

0.9.0 (2026-10-02)

Features

• deliver the preprod demonstration of one registry and one key (#300) (a08062d)

Fixes

• print and document #300's spending and preview flags where #326's flags check reads them (20fede1)

Singular is a registry of unique names on Cardano that applications can use
with their own rules. This archive includes the compiled smart contracts and
runnable examples: claim a name, change its payment destination, recover
control after losing a key, and retire it permanently so it cannot be reused.
Run the naming application on a local devnet or against your own test-network
node.

Use it

1. Download the singular-onchain-<version>.tar.gz archive and SHA256SUMS
   from this release. The checksum file also covers the documentation archive;
   download that too to check every listed file.
2. Run sha256sum --check SHA256SUMS, extract the on-chain archive, then run
   bash verify-identities.sh inside it to check the compiled validators.
3. For a local devnet, follow README.md in the archive. The runners use
   Nix. That README separates the commands verified against this release's
   source — the bounded registry journey and the identity and fixture
   checks — from the retained legacy row commands, which are not currently
   buildable or verified and must not be relied on. Release instructions
   are corrected forward; already published archives are never rewritten.
4. To use your own node and wallet, follow the
   onboarding runbook.
5. For the shared registry on preprod, follow docs/preprod.md once that
   deployment guide is published.

Singular 0.8.0 — one atomic backend interface for the ordinary CLI

0.8.0 (2026-10-02)

Features

• add the protected open-datum validator and envelope codec (382aece)
• add the protected open-datum validator and envelope codec (#316) (17df0cf)
• admit a retraction in the model driver before it is paid (03fd9e0)
• build open-datum bookings, payload updates and protected releases (adac455)
• build open-datum bookings, updates and protected releases (#317) (24ecba3)
• carry every exit's payments in the model's observations (24de43a)
• conformance: build the conformance DSL as operational programs (aa8ff93)
• conformance: read the conformance suite as Lean theorem, clause and example (08f779c)
• cover the foreign-asset update and the shared-controller and mixed settlement refusals live (2da604e)
• indexer views at one chain point (#324) (5f6550a)
• indexer-backed coherent reads through the acquired interface (a3730d0)
• judge the application's booking boundary and the terminating fold's settlement from receipts (bddf2d2)
• judge the CLI's lifecycle and the application's update and release boundary from receipts (8f48baa)
• judge the registry's refusal of duplicate and resurrected insertions from receipts (2d8af1e)
• keep a chosen boot seed unspent while reference scripts are published (#315) (c153238)
• lean: bind the insert-absent custody transaction (d92f35b)
• lean: prove and execute the insert-absent custody transaction (3f247d1)
• make the fold's required signers an observation with an obligation (edba595)
• make the model driver's operations the exits (6e4577d)
• model the protected open-datum application #310 (#312) (de34300)
• place every reject in a window and publish early rejection as CG24 (fb63107)
• port the singular registry command support onto current main (40e75ab)
• prove that no fold requires a signer (c75c52c)
• prove where every exit's deposit goes (6c6ec77)
• read the fold's required signers from the submitted transaction (52b413a)
• recover CLI state after uncertain submission and rollback (6bcc1d1)
• render the conformance evidence page from receipts (#326) (ff66ed4)
• report CG09 as an unmet consumer requirement kept by ruling (c389c90)
• run the protected open-datum lifecycle through the ordinary CLI (3f04e50)
• run the singular registry commands through the production builders (a0bb1ba)
• select the indexer backend at singular startup (#324) (85da504)
• ship the ordinary CLI's run page, DEMO1, in the on-chain archive and require it (6b163ef)
• state and compare retraction admission (80eba16)
• state every exit's obligations in the model (6cc928d)
• state which pending requests their owner can retract, and when (5a6e307)
• tell the CLI's process cases as client obligations bound to its specification's rows (3c1f001)
• the next command journals a rolled-back inclusion and an excluded transaction (#325) (97a1cf4)
• the next ordinary command reconciles an interrupted local commit (#325) (1d22a69)
• the on-chain release states the model revision the conformance evidence reads (#326) (b414dc1)
• verify-release checks a published release from its downloaded bytes (#326) (5a8a108)
• verify-release checks the released command's test-harness hooks stay inert (#326) (1bcb018)

Fixes

• a closed confirmation window is a wait failure; bound the window reads #281 (c58dd00)
• a Terminal read books with nothing under the application (a68c8bf)
• a wait failure's elapsed time is measured from the start of the call #281 (8d31827)
• admit a refusal only on its retained body and rejection, read back and attributed from their bytes (24378ec)
• admit a reject in every window at both purposes (db9354b)
• admit an ordinary command from the journal span it gained, not from its receipt's own read-backs (e23a9c5)
• admit an ordinary command's claims only on the bodies its journal kept (ce5d4cf)
• allow a folder to reject a pending request before the retraction deadline (95eb279)
• authenticate a key's leaf by the candidate that reproduces the chain's root (e950dad)
• bind a reference create read back, pay the controller short of its obligation, and meet an added asset's minimum (d568c14)
• bind the CLI's recovery, holdings and fold to exactly what each step names (6f46c26)
• book a Terminal read through the library ...

Singular documentation and on-chain release 0.7.0

0.7.0 (2026-09-20)

Features

• #157 D-BOOT carrier, and X1's harness on the derived pins (9cba521)
• #157 derive the obligations a registry-mode edge owes a fold (1b44867)
• #157 registry-mode encodings and the four derived pins (D-BOOT) (f71c0d2)
• #157 the blueprint reads a fixed tuple, and X1's local rows execute (a13b855)
• #157 the generic rows fold real edges (75dfad5)
• 173: admit the open application's approvals, and sweep the witness move (6bff250)
• 173: boot the open registry from its own blueprint, with no naming input (0122cba)
• 173: fold insertActive to a named wallet, and mirror each landed fold (7944105)
• 173: give a receipt somewhere to record an insertActive observation (d64f895)
• 173: model insertActive at transaction level and key the fold's mint guard (bc5852b)
• 173: refuse the duplicate insert instead of crashing on it (63f36c8)
• 173: ship insert-active in the release archive and run it from there (f5064f0)
• 177: observe the retirement live as conformance row CG22 (056cf9b)
• 177: reference the state validator at boot and restore the full guard (e71e893)
• 177: refuse a retirement by name instead of dying in the library (aed74e2)
• 177: run the retirement from the extracted archive (3a6aa25)
• 177: source the retirement's burn from the holder that carries it (a4e86e4)
• execute the insertActive conformance row (e88e306)
• implement registry-mode Aiken cage (#157) (240ede1)
• model the updateTerminal transaction row (019e258)
• model: complete all seven edge inversions in both directions (792b5ad)
• model: construct updateTerminal transaction row (759ceba)
• model: prove L1 and restate fold_batch_cons over the inner fold (1319bc4)
• model: prove P1, the read facts and the fold refusal (a047c9e)
• model: prove S1/S3/W1/W2/W4 and the tree-edge inversions (bbacfae)
• model: prove S2 permanence, O1 occupancy and T1 termination (7ee6ecb)
• model: prove the lifecycle statements; the model is sorry-free (567e84f)
• model: prove the naming instance statements (NM4, R-NM4, NM5) (a676001)
• model: prove the occupancy converse and the terminal-mint provenance (0c47025)
• model: prove the two workhorse lemmas the statements rest on (565f82d)
• model: prove the wire statements, byte-exactly (cf48231)
• model: prove W3, the plurality of the terminal witness (be66a50)
• model: regenerate the manifests, corpora and theorem page; just model green (3917517)
• simulator: transcribe the registry model; replay naming and its lifecycle (5bbfba1)

Fixes

• #157 authenticate the coupled transitions the audit found unbound (ca8611f)
• #157 bind the custody fold to its own registry, and fit the boot (de430ff)
• #157 carry the retired encodings through the derived executables (7b76227)
• #157 CG11, CG12 and CG19's bookings are edges (f22cc37)
• #157 duties follow the action, and the row folds discharge them (9edcb29)
• #157 every issue-70 request is a booking, and the folds balance it (6c5872f)
• #157 the custody rule binds by token, not by address (fdcf841)
• #157 the generic session funds, seeds and boots under registry mode (c9ebd0f)
• #157 the generic session's cages publish once and fund cleanly (fcfc085)
• #157 the issue-70 rows book edges too (9461344)
• #157 the wallet sweep leaves the CA seed alone (1dac2d4)
• 157: bind the E2E rows and the journey to real registry edges (dfe06f1)
• 157: drop the deleted consumer hook from the CG19 control binding (2da66f4)
• 157: find Fork #81's state UTxO by its policy token (b0ccdd8)
• 157: re-cut CG19 against the interface's routing, no hook (2006f5c)
• 157: read the fold's script identities from its reference inputs (c7c8ddd)
• 173: build the transaction, bridge the keyed witness, key the JS fold (854f56f)
• 173: read a validator's parameter count instead of writing it down (3587bcb)
• 177: carry the rebased receipt fields on CG21 and the CG22 refusal legs ([7b75a4e](https://github.com/lambdasistemi/singular/commit/...

Singular documentation and on-chain release 0.6.1

0.6.1 (2026-09-15)

Fixes

• classify a pending request by phase before resuming it (58dae70)
• classify a pending request by phase before resuming it (9ae4d3f)
• create the evidence directory before the Koios echo writes into it (fceba9c)
• create the evidence directory before the Koios echo writes into it (447b484)
• deploy window parameters; complete retirement inside its window (c27c3dd)
• deploy window parameters; complete retirement inside its window (1580d32)
• echo every register submission to Koios; gate resume on attached mode (84d9b17)
• fund public naming lifecycles from live protocol parameters (6ab1093)
• fund public naming lifecycles from live protocol parameters (345658d)
• preserve reserved lifecycle inputs during request funding (e4ae941)
• release: publish version changes and usable archive instructions (454aec3)
• release: publish version changes and usable archive instructions (1f85239)
• resume a pending claim and bound confirmation polls by validity window (4657615)
• resume a pending claim and bound confirmation polls by validity window (b1c453f)
• run the custody refusal probes before completion on devnet (01602a4)
• treat an unforecastable completion deadline as not-yet-passed (5808d77)

Documentation

• specs: repair 122 record per audit-123 FAIL (gist link, coverage residual) (6306c95)
• specs: retroactive record for PR #106 persistent deployment (b63055c)
• specs: retroactive record for PR #106 persistent deployment (25c99a1)
• specs: retroactive record for PR #109 rename script gate (76105ca)
• specs: retroactive record for PR #109 rename script gate (de8f957)
• specs: retroactive record for PR #112 representative name (7c5618a)
• specs: retroactive record for PR #112 representative name (745eaae)
• specs: retroactive record for PR #121 release notes (bb06044)
• specs: retroactive record for PR #121 release notes (9734298)
• specs: retroactive record for PR #122 lifecycle funding (7fbbb12)
• specs: retroactive record for PR #122 lifecycle funding (437611a)
• specs: speech companions for the 122 lifecycle funding record (b8586ee)

Singular is a registry of unique names on Cardano that applications can use
with their own rules. This archive includes the compiled smart contracts and
runnable examples: claim a name, change its payment destination, recover
control after losing a key, and retire it permanently so it cannot be reused.
Run the naming application on a local devnet or against your own test-network
node.

Use it

1. Download the singular-onchain-<version>.tar.gz archive and SHA256SUMS
   from this release. The checksum file also covers the documentation archive;
   download that too to check every listed file.
2. Run sha256sum --check SHA256SUMS, extract the on-chain archive, then run
   bash verify-identities.sh inside it to check the compiled validators.
3. For a local devnet, follow README.md in the archive. The runners use Nix.
4. To use your own node and wallet, follow the
   onboarding runbook.
5. For the shared registry on preprod, follow docs/preprod.md once that
   deployment guide is published.

Singular 0.6.0 — one deployed registry, and a name you can find with a hash

Singular 0.6.0 — one deployed registry, and a name you can find with a hash

Two things change for anyone using Singular on a real network.

A registry is deployed once and every run attaches to it. deployment deploy publishes the validators as reference scripts, boots one registry from your wallet and writes a manifest: network, seed, cage token, the applied script hashes, the reference-script UTxOs, the bootstrap transactions. deployment verify checks a node agrees with the manifest, claim by claim, and refuses by name when it does not. Every journey runner takes --deployment MANIFEST and attaches instead of booting and publishing; the registry's trie travels as a mirror file beside the manifest and the runner refuses if its root differs from the chain's. A rerun of a claim against a registry that already holds the spelling reports the duplicate refusal instead of inventing a new name.

A name's NFT is computable from the name. The representative asset name is blake2b_256(spelling), nothing else, under the deployment's representative policy id. That policy is now applied per registry, so it identifies one registry, and starting a retirement carries the policy's own witness so it cannot be pointed at a copied registry. To find alice on any indexer:

asset_name=$(printf %s alice | b2sum -l 256 | cut -d' ' -f1)
# ask for asset <representativePolicy><asset_name>: at the application address = active,
# at custody = retirement pending, absent = never claimed or permanently Over

docs/naming-demo.md has the full recipe, including how the asset's own mint/burn history tells Over from unclaimed.

Also in this release: the retract window is measured from the live tip; confirmations are observed from the node instead of sleeping; the rename script scans shell and Python files and its gate passes on a clean tree; every pull request runs every required check.

Use it

1. Download singular-onchain-0.6.0.tar.gz and SHA256SUMS, sha256sum --check, extract, bash verify-identities.sh.
2. Devnet: README.md in the archive.
3. Your own node: https://github.com/lambdasistemi/singular/blob/v0.6.0/docs/consumer-onboarding.md, then deployment deploy once and --deployment on every run.

Limits

Script hashes moved from 0.5.0 (the representative policy is parameterized), so a 0.5.0 registry is not a 0.6.0 registry. The attached runners still fund actors with devnet-sized amounts; the fix that sizes funding from live protocol parameters follows in the next release, together with the recorded preprod deployment in docs/preprod.md.

Changes since 0.5.0: https://github.com/lambdasistemi/singular/blob/v0.6.0/CHANGELOG.md

Singular 0.5.0 — run it against your own node

Singular 0.5.0 — run it against your own node

The first release you can run outside a devnet, and the first whose archive replays with no manual step.

• External-node mode. Every journey and row runner takes --node-socket, --network-magic and --wallet-skey and runs against your node with your wallet: preprod (magic 1) and other test networks; mainnet is refused. Before the first transaction the runner checks the wallet can pay and, if not, prints the address to fund, what is required and what is there. After each submission it waits for the output it created to appear rather than sleeping a fixed time, so a public network is slower than a devnet in proportion to its block time, not to a guess.
• A runbook for a new joiner: docs/consumer-onboarding.md — download, verify, point at a node, create and fund a wallet, run, read the output, rerun.
• The archive replays without a git checkout. It carries RELEASE-COMMIT; the runners read it, so no CANDIDATE_SHA variable is needed. From a fresh download, every runner exits 0 with no override.

Use it

1. Download singular-onchain-0.5.0.tar.gz and SHA256SUMS, sha256sum --check, extract, bash verify-identities.sh.
2. Devnet: follow README.md in the archive.
3. Your own node: https://github.com/lambdasistemi/singular/blob/v0.5.0/docs/consumer-onboarding.md

Limits

Each run publishes its own reference scripts and boots its own registry, so two runs do not share a registry yet. The persistent deployment (publish once, boot once, attach every run) is the next release.

Changes since 0.4.1: https://github.com/lambdasistemi/singular/blob/v0.5.0/CHANGELOG.md

Singular 0.4.1 — upstream MPF, lone-Fork absence proofs accepted

Singular 0.4.1 — upstream Merkle Patricia Forestry, and one more proof shape accepted

A fix release on top of 0.4.0, same lifecycle, same archive layout.

• Absence proofs whose root is a lone Fork are now accepted on chain. The vendored patch of the Merkle Patricia Forestry library is replaced by upstream v2.1.0, which fixes the excluding arm that refused them. With real keys this shape appears within a handful of registrations, so it mattered before any public-network run. The state script hash moves accordingly.
• The proof-variant rows (CS07) now execute on a devnet in CI with receipts, instead of being marked.

Use it

Same as 0.4.0: download the archive and SHA256SUMS, check, extract, bash verify-identities.sh, then follow README.md inside for the devnet journeys.

Limits

Devnet only; the archive replay still needs CANDIDATE_SHA set to the release commit. Both change in 0.5.0.

Changes since 0.4.0: https://github.com/lambdasistemi/singular/blob/v0.4.1/CHANGELOG.md