Launch, upgrade or declare. Sign only the record you read.
Inputs on the left. On the right, the unsigned record those inputs build, block by block. Nothing is signed until you approve it in the full review. A launched chain's own records are on Serve.
- T-5 Signer on board
- T-4 Mode set
- T-3 Manifests loaded
- T-2 Record reviewed
- T-1 Signed and sent
- T-0 Admitted
- Node
- …
- Resolvers
- Capabilities
- Signer
Unlocked in this browser only, or shared from an already-unlocked defxn.com tab.
Inputs · mode and manifests
Inputs open once a signer is on board.
What each mode publishes
Launch publishes your offer and grammar manifests as content-addressed blobs, then a signed ResolverLaunch naming them.
Upgrade supersedes the current declaration head with new manifests and restates the control authority.
Capability declares a pure mechanism (a CapabilityLaunch / CapabilityUpgrade naming a derived flx-capability-manifest/1) that resolvers compose and providers are checked against.
In every mode you review the exact unsigned record before anything is signed.
no record yet
Holding: no signer on board. The record's first block (G) is the signing key.
Built by the same body function the panel signs with. Blob CIDs are the SHA-256 of your text, which is what BLOB_PUT returns; M is stamped when you submit. The body in the review dialog is the one that is signed.
Loading…
As the node reports them (CAPABILITY_LIST). Explore shows each one's hash-verified manifest and signature-verified history.
Loading…