Skip to main content
AVOID.NET
← Router Protocol9 decisions on this page

Audit log

Every state-changing event for Router Protocol: moderation decisions on community submissions, plus corrections and updates from the news pipeline. URL-based decisions are designed to carry three independent witnesses — the original source, an Internet Archive snapshot, and a Solana memo signed by our publicly-disclosed publisher key. Archive coverage is still being backfilled, so each decision below reports its own snapshot status rather than assuming one exists.

  1. #1reviewby reviewerreviewer
    2026-10-27 10:35:31Z
    Score: 10 → 10 (no score change)
    The shutdown, burn, deadline, price collapse and funding facts are well supported by multiple outlets. The main defect is the framing that the 2025 incidents were undisclosed until the shutdown, which conflicts with the page's own cited July 2025 official incident report. The 'solver-related' label for the February incident and 'led by Coinbase Ventures' are not supported by the cited sources. The page uses future tense for a deadline that has passed.
    anchoranchored
    chain
    ●mainnet-betaslot 462,038,712
    sig
    4gJmJGRS95VM…YEJLoMLjexplorer ↗
    hash
    BEvkPCHnSKQk…hv8fuJWCsha256 → base58
    verifying row…full verify ↗
    canonical bytes (1310 B) ▸
    {"actor":"reviewer","artifact_identity":"5ee4482ff6cfc94b912d7bd4263528a7","decided_at":"2026-10-27T10:35:31.397Z","decision":"review","disputed_pct":0.1818,"findings_hash":"2pHCmugCsUhmd49FFciAB9KrUcVTzDiBAyDDk5tsfULz","investigation_id":"c4977f48-cf34-4231-9b67-bdbcf603306b","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":10,"omissions":{"material":0,"total":2},"page_content_hash":"07d8735cf09e1d0903e598d0c572acaf3b4c67162fa9db848c6bc6fceb831c7e","page_slug":"router-protocol","prev_score":10,"reason":"The shutdown, burn, deadline, price collapse and funding facts are well supported by multiple outlets. The main defect is the framing that the 2025 incidents were undisclosed until the shutdown, which conflicts with the page's own cited July 2025 official incident report. The 'solver-related' label for the February incident and 'led by Coinbase Ventures' are not supported by the cited sources. The page uses future tense for a deadline that has passed.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":1,"subject_status":"shut_down","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision 17aef875-7b69-4260-8b18-fa2694bb22eb
  2. #2review reviseby judgejudge
    2026-10-27 10:35:31Z
    Score: 10 → 0 (-12)
    Of 11 claims checked, 1 was disputed and 1 could not be verified (2 of 11, about 18%), which puts the page in the minor-issues band. The disputed claim (claim_findings[2]) is the section framing that the 2025 incidents were undisclosed until the shutdown, which conflicts with Router's own July 2025 incident report that the page itself cites; this is a critical-severity section, so the penalty sits toward the upper part of the band. The core facts (shutdown, 303M token burn, price drop, funding) were confirmed, and the smaller issues (the 'solver-related' label, 'led by Coinbase Ventures', the future-tense deadline) are correctable wording. The page also lacks a primary source for the February 2025 incident, which the review rates a high-priority coverage gap.
    anchoranchored
    chain
    ●mainnet-betaslot 462,038,717
    sig
    5Rs5kPBbnciF…c6kUGLfYexplorer ↗
    hash
    2Jots518CP2x…HXzbBeu4sha256 → base58
    verifying row…full verify ↗
    canonical bytes (1419 B) ▸
    {"actor":"judge","artifact_identity":"5ee4482ff6cfc94b912d7bd4263528a7","band_override":null,"decided_at":"2026-10-27T10:35:31.397Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.1818,"investigation_id":"c4977f48-cf34-4231-9b67-bdbcf603306b","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"router-protocol","prev_score":10,"reason":"Of 11 claims checked, 1 was disputed and 1 could not be verified (2 of 11, about 18%), which puts the page in the minor-issues band. The disputed claim (claim_findings[2]) is the section framing that the 2025 incidents were undisclosed until the shutdown, which conflicts with Router's own July 2025 incident report that the page itself cites; this is a critical-severity section, so the penalty sits toward the upper part of the band. The core facts (shutdown, 303M token burn, price drop, funding) were confirmed, and the smaller issues (the 'solver-related' label, 'led by Coinbase Ventures', the future-tense deadline) are correctable wording. The page also lacks a primary source for the February 2025 incident, which the review rates a high-priority coverage gap.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-12,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision edc04a6a-3edb-43af-865b-5da088a94327
  3. #3rescoreby systemsystem
    2026-11-01 12:37:32Z
    Score: 0 → 50 (+50)
    Rescored under Scoring v2, the published formula (avoid.net/scoring): 0 → 50. Problems weighed by who is responsible: concerns that are not fraud −6, problems around the subject, caused by others −4.1; legitimacy credit long-running +10; no longer operating, so capped at 50; 1 section(s) set aside until a failed fact-check is resolved; fact-check adjustments (−12) now shown as page reliability, not in the score.
    anchoranchored
    chain
    ●mainnet-betaslot 464,095,399
    sig
    5mmKoraqBPjH…QvedfKZxexplorer ↗
    hash
    3w3iJKbVA8x9…zhc32S2zsha256 → base58
    verifying row…full verify ↗
    canonical bytes (784 B) ▸
    {"actor":"system","decided_at":"2026-11-01T12:37:32.253Z","decision":"rescore","investigation_id":"c4977f48-cf34-4231-9b67-bdbcf603306b","new_score":50,"page_slug":"router-protocol","prev_score":0,"reason":"Rescored under Scoring v2, the published formula (avoid.net/scoring): 0 → 50. Problems weighed by who is responsible: concerns that are not fraud −6, problems around the subject, caused by others −4.1; legitimacy credit long-running +10; no longer operating, so capped at 50; 1 section(s) set aside until a failed fact-check is resolved; fact-check adjustments (−12) now shown as page reliability, not in the score.","score_delta":50,"score_model":"v2","sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision dc2faff1-fb67-4541-9182-b48ce55da39c
  4. #4rescoreby systemsystem
    2026-11-03 14:01:53Z
    Score: 50 → 40 (-10)
    Re-read and rescored after the page was re-researched (2026-11-03). Rescored under Scoring v2, the published formula (avoid.net/scoring): 50 → 40. Problems weighed by who is responsible: incidents the subject suffered −10, problems around the subject, caused by others −2.9; legitimacy credit long-running +10; no longer operating, so capped at 50; a recent unresolved incident −9.8.
    anchoranchored
    chain
    ●mainnet-betaslot 464,925,081
    sig
    5YZCDcf6MEh9…VVfZyJd2explorer ↗
    hash
    FaQVcRM2KCWq…KPWHjA6Fsha256 → base58
    verifying row…full verify ↗
    canonical bytes (754 B) ▸
    {"actor":"system","decided_at":"2026-11-03T14:01:52.986Z","decision":"rescore","investigation_id":"c4977f48-cf34-4231-9b67-bdbcf603306b","new_score":40,"page_slug":"router-protocol","prev_score":50,"reason":"Re-read and rescored after the page was re-researched (2026-11-03). Rescored under Scoring v2, the published formula (avoid.net/scoring): 50 → 40. Problems weighed by who is responsible: incidents the subject suffered −10, problems around the subject, caused by others −2.9; legitimacy credit long-running +10; no longer operating, so capped at 50; a recent unresolved incident −9.8.","score_delta":-10,"score_model":"v2","sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision 59fee9ed-ee94-48c2-8783-7198cb47f270
  5. #5reviewby reviewerreviewer
    2026-11-03 14:02:48Z
    Score: 40 → 40 (no score change)
    The core claims (shutdown, burn amount, 2021 raise, Router Chain wind-down, 2025 exploits) match The Block. The July 2025 incident report could not be fetched (403). The 60+ chains and 50% price-drop details are absent from The Block, and I did not check the other cited outlets for them. The page's status is consistent with current reporting, and it hedges appropriately on the unverified items.
    anchoranchored
    chain
    ●mainnet-betaslot 464,925,363
    sig
    3REWsDAcjyF1…SijrMr5Aexplorer ↗
    hash
    9uy1FCfjMoBp…C6FiFQ6Gsha256 → base58
    verifying row…full verify ↗
    canonical bytes (1251 B) ▸
    {"actor":"reviewer","artifact_identity":"c989eaf7a92ece274929e73c3a24ddbc","blocked_count":1,"decided_at":"2026-11-03T14:02:47.951Z","decision":"review","disputed_pct":0.3333,"findings_hash":"6L8fAYpqaUYk8XepuBbAdDztmtDmU4qju1gFdQLp7ZfJ","investigation_id":"c4977f48-cf34-4231-9b67-bdbcf603306b","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":40,"page_content_hash":"776429ca2a7c239c439d81b1b4ee3afeffca7c327f764f6fd07e0574d453e0dd","page_slug":"router-protocol","prev_score":40,"reason":"The core claims (shutdown, burn amount, 2021 raise, Router Chain wind-down, 2025 exploits) match The Block. The July 2025 incident report could not be fetched (403). The 60+ chains and 50% price-drop details are absent from The Block, and I did not check the other cited outlets for them. The page's status is consistent with current reporting, and it hedges appropriately on the unverified items.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"scored_claims":6,"sequence_num":5,"subject_status":"shut_down","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision e3af6d05-37f4-4976-b878-4a52f4ddd328
  6. #6review reviseby judgejudge
    2026-11-03 14:02:48Z
    Score: 40 → 40 (no score change)
    Of 7 claim findings, 1 was excluded because the source blocked the reviewer (claim_findings[4], Medium 403), leaving 6 countable findings. Two of those, the roughly 50% price drop (claim_findings[1]) and the 60+ chains figure (claim_findings[2]), could not be verified, which gives 33% and places the page in the significant-issues band. No claim was disputed, the core shutdown, burn amount, 2021 raise, Router Chain wind-down and 2025 exploits were confirmed against The Block (claim_findings[0], [3], [5], [6]), and the reviewer did not check the other cited outlets. Because of this and the reviewer's moderate confidence of 0.6, the penalty is set at the mild end of the band. The subject status (shut down) is already stated on the page, and no omissions were reported.
    anchoranchored
    chain
    ●mainnet-betaslot 464,925,368
    sig
    9Lyu5XKCLKNz…vAdYbwE6explorer ↗
    hash
    98ARJiA7PZsJ…KCximG22sha256 → base58
    verifying row…full verify ↗
    canonical bytes (1460 B) ▸
    {"actor":"judge","artifact_identity":"c989eaf7a92ece274929e73c3a24ddbc","band_override":null,"blocked_count":1,"decided_at":"2026-11-03T14:02:47.951Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.3333,"investigation_id":"c4977f48-cf34-4231-9b67-bdbcf603306b","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":40,"page_slug":"router-protocol","prev_score":40,"reason":"Of 7 claim findings, 1 was excluded because the source blocked the reviewer (claim_findings[4], Medium 403), leaving 6 countable findings. Two of those, the roughly 50% price drop (claim_findings[1]) and the 60+ chains figure (claim_findings[2]), could not be verified, which gives 33% and places the page in the significant-issues band. No claim was disputed, the core shutdown, burn amount, 2021 raise, Router Chain wind-down and 2025 exploits were confirmed against The Block (claim_findings[0], [3], [5], [6]), and the reviewer did not check the other cited outlets. Because of this and the reviewer's moderate confidence of 0.6, the penalty is set at the mild end of the band. The subject status (shut down) is already stated on the page, and no omissions were reported.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"scored_claims":6,"sequence_num":6,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision a1a3ee4a-f7ba-4282-bed4-540afa192373
  7. #7rescoreby systemsystem
    2026-11-04 09:51:39Z
    Score: 40 → 50 (+10)
    Re-read and rescored after the page was re-researched (2026-11-04). Rescored under Scoring v2, the published formula (avoid.net/scoring): 40 → 50. Problems weighed by who is responsible: incidents the subject suffered −6, concerns that are not fraud −6, problems around the subject, caused by others −1.1; legitimacy credit long-running +10; no longer operating, so capped at 50.
    anchoranchored
    chain
    ●mainnet-betaslot 465,258,253
    sig
    34aeHuDhvKdW…hohkx6M9explorer ↗
    hash
    Ap23fByRo6S9…GmUjcDZfsha256 → base58
    verifying row…full verify ↗
    canonical bytes (749 B) ▸
    {"actor":"system","decided_at":"2026-11-04T09:51:38.241Z","decision":"rescore","investigation_id":"c4977f48-cf34-4231-9b67-bdbcf603306b","new_score":50,"page_slug":"router-protocol","prev_score":40,"reason":"Re-read and rescored after the page was re-researched (2026-11-04). Rescored under Scoring v2, the published formula (avoid.net/scoring): 40 → 50. Problems weighed by who is responsible: incidents the subject suffered −6, concerns that are not fraud −6, problems around the subject, caused by others −1.1; legitimacy credit long-running +10; no longer operating, so capped at 50.","score_delta":10,"score_model":"v2","sequence_num":7,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision 915a5068-572d-45f0-b058-cfbb2d0b204c
  8. #8reviewby reviewerreviewer
    2026-11-04 09:52:46Z
    Score: 50 → 50 (no score change)
    Core claims (shutdown date, burn amount, reasons, funding, Router Chain history, 2025 exploits) match The Block and Crypto Briefing. One minor point: the page says the 50% price drop appears in a single outlet, but Diario Bitcoin reportedly also carries it. The Medium incident report was not fetched, and the page discloses this. The page already reflects the shutdown status.
    anchoranchored
    chain
    ●mainnet-betaslot 465,258,541
    sig
    5beATvcqfAiR…eFrANs7mexplorer ↗
    hash
    7hFTcwD2nWPP…nK53viCEsha256 → base58
    verifying row…full verify ↗
    canonical bytes (1226 B) ▸
    {"actor":"reviewer","artifact_identity":"3c29e67aef15e3c6edf50a275f7cbaee","blocked_count":1,"decided_at":"2026-11-04T09:52:46.016Z","decision":"review","disputed_pct":0,"findings_hash":"4doCKt8ejMKFvcUmma7Wwup9WnxoJdGo9RcWZia4CmhA","investigation_id":"c4977f48-cf34-4231-9b67-bdbcf603306b","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":50,"page_content_hash":"a1efd2d114b20f7ce2f003da8e9ef8800f1e520f79b2c58292f83b65f4d87882","page_slug":"router-protocol","prev_score":50,"reason":"Core claims (shutdown date, burn amount, reasons, funding, Router Chain history, 2025 exploits) match The Block and Crypto Briefing. One minor point: the page says the 50% price drop appears in a single outlet, but Diario Bitcoin reportedly also carries it. The Medium incident report was not fetched, and the page discloses this. The page already reflects the shutdown status.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"scored_claims":5,"sequence_num":8,"subject_status":"shut_down","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision 200dbd9e-fbba-47ea-b332-73302b91baab
  9. #9review approveby judgejudge
    2026-11-04 09:52:46Z
    Score: 50 → 50 (no score change)
    Of six claims checked, none were disputed. Four were confirmed against The Block and Crypto Briefing (claim_findings[0], [1], [3], [5]). One, the single-source price statement (claim_findings[2]), was only partially supported, because a second outlet reportedly also carries the figure. One, the Medium incident report (claim_findings[4]), could not be fetched and is excluded from the percentage; the page already discloses this. The page already reports the shutdown, and the review found no material omissions.
    anchoranchored
    chain
    ●mainnet-betaslot 465,258,546
    sig
    4p9LYVckZsxa…Mh4pu5eZexplorer ↗
    hash
    Cnz8zsAJLEpV…uwvhzRibsha256 → base58
    verifying row…full verify ↗
    canonical bytes (1194 B) ▸
    {"actor":"judge","artifact_identity":"3c29e67aef15e3c6edf50a275f7cbaee","band_override":null,"blocked_count":1,"decided_at":"2026-11-04T09:52:46.016Z","decision":"review_approve","delist_requested":false,"disputed_pct":0,"investigation_id":"c4977f48-cf34-4231-9b67-bdbcf603306b","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":50,"page_slug":"router-protocol","prev_score":50,"reason":"Of six claims checked, none were disputed. Four were confirmed against The Block and Crypto Briefing (claim_findings[0], [1], [3], [5]). One, the single-source price statement (claim_findings[2]), was only partially supported, because a second outlet reportedly also carries the figure. One, the Medium incident report (claim_findings[4]), could not be fetched and is excluded from the percentage; the page already discloses this. The page already reports the shutdown, and the review found no material omissions.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"scored_claims":5,"sequence_num":9,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}
    Verify offline (run on your own machine)
    python -m src.verify_decision 85641aa4-0454-49e6-b68f-3607d439d61c
How verification works. The “Row integrity” check above is computed in your browser — your machine recomputes the SHA-256 of the canonical bytes and compares against the stored hash. No avoid.net server can fake that check. The “full verify” link goes one level deeper: your browser fetches the on-chain transaction from a Solana RPC node and confirms the same hash is in the memo. If you don’t want to trust either avoid.net or the public RPC, run the CLI verifier on your own machine — python -m src.verify_decision <event_id>.