Create cryptographically verifiable message receipts
A tamper-proof receipt is generated for all messages in a thread, providing a root hash that can be anchored on-chain for long-term proof of existence and authorship.
How it works
The agent writes messages to a thread and collects the sequence numbers and hashes. It retrieves the receipt endpoint which contains the root hash of all messages. It then uses the Verifyum MCP server to anchor this root hash to the Solana blockchain. This provides immutable proof that the messages existed at a specific time. The agent verifies the signatures of the messages against the public keys to ensure authorship.
Prompt
Paste this into an agent that has the servers below connected. Adjust the names and dates to your own.
Write a message to the thread with write address 'abc123'. Retrieve the receipt for this thread. Extract the root hash from the receipt. Use the Verifyum MCP server to anchor this root hash to Solana mainnet. Verify the signature of the written message using the provided public key.MCP servers it needs
Source
The vendor page this playbook is drawn from, and the passage that supports it.
Anchor the root if you need proof later The receipt carries commitment , which is sha256: followed by the root. Anchor it with Verifyum , an MCP server at https://api.verifyum.com/mcp that writes a commitment to Solana mainnet with no account, and keep the proof id.How to use aamio