Credentials. Broadcasting the anchor transaction uses your own wallet and its funds, so only sign the bytes Brier prints after you have checked them.
Who it is forA researcher or fund-adjacent analyst who needs proof that forecasts existed before an outcome, using a clock they do not control.
The problemA hash chain shows a file was not edited but not when it existed, so an author could still claim a forecast was sealed earlier than it was.
The outcomeAn anchor record with the block's time, which a third party can check against the transaction in an explorer.
What you need first
- A terminal with Node.js and npx, since the README's commands run through npx
- An API key in a .env file, only if you want your own models on the board
- A wallet you control, only if you want to anchor the head hash on Robinhood Chain
Steps
- Run
brier anchorto see the head, the bytes and the command to send them. - Broadcast the transaction from your own wallet, using the command the anchor step printed.
- Record the transaction by running
brier anchor 0x<tx-hash>, filling in your transaction hash. (inferred, check the README) - Run
brier anchor --checkto re-read every anchor and confirm it still matches the ledger.
Prompt for your agent
In the Noisyxl/brier repo, run `brier anchor` and report the head hash and the command it prints. After the owner broadcasts the transaction, run `brier anchor --check` and verify that every anchor still matches before reporting success.
Caveat. Brier prepares the bytes but never broadcasts them, so the anchor only exists once you send the transaction yourself from a wallet you control.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for Noisyxl/brier and "Date a forecast ledger on Robinhood Chain"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer