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