Check Who Published What, Without Trusting a Server
Makechain is a public ledger. It records who published each object, to which project, and in what order. A person can publish, or an agent can publish for them.
Anyone can check that record in a browser, or from a contract on another chain.
What a Receipt Proves
Say an agent publishes a new version of your project. The agent then gets a receipt. Anyone who holds the receipt can confirm three facts:
- Who: your account, through the key you authorized for the agent.
- What: the exact object, named by its hash, and the project it went into.
- When: its position in a finalized block.
The checker takes its trust settings from its own configuration, never from the receipt. 15.9 Publication receipts gives each step of the check.
What Makechain Leaves Out
- No content
- The chain records each object's hash. Teams keep the bytes in stores they run or choose.
- No user programs
- The chain runs exactly seventeen commands, listed in 8. Commands, and nothing else.
- No token
- Usage costs credits at fixed prices. There is no fee market.
- No social data
- Links, reactions, reviews, and profiles are signed messages kept outside the chain.
Start Here
The overview explains the core ideas. It follows one publication from upload to receipt.
- SpecificationThe rules every implementation must follow, in 20 chapters. The rules start at chapter 3.
- GlossaryShort definitions of the terms the specification uses.
- DocumentationHow to build, run, and test Makechain. Where a document and the specification differ, the specification wins.
Companion Documents
The exact bytes and tables behind parts of the specification.