Seal & register
A workspace is not applied for. It is sealed, recorded and listed.
Your workspace charter is hashed in your browser, signed with a keypair that never leaves it, appended to the public hash-chained record layer, submitted to OpenTimestamps for Bitcoin anchoring and listed in the public registry.
What this produces, and what it does not
Produces: a SHA-256 digest of the text you enter, an Ed25519-signed receipt file downloaded to your device, one entry in the public record layer, an OpenTimestamps submission whose Bitcoin confirmation follows later, and a public registry listing.
Does not: deploy software, publish a package or SDK, create a smart contract, write to any blockchain other than the OpenTimestamps submission, transfer or hold any money, or create any legal entity, jurisdiction or status. “Workspace” and “charter” are names for software records. The on-chain mirror at /contracts remains specified and undeployed.
Pipeline
- Canonicalising Charter (RFC 8785)
- Sealing with Ed25519 (keys generated locally)
- Publishing to the append-only ledger
- Committing chain head to OpenTimestamps
- Registering workspace in the public registry