On-chain verification
Verify a Blosical agreement
Every split sheet and producer agreement signed on Blosical is recorded on the Polygon blockchain. Check one yourself: this page reads the chain straight from your browser, so you don't have to take our word for it.
How an agreement gets on chain
Four steps, each a transaction you can find in an agreement's history above.
- 01
Terms go out for signature
When a split sheet or producer agreement is sent for signing, Blosical opens it on the registry from the project owner's wallet. Only the parties' wallet addresses go on chain — no names, splits or terms.
createAgreementAgreementCreatedAgreementVersionCreated - 02
Each party signs
When a collaborator confirms in Blosical, their own wallet signs on chain. The transaction is the signature, and the contract records exactly which wallet sent it.
signAsSenderAgreementSigned - 03
The signed document is sealed
Once everyone has signed, the creator anchors the document's fingerprint: the keccak256 hash of its canonical JSON. A secret random value inside the document keeps the terms from being guessed back from the public fingerprint.
addDataHashAgreementExecuted - 04
Changes start a new version
If the terms change, a new version opens and everyone signs again. Each version points at the last sealed fingerprint before it, so earlier versions can’t be quietly rewritten.
createVersionAgreementVersionCreated
Every artist gets a smart wallet, and Blosical pays every transaction fee. On a block explorer, each transaction is sent by a bundler; the party is the wallet named in the event.
What a sealed agreement proves
And, just as important, what it doesn't.
It proves
- Every signer’s wallet agreed to this agreement and version, by its own transaction.
- The fingerprint was anchored after the last signature, within 30 days, and can never be changed.
- A matching document is exactly the one that was sealed. Changing one character changes the fingerprint.
- The version history is linked end to end. The contract has no admin, no upgrades and no delete.
It doesn't prove
- Who owns a wallet. The chain holds addresses only; which artist uses which wallet is in Blosical’s records.
- What the terms are. Only the fingerprint is public — the document itself is needed to see what was agreed.
- That signers saw the anchored document. Signatures cover the agreement and version; Blosical freezes the terms once signing starts, and the creator anchors them afterwards.