{
 "schema_version": 1,
 "generated": "2026-10-26",
 "id": "noisyxl-brier--date-forecasts-on-robinhood-chain",
 "repo": "Noisyxl/brier",
 "repo_url": "https://github.com/Noisyxl/brier",
 "repo_slug": "noisyxl-brier",
 "title": "Date a forecast ledger on Robinhood Chain",
 "page_title": "How to date a forecast ledger on Robinhood Chain with Brier",
 "summary": "Anchor the ledger head hash to a block so its existence date does not rest on the author's word.",
 "who": "A researcher or fund-adjacent analyst who needs proof that forecasts existed before an outcome, using a clock they do not control.",
 "problem": "A 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.",
 "outcome": "An anchor record with the block's time, which a third party can check against the transaction in an explorer.",
 "steps": [
  "Run `brier anchor` to 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 --check` to re-read every anchor and confirm it still matches the ledger."
 ],
 "agent_prompt": "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.",
 "agents": [
  "any"
 ],
 "difficulty": "Advanced",
 "time": "1 hour",
 "basis": "readme",
 "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.",
 "category": "Research",
 "tags": [
  "Research"
 ],
 "lang": "html",
 "requirements": [
  "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"
 ],
 "risk": "none",
 "seen_in_the_wild": false,
 "mentioned_publicly": false,
 "risks": [
  {
   "tag": "credentials",
   "notice": "Broadcasting the anchor transaction uses your own wallet and its funds, so only sign the bytes Brier prints after you have checked them."
  }
 ],
 "best": false,
 "score": 0.7,
 "evidence": [],
 "url": "https://dedupedai.com/use-cases/noisyxl-brier/date-forecasts-on-robinhood-chain/",
 "md": "https://dedupedai.com/use-cases/noisyxl-brier/date-forecasts-on-robinhood-chain/index.md",
 "disclaimer": "Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked \"Seen in the wild\", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email hello@dedupedai.com and we will look at it promptly.",
 "api": "https://dedupedai.com/api/v1/usecases/noisyxl-brier--date-forecasts-on-robinhood-chain.json",
 "api_version": "v1"
}