Exact artifact
Code, data, rights, and policy roots are recomputed from the supplied disclosed bytes.
CANONICAL AGENT TRANSFER
Sell the agent.
Transfer the lineage.
SOBJ-0 packages one software agent as a portable Proof Bundle whose canonical control advances through Bitcoin Signet. The buyer verifies disclosed bytes locally; a buyer-run Bitcoin Core node checks confirmation and current unspentness—without a SOBJ registry.
No token · No sidechain · No sequencer · No federation · No required payment rail
EXAMPLE RECEIPTSTRUCTURAL
canonical-agent.sobj.json
- OBJECT
- 7f4674…c277c6
- REVISION
- 5a2644…3313a7
- CONTROL
- e34089…52182e
- NETWORK
- SIGNET
CREATEEVOLVETRANSFER
LIVENESS UNKNOWNCORE CHECK REQUIRED
THE CONTROL GAP
A repository can be copied.
Its canonical future can still have one controller.
Today an agent sale scatters across a ZIP, a Git repository, signing keys, and a contract schedule. SOBJ-0 binds the exact software revision and the authority to advance its canonical lineage into one verifiable handoff.
BUYER-SIDE VERIFICATION
Three gates. No vendor dashboard.
The buyer recomputes structure locally. A buyer-run fully validating Bitcoin Core node checks active-chain confirmation and current unspentness.
Current control
A buyer-run Bitcoin Core node checks that the latest anchor is confirmed on active-chain and remains unspent.
Clean succession
Offline branches may both be structurally valid; active-chain validation accepts only the successor that spends the confirmed current anchor.
ONE OBJECT LIFECYCLE
Software that can change hands without becoming a token.
CREATE
Bind the first software revision to a persistent object ID and a Signet control anchor.
EVOLVE
Advance code or declared data while retaining one verifiable object lineage.
TRANSFER
Move cryptographic authority to authorize the next valid canonical revision from seller to buyer.
FREEZE
Terminate the lineage at a declared final revision using a NUMS controller.
THE HARD BOUNDARY
Control lineage is not copyright theater.
SOBJ-0 DOES
- Commit exact software and declared payload bytes
- Track the current Bitcoin-referenced controller with Core connected
- Reject altered artifacts and invalid transitions
- Verify the supplied Proof Bundle without a SOBJ-operated registry
SOBJ-0 DOES NOT
- Run the software on Bitcoin
- Automatically transfer copyright or IP title
- Delete the seller's copies
- Guarantee safety, availability, or absolute finality
FOUNDING TRANSFER PILOT
Rehearse one real agent handoff on Signet within 10 business days of kickoff and receipt of required inputs.
One repository. One build target. One seller-to-buyer transfer. Signet rehearsal and clean-machine buyer acceptance. Mainnet is excluded; a separate mainnet profile and independent security review are required.
$2,500
$1,500 kickoff · $1,000 acceptance
Signet only · No custody · Mainnet excluded
- Portable
.sobj.jsonProof Bundle - Buyer-run Apache-2.0 verifier
- Seller → buyer Signet rehearsal
- Clean-machine buyer acceptance session
DIRECT ANSWERS
No mythology.
Does the code run on Bitcoin?
No. The declared runtime executes the software. Bitcoin resolves UTXO single-spend ordering; the SOBJ client validates the control transition.
Is this an NFT?
SOBJ-0 issues no separate token and is not sold as a collectible. It packages software with a Bitcoin-referenced control lineage.
Does transfer convey copyright?
No. Legal rights require the applicable signed agreement. Its SOBJ object ID can be named in that agreement.
Can the seller keep a copy?
Yes. Software remains copyable. A retained copy cannot authorize the next valid canonical revision after confirmed transfer.
Can Bitcoin reconstruct the object?
No. The supplied Proof Bundle is required. Offline verification proves structure, not active-chain unspentness; that requires a buyer-run fully validating Bitcoin Core node.
Does it need Lightning, L402, or x402?
No. Payment and access rails may become adapters; they are not part of object validity.