BEACN Cardano DOGE Methodology — Anti-Waste, Anti-Fraud

Read This First

We do not tell anyone how to vote. We publish facts, links, and verification checklists.
We do not accuse by default. A "flag" means missing evidence (deliverables / reporting / payment proof), not proof of wrongdoing.
Fraud/waste hunting is evidence work. If the receipts are good, items get cleared. If receipts are missing, we escalate questions — publicly.

Make it cheap and easy for average delegators to answer:

Where?

did treasury money go

Who?

received it

What?

was promised vs delivered

Proof?

where's the evidence

Think "DOGE" as a tone: relentless about receipts, skeptical of vague budgets, focused on measurable outcomes.

Each source lives in its own snapshot subfolder so a bug in one doesn't corrupt another.

Governance actions, anchors, votes, TreasuryWithdrawal recipient maps.

Registry pages crawled via GitBook sitemap. Each page checked for public links.

Treasury-funded but tracked off-chain. Catalyst will be its own dataset.

Flags are evidence/process signals, not verdicts. Each maps to a clear, fixable gap.

Flag Code	Meaning	How to Clear
`NO_DELIVERABLE_LINKS`	No obvious public links to deliverables (repo, site, video, podcast feed)	Add links on the official grant/proposal page
`NO_REPORTING_LINKS`	No closeout, proof-of-work, or final report links	Publish a reporting/closeout page and link it
`NO_EXTERNAL_LINKS`	No external links found on the page at all	Add any relevant external links to the page
`MISSING_GRANT_VALUE`	ADA amount not clearly stated	State the grant value clearly on the page
`🟡 NO_DISCUSSION`	No public discussion links in governance action metadata	Add discussion forum link to anchor references
`🔴 NO_METADATA`	Anchor metadata missing or unresolvable	Ensure anchor URL is live and content accessible
`🔴 HASH_MISMATCH`	Anchor content hash doesn't match on-chain hash	Re-publish with correct hash or explain discrepancy

Ingest — Pull raw data from Koios / GitBook / (Catalyst API TBD)
Normalize — Convert to standard JSON with consistent field names
Flag — Run evidence checks (link detection, hash verification, value parsing)
Snapshot — Write to data/snapshots/YYYY-MM-DD/ (immutable)
Derive — Generate unified index, leaderboard, waste radar from snapshots
Report — Produce human-readable HTML/CSV/MD reports with source links

Anyone can validate this work:

Language we use — and don't use:

✓ We say:

✗ We avoid: