Wiki Maintenance Log

Auto-maintained by the wiki-sweep routine. Each run records what was swept, advances the category rotation, logs ecosystem signals, and tracks community reception. Do not hand-edit the state block – the routine overwrites it.

The sweep enforces RADIX Wiki's editorial policy: verifiability, neutral point of view, no original research, notability, conflict of interest, and freshness – the last of which sets the 180-day re-verification window this log exists to keep.

Current Status

Signal Watermarks

Backlog

• run 65 (developers): category link-CLEAN – 26 pages / 146 external; the only flags are the known false positives (4x npmjs.com/@radixdlt/* 403 anti-bot: rola/babylon-gateway-api-sdk/babylon-core-api-sdk/radix-dapp-toolkit; 5x /developers/* section-landing app routes). Verified install-scrypto Rust/Scrypto pins are CURRENT against the live repo (rust-toolchain.toml channel=1.92.0 + Cargo.toml 1.3.1 on main == page claim "Scrypto 1.3.1, Rust 1.81.0+ tested to 1.92.0"; the old v1.3.0 release-note about 1.82 incompatibility is SUPERSEDED – do not "correct" the page down to 1.81). Grow-authority: cross-linked the 4 new /developers/tools/* pages from the Radix Developer Resources hub (v5.2.0->5.3.0) – added internal links on Hookah + AgentWallet, new Radix Desktop Tool bullet in Community Tools. genkipool radixdlt-rust-sdk still unadopted (untouched since 2026-07-06, 1 star, no official radixdlt repo/crate) – keep WATCH, too early for a page.
• CLEANED run 64 (ecosystem): anthic – unwrapped 10 docs.anthic.io links (DNS SERVFAIL, anthic.io root also dead), added dormant-status note (platform never launched publicly; surviving record = live anthic.medium.com posts, kept). instabridge – unwrapped 19 learn.instabridge.io links (NXDOMAIN), added defunct-status note (instabridge.io domain lapsed, now 301->unrelated grocery site; eXRD->XRD wrapping concluded at mainnet migration; built by Instalabs). BANKED for next ecosystem rotation: mox-studio (moxstudio.net loads only with an expired TLS cert, ~40 dead-link occ across root/about/token/service/games/* – abandoned but domain not squatted; unwrap or Wayback-repoint next touch). Remaining 2026-06-29 dead-site pages still pending: radixcharts, beaker.fi docs, farbo, radket, singularityx, arcanelabyrinth, abandonedarena, stakebros, xrdegen, krulknul/leafnode, z3us/roadmap, radixdashboard, dead twitter/x status links (etherealdao, alphadex, fidenaro, radix-review). reizor/radix-foundation/dan web.archive.org 0s = archive.org timeout false-positives, NOT dead.
• CLEANED run 62 (from the 2026-06-29 dead-site backlog): dexian-protocol – unwrapped docs.dexian.io (x3, DNS-dead) + thesurferinvestor.com interview (x2), added dormant-status note anchored to on-ledger KaiYuan validator (dexian.io wholly gone, no successor). backeum – confirmed defunct (user-flagged); unwrapped dead backeum.com links (x5), added defunct-status note citing surviving GitHub Scrypto blueprint (v2.0.1). radstakes – unwrapped radstakes.com/blog 404, added offline-status note pointing to Radix staking dashboard. Remaining dead-site pages in that backlog item still pending.
• Ecosystem Closed/Dormant pages with dead sites/docs left as-is (unwrap or archive-repoint when next touched): docs.anthic.io, docs.radixcharts.com + radixcharts.com/project, docs.dexian.io, docs.beaker.fi, moxstudio.net (x9), farbo.me, radket docs, hard-money substack 404s, bluechicknfts.wtf, xrdegen.com, singularityx.net, arcanelabyrinth.io, abandonedarena.com, stakebros.info, backeum.com (x4), krulknul.com, learn.instabridge.io (x5), radstakes.com/blog, z3us.com/roadmap, radixdashboard.com, juicystake (502/404), radup.io (522), wearemonstas 404, dead twitter/x status links (etherealdao, alphadex, fidenaro, radix-review). Bulk medium/linkedin/defillama/projectnow 403s + linkedin 429/999 = anti-bot false positives, ignore.
• Developers category audited clean: the only real dead link was the decommissioned stokenet-console.radixdlt.com (HTTP 530), now repointed to the unified console.radixdlt.com. Recurring FALSE POSITIVES to ignore on future developers rotations: npmjs.com package pages (403 anti-bot, packages are live), radixdlt.medium.com (403 anti-bot), and the 5 brokenInternal section-index routes (/developers/getting-started, /scrypto, /transactions, /frontend, /infrastructure) which all render live as 200 landing pages.
• Ecosystem rotation 2026-06-30: fixed radix-wiki (2 internal radix.wiki 404s -> contents/history pages) + addix (2 legacy docs.radixdlt.com/docs slugs -> /docs/resources, /docs/concepts-native-token-xrd). brokenInternal /ecosystem (beaker, crumbsup) is the live ecosystem index landing page = FALSE POSITIVE, ignore. Remaining 122 brokenExternal are mostly dormant-project whole-domain fetch-failures (radixfoundation.org, backeum.com, instabridge.io, krulknul.com, abandonedarena.com, stakebros.info, bluechicknfts.wtf, xrdegen.com, arcanelabyrinth.io, singularityx.net etc.) + the already-banked docs.* subdomains + anti-bot 403s. Real-but-fixable leftovers for next ecosystem rotation: radstakes.com/blog 404, z3us.com/roadmap 404, juicystake docs 404, root-finance/proven/maya docs 404s, dead twitter/x status links (etherealdao, alphadex, fidenaro), caviarnine.com/trade 404 (hug, minnie), wikipedia Bonding_curve/MakerDAO 404s (caper, stabilis).
• Ecosystem rotation 2026-06-30 (run 9): fixed radixscan's 2 dead .shtml links (AboutUs, EmmogluStakeryArchiveNode -> live homepage; site is now a SPA). Checked but found NO clean canonical replacement for: en.wikipedia.org/wiki/MakerDAO (caper... actually stabilis) + Bonding_curve (caper) – both 404, Maker rebranded to Sky and 'Maker (cryptocurrency)'/'Sky (cryptocurrency)' titles also 404 via fetch; caviarnine.com/trade (minnie, hug) – caviarnine.com live but DEX moved, /dex also 404, app URL unknown; z3us.com/roadmap (z3us, dormant). Leave these as dead-but-banked or unwrap when those dormant pages are next touched.
• contents/tech rotation 2026-06-30 (run 10): banked-but-unfixed for next contents/tech rotation – docs.radixdlt.com/docs/core-api (3 pages: radix-core-api, rcnet, radix-mainnet-babylon; no clean canonical Core API overview on live docs – /docs/core-api-providers is a providers list, not a reference, so left as-is). Broken internals with no clean wiki target: /ecosystem/radix-dashboard (3 pages – no wiki page; repoint to dashboard.radixdlt.com or unwrap), /ideas/{validator-subsidy-sunset,mfa-security-shield,gateway-service-rfp,scrypto-modern-rust}, legacy-docs {scrypto-1/blueprints-and-components, integrate/radix-engine-toolkit}, and 2 empty-href links (unwrap or external-repoint case by case). FALSE POSITIVES to ignore next time: /contents/tech/research (live index landing, 200); anti-bot 403s (researchgate, coinbase, forbes, bitcointalk, linkedin 999, medium, theblock, cointelegraph, axieinfinity); radixscan.io status-0 (live SPA w/ browser UA); radixfoundation.org/licenses/license-v1 (dormant domain, www resolves 000). NOTE: /contents/tech/core-concepts/decentralized-science-desci carries ~25 dead DeSci external links (vitadao, genomicdao, frontierdao, molecule, curedao, etc.) – the DeSci cluster migrated to the Caper wiki; this page should likely be retired/stubbed rather than link-repaired.
• Ecosystem rotation 2026-07-01 (run 11): FIXED 14 dead-link occurrences across 3 live projects – root-finance /tecnical-guide/security ->/introduction/security (7 occ, page moved), proven-network /decentralisation ->/the-trust-model-and-cryptography (5 occ, consolidated), rrc-404 retired Scrypto v1 /main/scrypto/resources.html ->docs/docs/resources (2 occ). LEFT/BANKED (genuinely gone, no clean replacement): radixdlt.com/post/tokenizing-real-world-assets-on-radix (rrc-404) – radixdlt.com maintenance-mode pruned its /post/ articles; unwrap when rrc-404 next substantively touched. Remaining ~100 brokenExternal stay as before: dormant-project whole-domain fetch-fails (backeum, instabridge, moxstudio, anthic docs, radket docs, radixcharts docs, singularityx, nftwars, arcanelabyrinth, xrdegen, radland, abandonedarena, stakebros, dexian docs, krulknul, farbo, radixnodeio, radup 522, bluechicknfts) + anti-bot 403s (caviarnine blog/medium, redbubble) + AWS-signed Companies House S3 URLs (rdx-works, radix-foundation; repoint to canonical CH filing-history page when next touched) + wikipedia 404s (Bonding_curve, MakerDAO) + caviarnine.com/trade + z3us roadmap (all previously verified no-clean-replacement). brokenInternal /ecosystem = live index landing FALSE POSITIVE, ignore. Also banked: hyperscale-rs M2=Sharding Adaptation Telegram chatter (add to research/hyperscale-rs roadmap once M2 is formally announced).
• Ecosystem rotation 2026-07-01 (run 13): FIXED astrolescent – unwrapped 2 dead radixdlt.com/podcast/astrolescent-... anchors (confirmed 404, radixdlt.com maintenance-mode pruned its /podcast/ articles like /post/ and /blog/; no canonical replacement; astrolescent is a live/active project with live docs). Audit: 116 brokenExternal / 1 brokenInternal (the /ecosystem index = known FALSE POSITIVE). Remaining brokenExternal unchanged from run 11 – dormant-domain status-0 fetch-fails, anti-bot 403/429/999 (medium/linkedin/wikipedia/redbubble/defillama/projectnow), AWS-signed Companies House S3 URLs (rdx-works, radix-foundation), caviarnine.com/trade, z3us roadmap, dead x/twitter status links – all previously verified no-clean-replacement. FLAG FOR A HUMAN: the stalest /ecosystem pages are DeSci-cluster entities mis-filed as Radix ecosystem projects – /ecosystem/scinet, /ecosystem/desci-foundation, /ecosystem/foresight-institute, /ecosystem/soulstore (updated 2026-02/03, oldest in subtree). The DeSci vertical migrated to the Caper wiki (cf. recent commits removing the DeSci tag node + decentralized-science-desci page); these carry many dead DeSci external links and are not Radix projects – they should be retired/migrated by a human, not link-repaired. Do NOT delete unattended.
• community rotation 2026-07-01 (run 14): FIXED 20 dead-link occurrences across the 2 substantive community pages. radix-accountability-council (v1.3.2): 4 dead radixdlt.com/blog RAC articles (rac-consultation-results, establishing-the-rac; radixdlt.com pruned these while /blog/2026-strategy-* survive) -> repointed to the live RadixTalk Governance category (radixtalk.com/c/governance, where RAC elections + DAO-transition consultations now live); www.radixtalk.com fails TLS (cert = non-www only) -> stripped www; 2 dead /consultation/<id> dApp URLs -> governance category; radix-babylon-launch -> /contents/tech/releases/radix-mainnet-babylon; radix-rewards unwrapped; 5 /ideas/radix-accountability-council self-links -> /community/; legacy dApp Toolkit internal -> /developers/frontend/01-radix-dapp-toolkit. dan-hughes (v3.0.1): 2 TipTap-mangled Notion-id internal links (/hex) fixed (Radix unwrapped – no single canonical Radix page; RDX Works -> /ecosystem/rdx-works); dead radnode.io/blog Satoshi post unwrapped; removed Cointelegraph 'fallacy-of-scalability' article noted as unavailable. LEFT/BANKED: http://currentgames.digital (vandyill's own project list, ECONNREFUSED on 443 – likely http-only or transiently down, not a citation; leave). FALSE POSITIVES to ignore next community rotation: linkedin.com/in/dan-hughes (999 anti-bot), forbes.com death-of-blockchain (timeout anti-bot; the core Dan Hughes bio citation – resolved 200 on re-audit same run), /community index brokenInternal (live landing page). FUTURE DEEPEN: dan-hughes has ~5 notion.so 'Main article:' cross-refs (Cerberus, Radix Engine, Cassandra, RDX Works, Radnode) that should become internal wiki links.
• contents/history rotation 2026-07-02 (run 15): FIXED 21 dead-link occurrences across 3 pages – history-of-radix (15 occ: pruned radixdlt.com/blog olympia/babylon launch posts -> wiki release pages, docs/authorization -> docs/auth, 7 broken internal /ideas + legacy-docs links -> current pages, cuttlefish -> live docs.radixdlt.com/docs/cuttlefish), partnerships (pruned Argent /post/ announcement -> Wayback 2022-12-05 snapshot), radix-wiki-hackathon-1 (4 retired /docs/en/ slugs + transaction-manifest -> manifest). LEFT/BANKED on radix-wiki-hackathon-1 (historical hackathon record, unwrap when next substantively touched): github.com/radixnameservice/sdk 404, api.ociswap.com/ignition 500, app.orangefinance.io/arbitrum 404, app.dopex.io/clamm 404, api3.org fetch-fail, brunel-hack-25 drive.google.com slide deck 404 (possibly permission-gated). FALSE POSITIVES to ignore next history rotation: linkedin 999/429 (many), medium pillarproject 403, lsbu.ac.uk 403, coingecko learn 403, orange-finance.gitbook 403, x.com/beemdvp (x.com 404s ALL handles to curl – verified with control handle), t.me/ascarbek http fetch-fail (t.me live), /contents/history brokenInternal = live index landing (200). Staleness: oldest pages (scrypto-developer-event, token-unlock, scrypto-defi-challenge, hack-the-system; 2026-03-23) are evergreen historical event archives – no factual churn, left as-is.
• Ecosystem rotation 2026-07-02 (run 16): FIXED maya-protocol savings docs links (2 occ -> Wayback 2024-11-06 snapshot; savings page removed from live Maya docs, 0 mentions in llms.txt) + radix-foundation jerseyfinance.je directory links (3 occ -> opencorporates.com/companies/je/EXTUID_398248; jerseyfinance.je AND jerseyfinance.com entries both 404). BANKED for next ecosystem rotation: juicy-stake (docs.juicystake.org renders an empty GitBook shell, juicystake.io 502 – recheck; mark Dormant if persists), radstakes.com whole-site 404 (root + /blog; mark Dormant), wearemonstas.com 404, radixcharts.com/project 404 (root live), radixecosystem.com/projects/farbocoin 404 (farbo already dormant), fibonacci-finance radixdlt.com/blog/runs-on-radix-q-a status-0, dead x/twitter status+handle links (etherealdao, alphadex, fidenaro erik_fdn, radix-review NFTMachinist) need browser verification (x.com 404s all handles to curl). hyperscale-rs new-docs signal actioned (v4.3.0: infobox Docs row, Official Documentation section, 2 external links).
• blog rotation 2026-07-02 (run 17): FIXED 36 dead-link occurrences across 9 of 11 blog pages – retired docs slugs (transaction-manifest->manifest, gateway-api->network-gateway, authorization->auth), pruned radixdlt.com/blog/radix-babylon-launch -> /contents/tech/releases/radix-mainnet-babylon (2 pages), radix-rewards unwrapped (no Wayback snapshot), legacy-docs scrypto x8 -> core-protocols/scrypto-programming-language, radix-engine x3 -> core-protocols/radix-engine, asset-oriented -> core-concepts/asset-oriented-programming, /ideas/radix-accountability-council x3 -> /community/..., /ideas/validator-subsidy-sunset x3 -> /ecosystem/... (page exists!), /tech/hyperscale x2 -> research/hyperscale-rs, /tech/rola -> developers/frontend/03-rola-authentication; unwrapped no-target links (/ideas/{gateway-service-rfp,radix-rewards-s1-distribution,p3-services-handover}, /ecosystem/radix-ecosystem-fund, /contents/history/dapp-in-a-day-workshop-2 x2). Blog category now CLEAN of real breakage. FALSE POSITIVES to ignore next blog rotation: linkedin 999 x8 (rgh2024-debrief), twitter handles x2 (curl-404s all handles), mckinsey timeout, statista/opensea fetch-fail (http-only), escholarship/grandview/unrealengine/medium/slashdata-S3 403 anti-bot; brokenInternal /contents,/ecosystem,/leaderboard,/contents/tech,/contents/tech/core-protocols,/developers = live index routes. Staleness: blog posts are authored opinion/event pieces – evergreen, no factual refresh needed.
• contents/resources rotation 2026-07-03 (run 18): category now CLEAN – fixed 27 dead-link occurrences across 8 pages (auto-linkified http://RADIX.wiki self-links x13 -> https://radix.wiki on brand-assets + 3 legal pages; template-leftover acuwiki.com/terms x2 -> our Terms of Use; pruned Babylon/Olympia launch blog posts -> wiki release pages + dead xrd-domains grant post -> live babylon-booster-grants post on radix-booster-grants; legacy-docs scrypto x4 -> core-protocols page; auto-linkified pow.py x2 + DLTefficiency.py x2 unwrapped; /ecosystem/radix-ecosystem-fund unwrapped on radix-foundry-program). FALSE POSITIVES to ignore next resources rotation: hitbtc.com/xrd-to-usdt 403 (anti-bot, page live), /ecosystem brokenInternal (live index route). juicy-stake recheck 2026-07-03: juicystake.io still 502 but docs.juicystake.org now 200 – infra alive, do NOT mark Dormant yet; recheck next ecosystem rotation.
• Ecosystem rotation 2026-07-03 (run 19): FIXED 61 dead-link occurrences across 10 pages – dan (36 occ: danxrd.xyz NXDOMAIN -> Wayback 2026-05-14, global repoint), radix-foundation (7: radixfoundation.org + /licenses -> Wayback; expired Companies House S3 -> canonical officers page), radland (4: pruned babylon-launch post -> live Radland booster-grant post; app.radland.io -> Wayback; is live->was live), caper (3: DELETED Wikipedia Bonding_curve article -> caper.network/wiki/markets/bonding-curve; rook.fi -> Wayback), rdx-works (3: rdx.works -> Wayback; S3 -> filing-history), hug+minnie (4: caviarnine.com/trade 404 -> root), nftwars (2: NXDOMAIN -> Wayback), stabilis (1: DELETED Wikipedia MakerDAO article -> Dai (cryptocurrency)). NOTE: Wikipedia deleted both MakerDAO and Bonding curve articles (API: missing) – watch for other pages citing them. Stalest unrefreshed: soulstore (Feb 6), desci-foundation/scinet/foresight-institute (Feb 24) – consider whether DeSci-cluster ecosystem pages should stay (Caper wiki now owns DeSci).
• ideas rotation 2026-07-03 (run 20): category audited CLEAN – 1 page only (/ideas/radix-network-dao-charter), 0 broken links (charter body is a markdown code block, links not live anchors). Page is a COMMUNITY-AUTHORED draft proposal (status Discussion) – treat prose as authored content like blog posts, do NOT factually refresh; only structural/navigation maintenance appropriate. This run populated its empty infobox (v1.0.1: draft version, CC-BY-SA-4.0, Aragon provenance, RadixTalk governance link, RAC internal link). NEW PAGE: /ecosystem/oter (OTER optimistic oracle + live drand-aligned jury-randomness beacon, status Testnet) – no X/GitHub links found on site yet; add handles + flip status when mainnet ships; consider inbound link from religant (the other Oracle page) next ecosystem rotation.
• Ecosystem rotation 2026-07-03 (run 21): FIXED radixnodeio (radixnode.io NXDOMAIN verified -> Wayback snapshots x2 + archived-site note; metadata already Closed), rrc-404 (unwrapped radixdlt.com/post/tokenizing-real-world-assets + Forbes 2021 NFT-gaming, both 404 with no Wayback), soulstore staleness refresh v1.1.0 (added missing infobox from metadata + live-site check, http->https, corrected stale claim: XRD Domains integration 'in development' -> project closed). Verified-alive false positives to ignore: fred.stlouisfed.org deep link, t.me/EmmogluStakery, all web.archive.org status-0 timeouts. Next stalest ecosystem pages: desci-foundation, scinet, foresight-institute (Feb 2026) – DeSci-cluster orgs; DeSci content migrated to Caper wiki, review relevance before deepening.
• Developers rotation (run 22): FIXED the one genuine dead link in the subtree – www.x402.org/protocol (404, x402 site restructured, standalone /protocol page gone) repointed to docs.x402.org/core-concepts/http-402 (verified 200, canonical three-header wire-format + HTTP 402 flow overview) on /developers/infrastructure/ai-agents-and-x402 (v1.0.1). Post-fix developers is CLEAN. Recurring FALSE POSITIVES to keep ignoring: npmjs.com/package/@radixdlt/* x4 (403 anti-bot, packages live) and the 5 brokenInternal section-index routes (/developers/getting-started, /scrypto, /transactions, /frontend, /infrastructure – all live 200 landing pages). Whole developers subtree was rebuilt 2026-06-28 (oldest updated_at ~5d) so nothing genuinely stale to refresh.
• Ecosystem rotation 2026-07-04 (run 23): RESOLVED juicy-stake recheck-watch (open since runs 16/18) – juicystake.io 502 across runs 16/18/23, docs.juicystake.org degraded from real content (200 in run 18) to empty GitBook shell w/ 404 subpages (/how-to/staking-guide now 404). Domain resolves (not NXDOMAIN) -> marked 🟠 Dormant (not Closed), repointed 2 source links to verified Wayback snapshots (juicystake.io 20250506, staking-guide 20250217) + dormancy note (v2.1.0). Audit: 138 pages / 480 external, 80 brokenExternal / 1 brokenInternal (the /ecosystem index = live landing FALSE POSITIVE). Everything else is the fully-banked set: dormant-domain status-0 fetch-fails (moxstudio, backeum, instabridge learn, krulknul, anthic/radket/radixcharts/dexian docs, singularityx, arcanelabyrinth, xrdegen, abandonedarena, stakebros, farbo, bluechicknfts, radixdashboard, beaker.fi), 404s on already-Closed/Dormant projects (hardmoneyproject substack x5, radstakes/blog, radixecosystem farbocoin, radixcharts/project, wearemonstas, z3us roadmap, radup 522), anti-bot 403/999 (medium/linkedin/defillama/redbubble/projectnow), and dead x/twitter status+handle links (NFTMachinist, erik_fdn, EtherealDAO, cryptocoinfi – x.com 404s all handles to curl). Stalest 3 (desci-foundation, scinet, foresight-institute, all Feb 24) remain DeSci-cluster leftovers FLAGGED FOR A HUMAN (migrated to Caper wiki) – skipped.
• contents/tech rotation (run 24): FIXED 14 dead-link occurrences across 4 pages – radix-mainnet-babylon + rcnet (radixdlt.com/blog/radix-babylon-launch 404 -> /blog/babylon-mainnet-upgrade-complete; radix-olympia-launch 404 -> /blog/radix-olympia-mainnet-is-coming; learn.radixdlt.com/article/what-is-the-radix-wallet-for-babylon 404 -> radixdlt.com/articles-learn/start-here-radix-wallet-user-guide), docs.radixdlt.com/docs/core-api 404 x3 -> docs.radixdlt.com/docs/network-apis (RESOLVES run-10 bank: network-apis IS the clean canonical Core API hub), hyperscale-rs (hyperscale.rs/economics 404 -> hyperscale.rs root; en.wikipedia.org/wiki/Verkle_tree 404 no-such-article -> ethereum.org/roadmap/verkle-trees; unwrapped 4x defunct pprogrammingg.github.io tutorial, whole GH-Pages site 404). FLAG FOR A HUMAN: /contents/tech/core-concepts/decentralized-science-desci still carries ~20 dead DeSci external links (vitadao/genomicdao/frontierdao/molecule/curedao/futurefoods/opsci etc.) – DeSci cluster migrated to Caper wiki + tag node removed (commit 70be386); page should be RETIRED/STUBBED, not link-repaired (do NOT waste a rotation repairing it). BANKED for next contents/tech: stalest un-refreshed pages (dpos, honest-majority-assumption, trust-boundary @2026-03-15) – deepen next pass. FALSE POSITIVES confirmed again (ignore): anti-bot 403s (researchgate, medium/*, theblock, coinbase, forbes, axieinfinity, coinvise/mirror.xyz, aibc.world, stanford-jblp, papers.ssrn x3, cepr.org), file.notion.so 400 (expired signed whitepaper URLs on tempo-consensus), radixfoundation.org/licenses/license-v1 status-0 (dormant domain, banked), bankofengland.co.uk 404 + towardsdatascience 404 on stablecoins/sharding (low-value 3rd-party, leave).
• Ecosystem rotation (run 25): staleness refresh of the 3 oldest non-DeSci ecosystem pages (all thin VandyILL/community stubs) – radix-rolodex v1.1.0, doubt-it v2.2.0, radix-blue-balls v1.1.0: built proper infobox facts tables, verified live sites (radixrolodex.com SPA, doubtit.digital, sites.google.com/view/radix-blueballs, quack.space), rewrote/hyperlinked content, cleaned auto-linkified junk (http://Quack.Space -> quack.space, bare doubtit.digital/doubtitgame.com URLs), added ecosystem cross-links (quackspace, radix-rolodex, radix-blue-balls, what-is-radix). Link audit: 138 pages / 480 external, 82 brokenExternal / 1 brokenInternal = ENTIRELY the fully-banked set (dormant-domain fetch-fails, anti-bot 403/999, curl-404 x/twitter handles, our own Wayback snapshots status-0-timeout) + /ecosystem live-index FALSE POSITIVE; NO new real dead links. Stalest 3 (desci-foundation, scinet, foresight-institute @ Feb 24) STILL DeSci-cluster FLAGGED FOR A HUMAN – skipped.
• community rotation (run 26): category now clean of genuine dead links. FIXED 1 – vandyill: removed dead currentgames.digital project link (DNS resolves to 165.232.158.30 but :80/:443 ECONNREFUSED = server decommissioned, no Wayback snapshot; sibling links quack.space/doubtit.digital/cshwrd.com/radixrolodex.com all live 200). FALSE POSITIVES to ignore on future community rotations: /community brokenInternal x33 (valid top-level tag-landing route, not in checker known-list), and dan-hughes LinkedIn /in/dan-hughes-2a6b117 (999/anti-bot). NOTE: community category is ~40 user-authored personal profile pages (own author_ids) + 2 editorial pages (radix-accountability-council, dan-hughes, both refreshed run 14) – staleness refresh does not apply to member profiles, so no editorial rewrite this rotation.
• contents/history rotation (run 27): FIXED 4 genuine dead links across 2 pages – radix-wiki-hackathon-1 (RNS /sdk 404 org-retired -> live org page; app.dopex.io/clamm 404 -> stryke.xyz; unwrapped dead app.orangefinance.io) + brunel-hack-25 (placeholder Drive demo-video id -> "unavailable"). Frozen 2026-03 event stubs (european-blockchain-convention-2024 etc.) are thin photo-gallery records with no honest refresh available – leave as-is. Confirmed anti-bot FALSE POSITIVES to ignore next history rotation: all linkedin 999/429, medium 403, lsbu.ac.uk 403, coingecko 403, orange-finance.gitbook 403, x.com/beemdvp 404, api3.org & t.me/ascarbek status-0, api.ociswap.com/ignition 500 (sibling /tokens live), internal /contents/history section index.
• Ecosystem rotation (run 28): audited 138 pages. Fixed 2 genuine link issues – radix-blue-balls internal link /contents/tech/core-concepts/what-is-radix (no such page ever existed) repointed to /contents/tech/core-protocols/radix-engine (canonical Radix platform page, most-linked target); miow staleness refresh (oldest active non-DeSci page, v1.0.0->1.1.0) – added 4 internal cross-links (radix-engine, radix-wallet, radix-connect/ROLA, radix-economic-model) where the page previously had ZERO internal links. /ecosystem internal link (from beaker,crumbsup) is the valid category-index route (200) = FALSE POSITIVE, ignore. web.archive.org links showing status 0 are checker timeouts, archive.org is live – ignore. 84 brokenExternal are the known closed/dormant set (moxstudio, backeum, farbo, anthic docs, radixcharts docs, instabridge learn, etc.) + 403/999 anti-bot false positives – all previously banked, left as-is.
• Developers rotation (run 29): audited CLEAN again – 21 pages / 125 external, the only flags were the known false positives (4x npmjs.com/@radixdlt/* 403 anti-bot: rola/rdt/gateway-sdk/core-api-sdk, packages live; 5x brokenInternal section-index routes /developers/{getting-started,scrypto,transactions,frontend,infrastructure} all live 200 landings). Spot-verified npm 403-to-curl + /developers/getting-started 200 live. Whole subtree rebuilt 2026-06-28, ~7d old, nothing genuinely stale. No edits to developers this run.
• Ecosystem rotation run 30: cleared 2 of the dormant dead-site backlog pages via archive-repoint – blue-chick-nfts (bluechicknfts.wtf NXDOMAIN) and the-hard-money-project (Substack reset to empty; 5 articles). STILL PENDING from the 2026-06-29 dormant/closed dead-site list (unwrap/archive-repoint when next touched): docs.anthic.io, radixcharts.com/project + docs.radixcharts.com, docs.dexian.io (+ thesurferinvestor.com dexian interview), docs.beaker.fi, moxstudio.net x9, farbo.me + radixecosystem.com/projects/farbocoin(404), docs.radket.com, radup.io (0/522), www.radstakes.com/blog(404), z3us.com/roadmap(404), radixdashboard.com, backeum.com x4, krulknul.com(leafnode), learn.instabridge.io x5, singularityx.net, arcanelabyrinth.io, xrdegen.com, abandonedarena.com, stakebros.info, wearemonstas.com(404). Keep ignoring anti-bot false positives: medium.com/@* 403, fred.stlouisfed.org 403/timeout (alive), linkedin/defillama/projectnow/npmjs 403, /ecosystem brokenInternal (live app route).
• contents/tech rotation (run 31): DeSci page /contents/tech/core-concepts/decentralized-science-desci has ~15 GENUINE dead external links (curedao 404, frontierdao 404, futurefoodsdao/genomicdao NXDOMAIN, opsci/vitadao/a16z-future/cointelegraph/lifespan 404s). DeSci cluster migrated to the Caper wiki – FLAG FOR A HUMAN: decide whether to prune/redirect this page or bulk-repoint to Wayback rather than maintain a DeSci page on radix.wiki. Left as-is this run (out of scope for a bounded pass).
• contents/tech rotation (run 31): 2 internal links to /developers/legacy-docs/* (radix-engine-toolkit, scrypto-1/blueprints-and-components) on radix-mainnet-babylon + rcnet flag as broken (0 legacy-docs DB pages). Verify on the next DEVELOPERS rotation whether /developers/legacy-docs renders as a live app route (false positive) or is genuinely dead before touching.
• Ecosystem rotation run 32: DUPLICATE PAGE – /ecosystem/radix-accountability-council (v1.0.0, stale 2026-03-21) is a thin stub superseded by the canonical, refreshed /community/radix-accountability-council (v1.3.2, run 14). FLAG FOR A HUMAN: dedupe/redirect the ecosystem copy to the community page (do NOT delete unattended). Also: validator-subsidy-sunset refreshed this run (June 2026 sunset now elapsed) – recheck next ecosystem rotation only if a formal ‘jailing’/contingency-vote outcome is published.
• blog rotation (run 33): category CLEAN – 0 confirmable dead links across 11 pages / 100 external. Recurring FALSE POSITIVES to ignore on future blog rotations: 8x linkedin.com/in/* (999/429 anti-bot), grandviewresearch + unrealengine + escholarship.org + medium/@graycoding + slashdata-s3-pdf (403 anti-bot), statista.com/statistics/1101442 + mckinsey 2023-payments-report + instagram.com/paul_bakeryuk (status 0 = bot-block, alive in browser). UNRESOLVED-but-unverifiable: twitter.com/wyliepieote + twitter.com/beemdvp (404 via checker, X blocks WebFetch too) – attendee attribution links on rgh2024-debrief, left intact rather than strip a possibly-live profile. brokenInternal (/contents, /ecosystem, /leaderboard, /contents/tech, /contents/tech/core-protocols, /developers) all valid app routes. Staleness: 2 oldest (money-wealth-volcanos, pow-vs-pos) are timeless reposted-essay opinion pieces, no factual refresh warranted.
• Ecosystem staleness (run 35): ideosphere.io is now NXDOMAIN (verified) – /ecosystem/ideosphere is marked 🟠 Dormant but should be 🔴 Closed and has NO infobox block (metadata only). It is a DeSci-category Radix crowdfunding dApp – same cluster as the human-flagged desci-foundation/scinet/foresight-institute trio. Left untouched this run to stay clear of the DeSci human-review decision; a human should decide retire-vs-keep alongside the flagged trio, or a future pass can add its infobox + flip status to Closed. religantoracles.com ALSO confirmed NXDOMAIN this run (religant already 🔴 Closed, refreshed to v2.1.0).
• Ecosystem check-links FALSE POSITIVE to ignore: brokenInternal "/ecosystem" (referenced from /ecosystem/beaker, /ecosystem/crumbsup) is a valid CATEGORY route (wiki.ts parsePath type=category), not a missing page. RadUp radup.io confirmed still 522 (down ~1wk) – website dormant; on-chain validator status unverified, left page copy unchanged beyond existing.
• Developers rotation (run 38): category CLEAN again – 21 pages / 125 external. All 4 brokenExternal are the known npmjs.com/@radixdlt/* 403 anti-bot false positives (babylon-gateway-api-sdk, babylon-core-api-sdk, rola, radix-dapp-toolkit – packages live); all 5 brokenInternal (/developers/getting-started,/scrypto,/transactions,/frontend,/infrastructure) are valid section-index landing routes (render 200). No genuine dead links. GROW: added Hookah (github.com/xstelea/hookah, MIT, self-hostable Radix event-monitoring/webhook platform – hosted hookah.ing retired, now open-source) to the Community Tools section of /developers/radix-developer-resources (v5.1.0 -> 5.2.0), closing the run-29 Telegram signal.
• WATCH (developers rotation): genkipool published a Radix DLT Rust SDK (github.com/genkipool/radixdlt-rust-sdk) 2026-07-06, seeking transfer to the official Radix GitHub org / crates.io publication. Day-one, unadopted – do NOT stub yet. If it gains traction or the official team adopts it, add to /developers/radix-developer-resources Community Tools (like Hookah run 38). genkipool is an active community builder (validator + hyperscale community explainer page).
• Ecosystem rotation run 39: staleness refresh of the 3 stalest ACTIONABLE stubs (all dead 2023 projects, no infobox). reizor v2.1.0 – reizor.com REASSIGNED to an unrelated live music-ticketing business (checker sees 200 = false-alive); repointed ~9 reizor.com/* links to 2023-11-29 Wayback captures + added infobox (Music/Closed/$REI resource) + domain-reassignment Status note. project-elysium v2.1.0 – infobox (NFT/Dormant) + Status note (tapas archive still live but frozen at 1 Oct-2023 trailer). unix v2.1.0 – infobox (Social/Closed) + Status note (never launched). LESSON banked: a 200 on a dormant projects old domain is not proof of life – the domain may have been resold; verify identity, not just status. Stalest 4 overall (desci-foundation/scinet/foresight-institute/ideosphere) remain DeSci-cluster FLAGGED FOR A HUMAN. brokenExternal 89 / brokenInternal 1 = entirely the fully-banked set + /ecosystem live-index false positive; NO new genuine dead links.
• contents/tech rotation (run 40): FIXED 22 dead-link occurrences across 3 pages. decentralized-science-desci (v1.1.1): repointed future.a16z DeSci guide -> ethereum.org/desci, pulse.opsci.io -> opsci.io, vitadao.com/links -> vitadao.com; unwrapped 11 defunct DeSci-project links (FrontierDAO 404, FutureFoodsDAO/GenomicDAO NXDOMAIN, CrunchDAO ipfs whitepaper 502, CureDAO discord 404, VitaDAO youtube/newsletter, cointelegraph magazine 404, lifespan.io 404). radix-mainnet-babylon (v2.0.5) + rcnet (v1.3.5): repointed broken /developers/legacy-docs/* internals -> Radix Engine Toolkit GitHub repo + core-concepts/blueprints-and-packages. NOTE: DeSci page is off-mission (cluster migrated to Caper wiki) – FLAG FOR A HUMAN whether to keep/retire it on radix.wiki.
• New-project radar (run 40): genkipool community Rust SDK for Radix (github.com/genkipool/radixdlt-rust-sdk) – pending official-team adoption, too early for a page; watch for adoption then add to developers/ecosystem. genkipool AI<->mobile-wallet MCP (radix-community.genkipool.com/en/console/mcp) – novel, watch. Bank both.
• contents/tech FALSE POSITIVES to ignore on future rotations: the two radixdlt.com/blog posts radix-olympia-mainnet-is-coming + alexandria-scrypto-is-here (verified live 200, transient fetch-fail), blog.ethereum.org/2014 slasher (live 200), radixscan.io (live), en.wikipedia 429s, and the researchgate/medium/ssrn/bitcointalk/coinbase/forbes/theblock/mirror/coinvise/aibc 403 anti-bot walls. /contents/tech/research is a valid tag landing page (not a broken internal).
• FLAG FOR A HUMAN (sensitive, unverified): hyperscale_rs Telegram (2026-07-06) chatter referenced "Dan\u0027s passing" while calling the original Hyperscale MVP demo a dead end / "final tribute to Dan\u0027s work". This is unverified community chatter about a person and must NOT be added to any wiki page without authoritative confirmation (official Radix/Foundation statement). Do not act unattended.
• WATCH (accuracy signal): the hyperscale_rs community is self-policing claim accuracy on community materials – pushback on an 800k-TPS public-test figure and a 2^256-shards claim appearing on radix-community.genkipool.com/en/hyperscale. Our /contents/tech/research/hyperscale-rs page (v4.4.0, #2 traffic page) already uses sourced 500k/700k figures and does not claim 2^256 shards, so no correction needed – but keep any future hyperscale edits conservative and sourced.
• genkipool new-project radar (2026-07-06): now also published a Hyperscale explainer site + a Google-Wallet integration idea page (radix-community.genkipool.com) on top of the earlier Rust SDK + AI<->wallet MCP. Prolific community builder but all still unadopted/early – do NOT stub yet; if the official team adopts the SDK or the MCP gains traction, add to /developers/radix-developer-resources Community Tools.
• Ecosystem staleness (run 41): cleared radup from the backlog-#0 dead-site set – radup.io still HTTP 522 (re-verified), repointed its 2 links to Wayback (/our-fee 2025-01-14; /staking-with-us has no capture -> homepage 2025-04-01), added infobox (Validator/Dormant/1.95%) + Overview/Status note (Olympia-era body), removed stray [^6]. Next actionable stale ecosystem stubs (2026-03-28 batch): radixuid, xseed, topradixnode.
• FLAG FOR A HUMAN: the 4 stalest ecosystem pages (desci-foundation, scinet, foresight-institute, ideosphere; updated_at 2026-02/03) are orphaned DeSci-cluster content. The DeSci cluster migrated to the Caper wiki (commit 70be386 removed the empty DeSci tag node), so these general-DeSci orgs are not Radix-ecosystem projects and are candidates for removal/redirect from radix.wiki. Not auto-deleting (production, non-destructive discipline) – needs a human decision.
• contents/resources rotation (run 46): category CLEAN – 11 pages / 48 external, 0 genuine dead links. hitbtc.com/xrd-to-usdt flagged 403 is a WHOLE-DOMAIN Cloudflare anti-bot block (hitbtc.com root also 403s a browser UA; HitBTC is an operating exchange) – FALSE POSITIVE, do not strip. brokenInternal /ecosystem (on radix-booster-grants) is the known valid category route. STALENESS: refreshed radix-visuals (the clear outlier at updated_at 2026-03-15 vs all others 2026-07-02+) v1.0.0->1.1.0 minor – was a bare 79-image gallery with no infobox/intro/internal links; sampled 8 spr.so CDN images all 200 (alive), so added infobox + sourced Overview intro + 7 internal cross-links (radix-engine, radix-wallet, personas, radix-connect, smart-accounts, hyperscale-rs, brand-assets). Verified live render on radix.wiki.
• Developers rotation (run 50): FIXED the 2 genuine dead links in the subtree, both retired docs.radixdlt.com slugs on /developers/infrastructure/radixdlt-rust-sdk (404 after docs restructure): radix-connect (2 occ) -> docs/dapp-toolkit, transaction-manifest (1 occ) -> docs/manifest. v1.0.0->1.0.1. Category otherwise CLEAN: 4x npmjs.com/@radixdlt/* 403 = known anti-bot false positives; 5 brokenInternal section-index routes (/developers/getting-started,/scrypto,/transactions,/frontend,/infrastructure) = valid 200 landing pages, ignore.
• FLAG FOR A HUMAN (rotation starvation bug): the cursor advances via first-match indexOf on rotation.order, so ecosystem(index 0)->developers and developers->ecosystem oscillate forever – runs 49-53 have only hit ecosystem/developers and the cursor never reaches contents/tech, community, contents/history, blog, contents/resources, or ideas. Fix: track the cursor by index, or de-duplicate ecosystem in rotation.order (rely on weighting elsewhere), so full-coverage rotation resumes.
• Banked (partly cleared run 59 – radixstake + delphibets now have infoboxes/cross-links): the 2026-03-28 stub batch still needs infobox + status verification – topradixnode (v2.0.0, no infobox, stale "100,912,811 (2.81%)" stake; getradix/radixecosystem list ~34.4M XRD @1.99% fee, 99.76% uptime, Impahla DAO partner – verify current validator stake on-ledger before refreshing), plus dogecubex and delphibets (thin, near-sourceless).
• Developers rotation (run 54): audited CLEAN again – 22 pages / 137 external. All 4 brokenExternal = known npmjs.com/@radixdlt/* 403 anti-bot false positives; all 5 brokenInternal = known live-200 section-index routes (/developers/getting-started,/scrypto,/transactions,/frontend,/infrastructure). No genuine dead links. FIXED 1 accuracy issue on /developers/frontend/01-radix-dapp-toolkit (v1.1.1->1.1.2): annotated archived wallet-sdk external link. Verified live this run: create-radix-app (npm v1.1.0) + create-radix-dapp (v0.1.3) both exist, scaffolding cmd valid; RDT prose accurate for v2.3.0.
• contents/tech audited CLEAN (run 55): 82 pages / 333 external, 24 brokenExternal + 1 brokenInternal ALL false positives. Confirmed alive via WebFetch/curl: radixdlt.com/blog/hyperscale-update-500k-public-test-done (status 0 = transient fetch-fail, live), internal /contents/tech/research (renders live section landing). Recurring anti-bot 403/999/0 to ignore on future contents/tech rotations: researchgate.net, coinbase.com/learn, forbes.com, ssrn.com (x4), medium.com (x5), bitcointalk.org (x3), linkedin.com (999), cepr.org, theblock.co, mirror.xyz, aibc.world, twitter.com DeSci-DAO handles (Cerebrum_DAO, HairDAO_ – status 0 anti-bot). No fixes needed.
• Ecosystem run 56 false-positives to keep ignoring: radixuid -> radixscan.io/ValidatorTable 404s to raw fetch but is a live client-rendered SPA route (top search result is literally 'RadixScan - Validator table'); web.archive.org snapshot links (reizor x6, radix-foundation x2, dan) return 0 = checker timeouts, archive is alive; redbubble (wearemonstas) + unrealengine.com (infinite-labs) 403 = bot-blocks. topradixnode.metadata.website still lists dead topradixnode.com but status is already 'Closed' so acceptable. Remaining 85 brokenExternal = same banked dormant set (see 2026-06-29).
• community rotation (run 57): category is mostly auto-generated personal profile stubs + a few curated contributor articles (dan-hughes, now genki). Next community touch: dan-hughes already rich (v3.0.1); candidate deepenings if signal warrants – vandyill, xrdmosh. Ignore false positives: linkedin 999 (dan-hughes), /community brokenInternal (valid route).
• contents/resources swept (run 61): category link-CLEAN. hitbtc.com/xrd-to-usdt returns 403 to bots but page is LIVE + Google-indexed (anti-bot false positive on how-to-buy-xrd – do NOT strip). /ecosystem brokenInternal on radix-booster-grants is a valid app route (false positive, ignore). Refreshed radix-booster-grants (finished "Page to be updated soon" placeholder) and radix-foundry-program (added Current Status) to reflect Foundation maintenance mode (May 2026) – both grant programs no longer running new intakes.
• OPTIONAL (low prio): /ideas/radix-network-dao-charter renders its full ~53KB charter as a single <pre><code language=markdown> block (raw markdown source, incl. its own TOC anchors) – infobox is good, but the body reads as a monospace code dump. Consider a future bounded pass to convert the top sections (Intro, Charter, Voting, Treasury) to semantic HTML. Intentional verbatim-proposal shape though; not a bug. Page updated 2026-07-07, low traffic.
• contents/tech rotation (run 66): category link-CLEAN – 23 brokenExternal + 1 brokenInternal ALL known false positives (anti-bot 403/999 on researchgate/coinbase/forbes/ssrn/bitcointalk/medium/cepr/imf/mirror/theblock/aibc/linkedin; radixscan.io status-0 transient VERIFIED live via WebFetch = RadixScan Dashboard; /contents/tech/research is a live app-route section landing). GROW-AUTHORITY: deepened hyperscale-rs (#2 traffic, v4.4.0->4.4.1) – expanded 'Batch Sequencing on Contended State' to distinguish per-substate locking (divisible state, manifest+blueprintMetadata pre-analysis) from hot-state flagging (indivisible state like a DEX pool price; one shard batches under one amortized lock; trade-offs = higher compute/bandwidth + bounded intra-batch MEV + effective only from next ~5-min epoch), sourced to the project's Telegram design discussion; deliberately restated NO disputed TPS/block/committee figures per the accuracy-sensitive-TG-source caution. STALENESS: DPoS (oldest updated_at 2026-03-15, v1.0.0->1.0.1) – upgraded its verified-live radixscan.io citation http->https.
• Ecosystem run 70 – CLEARED 5 of 8 run-67 dead-site pages via archive-repoint (beaker/farbocoin/wearemonstas/stakebros/avaunt-staking). REMAINING confirmed-dead for next ecosystem slot (all verified dead 2026-07-12): singularityx (www.singularityx.net connect-fail; Wayback 20260418220758 for singularityx.net; 3 occ on /ecosystem/singularityx v2.0.1), abandoned-arena (abandonedarena.com NXDOMAIN; Wayback 20250323084437; 1 occ v2.0.1), mox-studio (moxstudio.net whole-domain dead ~9 distinct paths / 38 occ, v3.0.0 – needs per-path Wayback lookups, its own bounded run). projectnow.io = 403 anti-bot FALSE POSITIVE, do not touch.
• community rotation (run 68): category now link-CLEAN (45 pages / 44 external). FIXED 2 genuine dead links on /community/genki (v1.1.0->1.1.1): (1) internal ROLA link /developers/getting-started/rola-authentication (never existed) -> canonical /developers/frontend/03-rola-authentication; (2) retired docs.radixdlt.com/docs/radix-connect (confirmed 404 w/ browser UA, docs in maintenance mode) -> internal /contents/tech/core-protocols/radix-connect (SEO cross-link). Remaining flags are known FPs: linkedin.com/in/dan-hughes 999 (anti-bot), /community + /ecosystem brokenInternal (valid category routes). Community subtree is mostly auto-gen profile stubs + curated contributor articles (genki, dan-hughes) – no substantive staleness refresh needed this run.
• contents/history rotation (run 69): category link-CLEAN – 26 brokenExternal + 1 brokenInternal ALL known false positives (14x LinkedIn 999/429, medium/gitbook/coingecko/lsbu 403, x.com/beemdvp 404, t.me/ascarbek 0, and the /contents/history landing route). Deepened the 2 stalest thin stubs into sourced pages: scrypto-defi-challenge (2.0.1->2.1.0 – full prize/winners breakdown from Devpost + results blog: FlashyFi/Stoichiometric/ScrillaLending, 434 devs, 17 subs, $50k) and scrypto-developer-event (2.0.1->2.1.0 – first Scrypto dev event, Sud Hall Lisbon 9 Apr 2022, sourced to radixdlt.com blog). NEXT contents/history touch: token-unlock infobox mis-links "RDX Works" -> /contents/history (bad internal link, should be plain text or /ecosystem); next 2 stalest after this run = hack-the-system, flexathon (2026-03-23 stubs).
• Developers rotation (run 71): FIXED 1 genuine dead link on 2 pages – github.com/flightofthefox/polaris (POLARIS beacon-chain prototype) is 404, repo retired after being integrated into hyperscalers/hyperscale-rs (gone from both flightofthefox + hyperscalers accounts, NO Wayback snapshot). hyperscale-rs v4.4.1->4.4.2: unwrapped the prose POLARIS mention (kept as text – sentence already says it was integrated into hyperscale-rs) + dropped the dead External Links item. radix-developer-resources v5.3.0->5.3.1: unwrapped the POLARIS bullet + repointed "since integrated into hyperscale-rs" to github.com/hyperscalers/hyperscale-rs (live). Post-fix developers CLEAN: 4x npmjs.com/@radixdlt/* 403 (rola/gateway-sdk/rdt/core-api-sdk – anti-bot, packages live) + 5 brokenInternal section-index routes (/developers/{getting-started,scrypto,transactions,frontend,infrastructure} – live 200 landings) are the known false positives. VERIFIED-ALIVE this run (do NOT re-flag): pprogrammingg.github.io/web3_modules/hyperscale (200, was 404 in run 24/40 – GH-Pages back up), leomagal/Learn-Hyperscale-rs (live). genkipool radixdlt-rust-sdk still unadopted – keep WATCH.
• Blog rotation (run 72): FIXED 9 pages – normalized malformed footer self-link href="http://RADIX.wiki" (all-caps, http, imported-content cruft) -> https://radix.wiki across pow-vs-pos, radix-is-florence, rgh2024-debrief, ten-10x-moments, a-year-in-review-2023, money-wealth-volcanos, radix-is-what-web3-noobs, dappinaday-stage-1, building-radixs-developer-pipeline. Rest of category link-CLEAN modulo known false positives: 8x LinkedIn 999 + 2x twitter.com 404 (wyliepieote/beemdvp, unverifiable – x.com WebFetch 402s, kept per skeptic rule) on /blog/rgh2024-debrief; anti-bot 403 on grandviewresearch/escholarship/unrealengine/medium/slashdata-s3; timeout-0 on mckinsey/statista/fred.stlouisfed/rekt.news (verified rekt.news LIVE). 6 brokenInternal (/contents,/ecosystem,/developers,/leaderboard,/contents/tech,/contents/tech/core-protocols) = valid section/tag routes, false positives.
• contents/resources rotation (run 73): category CLEAN – 11 pages / 51 external, 0 genuine dead links. Both flags are known false positives: hitbtc.com/xrd-to-usdt 403 = whole-domain Cloudflare anti-bot (HitBTC operating, confirmed run 46/61); brokenInternal /ecosystem on radix-booster-grants = valid app route. VERIFIED CURRENT (no edit): how-to-buy-xrd – all 6 CEX listings live (Gate XRD/USDT confirmed top market via WebSearch; Bitfinex delisted Nov-2025 but is NOT on the page); radix-endowment-fund – structural 2024-fund facts unchanged, Foundation maintenance-mode does not alter Brevan-Howard-managed endowment. Stalest in-category are legal x3 + brand-assets boilerplate (no factual staleness – did not pad-edit). Thin run, no tweet.
• WATCH (new-project radar, run 73): igentix (demo.igentix.app) posted 6 x402/AP2 agent-payment protocol demos on Stokenet (RadicalVibing TG 2026-07-12). AI-agent payments angle. Early/unadopted – do NOT stub yet; if it ships to mainnet or gains adoption, add to /developers or /ecosystem. Also banked: Stokenet Q3 reset (clean genesis, no migration) announced by the infra operator on RadixDevelopers 2026-07-12 – dev-ops fact, not currently page-worthy.
• Ecosystem run 74 – CLEARED the last 3 confirmed-dead-site backlog pages from runs 67/70 via archive-repoint: singularityx (www.singularityx.net timeout -> Wayback 20260418220758, 3 occ, v2.0.1->2.0.2), abandoned-arena (abandonedarena.com NXDOMAIN -> Wayback 20250323084437, 1 occ, v2.0.1->2.0.2), mox-studio (moxstudio.net expired-TLS/dead, 38 occ across 9 paths -> per-path Wayback snapshots, v3.0.0->3.0.2; note initial map double-nested wrappers, repaired same run). Each got a dated dormant/offline status note in the intro; live LinkedIn on mox-studio kept. All snapshots verified 200. The 2026-06-29 ecosystem dead-site list is now fully closed. Remaining ecosystem brokenExternal are the known anti-bot 403/999 FPs + archive.org-timeout 0s FPs (single-wrap Wayback = alive) + /ecosystem live-index internal FP.
• Ecosystem rotation (run 76): category link-CLEAN modulo known FPs. FIXED 1 genuine dead link – radixscan.io/ValidatorTable (404, verified) -> radixscan.io/validators (200, verified) on /ecosystem/radixuid v3.0.0->3.0.1 (2 occ). Verified-alive FPs (do NOT strip): esports.net/news/paradox-metaverse (timeout FP, WebFetch 200, on /ecosystem/parabox); all web.archive.org 0/timeout = prior Wayback fixes (alive); projectnow.io 403 + LinkedIn 999/404 + medium/defillama/redbubble/unrealengine 403 + x.com/twitter 404 = anti-bot/unverifiable. brokenInternal /ecosystem = valid route.
• UNVERIFIABLE-THIS-ENV (run 76, do NOT strip): krulknul.com (/ecosystem/leafnode) + xrdegen.com (/ecosystem/xrdegen) – both DNS-resolve to live A records but TLS handshake resets (SSL_ERROR_SYSCALL) from this sandbox = egress-filter signature, not dead domains. check-links reports them status-0/timeout. Re-verify from a clean network before ever touching; treat as alive per skeptic rule.
• FLAG FOR REVIEW (wiki-wide accuracy, run 76): the Xi'an refresh corrected the Cerberus-vs-HotStuff framing on ONE page, but ~30 pages still cite 'Cerberus' as Radix's live/current consensus (grep CERB: babylon release, cerberus-consensus-protocol, consensus-evolution, sharding, comparisons/*, core-concepts/*). Our own hyperscale-rs page (better-sourced) states Xi'an does NOT implement Cerberus (per-shard = HotStuff-2-derived) and Babylon runs the unsharded/single-shard-group form. A careful, primary-sourced terminology pass is warranted but too big + accuracy-sensitive for one unattended run – do it deliberately, page by page, starting with radix-mainnet-babylon + cerberus-consensus-protocol. Do NOT bulk find/replace.
• OPS IDEA (run 76): hyperscale channel readers (msgs 9830/9832) explicitly want MAvRe's weekly hyperscale-rs progress summaries surfaced on @RadixWiki/X and in the wiki's News, so 'it's obvious the project is active and live'. Candidate: fold into radix-week-in-review, or add a News/recent block on the hyperscale-rs page (#2 traffic) sourced to hyperscale.rs. hyperscale.rs external site already banked for the next contents/tech/research touch.
• NEXT ecosystem staleness touch: stalest stubs are all 2026-03-28 auto-gen project pages – dogecubex, whynot, staatenlos-node, shardspace, stakingcoins, slightlyiffy, srwa, radnode. Refresh 2-4 with oldest updated_at; low traffic, so break ties toward any that appear in /ecosystem inbound paths.
• DONE – wiki-wide Cerberus-terminology pass (run 76 follow-up; resolves the run-76 FLAG-FOR-REVIEW item). Corrected the forward-looking 'Xi'an ships fully sharded Cerberus' framing on 5 pages: / home (v8.2.0->8.3.0, 2 edits – Xi'an-section + the 500k Hyperscale-test attribution), consensus-evolution (v1.3.1->1.4.0), radix-labs (v1.2.1->1.3.0), hyperscale-500k-tps (v1.0.1->1.1.0 – fixed the outright error 'hyperscale-rs = a Rust implementation of Cerberus'), radix-mainnet-babylon (infobox v2.0.5->2.0.6, 'Cerberus (unsharded – single shard group)', consistent with the Olympia page). Sourced to THREE independent primaries: our hyperscale-rs page (lead dev quotes + Apr-2026 Xi'an RFC), the Radix Foundation roadmap blog (frames Xi'an around a hybrid/Cassandra approach, explicitly not Cerberus – verified via WebFetch), and Olympia's existing 'unsharded Cerberus'.
• Cerberus pass – DELIBERATELY LEFT intact (accurate as design/historical/incidental, NOT errors): cerberus-consensus-protocol, cerberus-whitepaper, cerberus-vs-other-bft-protocols, history-of-radix, flexathon, tempo-consensus-mechanism, dan-hughes, consensus-evolution's Cerberus(2020-present) entry + stages infobox, all core-concepts/* (atomic-composability/blockchain-trilemma/bft/sharding/shard-groups/substate-model/tps/consensus-manager/network-emissions/defi/rollups – braiding is accurate Cerberus-design description), comparisons/* (radix-vs-eth/cosmos/polkadot/solana – design-level), and blog/ecosystem/developers incidental mentions. Principle applied: correct only claims that present Cerberus as the LIVE or CONFIRMED-FUTURE production consensus; leave Cerberus-the-peer-reviewed-design content untouched.
• FOLLOW-UP (low prio) from Cerberus pass: Alexandria + Stokenet release infoboxes also read 'Consensus Protocol: Cerberus' with 'Shard Groups: 1' – could take the same '(unsharded – single shard group)' precision as Babylon/Olympia for full consistency. Left this run (historical dev-env/testnet pages).
• STALENESS (deeper, surfaced during Cerberus pass, for next ecosystem touch): /ecosystem/radix-labs still frames Radix Labs as the entity 'focused on delivering Xi'an'. Post-Dan-Hughes (d. 27 Jul 2025) the homepage says development is community-led with hyperscale-rs as the leading Xi'an candidate. Verify whether Radix Labs still operates as a distinct active entity and refresh its status/ownership framing. (Cerberus wording already corrected.)
• Developers rotation (run 77): category link-CLEAN again – 4 brokenExternal = known npmjs.com/@radixdlt/* 403 anti-bot false positives (rola, babylon-gateway-api-sdk, babylon-core-api-sdk, radix-dapp-toolkit; packages live); 5 brokenInternal = valid section-index landing routes (/developers/{getting-started,scrypto,transactions,frontend,infrastructure}, all render 200). Whole subtree rebuilt 2026-06-28 – all pages share that updated_at (~15d, uniform), nothing differentially stale to refresh. GROW-AUTHORITY WATCH re-verified: genkipool/radixdlt-rust-sdk still unadopted (1 star, 0 forks, no push since 2026-07-06, no radixdlt/radixdlt-rust-sdk org repo) – keep WATCH, too early for a page. No edits this run. Thin run -> tweet skipped.
• DONE (run 78, contents/tech): (1) hyperscale-rs #2-traffic page – fixed the one genuine dead link (Wikipedia /Maximal_extractable_value 404 -> ethereum.org/en/developers/docs/mev canonical MEV doc; verified via WebFetch). Prior runs had ALREADY folded Foxy's state-contention Q&A into block 9 (Batch Sequencing on Contended State: per-substate locking + hot-state flagging, sourced to the July-2026 hyperscale_rs TG) and added hyperscale.rs to External Links (x2) – those two banked items were already resolved, only the dead MEV link remained. (2) cassandra (v1.1.3->1.2.0) – added the banked hyperscale-rs successor cross-link in Integration into Xi'an: one sourced paragraph naming hyperscale-rs as the live community-built Xi'an candidate carrying the Hyperscale/Cassandra research forward (internal link + radixecosystem Hyperscale-Alpha primary). contents/tech otherwise link-CLEAN: 23 brokenExternal all known anti-bot false positives (researchgate, coinbase, forbes, ssrn x3, bitcointalk x3, linkedin 999, medium x4, cepr, imf, theblock, coinvise/mirror, aibc, axieinfinity) + 1 brokenInternal (/contents/tech/research section-landing app route). DeSci page still carries dead links but is FLAG-FOR-A-HUMAN retire/stub, not link-repair.
• STILL BANKED (OPS, run 76): hyperscale channel readers (msgs 9830/9832) want MAvRe weekly hyperscale-rs progress summaries surfaced on @RadixWiki + wiki News. Candidate homes: radix-week-in-review, or a News block on the hyperscale-rs page. Not done this run (out of contents/tech scope / needs the News-feed source pattern).
• DONE (run 79, ecosystem rotation): staleness refresh of the 2 stalest sub-standard stubs (both 2026-03-28 auto-gen, oldest updated_at). whynot (v2.0.0->2.1.0): had NO infobox + stray <h1> – added facts infobox (🟠 Dormant, $WHY meme coin), cross-links to /ecosystem/ociswap + defiplaza + radixscan, cleaned intro; linktr.ee infra verified still live (Ociswap/DefiPlaza/RadixScan/GitBook). dogecubex (v2.0.0->2.1.0): “infobox” held only a YouTube embed – prepended a real facts infobox + Status section marking 🟠 Dormant (dogecubex.live now NXDOMAIN, verified ENOTFOUND); kept the YT block. Category otherwise link-CLEAN modulo known FPs (51 Wayback 0 = archive-repoints rate-limited, 25 t.me 0, 11 medium 403, 7 web 403 incl projectnow/unrealengine/defillama/redbubble, LinkedIn 999/404, X 404; brokenInternal /ecosystem = valid section route).
• PARTLY CLEARED (was backlog 2026-07-13 #67 stalest-stubs): whynot + dogecubex done run 79. STILL BANKED (next ecosystem staleness touch): staatenlos-node, shardspace, stakingcoins, slightlyiffy, srwa, radnode, supreme-stake, radixradio, project-now, mattianode, lucky8, crumbsnode – all 2026-03-28 auto-gen stubs. project-now flagged 4x projectnow.io 403 (anti-bot, likely alive – WebFetch to confirm when touched).
• community rotation (run 80): category link-CLEAN modulo known false positives. External flags on /community/dan-hughes: linkedin.com/in/dan-hughes-* = 999 anti-bot FP; t.me/delphibets/145020 = status-0 “fetch failed” because t.me message permalinks are unfetchable by the checker AND by WebFetch (ENOTFOUND in this sandbox) – same unverifiable-env class as LinkedIn 999, NOT dead; it is a properly-dated (12/12/2023) Dan Hughes quote citation, DO NOT strip. brokenInternal /community (29 pages) + /ecosystem (3 pages) = valid tag-index landing routes. Staleness queue = entirely auto-gen personal profile stubs (2026-03-15: /community/all, andy-murdock, artq-xrd, aure1is, bayesian…) – user content, left untouched (respect user content, no destructive ops). Curated contributor pages already fresh: dan-hughes v3.1.1 (07-11), genki v1.1.1, RAC now lives at ecosystem/radix-accountability-council v2.2.1 (07-11). No new wiki-worthy signal this run. THIN run – no tweet.
• contents/history rotation (run 81): category link-CLEAN modulo known anti-bot false positives. NON-FIXES (verified, do NOT strip): x.com/beemdvp 404 from checker+curl but WebSearch shows 'beem.xrd (@beemdvp) / X' as a live indexed profile => x.com anti-bot FP, NOT dead (beemdvp is a live Scrypto dev, mentor link on dapp-in-a-day-workshop-1/2/3); t.me/RadixHackathon (8 pg) + t.me/ascarbek status-0 = env DNS block (t.me unreachable this env), unverifiable NOT dead; LinkedIn 999/429 (14 profiles), medium.com/pillarproject 403 (x2), lsbu.ac.uk 403, orange-finance gitbook 403, coingecko 403 = standard anti-bot FPs.
• DONE (run 81, contents/history staleness): deepened the 2 stalest+thinnest stubs (both prev 2026-03-23/24, oldest updated_at). radix-team-hackathon (v2.0.1->2.1.0, 1688->4113 chars): added Format + Projects sections from the RDX Works blog (six balanced teams; POS Card, DecentraSign, Network Visualizer, Chess on the Ledger, Radix Planner, CLI winner w/ automated-payment-chains demo) + internal links to foohack/scrypto-developer-event/scrypto-defi-challenge/dapp-in-a-day. foohack (v2.0.1->2.1.0, 1802->4311 chars): added Background/What Was Built/Scrypto Significance (RedFoo + FooCrew built on-ledger chess engine w/ NFT board-state auction in 3 days; 'smooth as vegan butter'; Solidity-semester contrast) + links to scrypto-programming-language, asset-oriented-programming, radix-team-hackathon. Both audited via revisions row.
• STILL STALE (contents/history, next rotation touch): token-unlock (v3.0.1, 2026-03-23, 6506 chars – substantial, low prio) + hack-the-system (2026-03-23, 10738 chars – substantial). pillar-hackathon-1/foohack/radix-team-hackathon remaining raw-media-dump stubs: pillar-hackathon-1 (2323 chars, Pillar-org event, lower centrality) still thin – candidate next history slice. Many dapp-in-a-day-workshop-* pages carry the same beemdvp/t.me/linkedin FP cluster – do not re-flag.
• DONE (run 82, ecosystem rotation): (1) radix-labs (v1.3.0->1.4.0) – cleared the flagged deeper-staleness item (was framed as THE entity delivering Xi'an). Reconciled to primary source radixdlt.com/labs (R&D division of the Radix Foundation, Active) + added a cited Roadmap section from the official Radix Labs Roadmap blog (Xi'an Alpha early 2027 / Beta later 2027 / full launch H2 2027, full Rust reimplementation, Cerberus consensus) + External Links; kept the verified community hyperscale-rs divergence framing. (2) staatenlos-node (v2.0.0->3.0.0, oldest updated_at stub) – REMOVED a fabricated team section (false 'Matt Hamilton is CTO of Radix' claim + unsourced Hans Looman/Sander de Bruijn bios); rewrote with a verified facts infobox and correct operators (Ociswap co-founders Christoph Heuermann + Lukas). On-chain status pulled LIVE via RadixScan (validator_rdx1svp...zhrk4vyz: registered, ~94.9M XRD staked, 2.5% fee, 100% uptime, node.staatenlos.ch); cross-linked Ociswap + Radical Staking. Tweeted the Xi'an roadmap timeline (standalone, build-in-public).
• STILL BANKED (next ecosystem staleness touch): remaining 2026-03-28 auto-gen stubs after staatenlos-node done – shardspace, stakingcoins, slightlyiffy, srwa, radnode, supreme-stake, radixradio, project-now, mattianode, lucky8, crumbsnode, cobra-stakes, clarity-protocol, blockshard, bcw-technologies. NOTE: the node/staking stubs may carry the same auto-gen fabrication pattern as staatenlos-node (invented team bios / 'Matt Hamilton CTO' filler) – verify each validator on-chain via RadixScan and strip unsourced team claims when refreshing. project-now (18.5KB) is substantial; projectnow.io returns 403 (Cloudflare wall, likely alive – WebFetch to confirm before touching).
• blog rotation (run 83): category link-CLEAN modulo known anti-bot/SPA false positives (0 genuine dead links). VERIFIED NON-FIXES on /blog/rgh2024-debrief (do NOT strip): 8x linkedin.com/in/* = 999 anti-bot; twitter.com/beemdvp 404 (live per prior WebSearch, confirmed run 81); twitter.com/wyliepieote 404 + instagram.com/dorothysdeli status-0 = individual hackathon-participant socials, x.com WebFetch 402s so uncomfirmable, low-value archival, left in place; radixstats.web.app status-0 = live http SPA (serves "Radix Dashboard" title, no data) not dead, left. Essay citations (do NOT strip): unrealengine/medium/grandviewresearch 403 anti-bot; fred.stlouisfed.org M2SL + statista status-0 fetch-fail FP (major sites alive); mckinsey 2023 payments report timed out (heavy, alive); escholarship 403 anti-bot. Internal /contents,/ecosystem,/leaderboard,/developers,/contents/tech* = valid app routes, ignore. Staleness: all 12 blog pages share 2026-07-12 updated_at (bulk-touched by un-defer commit); week-in-review pages are point-in-time snapshots (do NOT refresh); no single essay worth a distorting rewrite this run.
• contents/resources rotation (run 84): category link-CLEAN modulo known FPs. NON-FIXES (verified, do NOT strip): hitbtc.com/xrd-to-usdt 403 = Cloudflare anti-bot, HitBTC live and XRD/USDT pair indexed (System Monitor active, WebSearch confirms); /ecosystem brokenInternal = valid tag-landing app route (47 visitors/30d), FP. DONE: (1) how-to-buy-xrd v1.1.0 to v1.2.0 – added Bybit + Bitpanda to CEX list (both verified vs primary source radixdlt.com/token + live listing URLs HTTP 200) and cited the token page as the canonical venue source; Kraken CHECKED and DELIBERATELY OMITTED (kraken.com/prices/radix states "not available on Kraken"). (2) brand-assets v1.0.1 to v1.1.0 – stalest+thinnest resources page had NO infobox (infobox-first bar); prepended facts infobox (RADIX.wiki brand kit: logomark/logotype/OG card; white/accessible/transparent PNG) + usage note; image blocks untouched. NEXT contents/resources staleness touch: legal/* boilerplate (skip), python-scripts/proof-of-work (3613 chars) + dlt-efficiency-metric are next stalest substantive.
• Ecosystem rotation (run 85): category link-CLEAN modulo known FPs (64 brokenExternal = 37 status-0 Wayback/dormant-domain fetch-fails + 19 anti-bot 403 + 5 x/linkedin-handle 404 FPs + staatenlos-node node.staatenlos.ch 526 transient Cloudflare origin on an already-refreshed page; /ecosystem brokenInternal = valid category route). Staleness refresh of the 3 stalest 2026-03-28 stubs (all lacked a rendered infobox block): shardspace v2.1.0 (added infobox; verified shardspace.app + launch.shardspace.app LIVE; fixed 3 Notion-export .md links -> /ecosystem/{avaunt-staking,alphadex,astrolescent} + bare YouTube URL), stakingcoins v2.1.0 (added on-chain-verified infobox via RadixScan: validator_rdx1sva6...z86 registered, ~15.47M XRD, 99.86% uptime/30d, 2% fee; REFRESHED stale infrastructure Italy/Czech Dell R440/R430 -> France/Germany 32GB/12-core per live site), slightlyiffy v2.1.0 (added infobox; unwrapped notion.so export link; dPoS internal link; slightlyiffy.com live but validator unconfirmed -> kept Dormant). NEXT stalest actionable 2026-03-28 stubs (same no-infobox pattern): supreme-stake, mattianode, cobra-stakes, lucky8 (Active validators/projects, verify on-chain); radnode + crumbsnode (Dormant); radixradio + project-now (Closed media, evergreen).
• ideas rotation (run 86): category link-CLEAN – 29 pages / 30 external, 0 broken internal. All 12 flagged brokenExternal = radixtalk.com 429 anti-bot FPs (confirmed alive: WebFetch on /t/consultation-v2-product-scope-document/2193 returned the live active thread). All 29 pages fresh (2026-07-07..07-13, from the dao-tasks seed) – none stale. Verified the 2 governance-sensitive pages accurate against fresh primary sources: dao-elect-permanent-rac (v1.0.0, 🔴 Discussion – correct, Permanent RAC not yet elected; interim Transition RAC still standing) + radix-network-dao-charter (v0.1.0 draft, 🔴 Discussion – correct). NO edits needed. STANDING: revisit ideas-card statuses next ideas rotation IF a primary source confirms a specific task completion (DUNA incorporation, treasury multisig stand-up, etc.) – do not advance statuses on general news alone.
• DONE (run 87, ecosystem staleness): refreshed the 2 stalest stubs (both 2026-03-28 auto-gen, oldest updated_at). (1) srwa (v3.0.0->3.1.0): substantially stale + broken links. Repositioned intro from Radix-only RWA lending to current blockchain-agnostic RWA *tokenization* company (verified vs live srwa.io: Portfolio Manager, tokenized shares/instruments, sandbox lending market, Katapult K24 cohort, pre-seed done; powers Ploughshare = registered NZ dairy financial-service provider, ploughshare.nz). Prepended a facts infobox to the video-only infobox block; added Recent-developments section; FIXED broken Notion .md export link (Ploughshare%20<uuid>.md -> https://ploughshare.nz/); dropped dead private notion.so team link; http://SRWA.io -> https://srwa.io. (2) radnode (v2.0.0->2.1.0): infobox-first violation (NO infobox block) – prepended facts infobox (0.75% fee, Radix-Foundation KYC, Betanet lineage). radnode.io now 404s + github.com/radnode has no public repos -> retained Dormant, surfaced in infobox. NOTE: ploughshare.nz 403s to WebFetch = Cloudflare anti-bot FP (alive per search index).
• STILL STALE (ecosystem, next staleness touch): remaining 2026-03-28 auto-gen stubs after srwa+radnode done – supreme-stake (v2.0.0, 1939 chars, verified 🟢 Active via supre.me, thin, no infobox – TOP candidate next), radixradio, project-now, mattianode, lucky8, crumbsnode, cobra-stakes, clarity-protocol, blockshard, bcw-technologies. Refresh 2-4 oldest updated_at per run.
• Developers rotation (run 88): category link-CLEAN modulo known FPs (4x npmjs.com/@radixdlt/* 403 anti-bot = rola/babylon-gateway-api-sdk/babylon-core-api-sdk/radix-dapp-toolkit; 5x /developers/* section-landing app routes). install-scrypto version pins REVERIFIED CURRENT (Scrypto v1.3.1 latest release 2026-01-20; radixdlt-scrypto main rust-toolchain channel=1.92.0 == page claim "Scrypto 1.3.1, Rust 1.81.0+ tested to 1.92.0") – no edit needed. DONE: staleness refresh of the stalest developers page /developers/infrastructure/03-oracle-integration (2026-06-28, oldest updated_at) – added Supra as a 2nd oracle provider (push+pull feeds for 100+ pairs + VRF randomness), verified vs primary-source integration announcement (PRNewswire 2023-12-07). Page had documented only RedStone. v1.1.1->1.2.0.
• STILL STALE (developers, next rotation touch): all remaining tutorial pages still 2026-06-28 batch (first-blueprint, scrypto/01-fundamentals, scrypto/02-resources-and-nfts, infrastructure/01-running-a-node, transactions/02-transaction-lifecycle, frontend/03-rola-authentication, gateway-sdk, vault-patterns, multi-component-architecture, events-metadata-royalties, testing-scrypto, radix-apis, radix-context). oracle-integration now moved to back of queue. Refresh 2-4 stalest next developers rotation.
• DONE (run 89, ecosystem staleness): 2 stalest 2026-03-28 auto-gen stubs, both infobox-first violations (no infobox). (1) supreme-stake (v2.0.0->2.1.0): prepended on-ledger facts infobox (RadixScan/Dashboard verified: validator_rdx1svug…ut5mmz8, ~66.0M XRD rank #27, 99.11% uptime/30d). CORRECTED now-STALE fee claim – page said “1.5% fee” but on-ledger fee_percentage=5 (raised from 1.5%, raw factor lags); fixed the “Low Fees” body line + linked intro to supre.me. (2) mattianode (v2.0.0->2.1.0): prepended on-ledger infobox (validator_rdx1s0qz…rzatmln, ~51.0M XRD rank #31, 1.5% fee, 99.99% uptime; on-chain name now 🍕 MattiaNode 🇮🇹♥🇺🇦). FIXED genuine dead link (private Notion export ?pvs=21 -> on-chain validator page); stripped 2 “network3” footnote artifacts; refreshed stale exchange line (Bitmax defunct / XRD not on Uniswap -> KuCoin/Gate.io/Bitget).
• STILL STALE (ecosystem, next staleness touch): after supreme-stake+mattianode done, remaining 2026-03-28 auto-gen stubs – radixradio + project-now (media/agency, evergreen, no infobox), then on-chain-verifiable validators: cobra-stakes (rank 16, ~92.4M XRD, 15% fee, 100% uptime 🟢), crumbsnode (rank 19, ~90.6M XRD, 25% fee, 100% 🟢), lucky8 (rank 81, ~7.96M XRD, 100% fee, 75.88% uptime – note poor uptime + 100% fee), clarity-protocol, blockshard, bcw-technologies. Refresh 2-4 oldest updated_at per run.
• contents/tech rotation (run 90): category link-audit – 82 pages / 345 external. brokenExternal=23 all verified FALSE POSITIVES except one genuine fix: 21x anti-bot 403 (researchgate/coinbase/forbes/ssrn x3/bitcointalk x3/medium x4/cepr/imf/theblock/mirror x2/aibc/stanford-jblp/axieinfinity) + 1x linkedin 999 + eprint.iacr.org/2019/752 522 (transient Cloudflare, IACR archive permanently live – do NOT strip). brokenInternal=1: shard-groups -> /contents/tech/research is a valid tag-LANDING route (research/* pages exist), app-route FP, left. GENUINE FIX: getradix.com hyperscale-500k link (DNS ENOTFOUND, domain retired) -> radixdlt.com/blog/hyperscale-update-500k-public-test-done, 2 occurrences on hyperscale-rs. Staleness: refreshed the 2 stalest (both v1.0.0, untouched since 2026-03-15, both infobox-first violations): honest-majority-assumption (v1.1.0, +infobox +"In Radix" Cerberus/DPoS/<1⁄3-BFT section +5 internal links) and trust-boundary (v1.1.0, +infobox +single-ledger/braided-sharding section +4 internal links).
• STILL STALE (contents/tech, next rotation touch): after honest-majority-assumption + trust-boundary done, remaining oldest core-concepts stubs from the 2026-03-16 batch – radix-vs-cosmos, radix-vs-polkadot (comparisons/), byzantine-fault-tolerance, component-royalties, finite-state-machines, liquid-stake-units. Comparisons pages worth a facts-table + freshness pass next contents/tech run.
• Developers rotation (run 92): category link-CLEAN modulo the known FPs (4x npmjs.com/@radixdlt/* 403 anti-bot = rola/babylon-gateway-api-sdk/babylon-core-api-sdk/radix-dapp-toolkit; 5x /developers/* section-landing app routes). Scrypto tutorial code REVERIFIED CURRENT for Scrypto 1.3.1 (#[blueprint], ResourceBuilder::new_fungible(OwnerRole::None), mint_initial_supply, prepare_to_globalize(OwnerRole::None).globalize(), Global<T>, Vault/Bucket/ResourceManager API all current) – no factual staleness, pages are timestamp-stale only. DONE staleness refresh of 2 stalest tutorial pages (both 2026-06-28 batch, oldest updated_at): (1) getting-started/02-first-blueprint (v1.2.1->1.2.2, patch) – fixed misleading infobox Official Docs row that self-linked to the wiki page; now points to the real official tutorial docs.radixdlt.com/docs/learning-to-build-a-gumball-machine. (2) scrypto/01-fundamentals (v1.2.1->1.3.0, minor) – page ended at Key Takeaways with NO forward nav into the tutorial series; added a Next Steps block linking scrypto/02-resources-and-nfts + scrypto/03-authorization-and-badges. Both moved to back of staleness queue.
• STILL STALE (developers, next rotation touch): getting-started/01-install-scrypto is now the oldest 2026-06-28 page BUT was reverified factually current runs 88 & 92 (Scrypto 1.3.1 pins) – refresh only if a genuine improvement exists, do not churn its timestamp. Remaining 2026-06-28 batch after first-blueprint+fundamentals moved back: scrypto/02-resources-and-nfts, 03-authorization-and-badges, 04-events-metadata-royalties, 05-testing-scrypto, 06-vault-patterns, 07-multi-component-architecture, getting-started/03-deploying, infrastructure/01-running-a-node, transactions/02-transaction-lifecycle, frontend/02-gateway-sdk, frontend/03-rola-authentication, radix-apis, radix-context, vault-patterns, multi-component-architecture. Refresh 2-4 stalest next developers rotation.
• Ecosystem rotation (run 93): REFRESHED weft-finance (v4.0.0->4.1.0), highest-notability stub in the 2026-03-28 stalest batch and an infobox-first violation (its only 'infobox' block was a bare YouTube embed). Prepended a facts infobox (V2 status, $WEFT 100M, founders, app/docs/X/GitHub/DefiLlama – verified 2026-07-16 vs weft.finance/docs.weft.finance); added 5 internal cross-links (radix-engine, scrypto, root-finance, ociswap, caviarnine – page had ZERO); added a Weft V2 section (Efficiency/Isolation modes, LSU/LSULP/LP collateral, configuration buffering); refreshed the stale 2024/DAO roadmap tail with V2-shipped status; unwrapped the dead private Notion export link on Atoumbre Kouassi; appended External Links. Category link-audit: 138 pages / 536 external, 80 brokenExt / 1 brokenInt = the fully-banked dormant-domain + anti-bot set + /ecosystem live-index FP; NO new genuine dead links. NEXT stalest 2026-03-28 actionable stubs (all single-block, no facts infobox): allnodes, clarity-protocol, 3syde, blockshard, bcw-technologies.
• community rotation (run 94): category link-CLEAN modulo known FPs (linkedin.com/in/dan-hughes-* = 999 anti-bot; /community + /ecosystem brokenInternal = valid category routes). Staleness refresh: vandyill (v5.0.1->5.1.0) was the stalest curated article + an infobox-LAST violation with empty <p></p> cruft and zero internal links – moved infobox to top + enriched it, reworked About into About+Projects with cross-links to /ecosystem/doubt-it and /ecosystem/radix-rolodex (verified both exist), kept the vandyill.github.io portfolio embed. All 5 external project links verified live 200. NEXT community touch: substantive curated set is dan-hughes (v3.1.1, rich), genki (v1.1.1), kangaderoo (v1.2.0), gilesmorris-me (v1.2.0) – all recently touched/healthy; remaining 40/45 are empty auto-gen profile shells (deletion candidates deferred 2026-07-12, needs human sign-off – do NOT deepen shells).
• DONE (run 95, contents/history staleness): refreshed token-unlock (v3.0.1->3.1.0), the #1 stalest page in the category – despite being a core tokenomics history page it had ZERO real internal links. Repointed the RDX Works infobox link -> /contents/history/history-of-radix; added a Related Topics infobox row (XRD Token / Network Emissions / Staking); added 4 contextual body internal links (XRD Token, Olympia mainnet launch, Alexandria upgrade, annual emission->Network Emissions); appended a Legacy section tying the unlock to Babylon 2023, ongoing network emission, and the (separate) Validator Subsidy Sunset. Facts unchanged (all Sept 2021 historical, radixdlt.com/post sources verified live by check-links). Script: scripts/update-history-token-unlock-95.mjs.
• STILL STALE (contents/history, next rotation touch): after token-unlock done run 95, stalest remaining are hack-the-system (v2.0.1, 2026-03-23, 10738 chars – substantial, evergreen LSBU hackathon; value-add would be internal cross-links) and pillar-hackathon-1 (v2.0.1, 2026-03-24, 2323 chars – THIN stub, mostly bare links/images; deepening BLOCKED on unverifiable 403 anti-bot sources (Medium/pillar.fi) + tangential Pillar Project content – low prio, do not invent facts). Also dapp-in-a-day-workshop-5 (2026-03-24, 6022 chars).
• contents/history FALSE POSITIVES to keep ignoring (run 95 audit, 23 pages / 168 external): brokenInternal "/contents/history" = valid CATEGORY route (same class as the known "/ecosystem" FP); brokenExternal all anti-bot/unreachable-by-checker FPs – 12x linkedin.com/in/* (999/429), medium.com/pillarproject x2 (403), coingecko.com/learn (403), orange-finance.gitbook.io (403), lsbu.ac.uk (403), t.me/ascarbek (0), x.com/beemdvp (404 to checker+curl but WebSearch-confirmed alive per run 81 – do NOT strip). 0 genuine dead links.
• STILL STALE (ecosystem, next staleness touch): after radixradio done run 96, remaining 2026-03-28 auto-gen stubs by oldest updated_at – project-now (Project $Now, Media/marketing agency, ~18.5k chars, no infobox = infobox-first violation; projectnow.io returns 403 anti-bot but is likely live, verify status before editing), then on-chain-verifiable validator stubs lucky8 / crumbsnode / cobra-stakes / blockshard / bcw-technologies / allnodes (build infobox via RadixScan validator lookup like supreme-stake/mattianode did runs 87/89).
• ENV FALSE-POSITIVE to remember (ecosystem link audits): mayaprotocol.com AND docs.mayaprotocol.com resolve ENOTFOUND (DNS) inside the sweep env, and the ~30 docs.mayaprotocol.com links on /ecosystem/maya-protocol show status 0 in check-links – but Maya Protocol is LIVE (CACAO active 2026, verified via DefiLlama/CoinGecko/LeoDex). Do NOT strip the maya-protocol links; always WebSearch/DefiLlama-verify a dormant-looking domain before touching it. Same class as the web.archive.org status-0 fetch-fails.
• blog rotation (run 97): category audit 12 pages / 107 external. ONE genuine fix – /blog/week-in-review-2026-07-12 cited getradix.com (DNS-dead ENOTFOUND, legacy domain retired); repointed 2x instances to canonical www.radixdlt.com/blog/hyperscale-update-500k-public-test-done (verified 200, v1.1.0->1.1.1 patch). ALL other blog broken links verified FALSE POSITIVES: LinkedIn 999 anti-bot; twitter.com/wyliepieote+beemdvp 404 (X automation block); unrealengine/medium/grandviewresearch/escholarship/slashdata-s3 403 anti-bot; fred.stlouisfed/mckinsey timeout; statista fetch-fail; radixstats.web.app fetch-fail but ALIVE (loads Radix Dashboard) – KEEP; internal /contents,/ecosystem,/leaderboard,/developers,/contents/tech = valid category/app routes. Blog pages all uniform 2026-07-12 updated_at; mostly evergreen Radix essay reposts + dated week-in-review recaps – deliberately NOT churn-refreshed (non-traffic category, over-investment).
• contents/resources swept (run 98): category link-CLEAN – 11 pages / 54 external, the only 2 flags are the long-known FALSE POSITIVES (hitbtc.com/xrd-to-usdt 403 = whole-domain Cloudflare anti-bot, HitBTC operating, confirmed runs 46/61/73/84; /ecosystem brokenInternal on radix-booster-grants = valid app route). RESOLVED the run-84 bank (python-scripts = next stalest substantive; legal/* boilerplate skipped as no-factual-churn). Both python-scripts pages carried a REAL breakage that check-links CANNOT see (a pip step is not a link; an iframe is not an anchor): (1) proof-of-work v1.1.1->1.2.0 – step 5 said `pip3 install hashlib datetime`, but both are Python STDLIB and the script imports nothing else; PyPI `hashlib` = 2008 Python-2.4 backport v20081119 (no py3 classifiers, fails to build), PyPI `datetime` = Zope DateTime v6.0 (unrelated) – so the step broke the tutorial. Replaced with a no-deps note + docs.python.org citations; VERIFIED empirically (page's own script runs on stock python3.9, zero installs, nonce 156056). (2) dlt-efficiency-metric v1.2.1->1.3.1 – the 'Repl' section's iframe pointed at replit.com/@art-desk0f/DLTmetric = 404/GONE; NOT anti-bot (control-verified: replit.com root 200, public repl @replit/Python 200, author profile @art-desk0f 200, only the repl 404s; no Wayback snapshot) -> removed dead embed, method+script remain. Also fixed garbled MathJax formula, 5x Notion-export 'Copy' cruft items (restored step numbering), added 14-Jul-2023 snapshot note on the results table. BOTH pages were infobox-first violations -> added facts infoboxes w/ internal cross-links. NEXT contents/resources touch: category is now infobox-complete and link-clean; stalest remaining are legal/* + brand-assets boilerplate (do NOT pad-edit). Consider whether the dlt-efficiency-metric pytrends script still runs (pytrends is unmaintained vs current Google Trends) – needs verification, do not assert unsourced.
• WATCH (hyperscale_rs, Jul 15): Permanent RAC candidacy discussion – Gilis Morris (GM) proposal + a second self-nominee (construction-biz background, planning validator + Scrypto) putting themselves forward for the Radix Accountability Council. Governance-in-motion; if a Permanent RAC actually forms, the contents/history or radix-governance page (contents/tech/core-concepts/radix-governance) may need a dated 'Governing Bodies (as of 2026)' update. Too early/informal to seed now – revisit when there's a formal RAC outcome or forum post.
• DONE (run 101, ecosystem staleness): refreshed the 3 stalest 2026-03-28 auto-gen stubs (top of pagesByStaleness), all infobox-first violations. (1) crumbsnode v2.0.0->2.1.0 – CORRECTED status Dormant->Active: on-ledger the CrumbsNode validator is rank #19 of 189, ~89.9M XRD, 25% fee, 100% uptime (RadixScan epoch 326958). Removed hallucinated multi-chain content (had claimed Ethereum/BSC/Polygon/Avalanche/Polkadot support – Crumbs is Radix-native). Reframed via WebSearch: CrumbsUp = no-code DAO-tooling platform on Radix, $CRUMB governance token (1B fixed supply), monthly $CRUMB airdrop to CrumbsNode stakers. (2) cobra-stakes v2.0.0->2.1.0 – validator alive on-ledger (rank #17, ~92.4M XRD, 15% fee, 100% uptime) but cobrastakes.com is now a Coming-soon placeholder; trimmed generic filler, added infobox + note. (3) lucky8 v2.0.0->2.1.0 – added infobox with the 100% validator-fee model (all rewards fund the jackpot; lucky8xrd.com live, validator rank #81 ~7.96M XRD, 75.15% uptime). All 3 verified live via /api/wiki.
• STILL STALE (ecosystem, next staleness touch): after lucky8/crumbsnode/cobra-stakes done run 101, remaining oldest 2026-03-28 auto-gen stubs by updated_at – blockshard, bcw-technologies, allnodes, 3syde, xidar (XIDAR-DGC on-chain rank #29 ~61M XRD verifiable), vikingland, the-meme-studio, surge, stream-wallet, stakesafe (StakeSafe Amsterdam/Rotterdam ranks #21/#23 on-chain), radlock. Refresh 2-4 with oldest updated_at; break ties toward /ecosystem inbound (it carries #3 site traffic, 44 visitors/30d).
• ENV false-positives re-confirmed run 101 (ecosystem check-links, 138 pages/544 external, 0 genuine dead links): docs.mayaprotocol.com (~23 links status-0 = sandbox DNS ENOTFOUND, Maya LIVE); defillama.com/protocol/* (caviarnine/weft 403 anti-bot); www.unrealengine.com + redbubble.com (403 anti-bot); node.staatenlos.ch 526 (transient CF origin, page already refreshed); fred.stlouisfed.org/graph 0 (checker FP, FRED live); projectnow.io 403 (anti-bot, likely live); /ecosystem brokenInternal = valid category route. Do NOT strip any of these.
• DONE (run 102, developers rotation): category link-CLEAN modulo the known FPs (4x npmjs.com/@radixdlt/* 403 anti-bot = rola/babylon-gateway-api-sdk/babylon-core-api-sdk/radix-dapp-toolkit; 5x /developers/* section-landing app routes). Fixed 1 GENUINE defect on the stalest page developers/infrastructure/01-running-a-node (v2.0.1->2.0.2): guided-install code block read "babyonnode docker install" (missing an l) = a broken copy-paste command -> "babylonnode docker install". Node facts REVERIFIED CURRENT: Ubuntu 22.04 still supported OS (babylon-nodecli README + docs/node-setup), babylonnode CLI guided cmd correct, download asset babylonnode-ubuntu-22.04 exists in latest release 2.2.4. STALENESS: install-scrypto still #1-oldest but factually current per items 88/92/96 (do not churn); scrypto/02-resources-and-nfts (#2) = conceptual, no version pins, no stale facts, left. Thin run – tweet SKIPPED.
• DONE (run 105, ecosystem staleness): added infoboxes to the 3 stalest 2026-03-28 auto-gen stubs (all infobox-first violations). (1) bcw-technologies v3.0.0->3.1.0: +infobox AND corrected a factual conflation – the page claimed BCW Technologies "is part of BCW, a global communications agency"; that is the unrelated Burson (formerly Burson Cohn & Wolfe) PR firm. bcw.group is the blockchain venture studio (Arkhia/hashport/TOKO, SOC 2, Google Cloud partner, BCW Ventures); repointed the dead-ended bcw-global.com/about source to bcw.group. Status 🟢 Active confirmed live. (2) allnodes v2.0.0->2.1.0: +infobox with live XRD staking fact (~14% APR, verified allnodes.com/xrd), refreshed network count "over 70"->"over 90 protocols", added allnodes.com/xrd source. 🟢 Active. (3) 3syde v2.0.0->2.1.0: +infobox, added dated "Status (July 2026)" note – site still shows "SOON" placeholder, never left Stokenet beta, pre-sale unannounced; 🟠 Dormant confirmed.
• STILL STALE (ecosystem, next staleness touch): after bcw-technologies/allnodes/3syde done run 105, remaining oldest 2026-03-28 auto-gen stubs by updated_at – the-meme-studio, surge, stream-wallet, stakesafe (StakeSafe Amsterdam/Rotterdam, on-chain ranks #21/#23 – build validator infobox via RadixScan like supreme-stake/mattianode runs 87/89), radlock, blockshard, xidar (XIDAR-DGC on-chain rank #29 ~61M XRD), vikingland. Refresh 2-4 oldest; break ties toward /ecosystem inbound (#3 site traffic, 44 visitors/30d).
• contents/history rotation (run 107): FIXED 1 genuine broken internal link on ecosystem-asset-fund (v1.4.1->1.4.2) – XRD link pointed at /contents/tech/core-concepts/xrd-token (no such page); repointed to canonical /contents/tech/core-protocols/xrd-token (verified live via /api/wiki). All 26 brokenExternal = the known history-rotation anti-bot FPs (LinkedIn 999/429 x18, medium/pillarproject 403 x2, lsbu.ac.uk 403, coingecko/learn 403, orange-finance.gitbook 403, x.com/beemdvp 404, t.me/ascarbek status-0). Other 2 brokenInternal (/contents/history section index, /ecosystem category route) = valid app routes, ignore. Staleness: 3 stalest (hack-the-system, pillar-hackathon-1, dapp-in-a-day-workshop-5 @ 2026-03-23/24) are frozen event-archive photo-galleries with no honest factual refresh (per runs 15/27) – left as-is. Telegram: hyperscale_rs speculative PQ-privacy/confidential-transfer chatter (flightofthefox: no concrete plan, quantum-fragility concern) – not wiki-worthy, no action.
• WATCH (ecosystem): /ecosystem/staatenlos-node node.staatenlos.ch persistently 526 this run (Cloudflare origin-down), used x3. Root staatenlos.ch is 200 (live) and the live official node guide staatenlos.ch/staatenlos/radix-staatenlos-node/ is already linked on the page, so NOT touched (526 plausibly transient origin outage). Recheck next ecosystem rotation; if still 526, repoint the 3 node.staatenlos.ch links to the guide.
• Blog rotation (run 109): category link-CLEAN modulo known FPs – 20 brokenExternal all anti-bot/timeout false positives (8x LinkedIn 999, twitter/beemdvp+wyliepieote 404, instagram/fred/mckinsey/statista status-0 timeouts, unrealengine/medium-graycoding/slashdata-s3/grandview/escholarship 403), 6 brokenInternal all valid app-route landings. FIXED 1 recurring FP source: /blog/rgh2024-debrief carried a lone http:// radixstats.web.app anchor (301s to https, loads 200 – Firebase Hosting; checker fails the plain-http fetch and flags status-0 every rotation) – upgraded to https:// to match its 2 sibling https radixstats links (v2.2.3->2.2.4 patch). Staleness: stalest pages are Week-in-Review recaps + evergreen opinion essays (POW-vs-POS, Radix-Is-Florence, RGH2024-Debrief) – authored/evergreen, no factual refresh. No tweet (thin run).
• DONE (run 111, ecosystem staleness): prepended facts infoboxes to the 3 stalest 2026-03-28 auto-gen stubs (all infobox-first violations). (1) stakesafe v2.0.0->2.1.0 – on-ledger validator infobox: StakeSafe runs TWO mainnet validators, Amsterdam (rank #21, ~84.4M XRD) + Rotterdam (rank #23, ~80.5M XRD), ~165M XRD combined, both 100% uptime, fee 15% (verified RadixScan epoch 327438). Softened stale source line. (2) the-meme-studio v2.0.0->2.1.0 – Web3 marketing-agency infobox (site live at thememestudio.com, content dated 2023; NOT Radix-specific, kept neutral). (3) stream-wallet v2.0.0->2.1.0 – dormant-wallet infobox: verified radix.stream last release v0.0.3 Jan 2022, audited by Red4Sec, built by Ideomaker; softened the now-false "most used wallet" claim (official Radix Wallet post-dates it).
• STILL STALE (ecosystem, next staleness touch): after the-meme-studio/stakesafe/stream-wallet done run 111, remaining oldest 2026-03-28 auto-gen stubs by updated_at – surge (surge.trade perps DEX, ~8985 chars, substantial but no infobox – high value, add one), radlock (radlock.io infra), radixtalk, radixplanet (validator rank #26 ~66.8M XRD – add on-ledger infobox), radix-review, radix-list, ploughshare. Refresh 2-4 oldest; break ties toward /ecosystem inbound (still #3 site traffic).
• BLOCKER (run 111): X API 402 credits-depleted ACCOUNT-WIDE today (both xread --mine and xpost --account radixwiki 402) – same exhaustion that blocked the Week-in-Review announce + RadixWiki afternoon tweet per daily log 2026-07-19. No wiki tweet possible until credits refill; thin-run this time so no loss.
• RESOLVED (run 113, ecosystem): /ecosystem/staatenlos-node – node.staatenlos.ch was persistently 526 (Cloudflare origin-down) since run 106; WebFetch confirmed staatenlos.ch/staatenlos/radix/ + root staatenlos.ch are LIVE. Repointed all 3 dead refs (infobox Website + Overview registration link -> live node guide radix-staatenlos-node/; External “official page” -> staatenlos.ch homepage). v3.0.0->3.0.1.
• STILL STALE (ecosystem, next staleness touch): after surge done run 113, remaining oldest 2026-03-28 auto-gen stubs by updated_at (top of pagesByStaleness) – radlock, radixtalk, radixplanet, radix-review, radix-list, ploughshare, ociswap (ociswap = flagship DEX, HIGH value + traffic, prioritise), nerds-republic, ice. Each is likely an infobox-first violation / thin stub; refresh 2-4 oldest per run.
• WATCH (ecosystem check-links, run 113): 4x X/Twitter 404 left UNTOUCHED – x.com/NFTMachinist (radix-review), twitter.com/erik_fdn (fidenaro), twitter.com/cryptocoinfi/status/1678146989303771137 (alphadex), twitter.com/EtherealDAO/status/1665509659824758784 (etherealdao). WebFetch on x.com/twitter.com 402s (X paywall) so cannot confirm genuine death vs bot-block; per skeptical-of-X rule, do NOT strip. The ~75 status-0 web.archive.org links are intentional archived citations for wound-down projects (moxstudio/farbo/radket/reizor/nftwars) – leave. 21x 403 = medium/defillama/unrealengine/projectnow/redbubble anti-bot, alive. fred.stlouisfed.org (caper page) = 403 anti-bot, FRED alive.
• DONE (run 114, developers): category link-CLEAN modulo known FPs (4x npmjs.com/@radixdlt/* 403 anti-bot + 5x /developers/* section-landing app routes). Verified version pins CURRENT against live radixdlt-scrypto@main: Scrypto still 1.3.1 (Cuttlefish, latest release 2026-01-20), rust-toolchain channel=1.92.0, install-scripts pin RUST_VERSION=1.92.0 / RADIX_CLI_VERSION=1.3.0 / LLVM 21 – install-scrypto page claim "Scrypto 1.3.1, Rust 1.81.0+ tested to 1.92.0" holds. Staleness refresh: deepened the stalest page developers/getting-started/01-install-scrypto (v1.1.1->1.2.0) with a new "Quick Install (Automated)" section pointing at the official scrypto-install-scripts (macOS/Debian/Windows one-command path) – genuine content, not a cosmetic touch.
• WATCH (developers): @radixdlt/radix-dapp-toolkit npm latest is now 2.3.0 (was 2.2.x); @radixdlt/babylon-gateway-api-sdk at 1.10.1. The frontend/01-radix-dapp-toolkit + frontend/02-gateway-sdk tutorial pages use UNPINNED npm install commands so they stay correct – no edit needed, but note the drift for any future version-specific claims.
• run 116 (contents/tech): 22 category broken-external are all the standard bot-block false positives (Coinbase/Forbes/SSRN/Medium/ResearchGate/LinkedIn-999/bitcointalk/IMF/CEPR/mirror.xyz 403/999). Left as-is. Remaining stalest core-concepts still on 2026-03-16 (byzantine-fault-tolerance, component-royalties, finite-state-machines, liquid-stake-units, native-assets-vs-token-approvals, network-emissions, staking, substate-model, transaction-manifests, vamos-database) – refresh 2-4 next time contents/tech rotates.
• DONE (run 117, ecosystem staleness): Ociswap (flagship Radix DEX, stalest 2026-03-28 stub, v3.0.0->3.1.0). Prepended a leading facts infobox – fixes the infobox-first violation (the prior "infobox" block held ONLY a YouTube + Rolodex embed, no facts table). OCI token facts verified on-ledger via RadixScan: fixed supply 100,000,000, symbol OCI, minter/burner/freezer/recaller all deny_all + rules_locked (mainnet epoch 327774, 20 Jul 2026). Appended an "Ociswap V2" section: Pool V2 (constant-product) + Precision Pool V2 (concentrated liquidity, per docs.ociswap.com) + Hooks modularity – the page predated V2 and described only the original CPMM MVP. Verified edit landed via DB (block0=infobox w/ table, V2 section present).
• STILL STALE (ecosystem, next staleness touch): after ociswap done run 117, remaining oldest 2026-03-28 auto-gen stubs by updated_at – radixtalk, radixplanet, radix-review, radix-list, ploughshare, nerds-republic, ice, gable-finance, foton. All 1-block infobox-first-violation stubs; refresh 2-4/run per rotation.
• WATCH (ecosystem check-links, run 117): 82 broken-external, ALL confirmed standard false positives – X/Twitter 404 (NFTMachinist, erik_fdn), LinkedIn 999, Medium 403 (alphadex/astrolescent/weft/bondefi/instalabs/dmanyio/blockshard/mighty-chick), defillama 403 (caviarnine-hyperstake, weft), archive.org 0/timeout (moxstudio/abandonedarena deliberate Wayback links for wound-down projects), t.me/EmmogluStakery 0, fred.stlouisfed 0. No genuine dead links. 1 brokenInternal = /ecosystem app-route (FP).
• WATCH re-verify (run 118, community rotation): genkipool radixdlt-rust-sdk STILL not on crates.io – searched crates.io API for radixdlt-sdk / radixdlt-rust-sdk / radix-rola / genki: no genkipool Radix crate exists (only unrelated `genkit`). A WebFetch of the GitHub repo hallucinated a `radixdlt-sdk` crates.io publication – DID NOT edit the /community/genki page; its current wording (community project, JS/TS primitives reimplemented in Rust, no crates.io claim) is correct. Repo: 1 star, last commit 2026-07-06, no official-org transfer. Keep WATCH.
• contents/history rotation (run 119): audited 24 pages / 173 external. Category link-CLEAN – all brokenExternal are standard bot-block false positives (lsbu.ac.uk 403, medium/pillarproject 403, LinkedIn 999/429, x.com/beemdvp 404 [prior x.com-404-FP policy], t.me/ascarbek status-0 VERIFIED ALIVE via WebFetch). brokenInternal /contents/history + /ecosystem are valid category-hub routes (FPs). STALENESS: deepened pillar-hackathon-1 (2nd-stalest 2026-03-24 + thinnest, 3 blocks/2.3k) v2.0.1->2.1.0: was a bare stub (infobox + raw image/link dump); added Overview + Three Integration Tracks (NEM/DigiByte/Radix) + Radix Integration, sourced to pillar.fi write-up (17-18 Jan 2019, Radix built a bridge = wallet-gen in Radix format + balance retrieval), fixed infobox Organiser link + added Dates/Format rows, internal cross-links to history-of-radix/pillar-unconference/radix-mainnet-babylon. Remaining stalest banked: hack-the-system (2026-03-23, already 9 blocks/10.7k), dapp-in-a-day-workshop-5 (2026-03-24, 6 blocks/6k).
• run 120 (ecosystem staleness): refreshed the 3 stalest 2026-03-28 Notion-export stubs – radixtalk (2.0->2.1), radix-list (2.0->2.1), radix-review (3.0->3.1). Prepended/filled a leading facts infobox on each, purged dead notion.so + relative .md links (RDX Works->/ecosystem/rdx-works, Olympia/Babylon->/contents/tech/releases/*, Kansuler/@0xMattia unlinked), added internal links (radix-list->alphadex,dexian-protocol), added excerpts. Verified radixtalk.com + radixlist.com LIVE (272 listings); marked RADIX REVIEW 🟠 Dormant – no episodes since late 2025 + co-host @NFTMachinist X 404 (2 signals), back-catalogue links (Spotify/Apple/linktr) preserved. Category link-CLEAN modulo known FPs (54 web.archive.org fetch-failed = env cannot reach archive.org, NOT dead; X 404 NFTMachinist/erik_fdn/status-tweets; LinkedIn 999; FRED timeout).
• STILL STALE (ecosystem, next staleness touch): after run 120 did radixtalk/radix-list/radix-review, remaining oldest by updated_at are ploughshare, nerds-republic, ice, gable-finance (all 2026-03-28 auto-gen stubs, likely same notion.so/.md dead-link + no-infobox pattern).
• blog rotation (run 121): category link-CLEAN modulo standard bot-block FPs (unrealengine/grandviewresearch/escholarship/slashdata-s3/medium-@graycoding 403; fred.stlouisfed/mckinsey/statista 0-timeout-but-alive; LinkedIn 999/429 x7 + twitter.com/wyliepieote+beemdvp 404 on rgh2024-debrief [x.com-404-FP policy]; /contents,/ecosystem,/developers,/leaderboard,/contents/tech,/contents/tech/core-protocols brokenInternal = valid app-route landings). FIXED 1 genuine broken internal link: week-in-review-2026-07-19 (v1.1.0->1.1.1) linked the retired /community/radix-accountability-council path (that page is GONE; canonical is now /ecosystem/radix-accountability-council v2.2.1) – repointed 3 occ. NOTE: the RAC dedup (run 32 flag) resolved the OPPOSITE way from what run 14 assumed – the /community copy was removed and /ecosystem/radix-accountability-council became the maintained canonical; scrub any other /community/radix-accountability-council links on future rotations. Blog posts are authored/dated evergreen pieces – no staleness refresh warranted.
• run 122 (contents/resources): audited 11 pages / 59 external. Fixed 1 genuine dead link on how-to-buy-xrd (v1.2.1->1.2.2): removed HitBTC (403 both ways; NOT on canonical radixdlt.com/token venue list; exchange widely reported insolvent/withdrawal-frozen) and added Bitfinex (trading.bitfinex.com/t/XRD:USD, verified 200) + AscendEX (ascendex.com/en/cashtrade-spottrading/usdt/xrd) – both on the canonical list, previously missing; CEX list now aligned to canonical. NOTE: AscendEX deep-path 404s to curl/WebFetch (client-rendered SPA + bot-block; bare domain 200) but is the EXACT href the canonical radixdlt.com/token page uses – authoritative, do not strip on the automated 404. FALSE POSITIVE: brokenInternal /ecosystem on radix-booster-grants is a valid app route (ecosystem landing), left as-is. Staleness: 3 oldest are legal boilerplate (AUP/Privacy/Terms 2026-07-02) – deliberately NOT refreshed for freshness' sake; next content pages radix-visuals (07-07)/brand-assets (07-14) still fresh enough. Thin/upkeep run – no tweet.
• run 123 (ecosystem staleness): refreshed the 4 stalest 2026-03-28 auto-gen Notion-export stubs, all infobox-first violations with dead notion/.md links. radixplanet v2.0->2.1 (Dormant DEX, frozen since Dec 2023; PLANET V2 fixed 100M supply mint-disabled, on-ledger; cleaned bare YouTube, added Status note + Ociswap/DefiPlaza cross-links). ploughshare v2.0->2.1 (Dormant standalone -- ploughshare.srwa.io now NXDOMAIN -- but SRWA/srwa.io is LIVE and still names Ploughshare a registered NZ financial-service-provider partner for tokenised agri-lending; repointed dead SRWA .md->/ecosystem/srwa, fixed malformed nested demo anchor, added Status note). nerds-republic v3.0->3.1 (Dormant NFT, all supply reserved/site frozen 2021-22; Genesis Nerds GNRD verified 10,000 fixed on-ledger = matches 10k-char claim; repointed dead Foton .md->/ecosystem/foton; page had a video-only infobox so the any-infobox idempotency guard misfired -- used a follow-up guarded on a <table>). ice v2.0->2.1 (Active, ice404.com live; ICE 'Water' RRC-404 ~723/1000 cap minted on-ledger; repointed 3 dead links RRC-404->/developers/tools/rrc-404, notion.so Scrypto->core-protocols page, Ociswap .md->/ecosystem/ociswap; cleaned bare YouTube). Link audit: 140 pages/592 external, 83 brokenExternal (ALL fully-banked dormant-domain + anti-bot FP set) / 1 brokenInternal (/ecosystem live-index FP). No new genuine dead links.
• STILL STALE (ecosystem, next staleness touch): after run 123 did radixplanet/ploughshare/nerds-republic/ice, the next oldest by updated_at (all 2026-03-28 auto-gen stubs, same no-facts-infobox + notion/.md dead-link pattern) are foton, fidenaro, fibonacci-finance, emberflow, easymoon, dexter, defiplaza, caviarnine, alphadex. NOTE foton is now cross-linked inbound from nerds-republic and is itself a stub -- good next candidate. GUARD LESSON: the 'already has infobox' check must test for a facts <table>, not just b.type===infobox, since several stubs carry a video-only infobox.
• run 124 (developers rotation): category link-CLEAN modulo known FPs – 4x npmjs.com/@radixdlt/* 403 anti-bot (rola/babylon-gateway-api-sdk/babylon-core-api-sdk/radix-dapp-toolkit) + 5x /developers/* section-landing app routes (appRoutesReferenced, ignore). Grow-authority/freshness: deepened ecosystem/genkipool (v1.0.0->1.1.0) – 'Community App' to 'Community App & Developer Console' (~20-tool browser console: MCP server, manifest build/send, package deploy, token creation, component dashboard, SBOR encoder, test faucet, wallet playground, royalty claim, Olympia->Babylon conversion) + new 'Radix Seal' section (ROLA-passkey doc signing / AES-256 file encryption / E2E chat, client-side, optional soulbound-NFT on-ledger anchoring). Verified vs radix-community.genkipool.com/en/seal 2026-07-22. Script: scripts/update-ecosystem-genkipool-124.mjs.
• DEFER (developers staleness): the 8 oldest developers pages are the 2026-06-28 Scrypto/transactions/frontend tutorial series. Per 2026-07-20 traffic feedback the developers subtree gets ~0 top_pages traffic and the tutorials read accurate + current (install-scrypto pins verified run 65). Low-value to churn accurate low-traffic tutorials; refresh only if a Scrypto/toolkit version actually moves. Next developers touch: spot-check scrypto/01-fundamentals + getting-started/01-install-scrypto against live release notes.
• Ecosystem staleness (run 125): refreshed the 4 stalest 2026-03-28 auto-gen Notion-export stubs, all facts-infobox violations. gable-finance v2.0->2.1 (ex-Sundae Finance; gable.finance live 200 & still branded, identity-verified; wrapped bare YouTube; +3 internal links root-finance/weft-finance/radix-engine; medium etymology + LinkedIn kept, verified 200). fidenaro v2.0->2.1 (social/copy-trading; fidenaro.com live 200 branded; Q1-2024 real-money launch never shipped -> kept Dormant; +2 internal links astrolescent/radix-engine; founder twitter attribution kept per x.com-404-FP policy). fibonacci-finance v2.0->2.1 (risk-analytics; fibonacci.fi live 200 branded; repointed dead notion.so Radix-Mainnet-Babylon -> internal release page; wrapped bare YouTube; +3 internal links defiplaza/ociswap/root-finance; radixdlt.com/blog runs-on-radix Q&A verified live 200). emberflow v2.0->2.1 (LifeBand health-data dApp; emberflow.org live 200 branded EmberFlow; unwrapped 2 dead private notion.so links; +1 internal link radix-engine). All 4 were infobox-first violations w/ zero internal links -> now facts-infobox-first + cross-linked. Link audit: 140 pages/609 external, 85 brokenExternal (59 status-0 dormant-domain/archive-timeout FP, 21 anti-bot 403, 2 LinkedIn 999, 3 twitter.com-status/handle 404 = x.com-404 FP incl fidenaro/erik_fdn) / 1 brokenInternal (/ecosystem live-index FP). NO new genuine dead links. Script: scripts/_sweep-ecosystem-125.mjs (deleted). Thin/upkeep run – no tweet (run 124 GenkiPool/Radix-Seal tweet already went out today).
• STILL STALE (ecosystem, next staleness touch): after run 125 did gable-finance/fidenaro/fibonacci-finance/emberflow, remaining oldest 2026-03-28 no-facts-infobox stubs are foton (v3.2, 2 blocks no table, has resource_rdx foton.is asset – verify on-ledger before refresh), easymoon (v2.0, no table, has easymoon.io resource asset), academia-scrypto, xrd-domains. Higher-version 2026-03-28 pages (caviarnine v4, defiplaza v3, dexter v4, alphadex v3) likely already have infoboxes – check hasTable before assuming stub.
• run 126 (contents/tech): category link-CLEAN – 82 pages / 347 external, all broken-external are known bot-block FPs (SSRN/Medium/ResearchGate/IMF/CEPR/mirror.xyz/theblock.co/Coinbase/Forbes/bitcointalk 403 + LinkedIn 999). /contents/tech/research from shard-groups is a valid section-landing route (200), not broken. Deepened the 3 stalest 2026-03-16 core-concepts stubs (2->5 blocks each, v1.2->1.3): byzantine-fault-tolerance (Byzantine Generals origin + 3f+1 threshold + Cerberus/HotStuff lineage), component-royalties (package vs component royalties, XRD/USD denomination, claiming roles – cited docs.radixdlt.com/docs/using-royalties), liquid-stake-units (per-validator LSU resources, exchange-rate accrual, unstake claim-NFT + 2016-epoch/~7d delay – cited learn.radixdlt.com). Fixed 1 introduced broken internal link (transaction-fees, no such page -> docs transaction-costing). Remaining stalest core-concepts still 2026-03-16 (native-assets-vs-token-approvals, network-emissions, substate-model, transaction-manifests, xrd-token) – next contents/tech pass.
• Ecosystem rotation (run 127): link audit CLEAN of new genuine deaths – 83 brokenExternal are entirely the banked set (Wayback status-0 timeouts incl. the maya-protocol docs Wayback batch, x/twitter handle 404s cryptocoinfi/ripsource/EtherealDAO/erik_fdn, fred.stlouisfed 0/anti-bot, lucky8xrd.com dormant, moxstudio/farbo/radket/reizor/nftwars/stakebros/wearemonstas Wayback), brokenInternal /ecosystem = live category route FP. STALENESS: refreshed the 2 stalest ACTIVE DEX pages (both updated_at 2026-03-28, both pre-Babylon future-tense w/ no facts infobox + TipTap-mangled Notion .md links) – dexter v4.0.0->4.1.0 (rewrote to present tense: live order-book DEX since Babylon; added facts-table infobox keeping hero video; DEXTR tokenomics 14.5M max/biweekly emissions to 2032/~3.8M circ w/ livecoinwatch+radixdlt-blog sources; fixed AlphaDEX+Radstakes .md links -> /ecosystem/*) and defiplaza v3.0.0->3.1.0 (present-tense shipped features + ALR metric; facts-table infobox; current metrics ~$183K TVL/$10.9M vol/~$69K fees from defiplaza.net; DFP2 section; fixed Astrolescent .md link). NEXT stalest ecosystem ACTIVE pages for a future rotation: dexter/defiplaza now at back of queue; next up foton (Dormant, thin), easymoon (Dormant), caviarnine (Active, 16k content – deepen/refresh metrics), academia-scrypto (Active, thin 3.3k), alphadex (Dormant).
• community rotation (run 128): category link-CLEAN modulo 2 verified false positives – gilesmorris.me flagged status-0 'fetch failed' by the checker but returns HTTP 200 to a real UA (curl + browser-UA, DNS 109.228.34.61); linkedin.com/in/dan-hughes-* = known 999 anti-bot. All brokenInternal are valid /community + /ecosystem category routes. Freshness+cross-link: gilesmorris-me v1.2.0->1.2.1 – RAC moved from nominee-pool to a seated five-member elected body, so repointed the RAC anchor to the dedicated /ecosystem/radix-accountability-council (v2.2.1) and reframed the future-tense transition sentence to the current elected state (approval voting, Foundation->Radix DLT DAO handover); Giles's own status ('named among the nominees') left unchanged (not verifiable he was elected). Structural note: /community holds 45 pages but only 5 substantive (dan-hughes 44k, genki, vandyill, kangaderoo, gilesmorris-me); the other 40 are empty auto-gen 'My Community Page'/profile stubs – known bloat, deletion deferred (see deletion-sweep findings 2026-07-12). Stalest substantive next touch: kangaderoo (v1.2.0, 2026-07-11) – accurate + link-clean, low priority.
• run 130 (ecosystem staleness): prepended leading FACTS INFOBOXES to the 4 stalest 2026-03-28 auto-gen stubs, all infobox-first violations whose only "infobox" was a stray YouTube embed. caviarnine v4.0->4.1 (flagship DeFi suite: products/tokens/founders/HQ table), foton v3.2->3.3 (status->Active, site foton.is + @FotonSDK verified live via WebSearch), alphadex v3.0->3.1 (facts table + FIXED stale "set to launch in 2023" -> now live & powers the community-built DeXter front-end, cross-linked /ecosystem/dexter; alphadex.net verified live), easymoon v2.0->2.1 (legacy Olympia-airdrop status + repointed 2 dead notion/.md links: Babylon-> /contents/tech/releases/radix-mainnet-babylon, Ociswap-> /ecosystem/ociswap). Category link audit: brokenExternal 92->89 (the 3 removals), remaining 89 all banked bot-block/Wayback/x-handle FPs (medium 403, fred.stlouisfed timeout, web.archive timeouts, x 404s); brokenInternal=1 = /ecosystem section landing app-route FP. No new external links flagged.
• STILL STALE (ecosystem, next staleness touch): after run 130 did caviarnine/foton/alphadex/easymoon, the remaining oldest 2026-03-28 auto-gen stubs by updated_at are: academia-scrypto, xrd-domains, quackspace (Quack Space) – all likely the same infobox-first violation (leading <p>, YouTube-embed-only "infobox"). Same fix: prepend a leading facts <table> infobox + verify status. Then the 2026-06-28 batch ($EARLY, radical-staking) surfaces.
• blog rotation (run 131): category link-CLEAN of genuine deaths, matching run-121 banked assessment (13 pages / 117 external). ALL flagged externals are standard false positives – LinkedIn 999/429 (rgh2024-debrief attendees), twitter.com 404 wyliepieote/beemdvp (X automation block, banked FP class since run 97/117), unrealengine/medium-@graycoding/grandviewresearch/escholarship/slashdata-s3 403 anti-bot, fred.stlouisfed/mckinsey/statista 0-timeout/fetch-fail (all alive). Internal /contents,/ecosystem,/developers,/leaderboard,/contents/tech(/core-protocols) = valid category/app routes (checker does not allowlist them). One genuine fix: /blog/ten-10x-moments-coming-to-web3 cited blur.io over insecure http:// (alive, redirects https) -> bumped to https://blur.io (v2.2.4->2.2.5, script update-blog-blur-https-131.mjs); clears the recurring status-0 checker false-flag. No new page/discovery hook -> tweet skipped.
• run 132 (contents/resources): BANK verified bot-block FP – ascendex.com/en/cashtrade-spottrading/usdt/xrd returns 404 to the checker + 403 to WebFetch, but XRD/USDT is LIVE (search index shows price 0.04582 on that URL). Do NOT strip the AscendEX link on /contents/resources/how-to-buy-xrd on future resources sweeps; trust this banked FP.
• run 133 (ecosystem): 4 X/Twitter 404s left for manual review (x.com WebFetch 402s, cannot verify): x.com/ripsource on /ecosystem/soulstore; twitter.com/EtherealDAO status 1665509659824758784 on /ecosystem/etherealdao; twitter.com/erik_fdn on /ecosystem/fidenaro; twitter.com/cryptocoinfi status 1678146989303771137 on /ecosystem/alphadex. Also: /ecosystem/academia-scrypto and /ecosystem/xrd-domains are thin (infobox + 1 content block, ZERO outbound citation links) – need cited body sections; verify project liveness first.
• Developers rotation (run 134): audited CLEAN – 27 pages / uniform 2026-06-28 rebuild (~25d, evergreen tutorials, nothing genuinely stale). Only flags = known FPs: 4x npmjs.com/@radixdlt/* (rola, babylon-gateway-api-sdk, radix-dapp-toolkit, babylon-core-api-sdk – 403 anti-bot, packages live) + 5x brokenInternal section-index routes (/developers/{getting-started,scrypto,transactions,frontend,infrastructure} – live 200 landings). RE-VERIFIED install-scrypto version pins against live radixdlt-scrypto main: rust-toolchain.toml channel=1.92.0 unchanged, latest release still v1.3.1 (2026-01-20) – page claim 'Scrypto 1.3.1, Rust 1.81.0+ tested to 1.92.0' STILL CURRENT, no edit. genkipool radixdlt-rust-sdk still unadopted (per run-131 RadixDevelopers TG watermark) – keep WATCH, no page. No edits this run.
• WATCH (hyperscale/RadicalVibing, 2026-07-23): quackstra (agent) + community member propose native pairing + MSM host functions for BN254 & BLS12-381 in a radixdlt-scrypto fork so a Groth16/zkVM proof can be verified on-ledger – pure-Scrypto verify measured ~466M cost units (aborts at the 100M ceiling), the host-fn version re-measures at 3.74M cu (~124x cheaper). Repos public: github.com/quackstra/radixdlt-scrypto (branch feature/crypto-utils-v3-bls12381-pairing) + github.com/quackstra/groth16-scrypto. Deliberately NOT a PR yet (wants feedback). Too early for a page; if it becomes an RIP/PR or ships, candidate for a contents/tech/research stub.
• contents/tech rotation (run 135): DEEPENED network-emissions (v1.2.0->1.3.0), the stalest cornerstone page (untouched since 2026-03-16 seed, single 2-para Overview) – expanded to sourced sections (Emission Schedule 12B/~40yr=~300M/yr minted per-epoch; How Rewards Reach Stakers, validator set of 100 by stake + commission + LSU compounding; Reliability & Penalties, missed-consensus penalty burned + uptime<98%=zero rewards for validator & delegators; Emissions & Supply, 50% base-fee burn). Fixed 2 would-be broken internal links pre-publish (Olympia -> /contents/tech/releases/radix-mainnet-olympia; no transaction-fees page exists -> cited tokenomics KB instead). STILL STALE (next contents/tech touch, all 2026-03-16 seed batch by oldest updated_at): native-assets-vs-token-approvals, substate-model, transaction-manifests, xrd-token, radix-economic-model. Category link-CLEAN modulo the standard bot-block FP set (SSRN/Medium/ResearchGate/Coinbase/Forbes/bitcointalk/IMF/CEPR/mirror/theblock 403 + LinkedIn 999) + the /contents/tech/research section-route internal FP.
• run 136 (ecosystem staleness): academia-scrypto deepened with facts infobox + primary-source citations (v3.1.0). LOCKED-PAGE INCIDENT: xrd-domains was also edited by the sweep but it is in LOCKED_PAGES (alongside radix-namespace) – the seed/update scripts write SQL directly and bypassed isLockedPage(). Edit REVERTED to v3.0.0, revision deleted; seed-utils.mjs now exports LOCKED_PAGES/isLockedPage() (parsed from src/lib/tags.ts) and insertPages()+update scripts guard on it. STANDING RULE: xrd-domains & radix-namespace are LOCKED – do NOT deepen them in future staleness passes even though they read as stale 2026-03-28 stubs; they stay as-is by design. The UNLOCKED 2026-03-28 auto-gen stub cleanup (runs ~117-136) is now complete. NEXT ecosystem staleness touch (unlocked only): the 2026-06-28 batch – /ecosystem/early ($EARLY) & /ecosystem/radical-staking, then the 2026-06-29 group (pokerxrd, p2p-lending, acuiq, hydraswap, crumbsup) – SKIP radix-namespace (locked). Verify facts-infobox-first & cited; newer rebuild generation, don't assume the old stub shape. Still-banked unverifiable X 404s (x.com WebFetch 402s, manual review): x.com/ripsource (soulstore); twitter.com/EtherealDAO status 1665509659824758784 (etherealdao); twitter.com/erik_fdn (fidenaro); twitter.com/cryptocoinfi status 1678146989303771137 (alphadex).
• community rotation (run 137): link-CLEAN modulo 2 known FALSE POSITIVES – brokenExternal linkedin.com/in/dan-hughes-2a6b117 (999 anti-bot, banked run 26) and brokenInternal /community + /ecosystem (valid category-index routes). FIXED 1 genuine dead link: unwrapped notion.so/Radnode-f20371f5d2404d49a7483625c4e7d210 on /community/dan-hughes (v3.1.1->3.1.2) – the Notion public share cited for the "Dan Hughes as Satoshi" theory now loops on redirect (gone), NO Wayback capture, no archive to repoint to; sibling radnode.io/blog Satoshi post already unwrapped run 14. Kept "Radnode" as prose attribution. Community = 45 pages (43 member profiles w/ own author_ids + 2 editorial: radix-accountability-council, dan-hughes) – member-profile staleness refresh N/A; stalest are 2026-03-15 hex-slug profiles.
• run 138 (contents/history): infrastructure-rfps refreshed with RadixTalk P1 status (ex-Foundation DevOps team Pujar+Karwacki proposed running all 3 P1 services on AWS/OVH; threads merged 18 Mar 2026). RECHECK when the proposal is formally accepted and pricing/SLA/pre-funding terms go public – RadixTalk thread /t/foundation-rfp-signalling-server/2204 is the watchpoint; the WebSearch summary claiming services already "transferred + pre-funded through Dec 2026" was NOT primary-source-confirmed, do not publish that until verified.
• ecosystem rotation (run 139): link audit CLEAN – 140 pages / 626 external checked, ZERO genuine dead links. All flags are known FPs: medium/defillama/linkedin(999)/redbubble/unrealengine/projectnow 403 bot-blocks; web.archive.org snapshots "fetch failed" = checker transient reaching archive.org (intentional archival citations of dead sites – do NOT strip); x.com/twitter 404s (soulstore@ripsource, fidenaro@erik_fdn, etherealdao/alphadex deleted-tweet status URLs) = X bot-block family, UNVERIFIABLE (WebFetch on x.com 402s) – search still surfaces @ripsource as live, so left in place per skill caution. Verified-live transients: doubtitgame.com (503→LIVE), rly.fun, fred.stlouisfed.org timeout. STALENESS: deepened radical-staking (v2.0.1→2.1.0), stalest non-locked ecosystem page (untouched since 2026-06-28) with NO rendered infobox – added infobox-first facts table + refreshed badly-stale on-chain figures (82M XRD/2,070 delegators → 125.2M XRD/8,753 delegators, now #1 Radix validator by delegator count, per radicalstaking.com Jul 2026). Skipped LOCKED xrd-domains + radix-namespace (both in top-8 stalest).
• run 141 (contents/resources) – SYSTEMIC IMAGE-CDN DEATH (FLAG FOR A HUMAN). The spr.so / Super.so image proxy (Cloudflare Images account j42No7y-dcokJuNgXeA0ig) is fully DECOMMISSIONED: every images.spr.so URL returns origin 'ERROR 9404 ... HTTP 404 Not Found' (verified with browser UA+Referer+Accept – genuine death, NOT a bot-block). Impact: 86+ images across 13 pages, all dead. 100%-broken galleries: contents/resources/radix-visuals (79 imgs) + contents/resources/brand-assets (wiki's own logo kit). Also degraded (prose survives, images gone): blog/{dappinaday-stage-1-complete,rgh2024-debrief,ten-10x-moments-coming-to-web3,a-year-in-review-2023,money-wealth-volcanos,radix-is-what-web3-noobs-think-they-bought,building-radixs-developer-pipeline-nine-events-and-counting} + contents/tech/{core-concepts/shard-groups,core-protocols/radix-wallet,releases/stokenet,research/emunie}. Anchor-only check-links can't see this. FIX (needs source files / re-scrape, beyond a headless sweep): re-source graphics from docs.radixdlt.com + re-host to Vercel Blob (blob.vercel-storage, the site's normal image host – 18 pages already use it); repoint brand-assets logomark to same-origin /logo.png as an interim. Query to find all affected: content::text LIKE '%images.spr.so%'.
• WATCH (hyperscale, 2026-07-24/25): Aptos paper 'Prefix Consensus for Censorship Resistant BFT' (arXiv:2602.02892; Xiang, Tonkikh, Spiegelman) – paper is REAL. Community claims foxy pulled it into hyperscale.rs, but the claim is contested in-channel ('I didn't publish it') and hyperscale.rs docs still cite only HotStuff-2. Do NOT add to the hyperscale-rs page until incorporation is verified from a primary source (hyperscale.rs docs / GitHub / an flightofthefox statement).
• WATCH (RadicalVibing, 2026-07-23): member measured a Groth16 zkVM verify in pure Scrypto WASM at ~466M cost units – the engine aborts at the 100M ceiling, so no on-ledger zkVM proof verification is feasible today. Raw experiment, 'not a PR yet'. If it matures into a real design/PR, it could seed a page on Radix ZK/proof-verification limits.
• Ecosystem run 142: $EARLY refreshed but its deep body (Market Metrics / Token Economics list items) still cites Oct-2024 figures all pointing to the stillearly.tech homepage root – a future touch could trim/consolidate those to the dated Overview snapshot. Next stalest actionable ecosystem stubs after early: /ecosystem/pokerxrd, /ecosystem/p2p-lending, /ecosystem/acuiq, /ecosystem/hydraswap (all 2026-06-29). $EARLY 7d on-ledger volume ~$160 (near-dormant trading) but site 200 + token live – kept 🟢 Active, revisit status if site lapses.
• WATCH (ideas run 143, radixtalk): 'RFC Radix Strategic Council' (radixtalk.com/t/rfc-radix-strategic-council/2266) proposes a NEW governing body beyond the RAC. Still an RFC (not adopted). If ratified: (1) add to the dated 'Governing Bodies (as of 2026)' section of contents/tech/core-concepts/radix-governance, and (2) consider a new dao-* kanban card. WebFetch-confirmed the Phase-1 DAO documents (Charter 2269 / Round-4 final 2279) remain pre-adoption (awaiting legal+Foundation review, Apr-2026). RECONFIRMED 2026-07-27 (ideas run 155): still un-adopted, latest thread activity Apr-2026, community drift toward small autonomous Working Groups over a top-down council – no July movement, WATCH holds.
• run 144 (ecosystem staleness): proven-network is the next-stalest non-locked ecosystem page (updated 2026-06-30, single content block, NO leading infobox – infobox-first violation, same as root-finance was). Prepend a facts <table> next touch; verify launch stage first – docs.proven.network gives no dates/mainnet-live status, so don't assert '🟢 Active' without a source (metadata currently claims founded 2024-05).
• run 144 (ecosystem staleness): root-finance DONE (v2.1.0) – added leading facts infobox + DeFiLlama-sourced 'Protocol Status' (TVL peaked ~$1.67M 24 Apr 2025, now ~$2K Jul 2026), status Active->Dormant. Deliberately did NOT assert an 'exploit' – Root's team stated the Jun-2025 $HUG turmoil was market selling, not a Root liquidation rug; kept framing neutral/TVL-only. Founded date in metadata (2023-05-01) left untouched (unverified, pre-Babylon).
• run 146 (ecosystem staleness): proven-network DONE (v2.0.1->2.1.0). Was infobox-first violation (single content block, no leading facts table). Prepended a sourced facts <table> infobox; CORRECTED metadata/infobox Status 🟢 Active -> 🟠 In development – no mainnet/testnet launch announced, docs say work is "focused on establishing and stabilizing the core network infrastructure", federation still a future consideration, and GitHub proven-node last public commit Nov 2025 (~8mo). Added dated "Development Status" section (GitHub-org-sourced), fixed lone <h1>Overview> -> <h2>, internal-linked Radix -> /contents/tech/releases/radix-mainnet-babylon. NEXT stalest actionable ecosystem stubs (per run 142 backlog): /ecosystem/pokerxrd, /ecosystem/p2p-lending, /ecosystem/acuiq, /ecosystem/hydraswap – same auto-gen no-facts-infobox pattern likely.
• run 147 (contents/tech): DEEPENING CANDIDATE for next contents/tech rotation – hyperscale-rs page. The Aptos "Prefix Consensus For Censorship Resistant BFT" paper (arXiv:2602.02892) is now confirmed merged into hyperscale.rs (hyperscale_rs msg 10143, 2026-07-24; foxy adopting best-in-class BFT primitives). hyperscale-rs is the #3 traffic page (43 visitors/30d) so worth a sourced Batch-Sequencing/consensus-lineage refresh when the rotation next lands on contents/tech.
• run 147 (contents/tech): BANKED TWEET HOOK (discovery-led, holder-targeted) – xrd-token deepen surfaced two facts most XRD holders do not know precisely: (1) 50% of every BASE network fee is permanently burned (the other 50% to validators: 12.5% round-leader / 37.5% epoch pool; tips 100% to leader); (2) current on-ledger supply ~13.5B of a fixed 24B cap. Skipped this run (WIR announcement already spent the day's @RadixWiki tweet). Fire as a standalone daily when the feed is clear.
• WATCH (hyperscale, 2026-07-25/26): gilesmorris preparing FIRST public write-up of hyperscale-rs testing/verification architecture (sans-io, deterministic sim, Quint work) for This Week in Rust submission + an r/rust post, coordinated in-channel with flightofthefox (attribution of foxy bug findings + Prefix Consensus paper). x.com/gilesmorris/status/2081354677556252897 flagged as "first one!!" Still DRAFT/unpublished as of 07-26 – NOT citable yet. If it publishes: add an "External write-ups / community coverage" note to /contents/tech/research/hyperscale-rs (the #3 traffic page, 43 visitors/30d) linking the This Week in Rust / r/rust post.
• WATCH (RadixDevelopers, 2026-07-25): two community consultation votes opened via consultation.mountain-top.live – (1) migrating the Radix website from Webflow to Cloudflare (tc/5), (2) continuation of Stokenet Operations (tc/4). Minor ops/governance signal; not yet decided. If either resolves, note on the relevant ecosystem/ops page. Do not cite the vote UI as a source of fact.
• run 150 (contents/history) WATCH: x.com/beemdvp returns 404 to the link checker on 3 dapp-in-a-day-workshop pages (1,2,3). X 402s WebFetch so unverifiable; X routinely 404s bots. Attribution link, not a citation – left in place, do NOT strip on unconfirmed 404. Recheck if it persists across runs. t.me/ascarbek (status 0) verified ALIVE this run = false positive, no action.
• run 151 (ecosystem): astrolescent DEEPENED (v3.1.1->3.2.0). Was 2 blocks / embeds-only infobox (NO facts table) + stale June-2023 plans prose (discontinued $USDA/Prime Trust, unlaunched DAO). Added leading facts infobox, on-ledger-verified $ASTRL section (resource_rdx1t4tjx4g3qzd98nayqxm7qdpj0a0u8ns6a0jrchq49dyfevgh6u0gj3: 36M FIXED supply, minter deny_all locked, div 18, not freezable/recallable – radixscan read 2026-07-26), current aggregator+bridge product suite, refactored 2023 content into History (revenue-share now LIVE via staking), cross-linked ociswap/caviarnine/defiplaza/XRD/Radix-Engine, fixed duplicate line, dropped unverifiable YouTube embed. pokerxrd checked – facts still current (site confirms $poker->$xrd testing phase), no edit needed.
• BANKED TWEET HOOK (discovery-led, XRD-holder-targeted) from run 151 astrolescent deepen: $ASTRL is a FIXED 36M-supply token (minter permanently deny_all) where 100% of Astrolescent protocol profits – from FIVE streams (DEX aggregator, cross-chain bridge, limit orders, liquidity pools, validator node) – are shared with stakers. On-ledger verifiable. Not tweeted (deepen-not-discovery + recent @RadixWiki validator post spacing). Use next ecosystem-worthy run, link /ecosystem/astrolescent.
• RESOLVED WATCH (hyperscale, run 146/147 -> 151): gilesmorris FIRST public write-up of hyperscale-rs testing/verification architecture is now LIVE (This Week in Rust + r/rust drafts; x.com/gilesmorris/status/2081354677556252897). Next contents/tech rotation: deepen /contents/tech/research/hyperscale-rs with the sans-io / deterministic-sim / Quint verification angle once the r/rust write-up publishes and is fetchable (X currently 402s).
• run 153: contents/resources/how-to-buy-xrd link-CLEAN – 11 exchange links spot-checked live, all alive; gate.io + mexc.com return 403 (anti-bot FALSE POSITIVES, both major live exchanges, do not strip). Legal pages (acceptable-use/privacy/terms, oldest at 2026-07-02) are boilerplate – no refresh needed. python-scripts pages not audited this run.
• developers rotation (run 157): category link-CLEAN – 29 pages / 155 external, 0 broken internal/external. Freshly reworked in commit 1059efe (single-sourced tutorial metadata + AI Agents section), all pages uniform updated_at 2026-07-27 – nothing genuinely stale, no forced edits. SPILLOVER EDIT (step-1 new fact, not developers cat): hyperscale-rs (contents/tech/research) v4.6.0->4.7.0 – added 'Interactive Browser Demo (July 2026)' H3 documenting the 27 Jul live in-browser WASM SimulationRunner demo (hyperscale.rs/demo), sourced to the demo + hyperscale_rs telegram.
• run 158 (ecosystem): RESOLVED the run-156 addix structural flag. addix (stalest non-locked ecosystem page, updated 2026-06-29) had an EMPTY infobox block (blocks:[]) sitting at index 1 after the content wall, so no facts table rendered. Populated the infobox with a facts <table> and reordered infobox-first; added on-ledger-verified Token section ($HIT resource_rdx1t4v2jke9…az via radixscan 2026-07-28: fixed 1,000,000,000,000 supply, mint/burn/freeze/recall all deny_all, rules locked; site addix.meme resolves) with a neutral 2024-era freshness caveat; added External Links + a Related-pages list – page had ZERO internal links, now 11 (astrolescent/ociswap/defiplaza/dogecube/radlock/dexter). v3.0.1->3.1.0, live-verified render (infobox table + External Links). Next-stalest non-locked ecosystem candidates for future runs: pokerxrd, acuiq, p2p-lending (all 2026-06-29). xrd-domains + radix-namespace are LOCKED – skip.
• run 158 (ecosystem): category link audit CLEAN of genuine deaths – 82 brokenExternal all confirmed false positives: 75x status-0 are web.archive.org Wayback snapshots (throttle the checker) used as archival citations for wound-down projects; 22x 403 (anti-bot); 4x 404 + 1x 999 are x.com/twitter.com social links (X 402s/blocks automated checks). 0 broken internal. Matches run 154 finding. Do NOT strip these – trust the banked bot-block list, spend budget on NEW suspects only.
• contents/tech rotation (run 159): AUDIT near-CLEAN – 83 pages / 373 external, 0 broken internal. Only 1 genuine dead external link fixed: radix-governance Caper-wiki citation moved /wiki/daos/concepts/how-daos-fail (404) -> /wiki/dao-governance/concepts/analysis/how-daos-fail (verified 200; Caper concept pages live under dao-governance/concepts/<theme>, theme=analysis). talkcrypto.org/.../2256 on /sharding flagged [0] = CHECKER TIMEOUT FALSE POSITIVE (WebFetch 200, live). All other 21 brokenExternal are the fully-banked anti-bot 403 set (SSRN x4, cepr.org, imf.org, axieinfinity, theblock, coinbase, forbes, bitcointalk x3 emunie, researchgate, medium/@cann_dao/molecule/coinmonks/paradigm, coinvise+mirror.xyz+aibc on desci) – do NOT strip. STALENESS deepen: native-assets-vs-token-approvals (stalest @2026-03-16, was 2 blocks/1 h2/1815 chars) -> v1.3.0 (6 h2 sections/4941 chars/9 ext links) – expanded approval-risk explainer (revoke.cash), how Radix removes approvals + guaranteed outcomes/clear signing (docs.radixdlt.com /docs/manifest + /docs/resources, both verified 200 browser-UA), Implications, External Links. Next-stalest contents/tech pages still @2026-03-16 for next rotation: substate-model, transaction-manifests (core-protocols), radix-economic-model (research).
• WATCH (RadixDevelopers, 2026-07-28): solo dev announced DOP – Digital Ownership Protocol, a modular ownership/commerce stack on Radix (ROLA wallet ownership proofs, on-ledger licence/ownership refs, resale + creator royalties, WooCommerce/WordPress adapters WooDOP+PressConnect, physical bridge Physidge, Product Passport w/ GS1 Digital Link, Commerce+Commodity engines). Substantial working code claimed. NO citable primary source yet – no website/GitHub/X handle posted; founder explicitly asking whether it is worth continuing amid Radix infra uncertainty. Do NOT create an ecosystem page until a primary-source URL exists. Re-check for a link before next developers/ecosystem rotation.
• WATCH (hyperscale_rs, 2026-07-28): rich beacon-chain design Q&A worth folding into hyperscale-rs later – beacon chain = epoch-boundary blocks contributed by all shards w/ timestamps; shard config/committee assignment is a deterministic fold over beacon data (every node computes locally, no gossip); DoS resistance vs MVX meta-chain (leadered, single-target) and NEAR sharded-chunks (also leadered) – hs-rs needs to DoS f+1 of the beacon committee AND even then nodes ratify a skip epoch (staking/installs delayed, network does not halt). Source is Telegram Q&A (flightofthefox), not a primary doc – cite the whitepaper/docs when deepening, not the TG msg. hyperscale-rs already touched today (v4.7.0 WASM demo); do not re-edit same-day.
• run 162 (ecosystem) MAJOR CORRECTION – DeXter is RETIRED, not Active. Discovered via a NEW checker suspect: dexteronradix.com came back status-0, and a browser-UA fetch showed it now serves a GoDaddy parked-domain lander (window._trfd ap:'parking', lander_type=parkweb-reseller); www too, content.dexteronradix.com NXDOMAIN, dexter-on-radix.gitbook.io 404. Telegram record: retirement proposed 2026-02-18 (t.me/dexter_discussion/27547 – lack of exchange activity, tapering validator subsidy, Foundation maintenance-mode uncertainty), community poll passed, wind-down confirmed 2026-03-08 (msg 27603). On-ledger: txid_rdx1ppaz0ttj0cpus5rqtfq5qnar7gd535d228nm40fcekukjyf7qwkq7vaydx (2026-03-08) withdrew 1,210,222.41 XRD from treasury account_rdx168qrzyn… and placed a limit BUY for 4,739,465.1 DEXTR @ 0.25535 XRD on the AlphaDEX order book; treasury holds 1,213,497.76 DEXTR as of 2026-07-28 (~26% repurchased, rest of the XRD still in the open order). Total supply 4,739,465.13 (page had claimed ~3.8M mid-2026 – WRONG) and NO burn executed despite proposal step 4. Validator kept running at 10% fee (was 100%). GitHub org last push 2025-03-27. Page -> v4.2.0, status 🔴 Closed, website metadata key deleted (parked domain), sourced Retirement (2026) section added.
• run 162 (ecosystem): AlphaDEX collateral fix -> v3.1.1. Its infobox Status row read 🟢 Active while metadata said 🟠 Dormant (visible contradiction); aligned to Dormant with a sourced qualifier (engine live on-ledger, alphadex.net 200, but its main front-end DeXter retired March 2026) and moved the front-end/DeXter prose to past tense. alphadex.net verified live 2026-07-28.
• BANKED TWEET HOOK (discovery-led, XRD-holder-targeted) from run 162: the first order-book DEX built entirely by the Radix community, DeXter, was wound down in March 2026 – and the wind-down is fully readable on-ledger (treasury converted everything to XRD and placed one limit order to buy back all 4,739,465 circulating DEXTR at 0.25535 XRD; ~26% filled to date). Angle: a community project that closed as transparently as it was built. Skipped this run only because @RadixWiki had already posted twice today (run 157 + 18:18 UTC).
• STILL STALE (ecosystem, next staleness touch) – run 162 deferred the staleness slice to spend the run on the DeXter correction. Stalest non-locked, both 2026-06-29: (1) p2p-lending – decent 7-block page but describes an UNNAMED Stokenet dApp with no project name, website, team or X in the infobox (weak ecosystem entry; either identify the project or consider whether it belongs in /ecosystem at all); (2) acuiq – INFOBOX-LAST structural violation (infobox sits at content index 5, so no facts table renders at the top; same class as the addix fix in run 158). xrd-domains + radix-namespace remain top-stale but LOCKED.
• BANK checker FPs (run 162, NEW suspects verified): dexteronradix.com status-0 was GENUINE (parked – see correction above). http://DSOR.io on /ecosystem/caviarnine status-0 is a FALSE POSITIVE – returns 200 with title "DSOR - DeFi / cDEX Aggregator" to a browser UA; the link is plain http:// though, worth upgrading to https on the next caviarnine touch. Rest of the 85 brokenExternal are the unchanged banked set (54x web.archive.org, 13x medium 403, 4x projectnow.io 403, 3x defillama 403, twitter/x 404s, linkedin 999, fred.stlouisfed, unrealengine, redbubble). 0 broken internal across 140 pages.
• BANKED TWEET HOOK (run 163, high value, time-sensitive): the Stokenet Governance Proposal is LIVE for XRD-weighted voting at consultation.mountain-top.live/proposal/1 (Timan's website proposal at /proposal/2). Hook: the person who wrote the Radix DAO's entire legal/governance framework has also been running the network's testnet – validators and Gateway – out of his own pocket since May, and the vote to fund it just went binding. Link /community/daffy. Deliberately NOT tweeted in run 163: @RadixWiki had already posted twice on 07-28 (18:18 and 20:13 UTC, last one 2.9h before) – lead with this on the next run while the vote is still open.
• run 163 (community rotation): /community/cryptoants is the LAST remaining default-template stub in the category ("This is your personal community page…", v1.0.1, stale 2026-06-01). Searched for citable signal – zero hits across 555 messages of RadixDevelopers/RadicalVibing (90d) and the full RAC channel. Nothing to source a real page from. Options next community rotation: leave as-is, or delete per the run-148 curation decision (7 curated pages) if still unsourceable.
• run 163: /contents/tech/core-concepts/radix-governance now carries a dated "Live Proposals (July 2026)" section. It will go stale when the two Governance Proposals close – RECHECK on the next contents/tech rotation and record the outcomes (proposal 1 Stokenet funding, proposal 2 website).
• run 163 WATCH: the Radix DAO founding sequence is GP-PRE-1 (Constitutional Ratification, "ready for review") → Formation → GP-ELECT-1 (Permanent RAC election) → GP-ACTIVATE-1 (Activation Vote). None have opened. When GP-PRE-1 goes to a vote that is a cornerstone-page event for radix-governance and a strong discovery tweet.
• run 164 (contents/history): category link-CLEAN – 24 pages / 211 external, 0 broken internal. Every brokenExternal is an already-banked false positive, no new suspects: 18x linkedin.com/in/* (999/429), medium.com/pillarproject x2 (403), lsbu.ac.uk (403), coingecko.com/learn (403), orange-finance.gitbook.io (403), x.com/beemdvp 404 (standing x.com-404-FP policy, attribution link on workshops 1/2/3 – do NOT strip), t.me/ascarbek status-0 (previously verified alive). Spent no checking budget re-confirming them.
• DONE (run 164, contents/history staleness): the five stalest pages in the category were all DApp In A Day workshop records (2026-06-28). Refreshed the two worst – dapp-in-a-day-workshop-1 (v3.0.0->3.1.0) rebuilt as the SERIES HUB: split the single wall block that held details + tweet embed + nine photos into Intro/Details/Series/Media, added a series index table of all six recorded workshops with hosts, dates, mentors and sponsor, 16 internal links (was 0). dapp-in-a-day-workshop-3-roehampton (v3.0.0->3.1.0): sourced intro + "In the series" section, 8 internal links (was 0). NEW SOURCED FACT: St Mary's advertised the 26 Feb 2025 event on Eventbrite as "DApp in a Day - Web3 Workshop - Workshop 6" (verified live) while this wiki records it as #5 and has no #6 – recorded on dapp-in-a-day-workshop-5 (v2.1.0->2.1.1) so the gap reads as explained rather than missing, plus a stray-asterisk typo fix in its Details date line.
• STILL STALE (contents/history, next rotation touch): dapp-in-a-day-workshop-2-st-marys-university and dapp-in-a-day-workshop-4 (both 2026-06-28, v3.0.0) are the remaining raw media dumps – both have real content (#2 carries four participant testimonials, #4 carries Brunel Blockchain Society quotes and 22 photos) but zero internal links; give them the same series-context treatment as #1/#3, linking back to the #1 series hub. dapp-in-a-day-workshop-7-roehampton (2026-06-28, v3.1.0) is a one-paragraph stub and the thinnest of the series.
• ROTATION GAP FIXED (run 164): the top-level `policy` category (5 pages – verifiability, neutral-point-of-view, no-original-research, notability, freshness) was NOT in rotation.order and had never been audited; all five are still v1.0.0 / 2026-07-18 as seeded. Same class of gap as the `economics` one flagged in July. Appended `policy` to rotation.order – it will come up after `ideas`. These are the wiki's own editorial standards pages, so an audit should check they match how the sweeps actually work.
• WATCH (RadixDevelopers, 28 Jul): "DOP — Digital Ownership Protocol", a large modular ownership/commerce stack one developer has been building on Radix (ROLA-based wallet ownership proofs, DOPass access verification, licensing engine, WooCommerce/WordPress adapters WooDOP + PressConnect, physical bridge, commodity engine). Substantial and Radix-native, but the post gives no public site, repo, or handle, and "DOP" collides with an unrelated Ethereum-based Data Ownership Protocol token – NOT stubbed. Revisit if it gets a public URL or repo; it would sit under /ecosystem.
• HOOK BANKED (run 164): Radix ran six one-day "DApp In A Day" Scrypto workshops at UK universities between Oct 2024 and Nov 2025 (Westminster, St Mary's x2, Roehampton x2, Brunel), plus the Brunel Hack 25 festival – now fully indexed on /contents/history/dapp-in-a-day-workshop-1. Retrospective, so it needs pairing with something live (a current dev-onboarding or education story) before it earns a tweet on its own.
• run 165 (ecosystem): category link-CLEAN – 140 pages / 660 external, 0 broken internal. All 85 externalFlags are ALREADY-BANKED false positives (web.archive.org status-0 fetch-failures x~45 incl. the whole mayaprotocol/moxstudio/reizor/radket/farbo snapshot sets; Medium 403 x~10; LinkedIn 999 x2; DefiLlama 403 x3; projectnow.io 403 x4; unrealengine/redbubble/stlouisfed; x.com/twitter.com 404s per standing FP policy). Zero checking budget spent re-confirming them – no NEW suspects appeared this run.
• DONE (run 165, ecosystem staleness + grow-authority): /ecosystem/oter rebuilt v1.0.0 -> 2.0.0 (it had never been revised since seeding and predated OTER publishing a protocol spec). Sourced from the oter.io datasheet marked rev. 2026-07 + LIVE reads of random.oter.io /info, /public/latest and /health on 2026-07-29. Added the full parameter table (4h challenge window; 48h vote cycle = 24h sealed commit + 12h reveal + 12h re-propose; 70% supermajority of revealed voting power; EMA quorum easing in at 5%; sqrt(stake) weighting; ~97% jury seating; losing bond slashed 100% split 80/15/5 winner/correct-voters/protocol paid in rUSDC; 25 questions per batch; 3 failed-round tries; 7-day unstake cooldown), the beacon-seeded jury draw (scheme oter-min-pk-g2-pop, unchained, G1 keys / G2 sigs, domain oter-jury-beacon:v1, 3s period; live at round 30,835,175, 2s behind head), staker-DAO governance (allowlisted targets, action bound at creation, fail-closed execution, rejected proposal bond forfeited to voters), pull-based atomic settlement, and the builder use-cases. 3.0KB -> 13.5KB, internal links 1 -> 13. Status refined 🟡 Testnet -> 🟡 Pre-launch (beacon live in production, oracle not on mainnet).
• NEW PAGE (run 165): /ecosystem/tahuna – Tāhuna, a decentralized prediction-market protocol on Radix mainnet and OTER's founding integration. The single biggest ecosystem gap surfaced this run: no wiki page existed and it was reachable only via oter.io's footer. Sourced from tahuna.org + tahuna.org/resolution (2026-07-29). Records the fully on-ledger order book (99 or 999 price levels, xUSDC quote, matching engine in the contract, no off-chain matcher), taker-pays fee model peaking at 1.80% at 50c with per-fill maker rebate, permissionless listing free or revenue-generating on a 10 xUSDC bond with a lifetime creator fee share, 4h proposer window escalating to OTER's single-round timelocked jury (drand releases the key), no token / no presale / no airdrop, and the Q3 2026 testnet / Q4 2026 mainnet targets. 8.5KB, 11 internal links, inbound link added from /ecosystem/oter.
• DISCREPANCY LOGGED (run 165) – recorded on /ecosystem/tahuna rather than resolved: tahuna.org/resolution says disputed-market jurors "earn OTER tokens", while the oter.io datasheet says voters are paid in rUSDC stablecoins, "actual money, not platform tokens". Both are pre-launch first-party docs and neither has settled on-ledger. RECHECK on a future ecosystem rotation once either project reaches mainnet – whichever way it lands is a correction to make on both pages.
• UNVERIFIED CLAIM (run 165, ecosystem): oter.io states it "upstreamed that verification into the Radix engine itself" (BLS12-381 beacon verification native to the Radix engine). Written on /ecosystem/oter as OTER's own attributed statement, NOT as independent fact – no radixdlt commit, RFC or release note was found backing it. If confirmed against a radixdlt repo or protocol release it is a genuinely notable Radix-engine fact worth its own mention on the Radix Engine page; if it cannot be sourced, keep the attribution as-is.
• STILL STALE (ecosystem, next rotation touch): after this run the stalest editable pages are p2p-lending (2026-06-29, v1.0.1 – and structurally weak: it describes an UNNAMED Stokenet fixed-rate lending dApp with no project name, site or team, so it reads as a concept page filed as a project; decide whether to name it or reframe it), acuiq (2026-06-29), caper (2026-07-03), stabilis (2026-07-03, already 21KB and deep), radland (2026-07-03, v1.2.3, only 1.4KB and dormant – thinnest in the category). xrd-domains (2026-03-28) and radix-namespace remain LOCKED_PAGES – permanently top of pagesByStaleness, skip them, they are not neglect.
• WATCH (run 165, hyperscale_rs TG 27-28 Jul): the in-browser WASM demo at hyperscale.rs/demo was ALREADY captured by run 158 same-day (hyperscale-rs v4.7.0, verified before editing – no duplicate). The new 28 Jul thread is a deep beacon-chain Q&A from flightofthefox: the beacon is only the epoch-boundary blocks every shard contributes, it appoints every committee by schedule, it never sees a transaction so it does not cap TPS, it can be checkpointed with anchors compiled into the node so sync starts from the last build, and a committed shard transaction carries an unforgettable obligation to include its wave certificate in a later block (state stays locked until then). The page already carries a 10.8KB beacon section – check for genuine gaps rather than appending on the next contents/tech rotation.
• run 166 (developers rotation): category link-CLEAN for the fourth consecutive sweep – 29 pages / 155 external, 0 broken internal or external, all pages uniform updated_at 2026-07-27 from the commit-1059efe rebuild. Nothing stale, no forced edits. Pivoted the run to GROW-AUTHORITY: created developers/scrypto/09-permissioned-and-regulated-assets, the gap behind the most repeatedly asked question in RadixDevelopers ("how do I make a token that only moves between KYC'd accounts?"). 03-authorization-and-badges covered badge-gated CALLS; nothing covered movement rules on the resource. Post-edit re-audit: 30 pages / 162 external, still 0 broken.
• WATCH re-check (run 166): DOP (Digital Ownership Protocol) STILL has no citable public source – the only artefact is the developer's own RadixDevelopers write-up (msgs 65819-65821, 28 Jul); the single reply (65825) asks whether it will be open-sourced and is unanswered. No site, no repo, no third-party coverage. Do NOT stub. Re-check when a URL or repo appears; the ownership-as-a-protocol-primitive framing plus working ROLA proof/licensing flows would make a strong ecosystem page if it becomes verifiable.
• FOLLOW-UP (developers): if radixdlt/sargon#452 and radixdlt/babylon-wallet-android#1446 (genkipool, opened 2026-07-23, both open at 2026-07-29) merge, update BOTH developers/scrypto/03-authorization-and-badges and developers/scrypto/09-permissioned-and-regulated-assets – each currently states wallet auto-attachment of required badges is proposed-not-shipped and dates that claim. Check with `gh api repos/radixdlt/sargon/pulls/452`.
• run 167 (ecosystem): category link audit CLEAN – 141 pages, 0 broken internal, 84 brokenExternal and ZERO new suspects. A regex filter against the banked FP set (web.archive.org, medium, linkedin, defillama, projectnow.io, unrealengine, redbubble, stlouisfed, x.com/twitter.com, DSOR.io) matched all 84, so no checking budget was spent re-confirming. Third consecutive clean ecosystem audit (runs 162/165/167).
• CORNERSTONE GAP CLOSED (run 167): /contents/tech/core-concepts/subintents-and-pre-authorizations created – the wiki had NO page on Radix subintents despite 9 pages referencing them in passing (blog/week-in-review-mar-16-22-2026, contents/history/brunel-hack-25, history-of-radix, developers/ai-agents/radix-context, ai-agents-and-x402, developers/infrastructure/radixdlt-rust-sdk, developers/transactions/02-transaction-lifecycle, ecosystem/p2p-lending, ecosystem/anthic), and no Cuttlefish release page exists either. 8 blocks: intent tree (root transaction intent + child subintents, YIELD_TO_PARENT, buckets on the starting worktop), the 4-part pre-authorization flow, expiry (setExpiration afterDelay/atTime) and the SubintentHeader field table, what the signer is actually guaranteed (ASSERT_ instructions, VERIFY_PARENT, GeneralSubintent classification), the 4 documented use cases, and a Limitations section. All sourced to docs.radixdlt.com (fetched with a browser UA – plain fetchers 403) and the radix-dapp-toolkit README via the GitHub API.
• STILL MISSING (contents/tech/releases): there is no Cuttlefish page, and no page for any protocol update after Babylon. Releases currently holds only radix-mainnet-babylon / -olympia / -xian, rcnet, stokenet, radix-developer-environment-alexandria. Anemone, Bottlenose, Cuttlefish and Dugong are all absent. Cuttlefish is the highest-value of these (Transaction V2 + subintents + CryptoUtils + Account getters; enacted 2024-12-18T10:48:58Z, epoch 105353, shipped as cuttlefish + cuttlefish-part2 back-to-back, Scrypto v1.3.0). Primary source: docs.radixdlt.com/docs/cuttlefish. Good next contents/tech grow-authority item.
• run 167 (ecosystem staleness): acuiq FIXED (v2.1.1 -> 2.2.0) – the infobox-LAST structural violation flagged in run 162 is resolved (facts table now leads at index 0). Also: replaced the precise dataset counts (7,637 symptoms / 575 acupoints / 1,035 protocols) with the figures the project actually publishes (7,000+ / 400+ / 200+, acuiq.com/llms.txt) because the precise ones are not publicly verifiable and the protocol count conflicted with the published one by 5x; deleted the internal go-to-market Backlog list (roadmap wishlist, not encyclopedic); added a sourced Research Output section (acuiq.com/research, the "TF4 Is Not a Point" namespace finding); and replaced the speculative DeSci paragraph with a plain "Relationship to Radix" section stating that AcuiQ has no Radix component, token or wallet integration and that the public site does not mention Radix or blockchain anywhere. Added metadata.onLedger=false.
• run 167: p2p-lending RESOLVED as far as it can be (v1.0.1 -> 1.1.0). It could not be named – a WebSearch for the Stokenet fixed-rate lending dApp surfaces only generic subintent coverage, no project name, site or team. Rather than leave it reading as a directory entry for a phantom project, it now carries a leading editorial note saying the developers have not published a name and that the page documents the mechanism, plus a "Project name: Not publicly disclosed" infobox row. Also repointed its body to the new subintents concept page and replaced the unlinked "Cuttlefish Upgrade (December 2024)" with the sourced 18 December 2024 enactment. RECHECK: if the project ever identifies itself, rename the page; if it never does, consider moving the content to contents/tech as a pattern page and retiring the ecosystem entry (it has ZERO real inbound links – only the maintenance log references it).
• LINK FIX (run 167): developers/transactions/02-transaction-lifecycle v1.2.0 -> 1.3.0 – two "Subintents" anchors pointed at /contents/tech/core-protocols/transaction-manifests, which is about manifests, not subintents. They resolved 200 so check-links never flagged them, but they sent the reader to the wrong concept. Both repointed to the new subintents page. LESSON: a link audit only catches links that 404 – anchors pointing at the wrong live page are invisible to it and need reading.
• STILL STALE (ecosystem, next rotation touch): after run 167 cleared acuiq and p2p-lending, the stalest editable pages are caper (2026-07-03), stabilis (2026-07-03, already 21KB and deep – low value), radland (2026-07-03, v1.2.3, only 1.4KB and Dormant – thinnest in the category, best candidate), radixnodeio (2026-07-03), juicy-stake (2026-07-03). xrd-domains and radix-namespace remain LOCKED_PAGES and sit permanently at the top of pagesByStaleness – skip them, that is not neglect.
• WATCH re-check (run 167): DOP (Digital Ownership Protocol) still has no citable public source. The only new artefact since run 166 is reply 65825 (28 Jul) asking whether it will be open-sourced, still unanswered. No site, no repo, no handle. Do NOT stub.
• run 168 (contents/tech): category link audit CLEAN – 84 pages / 382 external, 0 broken internal, 26 brokenExternal every one of which matches the fully-banked contents/tech false-positive set (SSRN x3, researchgate, medium x4, coinvise, aibc, mirror, theblock, coinbase, forbes, bitcointalk x3, cepr, imf, axieinfinity, stanford-jblp, linkedin 999, en.wikipedia 429 x4). ZERO new suspects, no checking budget spent re-confirming.
• RESOLVES the run-167 bank "STILL MISSING (contents/tech/releases): no Cuttlefish page, no page for any protocol update after Babylon". Closed as ONE page rather than four stubs: /contents/tech/releases/protocol-updates (v1.0.0, 10 blocks, ~13.4 KB) covers Genesis, Anemone, Bottlenose, Cuttlefish and Dugong plus the readiness-signal enactment mechanism (75% stake threshold, consecutive-epoch support, lower/upper epoch bounds, flash transactions). Anemone/Bottlenose/Dugong are 4-bullet docs entries – four thin stubs would have been worse than one cornerstone. Inbound links added from radix-mainnet-babylon and subintents-and-pre-authorizations.
• FACTUAL ERROR IN OFFICIAL RADIX DOCS (run 168, corrected on-wiki): docs.radixdlt.com/docs/cuttlefish lists Cuttlefish enactment as "Epoch: 105353". That is Bottlenose's epoch. Real value 160923. Two independent verifications: (1) mainnet Gateway /stream/transactions at_ledger_state by timestamp returns epoch 160922 round 2115 at 2024-12-18T10:48:57.955Z, immediately before the docs' own enactment stamp 2024-12-18T10:48:58Z, and epoch 160923 opens at 10:49:01.607Z, while epoch 105353 opened 2024-06-07T10:32:48.388Z (= Bottlenose); (2) the configured Cuttlefish enactment window in /docs/node-protocol-updates is [158682; 161562), which contains 160923 and excludes 105353 (105353 sits in Bottlenose's [104291; 112355)). Run 167 had propagated 105353 into the new subintents page infobox – corrected there (v1.0.0 -> 1.1.0). METHOD WORTH REUSING: any docs-published epoch can be checked in one Gateway call.
• run 168 (contents/tech staleness): substate-model v1.2.0 -> 1.3.0, the stalest page in the category (untouched since the 2026-03-16 seed) and a 2-block/1.6 KB cornerstone that asserted fine-grained parallelism without ever saying what a substate is addressed by. Now 6 blocks / ~9 KB: NodeId -> Partition Number -> SubstateKey addressing, the kernel/database layer split (kernel defines the Node/Partition/Substate abstraction and is implemented on the database layer's partition-key/sort-key over a key-value store), where a component's substates come from (blueprint Fields + Collections mapped to partition numbers by the System Layer, plus metadata/royalty/access-rule object modules), and what the granularity buys vs account and UTXO models, tied to hyperscale-rs per-substate locking vs hot-state flagging. Sourced to radix-engine-docs.radixdlt.com (layers / kernel / database / blueprint_impl) – a primary source the wiki was barely citing.
• STILL STALE (contents/tech, next rotation touch): after run 168 cleared substate-model, the stalest are transaction-manifests (2026-03-16) and radix-economic-model (2026-03-16), then the 2026-04-05 operations pages (improvement-log, control-chart) and the 2026-05-03 core-protocols/core-concepts block (vm-layer, kernel-layer, consensus-manager, locker-blueprint, transaction-tracker, resources, metadata-module). transaction-manifests is the highest-value of these – it is the target several pages link for manifest semantics and it now has a sibling subintents page to cross-link.
• TWEET HOOK BANKED (run 168, not posted – @RadixWiki already at the 2-per-day ceiling with runs 165 and 167, the most recent ~hours old): "the official Radix docs give Cuttlefish the wrong enactment epoch — it is Bottlenose's — and you can prove it with one Gateway call". Discovery-led, builder-facing, verifiable, and the exact shape that measures best for this account. Links /contents/tech/releases/protocol-updates. Use it on the next run that is clear of the daily ceiling.
• AUDIT HYGIENE (run 168): re-run check-links on the category AFTER editing, not just before. The new protocol-updates page cited the Gateway as the bare endpoint https://mainnet.radixdlt.com/stream/transactions, which is POST-only and returns 405 to a GET – it would have entered the banked false-positive set forever. Caught by the post-edit audit and repointed to docs.radixdlt.com/docs/network-apis (v1.0.0 -> 1.0.1). RULE: cite API documentation pages, never bare POST endpoints.
• run 169 (ecosystem): audit link-CLEAN for the FOURTH consecutive ecosystem run – 141 pages / 668 external, 0 broken internal, 86 brokenExternal all matching the banked FP regex (web.archive.org, medium, linkedin, defillama, projectnow.io, unrealengine, redbubble, stlouisfed, x.com/twitter.com, DSOR.io) with ZERO new suspects, so no checking budget was spent. Post-edit re-audit: 0 broken internal, brokenExternal up to ~98 – the 18 new flags are all web.archive.org status-0 fetch failures (archive.org rate-limits bursts; the specific snapshots were each verified 200 by curl) plus one transient t.me/phoenix_xrd status-0 that returns 200 on retry. NOTE the checker itself is the finding this run: it cannot see re-registered domains or metadata-borne links.
• STILL DEAD, not yet reflected on their pages (run 169 metadata-website scan, 126 checked): rdx.works and radixfoundation.org BOTH refuse the TLS handshake (tlsv1 alert internal error) at their Webflow host – recorded on both pages this run. Remaining unrecorded: token-trek/tokentrek.io, ploughshare.srwa.io, xrdegen.com, ideosphere.io, beaker.fi, arcanelabyrinth.com, anthic.io, religantoracles.com, singularityx.net, danxrd.xyz, backeum.com, lending.dexian.io, easymoon.io, radiator.run, xidar.io, inflabs.net, radnode.io (404), radstakes.com (404), hug.meme, trove.tools (404), beta.launchspace.app, topradixnode.com (404), dogecubex.live, wearemonstas.com (404 at a prositehosting holding page). Most are already 🔴 Closed/🟠 Dormant so the dead site is consistent – the ones to check first are any still marked ACTIVE. Also benign: crumbsup.net -> crumbsup.io and hardmoneyproject.com -> its Substack (same projects, just moved).
• STILL STALE (ecosystem, next rotation touch): run 169 cleared radland, instabridge, radixnodeio, vikingland, rdx-works, radix-foundation, radixscan, anthic, dogecube, etherealdao and radit. Next stalest editable are caper (2026-07-03), stabilis (2026-07-03, already 21KB and deep – low value), juicy-stake (2026-07-03, and juicystake.io now 502s), blue-chick-nfts (2026-07-05), the-hard-money-project (2026-07-05). xrd-domains and radix-namespace remain LOCKED_PAGES at the permanent top of pagesByStaleness – skip them.
• run 170 (developers rotation): category link-CLEAN for the FIFTH consecutive developers sweep – 30 pages / 162 external, 0 broken internal, 0 broken external (even the four npmjs.com/@radixdlt/* 403s that used to flag are gone). Applied the three run-169 checker-invisible audit classes to the subtree and all three came back clean: zero Notion-export anchors (href="<Name> <32-hex>.md"), zero non-http non-/-prefixed relative hrefs, and the only two metadata.website URLs in the category (agent-wallet-ai -> wallet-agent-ai.github.io, igentix -> demo.igentix.app) both resolve 200 on their ORIGINAL registrable domain with no off-site redirect. Version pins re-verified against live sources: Scrypto 1.3.1 is still the latest radixdlt-scrypto release (published 2026-01-20), so 01-install-scrypto's "Scrypto 1.3.1 / Rust 1.81.0+ tested to 1.92.0" claim stands; radix-desktop-tool's "v0.2.4 (April 2024)" is a deliberate dormancy statement, not staleness; the 1.0.0 hits on the two frontend pages are applicationVersion values inside sample code, not pinned dependency versions. Staleness sort offered nothing real – 29 of 30 pages share updated_at 2026-07-27 from the commit-1059efe rebuild, so no timestamp-bump edits were manufactured.
• CORNERSTONE GAP CLOSED (run 170): /developers/transactions/05-addresses-and-entity-types created (12 blocks, ~21 KB, v1.0.0) – the wiki had NO page on Radix address encoding across all 344 pages. Found with the run-167 grep method: Bech32/HRP/address-format terms appeared in page content but no page carried the concept, and zero pages had 'address' in a title or slug. Covers the Bech32m three-part structure, the decoder's three checks (Bech32m variant enforced, entity-type byte must resolve, HRP must match the type byte or InvalidHrp), the global entity prefix table with u8 discriminants, why the first two payload characters are readable (top 5 bits of the entity byte select char 1, bottom 3 constrain char 2 to one of four), the network suffix table (mainnet rdx/1, stokenet tdx_2_/2, localnet loc/240, simulator sim/242, plus the five retired testnet reservations), global vs internal HRPs, preallocated Ed25519 (81) vs Secp256k1 (209) vs allocated (193) accounts, the seven transaction-part prefixes incl. subtxid_, and the well-known native addresses. All facts cited to radixdlt-scrypto main source files (hrpset.rs, entity_type.rs, network/mod.rs, decoder.rs, native_addresses.rs) rather than to docs prose – docs.radixdlt.com/docs/addresses 403s WebFetch. Inbound link added from 04-radix-engine-toolkit Next Steps (v1.1.0 -> 1.2.0). Post-edit re-audit: 31 pages / 169 external, 0 broken internal, 0 broken external.
• FOLLOW-UP re-checked (run 170): radixdlt/sargon#452 ("feat: add RequiredBadge support to PerAssetTransfers manifest builder") and radixdlt/babylon-wallet-android#1446 ("Feature: Auto-attach Required Badges for Restricted Token Transfers") are BOTH still open, merged:false, at 2026-07-30. No edit needed – developers/scrypto/03-authorization-and-badges and 09-permissioned-and-regulated-assets both correctly state wallet badge auto-attachment is proposed-not-shipped. Keep the follow-up banked; re-check with `gh api repos/radixdlt/sargon/pulls/452`.
• GAP TRACKER (run 170, from the term-grep): remaining high-frequency terms with no page of their own – (a) Decimal / PreciseDecimal, the fixed-point arithmetic types, 19 pages reference them and none define the I192/I256 backing, the 18-decimal scale, or the rounding modes; strong next developers/scrypto item. (b) The Radix Wallet MFA Security Shield (6 pages mention 'multi-factor' or 'shield', none is about it) and Sargon, the shared wallet core (3 refs, no page) – both belong under contents/tech/core-protocols alongside radix-wallet. (c) Epoch: 30 pages use the word, none defines the unit; probably a section on an existing consensus page rather than its own cornerstone.
• run 171 (ecosystem): the standard audit came back CLEAN for the FIFTH consecutive ecosystem run (141 pages / 671 external, 0 broken internal, 87 of 88 brokenExternal matching the banked FP regex, the single new suspect a gitbook.io timeout that returns 200 on retry). So the run generalised the run-169 method instead: EVERY distinct external hostname on the wiki (463, extracted from all 345 pages plus every metadata.website) was probed with a browser UA, following up to 6 redirects, and the final registrable domain compared with the original. A 200 that lands on somebody else's domain is structurally invisible to check-links. 20 off-domain redirects and 75 non-200s came back.
• MAJOR FINDING (run 171): THE FIRST-PARTY RADIX WEB dAPPS NOW RUN ON RadixScan. Verified 2026-07-30 with header inspection: dashboard.radixdlt.com 302s to dashboard.radixscan.io and console.radixdlt.com to console.radixscan.io, both PATH-PRESERVING (a validator, resource, transaction or /deploy-package deep link arrives at the same route). sandbox.radixdlt.com has no DNS record while sandbox.radixscan.io serves the app. radixscan.com also 302s to the RadixScan dashboard. The redirects are issued from radixdlt.com's own Cloudflare edge, which only the domain holder can configure, so this is a deliberate handover and not a lapsed domain. No public announcement was found. Enabling commit trail in radixdlt/dapps-monorepo: #1034 (Feb) removed the PostgreSQL dependency, #1035 (Mar) added a deployment guide, #1036 (Mar) made the dApp definition env-configurable. /ecosystem/radixscan rebuilt v2.1.0 -> 3.0.1 around it (9 blocks, ~12.5 KB, and it finally has the infobox it never had).
• STOKENET HAS NO HOSTED DASHBOARD OR CONSOLE (run 171): stokenet-console.radixdlt.com and stokenet-sandbox.radixdlt.com return HTTP 530 from Cloudflare with no origin; stokenet-dashboard.radixdlt.com 302s to the MAINNET dashboard homepage, discarding both network and path; no stokenet-* hostname resolves under radixscan.io. /contents/tech/releases/stokenet was sending developers straight at all three – fixed v1.1.2 -> 1.2.1: Resources table replaced with the verified position plus self-hosting instructions (PUBLIC_NETWORK_NAME=stokenet, PUBLIC_DAPP_DEFINITION_ADDRESS, turbo build + node apps/console/build or the Vercel adapter), infobox moved from index 1 to index 0, 9 dead images.spr.so screenshots removed and the 7 orphaned single-item <ol> step lists merged so the walkthrough numbers 1..n again.
• HIJACK on a CONCEPT page (run 171): moreequalanimals.com – Dan Larimer's blog, cited on /contents/tech/core-concepts/delegated-proof-of-stake-dpos as the source for 'invented by Dan Larimer' – has been re-registered and now serves ProTogel, an Indonesian online-gambling site. Repointed to Larimer's own DPoS paper (steemit.com/dpos/@dantheman/dpos-consensus-algorithm-this-missing-white-paper, 200). LESSON: run 169 assumed this class lived on project pages; it does not. Concept and history pages cite small personal domains too.
• LabDAO wound down (run 171): labdao.com is a HugeDomains for-sale lander ($13,795) and labdao.xyz a Sedo parking page. Its own GitHub org description reads 'LabDAO used to be an online computational life science research collective' – a primary, past-tense source. /contents/tech/core-concepts/decentralized-science-desci v1.1.2 -> 1.2.0: the DeSci directory row repointed to github.com/labdao with the status recorded.
• DONE (run 171) – closes the run-169 bank 'STILL DEAD, not yet reflected on their pages': 26 /ecosystem pages had their metadata.website cleared or repointed (that field is linkified into the rendered infobox, so it is the page's most prominent link, and an unregistered domain can be bought by anyone). Four had a live successor and were repointed: ploughshare.srwa.io -> srwa.io (which still names Ploughshare as a live product; ploughshare.nz resolves but shows a maintenance page), dogecubex.live -> dogecube.io (parent community site alive, its own /swap 404s so the DEX itself is gone), crumbsup.net -> crumbsup.io (301, same project, new TLD), hardmoneyproject.com -> hardmoneyproject.substack.com (301, 'Coming soon', last post April 2025). 11 pages that had no site-status prose got a one-line dated Website note, inserted ABOVE any trailing See also / Further Reading / External Links heading. No status field was flipped: a dead website is not proof a token project closed.
• TRAP AVOIDED (run 171): anthic.io has no DNS record, but anthic.com DOES resolve – and serves an unrelated Lithuanian cycling-tourism site. Recorded on /ecosystem/anthic as an explicit 'do not treat as a successor' note. Guessing the .com of a dead .io is how a wiki acquires a hijacked link.
• NEXT DEVELOPERS ROTATION (run 171): ~40 wiki references to dashboard.radixdlt.com / console.radixdlt.com still describe them as the official Radix Dashboard and Developer Console. The LINKS all work (path-preserving 302) so nothing is broken and no urgent fix is needed, but the WORDING is now wrong – they are community deployments. 5 developer pages (transactions/01-manifest-language, frontend/01-radix-dapp-toolkit, frontend/04-dapp-definition-and-verification, getting-started/03-deploying, plus the stokenet page now fixed) and ~35 ecosystem pages linking validator/resource/account routes. Sweep the wording per-category as each comes up; /ecosystem/radixscan is the page to link.
• BENIGN off-domain redirects (run 171) – do not 'fix' these on a future probe: anchor.fm->creators.spotify.com, discord.gg->discord.com, twitter.com->x.com, youtu.be->youtube.com, www.notion.so->app.notion.com, doi.org->publisher, app.joinhandshake.co.uk->.com, keyrock.eu->keyrock.com, imt.cx->imtcoin.com, www.psydao.io->psydao.world, app.curedao.org->warondisease.org, studies.curedao.org->studies.dfda.earth. REAL and still unfixed: www.argent.xyz->www.ready.co on /contents/history/partnerships (Argent rebranded to Ready; the 2020 partnership record should say so). NOT LINKED but note for the future: dmany.io (Token Trek's builder) now redirects to sun-win.im, a gambling site – never add that domain.
• ROTATION (run 171): cursor deliberately set to `policy` rather than the next entry in order (`community`). Reason: the 5-page top-level policy subtree – verifiability, neutral-point-of-view, no-original-research, notability, freshness, all still v1.0.0 / 2026-07-18 as seeded – has NEVER been audited (flagged in run 164) and sits 13th in rotation.order, so following the order defers it indefinitely. It is cheap. After policy, resume the declared order at `community`.
• STILL STALE (ecosystem, next rotation touch): this run's 26 website edits reshuffled the queue, so the stalest editable pages are now caper (2026-07-03), stabilis (2026-07-03, already 21KB and deep – low value), juicy-stake (2026-07-03, and juicystake.io 502s), blue-chick-nfts (2026-07-05), phoenix (2026-07-05), project-elysium (2026-07-06). xrd-domains and radix-namespace remain LOCKED_PAGES at the permanent top of pagesByStaleness – skip them.
• AUDIT HYGIENE (run 171, second time this rule has paid): the post-edit re-audit caught TWO broken internal links I had just introduced on /ecosystem/radixscan – /contents/tech/core-concepts/radix-gateway-api (the Gateway page is under core-protocols) and href="/", which the checker reports as an empty URL. Patched to v3.0.1 / v1.2.1 before the run closed. Final ecosystem audit: 141 pages / 681 external, 0 broken internal.
• policy subtree had ZERO in-content inbound links from all 345 pages before run 172 (sidebar-nav only) – fixed by linking all six policies from the maintenance-log intro (scripts/maintenance-log.mjs render(), local-only: /scripts/ is gitignored so this never deploys, it just renders into the DB page on each write). Still worth a reader-facing inbound link from the homepage or /contents in a future run.
• CHECK-LINKS BLIND SPOT: references-block URLs (items[].url) are never scanned – check-links only reads hrefs inside content HTML. Only 6 of 346 pages use references blocks (all six are /policy/*), 8 distinct URLs, all probed 200 on-domain with a browser UA in run 172. If references blocks spread beyond policy, teach check-links to scan them.
• BANNER BLOCKS ARE UNUSED: six maintenance-banner variants (stub / unsourced / outdated / promotional / cleanup / coi) ship in BlockRenderer and are now catalogued on /policy/verifiability, but ZERO of 346 pages carry one. Next sweeps should actually apply them where warranted – start with the ecosystem pages flipped to Closed / Dormant in runs 169 and 171, and with thin stubs.
• QUALITY GRADES: 340 of 346 pages carry no quality metadata; before run 172 the only five graded pages on the wiki were the policy pages, which had graded themselves Featured at ~1.1 KB each (now honest). Grade in batches by category as the rotation reaches each one – do not bulk-grade.
• FRESHNESS WINDOW: after run 172 stamped /policy/*, 35 of 346 pages have last_verified_at set and 0 pages are currently stale. Oldest COALESCE(last_verified_at, updated_at) is 2026-03-16, so the first automatic outdated banners fire around 2026-09-12. Run a proactive verification pass (scripts/mark-verified.mjs) on categories confirmed current before then, rather than letting banners appear on pages that are actually fine.
• hyperscale.rs/xian_proposal.pdf now 404s (asked about in hyperscale_rs TG, 31 Jul 14:06 UTC). No wiki page cites it – the hyperscale-rs page cites hyperscale.rs and /demo, both 200, and /proof.html 200s via a redirect to /proof. If the Xi'an proposal resurfaces at a new URL, cite it on /contents/tech/releases/radix-mainnet-xian.
• COSMETIC: the homepage infobox block (index 6) still carries seeded placeholder fields – title "Test", a blob image, rows [{Something: Something}]. InfoboxBlockView renders only block.blocks, so none of it reaches readers. Safe to strip whenever the homepage is next edited; not a reader-visible defect.
• run 173 (community): category link-CLEAN – 7 pages / 67 external, 0 broken internal, and the sole brokenExternal is the long-banked linkedin.com/in/dan-hughes 999 anti-bot FP. Zero new suspects, so no checking budget spent. Re-audited after the run's two edits: still clean.
• DONE (run 173, community staleness): /community/gilesmorris-me v1.2.1 -> 1.3.0 (2.7 -> 5.3 KB), the thinnest curated page in the category and stale since 07-22. Added a sourced 'Radix network economics model' section: Morris (a former accountant) published a 2026-2030 budget model for the network on 28 July 2026 (gilesmorris.me/my-blog/radix-midao-budgeting/) that sets the Foundation treasury to ZERO and asks whether XRD emissions alone clear the real USD cost of running and developing Radix, treating validators and holders as one stakeholder group; his answer after varying assumptions is 'probably, yes'. Published as a live Google Sheet + .xlsx, so the assumptions are re-runnable – that is what makes it citable rather than an opinion post. Also closed the dangling RAC framing (he was a NOMINEE; the five founding seats went to others) and added 6 internal links where there were 3 (radix-governance, radix-foundation, network-emissions, validator-nodes, validator-subsidy-sunset, RAC).
• DONE (run 173): /community/genki v1.1.1 -> 1.2.1. Its Rust-SDK section pinned the connector at connector-v0.2.0; the repo has tagged through connector-v0.2.5 (28 Jul 2026, GitHub releases API – v0.2.2/0.2.3/0.2.4 all shipped the same day). Also cross-linked the two sibling pages the profile never linked despite both covering the same work in depth: /developers/infrastructure/radixdlt-rust-sdk and /ecosystem/genkipool.
• SCRIPT LESSON (run 173): a replacement in sweep-173-community.mjs silently no-opped – the span /It is an early-stage effort[^.]*?rather than an official Radix release/ cannot cross the periods inside 'v0.2.0'. Worse, the script's success guard tested the MATCH CONDITION (/connector-v0.2.0/ present) rather than the post-replacement text, so it reported the edit applied and bumped the version. Fixed by a separate idempotent follow-up (scripts/sweep-173-genki-release-fix.mjs). Rule for future sweep scripts: assert on the AFTER text (or on before!==after), never on the condition that selected the block.
• CLOSED (run 173) – /community/cryptoants: THIRD consecutive failed sourcing attempt (web search this run; 555 Telegram messages + full RAC channel in run 163). It is the last default-template stub in the category ('This is your personal community page…', v1.0.1, 834 b, stale 2026-06-01) and its infobox already declares 'Placeholder / Not yet customized'. DECISION: KEEP, and stop re-litigating it each community rotation. It is a signup-created PERSONAL page belonging to a wallet holder who may still return to it – deleting someone's own member page is not an autonomous call for this routine, and the run-148 curation decision was about 38 EMPTY auto-generated shells, not this. If a human wants it gone it is a one-line delete; otherwise leave it.
• WATCH (RadixDevelopers, 2026-07-30/31): radixtalk.com/t/adding-radix-to-the-x402-payment-standard-and-the-caip-namespaces-registry/2321 – opened by Avaunt (a seated RAC member) 30 Jul 16:06 UTC. Proposes (1) registering Radix in the Chain Agnostic (CAIP) namespaces registry with blockchain/account/asset-ID profiles under radix:mainnet and radix:stokenet, and (2) adding Radix as a supported network in the x402 open HTTP payment standard so AI agents can pay for API access without accounts or cards. A draft spec is written; a NON-BINDING temperature check was announced but had NOT opened as of 31 Jul. If it advances, the page to update is /developers/ai-agents/ai-agents-and-x402 (already exists and already covers x402), plus a line on /ecosystem/radixtalk. Do not cite the forum thread as proof of adoption.
• OPPORTUNITY (run 173, hyperscale_rs 2026-07-31): hyperscale.rs has been REBUILT as a full explainer site and /xian_proposal.pdf now 404s (raised in-channel 14:06 UTC by a reader who could not find it). No wiki page links the PDF – our only two hyperscale.rs links (root + /demo) are both 200 – so nothing is broken, but the #3 traffic page /contents/tech/research/hyperscale-rs (37 visitors/30d) still cites only the bare root. The site now has ~16 named explainer pages worth citing individually (The System, The Journey, The Clock, The Census, The Overlap, The Generals, The Library, The Testament, The Kleroterion, The Governor, The Crash Lab, The Proof, The Asterisks) plus github.com/hyperscalers/hyperscale-rs docs/00-overview.md and docs/08-invariants.md. NEW DESIGN DETAIL from the same thread, not yet on the page and worth sourcing properly before use: there is no 'braided' cross-shard VOTING – each involved shard executes independently and exchanges proofs of execution, and the tx commits only when every involved shard's matching proof has landed; the beacon chain is a deliberately slow chain (one block per epoch) tracking validators, stake and the shard map, and never sees a transaction.
• TOOLING LIMIT (run 173): the outcome of Governance Proposals 1 and 2 (Stokenet operations funding; website migration) is NOT readable headlessly. consultation.mountain-top.live is a client-rendered SPA; its /config.js exposes VOTE_COLLECTOR_URL=https://api-consultation.mountain-top.live, but every plausible path there (/proposals, /api/v1/proposals, /proposal/1, …) returns 404, and the only templated base URL in the JS bundle is the Radix Connect relay. t.me/RadixAccountabilityCouncil has been silent since the 28 Jul vote-open announcement. To confirm the result a run needs a browser (Chrome MCP) or an in-channel/RadixTalk announcement – do not burn another run guessing API paths.
• BANKED TWEET HOOK (PRIORITY, run 173) – discovery-led, aimed squarely at XRD holders: someone in the community sat down and modelled whether the network can pay for itself with the Foundation treasury set to ZERO – three-year budget, emissions on one side, the real USD cost of running and developing Radix on the other, validators and holders treated as one stakeholder group. Answer: probably, yes – and he published the spreadsheet so you can change the assumptions yourself. Link /community/gilesmorris-me (or reply into @gilesmorris's own post about it – a genuine, accessible person surfaced by this very run, which satisfies the pull-someone-in bar). SKIPPED THIS RUN ONLY on the rate limit: @RadixWiki had already posted twice in the 07-31 UTC day (21:06 + 21:07) and the second was 2.4 h before this run finished. Fire it early in the next UTC day.
• run 174 (contents/history): standard audit CLEAN – 24 pages / 211 external, 0 broken internal; all 26 brokenExternal are banked FP classes (14x LinkedIn 999/429 profile links across the workshop/hackathon participant lists, 2x Medium 403 pillarproject, 1x orange-finance gitbook 403, 1x coingecko 403, 1x lsbu.ac.uk 403, 1x x.com/beemdvp 404). The one NEW suspect, http://t.me/ascarbek (status 0), was re-verified live at 200 – banked as an FP, t.me consistently returns 0 to the checker. No checking budget spent on the banked sets.
• run 174 FINDING – WRONG-EVENT LINK, checker-invisible: contents/history/dapp-in-a-day-workshop-4 (Brilliant On Chain, 4 Dec 2024) carried a REGISTRATION link to the Eventbrite listing for Brunel Hack 25, verified live as 12-13 July 2025, $10k prize festival, organised by Brunel Blockchain Society – a different event seven months later with its own wiki page. Copy-paste bleed between the two Brunel records; the URL resolves 200 so every link audit passed it. No registration page for the Dec-2024 event is known, so the line now records the organiser rather than a guess. LESSON for future audits: a 200 says the URL is alive, not that it is the right URL – spot-check that event/registration links on dated pages match the page's own date.
• run 174 FINDING – Null Island map embeds: contents/history/dapp-in-a-day-workshop-4 and brunel-hack-25 both carried an identical Google Maps iframe pinned at !1d5000!2d0!3d0! (lat 0 / lng 0, Gulf of Guinea) instead of the Uxbridge campus, while their data-url short link pointed at the real place. Renders without error, so structurally invisible. Both recentred on 51.5331 / -0.4729. SWEPT WIKI-WIDE afterwards: 6 pages carry data-map-embed, 0 remaining with !2d0!3d0 – this class is now fully closed, no follow-up needed.
• run 174: finished the series-linking pass run 164 began. #2, #4 and #7 all had a bare one-line lead and ZERO internal links; each now has a contextualised intro plus an 'In the series' section (links 0 -> 7/10/9), and brunel-hack-25 is linked in as the Brunel society's second Radix event (0 -> 3). The whole DApp In A Day series (#1-#5, #7) plus Brunel Hack 25 is now mutually cross-linked with #1 as the index. REMAINING in contents/history by staleness: radix-wiki-hackathon-1 (2026-07-07, 20.8 KB), validator-subsidy-sunset (2026-07-07, 5.1 KB), history-of-radix (2026-07-07, 9.7 KB) – history-of-radix is the cornerstone of the three and the natural next target.
• run 174 BANKED (structural, series-wide, needs a decision not a fix): every DApp In A Day / hackathon page in contents/history puts its infobox LAST and fills it with a map embed only – no facts table, against the wiki's infobox-first quality bar. This is consistent across all of them including the ones runs 164 and 173 refreshed, so it reads as a deliberate house pattern for event records rather than rot. If it should change, it is one pass over ~8 pages adding date/venue/host/mentors facts tables and reordering infobox-first – do it all at once or not at all, not page by page.
• run 174 BANKED from hyperscale_rs TG: the current design has NO braided voting between shards. Validators fold the beacon chain to derive which shards and nodes a transaction touches; those nodes exchange proofs of execution; the transaction commits once every involved shard holds every proof. Braiding was rejected as making shards co-dependent for liveness. Also a member noting the Cerberus whitepaper's 'global shard' as the precedent for the beacon chain. contents/tech/research/hyperscale-rs does not yet reflect this – good material for the next contents/tech rotation, but confirm with Fox's own messages rather than the surrounding replies before publishing.
• run 175 (ecosystem): standard audit CLEAN for the SIXTH consecutive ecosystem run – 141 pages / 681 external, 0 broken internal. All 88 brokenExternal fall in banked FP classes (61x web.archive.org status-0 Wayback timeouts, Medium/DefiLlama/projectnow.io/redbubble/unrealengine 403, LinkedIn 999, x.com+twitter.com checker-404s for ripsource/erik_fdn/EtherealDAO/cryptocoinfi, rly.fun and fred.stlouisfed status-0). The only two URLs not previously named – linkedin.com/in/joostdelaere123 and /in/lindseylim, both 999 – are the same LinkedIn anti-bot class. No checking budget spent re-verifying banked sets.
• run 175 FINDING – STATUS INVERSION on /ecosystem/juicy-stake, invisible to every link audit because all its links return 200. The page said the website and documentation "are no longer functional" and treated the project as plainly dormant. Both halves were wrong. The service MOVED domains: juicystake.io 502s, but juicystake.org is live, is the website recorded in the validator's OWN on-ledger metadata, and still advertises 19,726,201 XRD staked at 6.77% APY while inviting new delegation. On-ledger the opposite is true – validator_rdx1s0tkjt8mureaw3kkfl3900law5tnrlg3wte9f4vlaruxe4nfjzdam7 has registered=false at epoch 331088 (1 Aug 2026), which removes it from the active set, so the 12,610,520 XRD still delegated to it earns no emissions (~7.1M XRD below the figure the site shows). Fee 2%; stake-unit resource_rdx1t5d8gv6fmwv40sreuypwrwh2mmknr4vf7fdtyrmfr7upjmschwczn0 and claim NFT still live, so stake can be withdrawn normally. Page v2.1.0 -> 2.2.0 with a dated Status section citing docs.radixdlt.com/docs/validator + the learn.radixdlt.com emissions article, plus an `outdated` banner. LESSON: a project's on-ledger validator/resource state is a status source the checker cannot reach – for staking and token pages, read the ledger, not just the domain.
• run 175 CORRECTION to a standing assumption, worth several runs of wasted work. "Page has no infobox block = infobox-first violation" is FALSE for ecosystem pages. InfoboxSidebar (src/components/BlockRenderer.tsx:253) calls buildMetadataBlock(metadata, tagPath) and renders a facts <table> synthesised from page.metadata for any tag whose getMetadataKeys() returns keys, plus an AssetPriceBlock for every resource_address key – with or without an infobox block in content. 38 of 141 ecosystem pages carry no infobox block (caper, stabilis, maya-protocol, dogecube, juicy-stake, …) and every one of them still renders a facts panel. Runs 117/123/125/130/146/158 spent their staleness slice prepending facts infoboxes partly on this basis. Do NOT keep doing that: add an infobox block only when the page needs facts the metadata schema cannot hold (on-ledger token detail, a map, an embed). Separately, 9 pages have an infobox with no <table> and 16 have the infobox not first – both harmless, since the sidebar filters infobox blocks out of the main flow and renders them last regardless of position.
• run 175 – CLOSES the run-173 bank "BANNER BLOCKS ARE UNUSED (0 of 346 pages)". Wrote a first-person / launch-copy scan over the whole ecosystem subtree (16 markers: "we believe", "our mission", "join us", "we offer", "you receive", …); exactly 4 of 141 pages trip 2 or more. Three are verbatim project marketing and got a `promotional` banner: blue-chick-nfts v1.2.0 ("We believe that NFTs & Gaming are the perfect play", "Juicy, right?"), unisci v2.1.0 ("We specialize in creating handmade NFTs", "So what are you waiting for? Come join us"), unix v2.3.0 ("UniX wasn't just a platform; it was a movement", second person throughout). hug was deliberately NOT bannered – its first-person strings sit inside a block already headed "Roadmap (historical)" with a neutral editorial caveat, so the page is already doing the right thing. NEXT: run the same scan over contents/*, developers and community (it is ~20 lines of SQL + regex, cheap); and consider `unsourced` where a page cites nothing, `stub` for thin ACTIVE pages only (a short page about a closed project is not a stub, it is finished).
• STILL STALE (ecosystem, next rotation touch): after run 175 touched juicy-stake, blue-chick-nfts, unisci and unix, the stalest editable pages are caper (2026-07-03, repeatedly deferred), stabilis (2026-07-03 – 21KB, deep, and its metadata already renders both a facts panel and a live STAB asset widget, so genuinely low value), project-elysium (2026-07-06), soulstore (2026-07-07), radix-blue-balls (2026-07-07), doubt-it (2026-07-07). xrd-domains and radix-namespace remain LOCKED_PAGES at the permanent top of pagesByStaleness – skip them, that is not neglect.
• HOOK (banked, not yet tweeted): CAIP/x402 Temperature Check 6 is open for XRD-weighted voting at consultation.mountain-top.live/tc/6 and needs quorum, with the submission drafts public for technical review (AVaunt-consulting/namespaces/radix; AVaunt-consulting/x402 scheme_exact_radix.md) and a three-PR plan (spec, TypeScript reference impl, extra SDK). NOT tweeted in run 176 because @RadixWiki already posted the CAIP registry angle 31 Jul 21:06 (21L/142I) and @radixdlt posted the proposal itself the same day to heavy ecosystem RT. The stronger, non-duplicative beat is LATER: when the PRs are actually filed against ChainAgnostic/namespaces and x402, or when the vote result lands. Watch both repos.
• BLOG STRUCTURE: the three July Week-in-Review recaps (2026-07-12/-07-19/-07-26) had no series navigation at all and the two March ones pointed at a hardcoded "latest recap" that goes stale every week – fixed in run 176 by chaining all five chronologically and replacing the latest-pointer with the stable /blog index. THE radix-week-in-review ROUTINE MUST APPEND TO THIS CHAIN when it publishes a new recap: add "← Previous: <range>" to the new page and "Next: <range> →" to the one before it, both plus "All recaps" -> /blog. Otherwise each new recap re-orphans itself and the chain stops at 2026-07-26.
• BLOG: /blog/week-in-review-2026-07-19 and /blog/week-in-review-2026-07-26 lack the standard RADIX.wiki footer block (Contents | Ecosystem | Leaderboard) that every other blog page carries – the two March recaps and 2026-07-12 have it. Cosmetic, deliberately left out of run 176 to keep the edit surgical; fold into the next blog rotation.
• PRIORITY TWEET HOOK (run 177, discovery-grade, exclusive): hyperscale-rs is NOT adapting the Radix Engine – flightofthefox confirmed on 1 Aug 2026 that a purpose-built VM is underway (t.me/hyperscale_rs/10334, "yeah, it's underway"), because "the sharding adjustments are so many that it'd require touching everything. at some point it becomes easier to start with intention than to retrofit" (10336), and the RE for sharding is "not in the same zip code as the ballpark" (10332). Full April rationale at 6018 (data dependencies, "too loose", preview cannot scale). Written up at contents/tech/research/hyperscale-rs v4.8.0. NOT tweeted this run: the 08-01 UTC day already carried two @RadixWiki posts (07:16 sweep-175 Juicy Stake, 14:20 radixwiki-tweet) and the 14:20 post was ALSO hyperscale-rs, so a third would bunch one subject four hours apart. LEAD WITH THIS next run. Before posting, re-check whether the Scrypto question (t.me/hyperscale_rs/10338, "So will scrypto also be scrapped?", unanswered at 18:20 UTC 08-01) has been answered – an answer either way makes the post materially stronger.
• METHOD BANKED (run 177): exchange listings must be verified against each venue's OWN public market API, never against its web page – five of the nine CEXes on how-to-buy-xrd had withdrawn XRD while their listing pages still loaded, and the single URL the link checker caught (AscendEX 404) was the least informative of the five. Endpoints that answered cleanly: bitfinex api-pub /v2/conf/pub:list:pair:exchange (plus pub:map:currency:label), bitget /api/v2/spot/market/tickers (error 40309, "The symbol has been removed"), bitmart /spot/quotation/v3/ticker and /spot/v1/symbols, bybit /v5/market/instruments-info?category=spot, mexc /api/v3/ticker/24hr, coinex /v2/spot/ticker, gateio /api/v4/spot/tickers, kucoin /api/v1/market/orderbook/level1, bingx /openApi/spot/v1/ticker/24hr, bitpanda api.bitpanda.com/v1/ticker (BROKERAGE – absent from CoinGecko yet genuinely live in 12 fiat currencies; never strip a venue merely because an index omits it).
• NEW FP CLASS (run 177): www.coingecko.com returns 403 "Challenge Verification" (Cloudflare) to automated requests – alive for humans, do NOT strip. Also re-confirmed alive-behind-403: gate.io and mexc.com listing pages (first banked run 153). DigiFinex does have an xrd_usdt market but quotes ~0.005141 against a real ~0.00096 (~5.4x) and CoinGecko flags it is_anomaly, so it was deliberately NOT added to how-to-buy-xrd.
• STALE UPSTREAM SOURCE (run 177): radixdlt.com/token cannot be treated as a canonical venue index – it still links AscendEX, Bitfinex, Bitget, BitMart and Bybit (none of which has an XRD market), still links the hijacked instabridge.io, and carries a caviarnine.com/trade?crosschain=true that 404s. how-to-buy-xrd now says so explicitly. CHECK where else the wiki defers to that page as authoritative.
• WATCH (run 177): the squatted instabridge.io redirect target ROTATES – www.homesofjoy.org on 30 Jul 2026, rescuedandco.com (Indonesian slot-gambling) on 1 Aug 2026. Recorded on /ecosystem/instabridge v2.2.1. The other retired-project domains found squatted in run 171 may rotate the same way; re-probe destinations rather than trusting the banked string at the next ecosystem rotation.
• SPR.SO IMAGE DEATH – 10 pages left (run 177 cleared contents/resources entirely: brand-assets in run 153, radix-visuals now). Remaining: 7 blog essays (a-year-in-review-2023, building-radixs-developer-pipeline-nine-events-and-counting, dappinaday-stage-1-complete, money-wealth-volcanos, radix-is-what-web3-noobs-think-they-bought, rgh2024-debrief, ten-10x-moments-coming-to-web3) plus contents/tech/core-concepts/shard-groups, contents/tech/core-protocols/radix-wallet, contents/tech/research/emunie. On those the prose survives and the images were decoration, so stripping the dead img tags is a clean bounded job for the blog and contents/tech rotations. Find with: content::text LIKE '%images.spr.so/cdn-cgi%'.
• GAP (run 177): RadQuest has no wiki page despite being the Radix learn-to-earn onboarding campaign; its radquest.io apex now redirects to www.radixdlt.com and www.radquest.io 403s behind Cloudflare, so establish whether it is retired or merely rehosted before writing anything. Referenced from contents/resources/radix-visuals.
• RE-RUN THE TELEGRAM PROBE each ecosystem rotation. The squat campaign is live and adding handles (Radixnode taken 2026-07-30, a month after the 29 Jun batch of seven). Method: pull every t.me handle from ecosystem content+metadata, fetch https://t.me/s/<handle>, and flag any channel with ~1 subscriber whose posts contain "Channel created" + a Collab.Land token gate. 51 of the 62 handles are groups with no public preview, so they cannot be cleared this way – if a cheap check for those appears, use it. Also worth extending the probe beyond /ecosystem to /community and /contents/history.
• The same recycling risk applies to project WEBSITES, not just handles (Instabridge, run 177). Consider a periodic domain-integrity probe over ecosystem infobox websites: flag any that now redirect off-domain or whose registration looks recent relative to the project's recorded closure.
• PHOENIX NODE (validator_rdx1sde3jp4g6ldh2mg4af0v0sq3c8en4agk3p7p63zcv58l5h05sej4kh) is unregistered with 7,807,033 XRD still delegated – the second such find in two runs after Juicy Stake (12,610,520 XRD, run 175). Worth a systematic pass: pull the full validator list, intersect with ecosystem/community pages, and flag every page whose validator is unregistered while still holding stake. That is a recurring, high-value, XRD-holder-facing class no link checker can see.
• Scrypto's position under Xi'an is still unanswered (asked at t.me/hyperscale_rs/10338, 1 Aug 18:12 UTC, no reply). Now that option B is confirmed, this is the single biggest open question for Radix builders. Watch the channel and update /contents/tech/research/hyperscale-rs the moment it is answered – that is a PRIORITY tweet hook.
• hyperscale.rs/xian_proposal.pdf returns 404 (the domain is now the CI-deployed demo). The wiki does not cite it, but the Xi'an RFC on radixtalk (t/rfc-xian-delivering-hyperscale-for-radix/2280) does resolve and is the citable source. If Fox moves the PDF to an assets subdomain, add it to the hyperscale-rs external links.
• STAB is a fully-documented protocol with a 2,665.86-token loan book. Several other DeFi pages in /ecosystem likely carry the same gap between documented design and actual on-ledger scale. Next ecosystem rotation, read total supply / TVL for the DeFi entries marked Active and record scale where the page implies more than the ledger shows.
• RE-MEASURE TRAFFIC (run 179): the 25 Jul - 1 Aug window in Plausible is a measurement hole (CSP blocked the beacon; fixed by ac28a02 on 1 Aug, verified live at 202). Do NOT compare any page's before/after visitors across that boundary or conclude an edit failed to land. From ~3 Aug the daily numbers are trustworthy again – re-baseline top_pages then, and expect the 30d totals to keep falling for four more weeks as the good pre-25-Jul days roll off the window.
• WATCH (ideas run 179): Governance Proposals 1 (Stokenet operations, Daffy) and 2 (Radix website to Cloudflare, Timan) opened 28 Jul for binding XRD-weighted voting; the RAC channel has been silent since and the outcome is still not readable headlessly (see the run-173 TOOLING LIMIT). When a result is announced, update /ideas/dao-website-redesign (status 🟡 Approved -> 🟢 Done or back to 🔴 Discussion) and the Latest infobox row, and consider whether the Stokenet funding result belongs on /ideas/dao-operating-budgets as the DAO's first funded core function.
• IDEAS BOARD, remaining drift (run 179 touched 3 of 29 cards): the other 26 dao-* cards are still at v1.0.0 / 2026-07-11 seed state with no dated status. Highest-value next: dao-elect-permanent-rac (is the Permanent RAC elected yet?), dao-incorporate-duna-llc + dao-foundation-ip-asset-transfer (Foundation is in maintenance mode since 28 Apr – has anything transferred?), dao-vote-delegation-jazzer-bot (delegation is the named backlog of the now-shipped Consultation v2), and dao-proposal-voting-framework (the RFC -> TC -> Proposal pipeline it describes has now run end-to-end twice, which is evidence the framework is in use). Take 2-4 per ideas rotation, not all of them.
• NEW CARD CANDIDATE (run 179): there is no dao-* card for the CAIP namespaces + x402 registry submission, now at TC 6 with a three-PR plan (spec, TypeScript reference impl, extra SDK) championed by Avaunt. It is Dev/BizDev WG work with a live governance vote behind it. Create the card when the PRs are filed against ChainAgnostic/namespaces and coinbase/x402, so the card opens with a verifiable artifact rather than an intention. Page /developers/ai-agents/ai-agents-and-x402 already carries the technical side.
• run 180 (policy): the policy subtree audits CLEAN - 6 pages, 1 external link checked, 0 broken external, 0 broken internal. All six were rewritten in run 172 (31 Jul) and carry honest quality grades, so there was nothing to fix. The category's remaining value is in APPLYING the policies across the wiki rather than editing them, which is what this run did (one verifiability correction, two stub deepenings, three stub banners). Treat future `policy` slots the same way.
• PRIMARY-SOURCE DRIFT ON THE FLAGSHIP PAGE: /contents/tech/research/hyperscale-rs - the wiki's top non-hub traffic page - carried two claims its own primary source contradicts. Cross-shard atomicity was described as two-phase commit with a coordinator sending prepare messages; docs/04-atomic-commitment.md opens by rejecting exactly that comparison (no coordinator, no outcome votes, participants are BFT committees). And provisioning proofs were attributed to verkle trees in TWO separate places (the second was missed on the first pass and needed a v4.10.1 follow-up); 'verkle' appears ZERO times across all nine design documents - state is one binary Jellyfish Merkle Tree over a 256-bit keyspace hashed with Blake3. Root cause: the page has been extended ~15 times from Telegram signal without anyone re-reading docs/*.md end to end. ACTION: schedule a full reconciliation of the page against all nine design documents - other early claims may be equally stale.
• STUB BANNERS: 3 applied this run (application-layer, vm-layer, kernel-layer), so 7 of 347 pages now carry one, up from 4. The homepage 'Engine Layers' grid links six pages: system-layer was deepened this run, three are now flagged, and vamos-database + radix-engine were not examined. Next: check vamos-database, then work the thin core-concepts tier (~20 pages at 850-1000 chars of prose) - deepen where there is source material, banner where there is not.
• hyperscale.rs/xian_proposal.pdf now returns 404 (site root 200). Markus asked about it in-channel on 31 Jul (t.me/hyperscale_rs/10303) and got no answer. Only the maintenance-log page links it; the hyperscale-rs RFC section cites radixtalk.com/t/rfc-xian-delivering-hyperscale-for-radix/2280 instead, so no reader-facing link is broken. Re-check whether it comes back or moves.
• TC 6 (CAIP namespaces + x402) submission material is now PUBLIC and reviewable: github.com/AVaunt-consulting/namespaces/tree/main/radix (README, caip2.md, caip10.md, caip19.md) and the x402 fork's specs/schemes/exact/{scheme_exact.md,scheme_exact_radix.md}, aligned with upstream. Three PRs planned - spec addition, a reference implementation (TypeScript proposed), and an SDK implementation - and a diagram was requested for the Protocol Flow section. This is exactly the detail the 1 Aug feedback said outranks a third announcement of the event. Add to the /ideas consultation card and post once the PRs are actually filed.
• Thin-page tier, unchanged by this run and ordered by prose length: pillar-unconference 549, cryptoants 586, vandyill 827, transaction-tracker 837, radix-pools 863, application-layer 868, vm-layer 873, radix-economic-model 874, transaction-processor 877, kernel-layer 891, radix-gateway-api 891, locker-blueprint 901, components 912, consensus-manager 920, worktop 938, role-assignment-module 949, metadata-module 949, validator-nodes 951, badges 967, brand-assets 977. radix-core-api and system-layer left this tier in run 180.
• CLEARED (run 181): the hyperscale-rs full reconciliation banked by run 180 is DONE – /contents/tech/research/hyperscale-rs v4.10.1 -> 5.0.1, 18 exact-match edits checked against all nine design documents. Eight further contradictions were found beyond the two run 180 caught in passing: 'one-round finality' stated twice (a QC is not a commit – commit needs a round-contiguous two-chain, INV-SHARD-4); the Transaction Flow section still carrying the coordinator-based 2PC description corrected three sections above it in v4.10.0; the `execution` crate described as 2PC coordination; '28 crates' stated three times (actual 32); '20% of each shard per day' shuffling (actual: one seat per shard per interval, make-before-break, FIFO victim); the shuffling security claim stated in the opposite direction to 05 §1.2/§2; 'hands its in-flight work to its two child shards' (inheritance was explicitly REJECTED – settled-set fence instead); and fee-driven split triggers (byte-threshold only). LESSON GENERALISED: a page extended N times from chat signal drifts from its primary source in ways no link audit can see. Schedule the same treatment for any other page with a large documented primary source and a long Telegram-driven edit history.
• hyperscale-rs explainers/ directory (15 HTML pages: archive, asterisks, census, clock, crashlab, generals, governor, journey, kleroterion, library, overlap, proof, testament, triage, index) was NOT examined in run 181's reconciliation, which covered docs/ and specs/ only. These appear to be the narrative explainer layer behind hyperscale.rs. Read them next time the page is touched – they may carry framing worth citing, and they are a candidate source for an infographic.
• PUBLISHED RESIDUAL WORTH TRACKING: hyperscale-rs specs/README records finding G-1 as adjudicated and open – in the f+1..2f recovery band the certified re-bind's one-window tolerance is calibrated for an adversarial minority, but a retained committee there is beyond f, so its corrupt majority can drag the QC weighted-time mean into the suffix band and escape the re-bind, letting a folded replica admit an orphan two-chain commit past the halted tip. Now recorded on the wiki page. Watch for its resolution and update; it is the clearest example of the project documenting a weakness against itself.
• NEW PAGE CANDIDATE from run 181: the formal-verification layer (9 Quint models, Apalache, the broken-twin discipline, transitions transcribed from code rather than prose, the 75-property register, SEC-1's statistical analysis) is currently two paragraphs inside the hyperscale-rs page. It is arguably its own article and is the strongest single differentiator the project has – the 1 Aug @RadixWiki post on it was the second-best performer of the window (26L/212I). Consider /contents/tech/research/hyperscale-formal-verification with the hyperscale-rs page linking to it.
• CHECKER BLIND SPOT, now measured (run 182): scripts/check-links.mjs resolves <a href> anchors only, so every <iframe> and every <img> on the wiki is invisible to it – and an iframe src returns 200 whether or not the thing behind it still plays. 122 iframes wiki-wide (85 YouTube / 76 unique video IDs, 12 platform.twitter.com tweet embeds, 5 google-maps embeds, 5 radixrolodex decks, 1 quack.space widget, 1 google-slides deck, 1 sociablekit shopify widget, 1 notion x-embed, 1 vandyill.github.io). All 76 YouTube IDs were checked this run through youtube.com/oembed (200 public+embeddable, 404 deleted, 403 restricted) and three were dead – see the run summary. RECOMMENDED DURABLE FIX: teach check-links to extract iframe/img srcs, and for youtube-nocookie.com/embed/<id> and youtube.com/embed/<id> resolve https://www.youtube.com/oembed?url=...&format=json instead of the embed URL. Everything else can be HEAD-checked as normal. NOT implemented this run (app-repo code change, kept out of a bounded sweep).
• UNVERIFIED EMBEDS (run 182): six JS-rendered widgets returned a 200 shell whose actual content loads client-side, so their liveness is NOT established – 5x radixrolodex.com/embed.html (deck-ids l22Bmkh70rxJs6SyU0ut on radix-blue-balls, D7yPu25MGR1GkFrGoBiX on astrolescent, vf5trPBMoSQqJq4SYBlP on foton, ixDFx5ax0ZPvOxSPktBE on ociswap, stable-id quack-space-landing-page on radix-rolodex + quackspace) and widgets.sociablekit.com/shopify-store/iframe/25653346 on doubt-it. The rolodex shell is 630 bytes of module loader; the sociablekit shell renders only the words "Shopify Store". radixrolodex.com, doubtit.digital and doubtitgame.com are all live 200, so the hosts are fine – it is the deck/store IDs that cannot be confirmed headlessly. Needs one browser render; the Browser pane timed out at 300s in this run. Three of the affected pages (doubt-it, radix-rolodex, radix-blue-balls) are 2.0-2.3 KB and are MOSTLY the widget, so a dead deck would empty them.
• Ecosystem staleness, unchanged by run 182 and ordered after the two LOCKED_PAGES (xrd-domains, radix-namespace, skip them): caper (2026-07-03, 16 KB and already deep), soulstore (2026-07-07 – note its metadata.team field holds raw HTML, <a href="https://x.com/ripsource">rippy.xrd</a>, rather than a plain value, which is a data-shape defect worth checking across the subtree), radix-rolodex / radix-blue-balls / doubt-it (all 2026-07-07, all thin widget-shells – see the unverified-embeds item, they should be refreshed together once the decks are confirmed), radix-kingdoms (2026-07-08), xseed (2026-07-08), ascent (2026-07-08), radixstake (2026-07-10). project-elysium left this queue in run 182.
• CLEARED (run 183): backlog item 277 – 'Scrypto's position under Xi'an is still unanswered' – is now partly answered and published. t.me/hyperscale_rs/10346 (2 Aug 12:12 UTC) puts dApp migration at "best case scenario - contracts will just need a recompile. worst case scenario - there'll be some automatic transpiler devs can use to upgrade source code". Both ends describe migrating source, not rewriting it. What is STILL unanswered is whether Scrypto survives as a named language – /10338 drew no direct reply, and no mapping from today's blueprint model to the new VM has been published. Keep watching.
• STRUCTURAL GAP CLOSED, PARTIALLY (run 183): the developers subtree teaches Scrypto against the Radix Engine across 31 pages and carried ZERO forward signal that Xi'an is expected to replace that engine – a builder starting the tutorial series learned nothing about it. Fixed at the two entry points (scrypto/01-fundamentals v1.4.0, radix-developer-resources v5.6.0). The other 29 pages still read as if the Radix Engine is permanent. Do NOT bolt the notice onto every page; the two entry points plus the hyperscale-rs link is the right dose. Revisit only if the VM's language story is actually decided, at which point transactions/01-manifest-language and getting-started/03-deploying are the next two that would materially change.
• RATE-LIMIT DATA POINT (run 183): @RadixWiki posted FOUR times between 11:12 and 14:25 UTC on 2 Aug, and the 14:25 post is the exact hook this run's edit was built on (dApp migration under the new execution layer). Engagement across those four is L12/L2/L1/L1 against a 21-like median – the feed is saturated on one subject. The sweep tweet was skipped for duplication, not for thinness: the finding was strong, it had simply already been posted by another routine 45 minutes earlier. Worth a cross-routine check that the wiki sweep and the standalone posting routine are not racing to publish the same discovery.
• CLEARED (run 184): the run-183 bank "check whether any wiki page still says Hyperscale/Xi'an state is pre-sharded or uses global shard as a synonym for the beacon chain". Grepped every page for pre-shard/global shard/shardgroup/2^256. No page uses "global shard" or "shardgroup" at all. The reconciliation defect was elsewhere and larger: /contents/tech/core-concepts/sharding v1.2.2 -> 2.0.0 carried TWO mutually exclusive shard counts. Its Technical Fundamentals section said Radix "launches with a maximum number of shards (2^64 or approximately 18.4 quintillion)"; its Sharding in Radix section said "a fixed number of 2^256 shards". A factor of 2^192, two sections apart, on the cornerstone concept page. The smaller figure is TEMPO's: it comes from radixdlt.com/blog/sharding-in-radix (2 Aug 2018) and /blog/test-method-part1 (12 Jun 2019), both pre-Cerberus, and the wiki's own tempo-consensus-mechanism page states 18.4 quintillion correctly as Tempo's. The current figure is 2^256, per radixdlt.com/articles-learn/what-is-sharding. Both are now attributed to the design they belong to.
• run 184 (contents/tech): standard audit – 85 pages / 421 external / 40 embeds, 0 broken internal, 0 non-standard images. All 25 brokenExternal are the fully-banked contents/tech FP set (SSRN x3, researchgate, medium x4, coinvise, aibc, mirror, theblock, coinbase, forbes, bitcointalk x3, cepr, imf, axieinfinity, stanford-jblp, assets.super.so x3, linkedin 999) with ZERO new suspects, so no checking budget was spent re-verifying them. The en.wikipedia 429s banked at run 168 no longer fire. Post-edit re-audit: 85 pages / 422 external / 39 embeds, 0 broken internal, 0 broken embeds, 25 brokenExternal, no new flags introduced by the four edits.
• BROKEN EMBED FIXED (run 184): /contents/tech/research/cassandra v1.2.1 -> 1.2.2 carried a dead embed.notion.co/api/iframe iframe (HTTP 404) wrapping x.com/fuserleer/status/1495901628439879690 – a Notion embed proxy that has stopped serving, rendering as an empty box mid-Background-section. It was the ONLY brokenEmbed in the entire contents/tech audit, and no anchor-only link checker would ever have seen it. The tweet text could not be recovered (WebFetch is blocked from web.archive.org and x.com 402s), so the embed was removed rather than replaced with an unverifiable description. Third category in a row where the embed audit, not the anchor audit, found the real defect.
• CITATION MISMATCH (run 184): /contents/tech/core-concepts/shard-groups v1.5.0 -> 1.5.1 sourced its lede sentence about the 2^256 shardspace to a #:~:text= fragment of the 12 Jun 2019 test-method blog reading "the network has a fixed shard space of 18.4 quintillion shards" – a citation that contradicts the sentence it supports. Repointed to Dan Hughes on dynamic shard-group coverage (youtu.be/FZWT3j9XHMI), the source already used for the same claim on the sharding page. LESSON: a link checker resolves the URL and stops. A live 200 tells you nothing about whether the page behind it says what the sentence claims.
• BRAIDING STATED AS RUNNING ARCHITECTURE (run 184): two contents/tech pages still described Cerberus braiding in the present tense as something the Radix network does – /contents/tech/core-concepts/sharding ("This unique braided architecture ensures that Radix can securely scale...") and /contents/tech/core-concepts/rollups v1.0.0 -> 1.1.0 ("its Cerberus consensus braids validation across shards"). The cerberus-consensus-protocol page has carried the correction since run 183 (braiding has never run in production; Babylon runs Cerberus unsharded = original HotStuff; the Xi'an candidate uses a HotStuff-2 two-chain commit with execution asynchronous to consensus). Both pages now say so and link the Cerberus page. PATTERN worth generalising: when a correction lands on the main article, grep the concept pages that summarise it – the summary is where the superseded claim survives.
• STILL STALE (contents/tech, next rotation touch): run 184 cleared none of the staleness queue – it spent its budget on the shard-space reconciliation instead. Unchanged and ordered: transaction-manifests (2026-03-16) and radix-economic-model (2026-03-16, also in the thin tier at 874 chars of prose), then the 2026-04-05 operations pages (improvement-log, control-chart), then the 2026-05-03 core-concepts block (consensus-manager, locker-blueprint, transaction-tracker, resources, metadata-module). transaction-manifests is the strongest candidate: it is the stalest page in the category and run 167 found two Subintents anchors elsewhere on the wiki wrongly pointed at it.
• OPEN QUESTION unchanged (run 184): Scrypto's position under Xi'an is still unanswered – asked at t.me/hyperscale_rs/10338 on 1 Aug, no reply through 2 Aug 22:13 UTC. Still the single biggest open question for Radix builders and still a PRIORITY tweet hook the moment it is answered.
• CHECKER BLIND SPOT #2, now measured (run 185): scripts/check-links.mjs calls extractLinks(row.content) and NEVER reads page.metadata, so every URL that lives only in a metadata field has gone unprobed for 185 runs. Measured wiki-wide: 144 pages carry a URL in metadata, 280 metadata URL instances, and 98 distinct URLs appear in metadata and nowhere in content. Probed all 98 with a browser UA following redirects: 90 return 200 and EIGHT are dead – x.com/TheCadorXRD (phoenix#x), x.com/astaborter (astrolescent#x), x.com/Impahla_dao (impahla#x), radix.wiki/talent-pool/libertant (radix-wiki#team), github.com/z3us-dapps/z3us (z3us#github), x.com/HardMoneyProjec (the-hard-money-project#x), x.com/TroveEco (trove#x), x.com/topradixnode (topradixnode#x). All eight are fixed. These render as live-looking rows in the infobox facts table, so a reader sees them and a link audit does not. FLAG FOR A HUMAN: folding metadata into the checker is a small change at the extractLinks call site (scripts/check-links.mjs:202) and would make this class self-auditing; until it lands, re-probe metadata URLs by hand each ecosystem rotation.
• A BANKED FALSE-POSITIVE CLASS WAS ITSELF FALSE (run 185): every run since ~122 has filed x.com and twitter.com 404s as anti-bot false positives ("x.com-404 FP policy"), alongside the genuine Medium/LinkedIn/DefiLlama 403 blocks. That is wrong. Probed all 135 x.com/twitter.com URLs in the ecosystem subtree with a browser UA following redirects: 131 return 200 and exactly 4 return 404. x.com does not blanket-404 automated requests – a 404 there is a true signal, and the class had been suppressing four genuinely dead citations across nine ecosystem audits (soulstore x.com/ripsource, fidenaro twitter.com/erik_fdn, alphadex twitter.com/cryptocoinfi/status/1678146989303771137, etherealdao twitter.com/EtherealDAO/status/1665509659824758784 – the last two also had dead ACCOUNTS, not just deleted tweets). All four fixed. NEXT: the banked FP lists for contents/tech and developers name x.com/twitter.com 404s too – re-probe them the same way at those rotations before trusting the bank again.
• UNVERIFIED HANDLE CANDIDATES (run 185): two metadata.x fields were REMOVED rather than repointed because no primary source confirms the live candidate. x.com/phoenix_xrd is live 200 and plausibly Phoenix’s project account, but phoenixradix.com links only individual team handles (CorsicanEmperor, IupTutu, RequinTyrex, and the now-deleted TheCadorXRD) and no project account. x.com/impahla is live 200 but impahla.io renders client-side and exposes no social links, and Impahla is a closed project. Restore either field only against a primary source. Also of note: phoenixradix.com itself still links the deleted x.com/TheCadorXRD.
• CLEARED (run 185): the run-182 metadata.team data-shape bank. Six of 27 ecosystem team values carried raw HTML or &nbsp; where the other 21 carry a plain name, and formatMetadataValue() (src/components/BlockRenderer.tsx) injects the value as HTML – so ascent’s literal "<br>" rendered an empty Team row, ideosphere’s "Name:&nbsp;URL<br>Name:&nbsp;URL" rendered both handles as unclickable plain text (the &nbsp; defeats the renderer’s URL test), and soulstore/radix-review/radix-wiki carried hand-written <a> elements missing the target/rel/class the renderer adds. Normalised: ascent team removed, quackspace VandyILL, ideosphere "Rei Jarram, Mariana Oka", radix-wiki "Bayezien", radix-review "x.com/felixxrd" and soulstore "github.com/ripsource" using the bare-URL form the renderer linkifies properly (t.me/bromerxrd on hydraswap is the precedent). No other ecosystem metadata field carries markup.
• WATCH, unchanged (run 185): instabridge.io still redirects to rescuedandco.com, the same squatted target recorded on 1 Aug – it did NOT rotate this time (it had rotated from www.homesofjoy.org on 30 Jul). Keep re-probing destinations rather than trusting the banked string.
• Ecosystem staleness after run 185, ordered (skip the two LOCKED_PAGES xrd-domains + radix-namespace): the 16 pages touched this run left the queue, so the head is now radix-rolodex / radix-blue-balls / doubt-it (all 2026-07-07, thin widget-shells that should be refreshed together once the radixrolodex.com deck IDs are confirmed – see the unverified-embeds item), radix-kingdoms (2026-07-08), xseed (2026-07-08), radixstake (2026-07-10), world-cup-badge-arena / ideomaker / hermes-protocol / miow (all 2026-07-11). NOTE on the freshness stamps written this run: last_verified_at was set on all 16 edited pages, and it certifies a LINK AND METADATA verification pass, not a full re-reading of each page’s prose.
• CLOSED (run 186) – the run-176 banked "systematic validator-registration pass". Method, now repeatable: regex every validator_rdx address out of pages.content::text AND pages.metadata::text (13 distinct across 348 pages), POST them all to mainnet /state/entity/details, read details.state.is_registered, then radixscan radix_get_validator for total_stake_xrd. FOUR are unregistered while still holding delegated stake: TopRadixNode 25,392,103 XRD (fee now effectively 25%, raw on-ledger 1.99%), Juicy Stake 12,610,520, PHOENIX NODE 7,807,033, RadixUID/'Lauta Army' 1,345,074 – about 47.15M XRD total sitting outside the active set earning no emissions. All four pages already SAID unregistered; only phoenix and juicy-stake carried the number, which is the fact a delegator actually needs. Fixed topradixnode (v2.2.1->2.3.0) and radixuid (v3.0.1->3.1.0). Re-run this pass each ecosystem rotation – registration flags flip silently and no link checker can see them. Script: scripts/sweep-186-stranded-stake.mjs.
• run 186 (community): audit CLEAN for the eighth consecutive community rotation – 7 pages / 67 external / 4 embeds, 0 broken internal, 0 broken embeds, 0 non-standard images, sole flag the banked linkedin.com/in/dan-hughes 999 anti-bot FP. Post-edit re-audit 7 pages / 74 external, same single FP. Staleness head is cryptoants (2026-06-01), which is the run-173 KEEP-and-stop-relitigating decision (signup-created personal page, third failed sourcing attempt) – do not re-open it. Next actionable head after this run: kangaderoo (stamped verified this run, all 3 external links 200 and the RRC-404 + community-scrypto-examples facts re-checked), then daffy (2026-07-28), gilesmorris-me and genki (both 2026-07-31).
• BANKED TWEET HOOK (PRIORITY, run 186) – hard-number discovery, the shape this account measurably responds to, and durable (a benchmark does not go stale in a day). A community builder wrote a BN254 Groth16 verifier for Radix and benchmarked it against Radix's own cost model: a single proof verification costs ~149-263 MILLION cost units against a 100M per-transaction ceiling. Groth16 is the compression target RISC Zero and Succinct SP1 zkVMs both output, so the finding is that pure-WASM zkVM proof verification cannot run inside a Radix transaction as the engine stands – native pairing operations are a prerequisite, not an optimisation. Correct, fits memory and binary size; it is purely a compute wall. Source github.com/quackstra/groth16-scrypto (BENCHMARK.md + recon/RECON.md), now recorded on /community/vandyill. SKIPPED THIS RUN ONLY on the feed rule: @RadixWiki had already posted twice today, the second at 06:11 UTC, ~1h before this run.
• run 186 – /developers/ai-agents/ai-agents-and-x402 does not mention quackstra/x402-radix, an independent TypeScript implementation (client/server/facilitator/core packages) written in March 2026 against Stefan Telea's scheme_exact_radix gist – the SAME scheme AVaunt is now preparing for formal submission. Worth one line on that page when it is next touched, framed as an early independent implementation rather than a competing design (no commits since March 2026). It is now recorded and cross-linked from /community/vandyill.
• run 186 minor, banked not fixed: /ecosystem/radixuid's infobox Status cell opens with a RED circle glyph while metadata.status reads '\U0001F7E0 Dormant' and the cell's own text says Dormant. Same page, two different status colours. Worth a sweep of glyph-vs-metadata agreement across the ecosystem infoboxes rather than a one-off fix.
• run 187 (contents/history): applied the run-185 x.com correction to this category. Probed all 33 distinct x.com/twitter.com URLs in the contents/history subtree with a browser UA following redirects: 32 return 200, exactly ONE returns 404 - x.com/beemdvp, cited as the mentor on the three autumn-2024 dApp-in-a-Day workshops. Every handle variant 404s (beemdvp, beem_dvp, BeemDvp, on both x.com and twitter.com) against 200 controls on radixdlt/flightofthefox/RadixWiki, so it is a true death, not a block. Nine contents/history audits (runs 81, 95, 107, 119, 138 among them) had filed it as an anti-bot FP under the now-refuted x.com-404-FP policy. Repointed all 6 occurrences to github.com/beemdvp (live 200, name 'Beem', 28 repos, profile updated 2026-07-28, twitter_username null - consistent with the X account being deleted). workshop-1/-2/-3 each v3.2.0 -> 3.2.1. The FP class is now cleared in BOTH the categories it was measured in; assume it is still suppressing deaths in developers, blog, contents/tech and contents/resources and re-probe on each of those rotations.
• run 187 (contents/history audit): 24 pages / 216 external / 129 embeds, 0 broken internal, 0 broken embeds, 0 non-standard images. Post-edit re-audit 24 brokenExternal, ALL in the banked FP set and no new suspects - linkedin.com/in/* 19 (999/429), medium.com/pillarproject 2 (403), lsbu.ac.uk (403), orange-finance.gitbook.io (403), coingecko.com/learn (403). x.com is now absent from the flag list entirely. Category is genuinely link-clean.
• DONE (run 187, contents/history staleness head): /contents/history/history-of-radix v1.4.1 -> 1.5.0. The cornerstone entry point for the whole wiki narrative had never been reconciled with the corrections runs 183-186 landed on contents/tech, and carried three defects. (1) Cerberus described in the present tense as a protocol 'that braids consensus across shards' - reframed as a specification, with the explicit statement that braiding has never run in production (Babylon runs Cerberus unsharded = original HotStuff arXiv:1803.05069; the Xi'an candidate does not braid), matching cerberus-consensus-protocol v6.0.0 / sharding v2.0.0 / rollups v1.1.0. (2) The Hyperscale 500k test dated 'in late 2025' and attributed 'Led by team member Timan' - the canonical hyperscale-500k-tps v2.0.0 dates the final public test to January 2026 and carries NO lead attribution; a grep found 'Timan' as test lead nowhere else on the wiki, so the claim was unsourced. Corrected the date, removed the attribution, and attributed the result to the Radix Foundation's reference implementation rather than to Cerberus. (3) Xi'an described only as 'the fully sharded mainnet' with no mention of the execution-layer change - added the purpose-built VM replacing the Radix Engine (t.me/hyperscale_rs/10334, /10332) and the dApp migration expectation (recompile, worst case an automated transpiler, /10346). Verified landed via /api/wiki. Script retained: scripts/sweep-187-history-of-radix.mjs.
• BANKED, not written (run 187): Hyperscale Weekly Week #12 (27 Jul - 2 Aug 2026, t.me/hyperscale_rs/10399, posted 05:00 UTC 3 Aug) - committee rotation, the one-seat-at-a-time shuffling at the core of adaptive sharding, is wired in and running make-before-break; beacon randomness rebuilt; the whole node runs in a browser. Milestone 1, week 14, 78 commits. /contents/tech/research/hyperscale-rs v6.1.1 mentions NONE of 'committee rotation', 'make-before-break' or 'beacon randomness'. Left for the contents/tech rotation rather than edited here: the page was refreshed 2 Aug and this run's rotation is contents/history. NOTE the standalone posting routine already tweeted the committee-rotation item at 06:11 UTC today (x.com/RadixWiki/status/2084160221400719716), so the page is behind its own account.
• READER DEMAND, high value (run 187): on 3 Aug 09:41-09:49 UTC a holder asked in hyperscale_rs (t.me/hyperscale_rs/10402) 'Does anyone have a list of which Radix dapps are still operational and which have been abandoned', reasoning that operational dApps need to be part of the new-VM migration conversation, and a second member replied 'Perhaps you can curate such a list for us' (/10404). That is a direct request from the target demographic for exactly the asset the wiki already holds: 141 ecosystem pages each carrying metadata.status. There is no single index page presenting it. Proposal for a future ecosystem rotation: an /ecosystem operational-status index (Active / Dormant / Closed counts plus the list), built from metadata.status, with the status glyph-vs-metadata disagreement from run 186 fixed first. This is also the strongest unposted tweet hook of the week if it ships.
• CLOSED (run 188) – the run-187 READER DEMAND item. Built /contents/resources/radix-ecosystem-operational-status v1.1.0: all 141 /ecosystem pages grouped by status (54 operational, 8 testnet/pre-launch/in-development, 41 dormant, 38 closed/departed), each linked, with a stated method and its limits. Placed under contents/resources, NOT under /ecosystem – the ecosystem node requires status+category metadata on every page and the section is projects-only, so an index page there would render as a stray project card. The page is GENERATED by scripts/sweep-188-operational-status-index.mjs: re-running it rebuilds the lists and re-probes every site, so correcting a project page and rebuilding is the way to correct the index, and a rebuild that changes nothing but the date does not write. Inbound links added from /contents/history/radix-ecosystem-funding and /contents/resources/recycled-telegram-handles.
• FINDING (run 188) – a live website is not evidence of a live project, now measured on this directory. Probed every ecosystem page that publishes its own website, in BOTH directions: 57/57 live-claimed projects resolved, and 35/42 dormant-or-closed projects ALSO resolved. 83% of the projects this wiki says are dead still serve a page. The clean illustration is Ploughshare – ploughshare.nz returns HTTP 200 and the page it returns reads "Ploughshare is under maintenance". This is why the index is built from curated status rather than uptime, and why any future "just check if the site is up" shortcut should be refused. Recorded in the page itself and regenerated on every rebuild.
• NEXT STEP for the operational-status index (the real answer to the reader question): per-dApp ON-LEDGER activity – last transaction against each project's components, and for Token entries the current supply/holder count from the resource address already in the infobox. Website liveness is measured worthless (see the 35/42 finding above); ledger activity is the check that would actually separate operating dApps from parked domains ahead of the Xi'an migration. Sized as its own run: ~140 pages, Gateway queries, and a component-address extraction pass most pages do not yet carry.
• FLAG FOR A HUMAN (run 188, code change) – five ecosystem pages carry a metadata.status value that the editor cannot produce: "🟠 In development" (muan-protocol, tahuna, proven-network), "🟡 Pre-launch" (oter) and "🔴 Departed (pivoted off Radix)" (ideosphere). The ecosystem node in src/lib/tags.ts declares status as a select over exactly four options (Active/Testnet/Dormant/Closed), so these came in by seed script and anyone editing one of those pages in the app would be silently forced to change its status. The values carry real information the four options do not, so the fix is to add them to the select in src/lib/tags.ts (a deploy), not to flatten the pages. The index buckets all five explicitly so none of them can vanish – the generator throws on an unbucketed status.
• Dead-site list refreshed (run 188), for the standing unwrap/archive-repoint backlog: of the 42 dormant/closed pages publishing their own site, 7 no longer resolve – stakebros.info, farbo.me (farbocoin), radket.com, nftwars.app, moxstudio.net (mox-studio), projectnow.io (403, likely a bot-block rather than death) and juicystake.org. juicystake.org answered 200 on the first pass of this run and failed on the second, so treat it as intermittent rather than dead. Everything else in the dormant/closed set still serves a page and needs no link work.
• PRIORITY TWEET HOOK banked (run 188, cadence-blocked): the new operational-status index plus its measurement – "83% of the Radix projects this wiki lists as dormant or closed still serve a live website; 35 of 42. You cannot tell a dead project from a live one by its domain." Discovery-led, hard-number, reader-requested, and on a subject the account has not touched. Does not decay. Link /contents/resources/radix-ecosystem-operational-status. Optional human hook: the request came from the hyperscale_rs channel (t.me/hyperscale_rs/10402).
• PRIORITY HOOK (run 189, unposted). The wiki's Xi'an/VM section had said in as many words that what the new VM means for Scrypto "has still not been stated". On 3 Aug 18:51 UTC the hyperscale-rs lead developer stated it: Scrypto parity is "not particularly hard to hit" because "Scrypto is literally just a couple of Rust macros"; manifest, resources, subintents and badges are "genuinely good ideas" the new VM is not trying to change; what is being replaced is "the lower layers like state, locks, parallelism" (t.me/hyperscale_rs/10414). This is the direct follow-on to the account's best-performing post in the current window (2 Aug, "the Radix Engine will not be adapted for sharding", 37L/11RT/308I) and answers the migration-cost worry a real holder raised in the same thread. Live at /contents/tech/research/hyperscale-rs v6.2.0. SKIPPED ON CADENCE ONLY: @RadixWiki posted four times on 3 Aug (06:11, 11:15, 14:13, 20:12 UTC) and the last was ~25 min before this run. Does not decay.
• SYSTEMATIC PASS BANKED (run 189). Empty-infobox defect class: a block of type infobox with blocks:[] renders nothing, and because the link checker only walks anchors it is invisible to every audit. 7 of the 15 blog pages carried one, always at the END of the page (index 1 of 2, or 9 of 10 on rgh2024-debrief) – the whole legacy-essay cohort, while all four week-in-review pages plus money-wealth-volcanos and pow-vs-pos already had a populated infobox at index 0, i.e. a migration was started and stalled. All 7 fixed this run. Run 158 found the same defect once on /ecosystem/addix. NOT YET SWEPT: contents/tech, contents/history, developers, ecosystem, community, contents/resources, ideas, policy. One query finds them: SELECT tag_path, slug FROM pages, then filter blocks where type=infobox and (blocks IS NULL OR length 0). Cheap and mechanical – worth one bounded pass per rotation rather than a single bulk run.
• run 189 (blog): category audit link-CLEAN of genuine deaths after fixes – 15 pages / 147 external / 66 embeds, 0 broken internal, 0 broken embeds, 0 non-standard images. Two GENUINE deaths found and fixed on /blog/rgh2024-debrief (twitter.com/wyliepieote and twitter.com/beemdvp, both 404 with a browser UA against a 200 x.com/radixdlt control) – beemdvp was fixed in contents/history by run 187 but the blog credit sat outside that rotation, so check for cross-category survivors whenever a handle is retired. Post-edit re-audit: 19 brokenExternal, all banked FP classes (linkedin 999/429 x8, medium/unrealengine/slashdata/grandviewresearch/escholarship 403, fred/mckinsey/statista/instagram/rekt.news/x.com status-0). CONFIRMED TRANSIENT, do not re-verify: github.com/Sahid-m/radix-hack and t.me/hyperscale_rs/10344,10346,10352 flagged status-0 in the first audit, all probed 200 directly, and all cleared in the second audit 40 minutes later – the checker throttles under load. status-0 in this category means checker throttle, not death.
• run 189 (blog): traffic case for the week-in-review series. /blog/week-in-review-2026-08-02 is the #2 page on the whole wiki at 65 visitors over 30d, second only to the homepage and ahead of /ecosystem (57) and hyperscale-rs (37) – the series is now the wiki's biggest single draw after the front door, and it is produced by the radix-week-in-review routine rather than by sweeps. Implication for the blog rotation: the four week-in-review pages are the traffic, the eight legacy essays are the archive. Deepen the archive for correctness (as this run did with infoboxes and dated caveats), but spend discovery effort where the readers are.
• run 189 (blog): dated-caveat pattern worth reusing. Three of the seven legacy essays carried a frame that has since been overtaken, and rather than rewrite an archived opinion piece the infobox now carries an explicit dated row: ten-10x-moments (13 Mar 2023) written before Babylon shipped at epoch 32717 on 28 Sep 2023; a-year-in-review-2023 cites a jobs board and talent pool that were retired and now 404 (the same retirement run 185 found still advertised on /ecosystem/radix-wiki); radix-is-what-web3-noobs-think-they-bought (18 Oct 2024) describes a scaling roadmap that has since moved to the Hyperscale/Xi'an programme. Preserves the piece as published while stopping a reader dating it wrong. Applies to any archived editorial the wiki hosts.
• run 190 (contents/resources): category audit link-CLEAN - 10 pages / 44 external / 3 embeds, 0 broken internal, 0 broken embeds, 0 non-standard images. The single brokenExternal is coingecko.com/en/coins/radix (403), re-probed this run with a browser UA following redirects and still 403: CoinGecko blocks the whole domain to automated clients, same class as the already-banked coingecko.com/learn. Do not strip it.
• DONE (run 190, contents/resources staleness head): /contents/resources/legal/privacy-policy v1.0.1 -> v1.1.1. The policy is an inherited UK law-firm template and still named the Data Protection Act 1998 as the governing statute - repealed and replaced by the Data Protection Act 2018 and the UK GDPR on 25 May 2018 - and quoted the GBP 10 subject-access fee that regime abolished. Also carried a template leftover offering 'a legal advice line quote or call-back', a service this wiki has never had. Three surgical replacements, cited to legislation.gov.uk and the ICO; no new commitments introduced.
• LESSON (run 190): the ICO right-of-access URL added in the privacy-policy edit 404'd, and was caught only because the run happened to status-check its own new citations afterwards - the correct page is ico.org.uk/for-the-public/getting-copies-of-your-information-subject-access-request/. Fixed the same run (v1.1.1). Status-check every NEW outbound link before the write, not after; check-links only audits links that are already live on a page, so a bad citation published between two rotations sits there until that category comes round again.
• DONE (run 190, contents/resources): /contents/resources/python-scripts/proof-of-work v1.2.1 -> v1.3.0. Ran the tutorial's script rather than only its links (per the standing 'a clean link audit is not a healthy page' rule) - it works on CPython 3.13 and the page's '5 = ~ 1 second' hint holds. Added the part the page left to guesswork: 16^z expected attempts, ~1.8M hashes/s measured single-core, so ~0.6s at five zeros, ~10s at six, ~2.5 min at seven; the geometric spread around those means, shown with this run's own two results (156,056 nonces at five zeros, 33,290,382 at six); and Bitcoin's 2,016-block retarget as the network-scale version of the same arithmetic.
• NEXT contents/resources rotation: the legal trio is all boilerplate from the same law-firm template and only the privacy policy has been read line by line (run 190 found three defects in it). /contents/resources/legal/terms-of-use (13.1 KB, England-and-Wales jurisdiction clauses) and /acceptable-use-policy (6.5 KB) have not been checked for the equivalent leftovers or for statutory references that have moved on. Neither carries a dated 'last updated' line, which is itself worth adding.
• BANKED (run 190, too thin to publish alone): hyperscale_rs /10416-/10417, 4 Aug - asked whether the new VM's contract language is 'a discipline making it a subset of Rust or is it Rust and a little more', the lead developer answered 'It's not a separate language... it's just Rust'. It reads as a statement about the new VM's programming surface and sits directly alongside the Scrypto-parity quote already on the page, but the antecedent is not pinned in the thread. Revisit when the VM's language surface is discussed again, and quote both together.
• CHECKER ARTIFACT, new false-positive class (run 191). The ecosystem audit reported 104 brokenExternal against 0 on the previous nine consecutive ecosystem runs. 58 of the 104 are web.archive.org URLs returning status 0 — the checker being rate-limited by the Wayback Machine on a bulk pass, not dead snapshots. Two were re-probed with a browser UA and both returned 200 (20221020185418/twitter.com/RadketRDK and 20231129122504/reizor.com). BANK THIS: a mass web.archive.org status-0 block in any category audit is Wayback throttling and needs no per-link re-verification — spend the checking budget on non-wayback suspects only. The remaining 46 are the already-banked bot-block set (medium/anthic.medium/blog.caviarnine 13+, notion.so 10, defillama 3, linkedin 999, redbubble, unrealengine, jerseyfsc) plus two NEW confirmed-alive bot blocks: projectnow.io x4 (Cloudflare 403 even with a browser UA; its page is already 🔴 Closed so no status implication) and fred.stlouisfed.org (HTTP/2 stream reset then timeout to curl, 403 to WebFetch — a major institution, alive). 0 broken internal, 0 broken embeds, 0 non-standard images.
• DONE (run 191), grow-authority gap closed: /ecosystem/rly-fun created. rly.fun was cited as "the Radix launchpad" from three existing pages (ASCENT infobox, Reddicks treasury section, and $BlueBalls via its Ociswap info_url) and had no page. Mechanics sourced from rly.fun/about: 1B fixed supply per coin, 800M into the bonding curve and 200M into an Ociswap precision pool, graduation at 690k XRD market cap on ~240k XRD of inflow, migrating to Ociswap at ~1.1m XRD cap with 400k XRD perma-locked liquidity; fees 0.9% buy / 1% sell / 1% graduation / 2.5% dev reward, with all post-cost XRD profit going to open-market $EARLY buybacks; bridge operated by Astrolescent, not rlyfun. Site header 2026-08-05: 1,195 coins, 26.6M TVL, 51.0M volume (units unlabelled — recorded as most plausibly XRD, flagged as such on the page). Dated to late 2024 via Shardspace's 30 Dec 2024 Breakout review naming "EarlyQuest and now rly.fun". Self-declared alpha v0.01, unaudited — the page says so.
• PRIORITY TWEET HOOK banked (run 191, cadence-blocked — @RadixWiki had posted three times 2.6-2.9h before this run). Discovery-led and hard-number, the shape this account measurably responds to: a Radix launchpad has minted 1,195 coins and the wiki had been citing it from three pages without ever describing it. The sharper angle is the fee model — rlyfun sends ALL post-cost profit into open-market $EARLY buybacks rather than keeping it, which is unusual for a launchpad, and graduation perma-locks 400k XRD of liquidity on Ociswap. Link /ecosystem/rly-fun. Does not decay.
• ECOSYSTEM STALENESS, next in queue after run 191 (which took doubt-it, radix-blue-balls). The two at the head — xrd-domains (2026-03-28) and radix-namespace (2026-06-29) — are LOCKED_PAGES and must stay untouched; they will sit at the head of pagesByStaleness permanently, so read past them. Next real targets: radix-rolodex (2026-07-07, still zero on-ledger or usage detail; its embed.html shells are unverifiable by the checker by design), radix-kingdoms (2026-07-08, quotes ~598 KDMKEY minted and ~22.9M KGLD circulating — both re-checkable on-ledger, and the page carries two typos: "andd" and "orcale"), xseed (2026-07-08).
• run 192: /ideas cards NOT touched this run but now demonstrably behind reality. (1) dao-incorporate-duna-llc (In Progress, 11 Jul) - the DAO application filing is now the explicit gate on the Constitutional Proposal ('as soon as the DAO application is submitted'), which makes the filing date the most load-bearing unknown on the whole board; add the dependency and chase the filing date. (2) NO CARD EXISTS for the CAIP-namespaces / x402 registration workstream, which has now passed a temperature check (quorum 3 Aug) and has a PR in flight - it is a live pipeline item the board does not depict. (3) The Constitutional Proposal's SCOPE is unpublished: the announcement does not say whether it ratifies the full ten-document Phase 1 set or the Charter alone. Chase it, and record the answer on dao-adopt-phase1-governance-docs. (4) When the DAO-dedicated Consultation instance goes live, capture its URL and dApp-definition account the way run 179 did for the Mountaintop instance.
• DONE (run 193): the run-189 empty-infobox systematic pass is CLOSED. A full-DB walk (350 pages, recursing into nested blocks and columns) found exactly three survivors, not the long tail the banked item assumed: ecosystem/dexian-protocol, ecosystem/hydraswap and ecosystem/xrd-domains. The first two are fixed (infobox populated at index 0 from facts verified this run, empty trailing block dropped). xrd-domains is a LOCKED page and was refused by the isLockedPage guard — it will keep showing up in any future scan and should be left alone. Note the scan only catches infobox blocks that are EMPTY; a page with NO infobox block at all (juicy-stake was one) is invisible to it, so infobox-first is worth a separate check.
• DONE (run 193): /ecosystem/dexian-protocol v3.2.0 -> 3.3.0 and /ecosystem/hydraswap v1.3.1 -> 1.4.0. dexian: dexian.io is NXDOMAIN (not merely offline) and goxrd.com — the website in the KaiYuan Epoch validator’s own on-ledger metadata — serves a host-suspension page over HTTP with a broken TLS handshake on HTTPS. The validator is still REGISTERED with ~3.76M XRD staked at rank 87/188, and reads 0% uptime over both the trailing week and the trailing month (epoch 332526), which is what makes the 🔴 Closed status evidenced rather than assumed. hydraswap: the page quoted supply as "roughly 966.8 million" read 26 Jul; the live total is 965,821,366 — minting is deny_all and LOCKED while burning is allow_all, so the supply only falls, and about a million tokens burned in eleven days. Corrected with the mechanism named.
• DONE (run 193, the policy slot’s real job): /ecosystem/juicy-stake v2.3.1 -> 3.0.0. Run 175 placed an `outdated` banner on it with an explicit reason — "the remaining sections describe the service in the present tense" — and four revisions later nobody had acted on it. /policy/verifiability says a banner "is a request for help ... Remove it when the problem it names has been fixed", so the correct move was to fix the body and take the banner down, NOT to remove a banner that was still true. Replaced ~1,200 words of unsourced present-tense marketing copy (secure infrastructure, experienced team, positive user feedback, "has established itself as a trustworthy and reliable staking service provider") — a plain NPOV and no-original-research failure — with a past-tense account sourced to the archived operator docs, and added the infobox the page never had. NEW on-ledger finding: still unregistered at epoch 332527, and the 12,610,520.465017496855168922 XRD delegated is byte-identical to the 1 August reading — nobody has withdrawn anything in five days from a node that pays no emissions, while the operator site still advertises 19,726,201 XRD and 6.77% APY.
• BANNER INVENTORY (run 193, first wiki-wide count): only 7 of 350 pages carry a maintenance banner — juicy-stake (outdated, now cleared this run), blue-chick-nfts + unisci + unix (promotional), and the three Radix Engine layer stubs. The three promotional banners are the obvious next application slot: each names an NPOV problem nobody has fixed, exactly as juicy-stake’s did. Do one per policy rotation rather than all three at once.
• GROW-AUTHORITY TARGET (run 193): /contents/tech/core-protocols/{kernel,vm,application}-layer are all still one-paragraph stubs (~1.7KB each) with accurate stub banners. vm-layer is the pick — the Scrypto VM / Native VM split is the exact thing the Hyperscale/Xi’an programme is replacing, hyperscale-rs is the wiki’s #4 page by traffic, and the two would cross-link naturally. kernel-layer next (substates, actors, invocation, costing are a section each, per its own banner text).
• ROTATION COVERAGE CHECKED (run 193): grouped every page by top-level category — blog 15, community 7, contents/history 24, contents/resources 10, contents/tech 85, developers 31, ecosystem 142, ideas 29, policy 6. All nine appear in rotation.order; no category is sitting outside the rotation the way economics once did.
• PRIORITY TWEET HOOK banked (run 193, cadence-blocked — @RadixWiki posted 03:10 UTC, ~4h before this run, and a reply went out 11 minutes before it). Discovery-led and hard-number, the shape this account measurably responds to: 12.6 million XRD is sitting delegated to a Radix validator that deregistered itself and therefore pays no emissions, and not one token has moved in five days — while the operator’s site still advertises 19.7M staked at 6.77% APY. Link /ecosystem/juicy-stake. Re-read the stake figure before posting; the "five days" detail is the only part that decays.
• NEGATIVE RESULT, do not re-chase: infobox POSITION in the content array is irrelevant to rendering. PageContent.tsx calls findInfobox(content) and filters the block out of mainBlocks, rendering it as a floated <aside>; the editor always appends it last (setContent([...blocks, infobox])). A DB-wide walk of all 350 pages found 258 with the infobox at index 0, 36 elsewhere and ~29 of those at the very END - that is what the editor produces, not a defect. Run 189 flagged END-position infoboxes only because they were EMPTY, which run 193 closed.
• NEGATIVE RESULT, do not re-chase: "no infobox block" does NOT mean "no facts table". infoboxHasContent(block, metadata, tagPath) in BlockRenderer.tsx returns true on declared metadata alone, and InfoboxSidebar renders buildMetadataBlock() plus an assetPrice widget for every resource_address key. 56 of 350 pages carry no infobox block and most still render a sidebar from status/website/category/assets. Do not treat that count as a work queue - check the metadata first.
• FP classes banked from the run-194 ecosystem audit (107 brokenExternal, 0 genuine). NEW and now trusted: www.notion.so 403 x10 (re-probed with a browser UA, returns 200 - Notion blocks the bulk pass); blog.caviarnine.com 403 x3 (307-redirects to medium.com/m/global-identity-2, so it is the banked Medium class under a custom domain). UNRESOLVED, do not strip: www.jerseyfsc.org 403 on /ecosystem/radix-foundation - the Jersey FSC registry 403s at the site ROOT too, with curl and WebFetch alike, so it is a site-wide WAF and not a dead entity page. Everything else was the standing set (web.archive.org status-0 x60, medium x21, projectnow x4, defillama x3, linkedin, unrealengine, redbubble, fred.stlouisfed, dsor.io).
• FOLLOW-UP from the xseed correction: sweep the ecosystem pages whose status was set from a project WEBSITE rather than the ledger. xseed sat at 🟠 Dormant since run 175 because xseedstaking.com prints "0 M+ staked" and "1% uptime" for a node that is rank 13 of 188 with 100.24M XRD and 100% uptime. Candidates are the 🟠 Dormant / 🔴 Closed staking pages that carry a validator or an assets resource address - radixstake, radixnodeio, radstakes and any other Staking-category page - each of which can be settled with one radix_get_validator / radix_get_resource call. Run 188 measured that a live site proves nothing about a dead project; this is the same error running the other way.
• CLAVIS / "Radix Manifest Games" is uncovered. The badge gating KGLD burn on /ecosystem/radix-kingdoms is the non-fungible <RadixKingdoms> inside resource_rdx1ntjxf4xrtmslncf8a8dqt55txhd5n3e6yk2egjtnsrzf0e5s0m5fyw, whose collection is named CLAVIS and described on-ledger as "NFT to be used for Radix Manifest Games", total supply 9. Nine badges implies up to nine games or components under one developer. Identify the holder and the other eight badges (radix_get_resource_holders / radix_get_nft) before deciding whether this is one ecosystem page or several.
• UNSOURCED chat claims from t.me/radix_dlt 5 Aug 2026, do NOT publish without a primary source: that "Gary said we should have one later this year" about a native Radix stablecoin, and the surrounding speculation about what RDX Works is building. Also seen and unchecked: github.com/wallet-agent-ai/wallet-agent-ai and radix-community.genkipool.com/es/console/mcp - compare both against the existing /developers/ai-agents/agent-wallet-ai page before creating anything.
• DELIVERED + DECISION RECORD (run 195): the two run-194 stub candidates (xstelea/radix-web3.js and rdx-cli) were published as ONE page, /developers/tools/radix-web3-js, not two. They are the same pnpm workspace — rdx-cli is packages/cli of radix-web3.js — and the funding-pages precedent says one subject, one page with sub-sections. Do NOT create a separate /developers/tools/rdx-cli stub in a later run; deepen the rdx section of the existing page instead.
• developers CATEGORY AUDIT (run 195): 32 pages / 194 external links / 1 embed. ZERO broken internal links, zero broken embeds, zero non-standard images. The single brokenExternal is radixdlt.medium.com/scrypto-oracles-challenge-is-live (403) on /developers/scrypto/08-oracle-integration — the banked Medium anti-bot class, deliberately not re-verified per the trust-the-banked-list rule. The staleness queue is not actionable: the oldest developers page is 2026-07-27, ten days old, because the whole category was refreshed then. Category is CLEAN; the useful work here is growth, not repair.
• TWEET HOOK banked (run 195, cadence-blocked): the licence split on radix-web3.js. Eight of nine npm packages declare MIT in package.json; the GitHub repository carries no LICENSE file at all, so npm and the repo disagree about what a user may do with the code — and radix-skills tells an AI coding agent to clone that repo as one of its two authoritative Radix source checkouts. Sharp, checkable, discovery-shaped. Not posted because @RadixWiki had already posted twice today (03:10 and 11:15 UTC) and the 11:15 post was itself about xStelea tooling (radix-skills); a second xStelea post four hours later would read as repetition to the same timeline. Hook does not decay.
• GROW-AUTHORITY TARGET for the next developers rotation: /developers/tools now holds 3 pages (hookah, radix-desktop-tool, radix-web3-js) against 6 in /developers/ai-agents. Candidates surfaced but not yet written — (1) shardspace.app, dApp definition manager; (2) Radix Billboard / instruct.radixbillboard.com, visual manifest builder; (3) GenkiPool Community Tools, radix-community.genkipool.com. All three are already cited from the Developer Resources hub, so each has an inbound link waiting.
• UNRESOLVED from the run-195 research, worth one probe later: @radix-effects/sbor is the only package in the radix-web3.js workspace with no license field in its package.json, and it is the one that continues daan_xrd sbor-ez-mode / CalamariRadix gateway-ez-mode work. Whether that omission is deliberate (derived work, unclear upstream terms) or an oversight is unknown — the page states the fact and asserts neither reading.
• CLASS CLOSED (run 196): the run-194 xseed follow-up — 'sweep the ecosystem pages whose status was set from a project WEBSITE rather than the ledger' — is done for the Staking category. All 23 Staking pages were matched by name against the full mainnet validator list (287 entries, 188 registered) read live at epoch 332670. FOUR were wrong and were corrected: radstakes 🔴 Closed -> 🟢 Active (registered, 99,875,144.75 XRD, RANK 14 OF 188, 100% uptime 1mo), radup 🔴 Closed -> 🟢 Active (36,315,647.36 XRD, rank 36, 99.99%), slightlyiffy 🟠 Dormant -> 🟢 Active (42,867,757.02 XRD, rank 35, 99.99%), leafnode 🟠 Dormant -> 🟢 Active (34,181,988.28 XRD, rank 38, 1% fee, 99.95%, and leafnode.info serves a live 200). The INVERSE error does not exist: every page still marked 🟢 Active resolves to a registered validator. The remaining non-Active staking pages are ledger-consistent — radnode (unregistered, accepts_delegated_stake FALSE), radixnodeio (unregistered, node literally named 'Radixnode.io - UNSTAKE'), topradixnode (unregistered, and its page already carries the 25,392,103 XRD stranded figure), juicy-stake (unregistered, run 193), stakebros (no validator of that name exists in the list at all).
• NEXT for the same class: run the ledger check against the OTHER ecosystem categories that carry an on-ledger handle. Token (13 pages) and Finance (35) both have resource_address or component metadata that radix_get_resource / radix_get_component_state can settle the same way a validator settles a staking page. Do it a category at a time; the Staking pass cost one radix_get_validator_list call plus four detailed reads.
• FEE FACTS ARE A SEPARATE STALENESS CLASS from status (run 196). Two of the four corrected pages quoted a fee the node no longer charges, because a Radix validator's stored fee factor and its EFFECTIVE fee diverge once a fee-change request passes its epoch: radup stores 0.0195 but has charged 15% since epoch 312126 (27 May 2026) — a factor of nearly eight — and slightlyiffy stores 0.025 but has charged 15% since epoch 289095 (8 March 2026). Read BOTH validator_fee_factor and validator_fee_change_request from POST mainnet.radixdlt.com/state/entity/details; the radixscan tool reconciles them for you (fee_percentage = effective, raw_fee_percentage = the lagging stored value). Any wiki page quoting a validator fee is suspect until checked this way.
• PRIORITY TWEET HOOK banked (run 196) and THIS ONE DECAYS — unusually, since the standing complaint is that banked hooks never expire. Radstakes carries an on-ledger fee-change request raising its fee from 15% to 25%, effective epoch 335294, roughly nine days after the 6 Aug reading at ~288 epochs/day. It is decision-relevant to the ~99.9M XRD delegated to the network's 14th-largest validator, nobody has published it, and it is checkable in one Gateway call. Post it BEFORE that epoch or drop it. Link /ecosystem/radstakes. Re-read the request before posting — the operator can cancel or replace it.
• ecosystem AUDIT (run 196): 142 pages / 711 external / 40 embeds. ZERO broken internal, zero broken embeds, zero non-standard images. All 104 brokenExternal are the banked false-positive set with NO new hosts at all — web.archive.org status-0 x58 (bulk-pass rate limiting), medium.com x13 + anthic x6 + surgetrade x1 + gablefinance x1, notion.so x10, projectnow.io x4, defillama x3, blog.caviarnine x3, linkedin 999, unrealengine, redbubble, fred.stlouisfed, jerseyfsc. Per the trust-the-banked-list rule none were re-probed; the run's checking budget went to the ledger instead.
• STALENESS HEAD after run 196 (ecosystem, past the two LOCKED pages): radix-rolodex (2026-07-07), radixstake (2026-07-10), world-cup-badge-arena / ideomaker / miow / hermes-protocol / radix-accountability-council / radixcharts (all 2026-07-11). radixstake's 🟢 Active status is ledger-confirmed this run (registered, rank 12 of 188, 107.9M XRD, 14.9% fee, 100% uptime 1mo) but the page body was not read, so it was NOT stamped verified.
• SIGNAL seen and deliberately not written up (run 196): TRADE VAULT (trade-vault-iota.vercel.app), a peer-to-peer Radix escrow dApp announced in t.me/radix_dlt at 11:48 UTC 6 Aug, built in ~3 hours by an AI coding agent working off xStelea's radix-skills, shipped with an explicit 'use at own risk'. The 17:35 UTC @RadixWiki post from another routine already covered it from the ledger. If it acquires users or an audit it earns an ecosystem page; a three-hour unaudited demo does not.
• DONE (run 197): the run-193 grow-authority target discharged. /contents/tech/core-protocols/vm-layer v1.1.1 -> 2.0.0, stub banner removed, 1.6KB -> a full page (Scrypto VM / Native VM / VM boundary / versioning / what Xi'an changes). STILL STUBS, same shape, same banner, next in line: /contents/tech/core-protocols/kernel-layer (1,740 bytes) and /contents/tech/core-protocols/application-layer (1,753 bytes). kernel-layer is the better next pick per its own banner text — substates, actors, invocation and costing are a section each — and it now has an inbound link from vm-layer.
• STALENESS HEAD, contents/tech, NOT touched by run 197 and now the two oldest pages in the entire category (both 16 March 2026, ~143 days, so the 180-day outdated banner fires around 12 September): /contents/tech/core-protocols/transaction-manifests (2,315 bytes, infobox + one Overview section + External Links) and /contents/tech/research/radix-economic-model (1,619 bytes, infobox + a single Overview section, NO External Links at all). The economic-model page states 300M XRD annual emissions, partial fee burn, component royalties and a 24B max supply as a bare bullet list with not one citation — and /contents/tech/core-concepts/network-emissions (refreshed 23 July) already carries the sourced version, so the fix is mostly reconciliation plus a live supply read, not research. Run 197 spent its slice on the signal-matched page (resources) and the banked grow target (vm-layer) instead; these two are the head of the queue for the next contents/tech rotation.
• contents/tech CATEGORY AUDIT (run 197): 85 pages / 434 external / 39 embeds before edits, 442 external after. ZERO broken internal links, zero broken embeds, zero non-standard images, both before and after. All 24 brokenExternal are the banked bot-block 403 class with NO new hosts and none were re-probed, per the trust-the-banked-list rule: papers.ssrn.com x3, bitcointalk.org x3, medium.com x4 (plus valleydao. and vitadao. subdomains), stanford-jblp.pubpub.org, cepr.org, imf.org, researchgate.net, coinbase.com, forbes.com, notion.so, theblock.co, coinvise.mirror.xyz, mirror.xyz, aibc.world, axieinfinity.com. Post-edit re-audit confirms every one of the ~20 external links added this run (github.com/radixdlt/radixdlt-scrypto blobs, t.me, dashboard.radixdlt.com) resolves, and every new internal link resolves.
• PRIORITY HOOK (run 197, unposted, does not decay). The 6 Aug 18:00-22:40 UTC hyperscale_rs thread argued for hours about marking tokens with an owner 'fingerprint' so a hacked holder could recover them, and nobody could answer the protocol question underneath it. The answer is now on /contents/tech/core-concepts/resources: XRD's recaller AND freezer are both deny_all with both updaters deny_all, read live at state version 546564033 (epoch 332718, 2026-08-06T23:05:36Z) - so XRD can never be recalled or frozen by anyone, and no vote or protocol update can change it, because there is no one the engine would accept the instruction from. Also on the page: XRD IS mintable, but only by a Global Caller badge (the consensus manager paying emissions), which surprises people who read 'fixed supply' into a native token. That mintable-but-unrecallable pair is the hook. SKIPPED ON CADENCE ONLY: @RadixWiki posted 4x on 6 Aug (03:10, 07:01, 11:15, 17:35 UTC), two of them wiki-sweep tweets, against a stated cap of ~1-2 wiki tweets/day; the 17:35 post was 5.7h before this run.
• DONE (run 198, grow-authority): /contents/tech/core-concepts/access-controller v1.0.1 -> 2.0.0, a 1,628-byte stub since 30 June expanded to a full page. Three roles with the Proposer asymmetry (Confirmation can neither initiate nor propose, so every change of control needs two of the three); quick_confirm pairings that stop a proposer confirming itself; the timed path, which belongs to the recovery role alone and completes through timed_confirm_recovery - declared MethodAccessibility::Public in the auth template, so once the on-ledger delay elapses the confirming transaction needs no badge, only a proposal that matches; the u32-minutes delay ceiling the source itself glosses as 8171.5511700913 years; lock_primary_role (recovery-only) blocking create_proof; badge withdraw returning the owner badge and setting all three roles to DenyAll, permanently retiring the controller; and the Bottlenose xrd_fee_vault (update_access_controller_to_add_xrd_fee_vault) with contribute_recovery_fee PUBLIC so a stranger can fund a recovery without gaining a say. 22 live methods confirmed against the native package on mainnet at epoch 332766.
• STILL STUBS in contents/tech/core-protocols after run 197 (unchanged, next in line): /kernel-layer (1,740 bytes) and /application-layer (1,753 bytes), same stub banner. kernel-layer remains the better next pick - substates, actors, invocation and costing are a section each - and now has inbound links from both vm-layer and the new access-controller page.
• FEE STALENESS CLASS - MEASURED (run 198, closes the run-196 open question with a number). A live paginated read of POST /state/validators/list at state version 546651692, epoch 332767: 287 validator components, 188 registered, and 62 OF THE 188 charge a fee different from their stored validator_fee_factor - 50 of them MORE. Those 62 hold 2,900,410,156 of the 4,727,137,240 XRD staked to registered validators, i.e. 61% of all delegated stake. Cause is in the engine, not in the data: update_fee leaves an effective request sitting in validator_fee_change_request and only folds it into validator_fee_factor when the owner requests the NEXT change, while apply_emission resolves the charged fee from the request whenever epoch_effective <= concluded_epoch. Any tool reading the stored field alone is wrong about a third of the register. Mechanism now documented on /contents/tech/core-concepts/validator-nodes (v1.2.1 -> 2.0.0, stub expanded), which also carries registration/active-set facts (max_validators 100, num_unstake_epochs 2016, num_owner_stake_units_unlock_epochs 8064, num_fee_increase_delay_epochs 4032, validator_creation_usd_cost 1000, all from ConsensusManagerConfig::mainnet_genesis) and the under-known fact that a validator fee is not paid out in XRD - it is staked back to the same validator and the minted stake units are locked in the owner vault.
• NEXT for the fee class (run 198): the census gives the exact work list. Sweep the 62 divergent validators against the wiki's Staking pages and correct every page quoting a stored factor. RadixStake was corrected this run (1.49% -> 14.9%, effective epoch 288573 = 6 March 2026, five months stale, ~107.9M XRD delegated at rank 12). Re-run the census with: paginate POST mainnet.radixdlt.com/state/validators/list, then for each registered validator compare validator_fee_factor against validator_fee_change_request.new_fee_factor where epoch_effective <= current epoch. Also worth a page-level check: /contents/tech/core-concepts/network-emissions claims a 98% uptime floor for rewards, but ConsensusManagerConfig::mainnet_genesis sets min_validator_reliability = 1.0, which in to_reliability_factor takes the dirac-delta branch (full emission only at exactly 100%, zero otherwise). The two cannot both be right; the Gateway does not expose the live ConsensusManager Configuration field, so settling it needs the Core API. DO NOT edit the emissions page until that is read.
• TWO PENDING FEE CHANGES on the whole register as of epoch 332767 (both decision-relevant, both DECAY): Radstakes 15% -> 25% at epoch 335294 (~9 days out, ~99.9M XRD, rank 14; already on /ecosystem/radstakes since run 196) and Cadwynbloc 50% -> 75% at epoch 332966 - only ~200 epochs, under a day away at the time of reading, on 68.3M XRD at rank 26. Cadwynbloc has no wiki page. Neither was tweeted this run; the systemic finding was the stronger hook and the Radstakes hook was already banked.
• ecosystem AUDIT (run 198): 142 pages, 717 external before edits / 718 after, 40 embeds. ZERO broken internal, zero broken embeds, zero non-standard images, before and after. brokenExternal 104 -> 109 with exactly ONE new host: ttabvue.uspto.gov x5 (all on /ecosystem/rdx-works, status 502). Probed directly the same minute and BOTH the raw and &amp;-encoded forms return 200 - a transient upstream 502, not a dead link. Bank it as a false positive and do not strip the USPTO trademark citations. The other 104 are the standing set with no change: web.archive.org x58, medium.com x13 + anthic x6 + surgetrade + gablefinance, notion.so x10, projectnow.io x4, defillama x3, blog.caviarnine x3, linkedin, unrealengine, redbubble, fred.stlouisfed, jerseyfsc.
• STALENESS HEAD after run 198 (ecosystem, past the two LOCKED pages): radix-rolodex (2026-07-07) is now the oldest un-refreshed page and was NOT touched this run - a 4-block page for VandyILL's Rad/Deck embed tool whose only external link is radixrolodex.com, and whose embedded Deck iframe is in the standing unverifiable-embed set (JS widget shell). Then world-cup-badge-arena / ideomaker / miow / hermes-protocol / radix-accountability-council / radixcharts (all 2026-07-11), avaunt-staking (07-12), mox-studio (07-13). radixstake left the queue this run.
• run 199 (community): PEOPLE COVERAGE is the section's remaining gap and it is now one page less empty. /community/piers-ridyard published; the next-largest missing figures, in order of how often the wiki already names them without linking anywhere: Adam Leslie Simmons (RDX Works director 2023-2025, RDX Holdings first owner, named in the Foundation maintenance-mode post as the most senior departure), Andrew/Andy Jarrett (sole director of the UK Radix Foundation since Feb 2025, on the Radix Tokens (Jersey) and Metaverse (Radix) boards), and Lindsay Bracegirdle / James Cunningham-Davis (same Jersey boards). Each is already sourced on /ecosystem/radix-foundation; a page is mostly a matter of assembling what the wiki holds plus the officer record. Do NOT reopen /community/cryptoants (run 173 KEEP decision).
• UNRESOLVED, run 199: the two RAC governance proposals (Stokenet funding, website) went to binding votes on 28 July at consultation.mountain-top.live/proposal/1 and /2, and /community/daffy still describes them as open. The outcome could not be read this run: the dApp is a client-rendered SPA with no public API (probed /api/*, /api/v1/* on both the app host and VOTE_COLLECTOR_URL api-consultation.mountain-top.live, all 404), the RAC Telegram channel has posted nothing since the 28 July vote-opening message, and preview_start timed out after 300s so the browser was unavailable. Two routes for the next run: drive the SPA in a browser, or resolve the consultation component from the dApp definition account (account_rdx12y8wqqgpjndcns9m94tjyhmfyx3hujf5snqqqjmu86vrcvg8zsx88y) and read the tallies on-ledger. This is a dated, decaying fact on a live page - worth doing.
• run 199 (community) AUDIT: CLEAN for the ninth consecutive community rotation - 7 pages / 67 external before the edits, 8 pages / 99 external / 4 embeds after, 0 broken internal, 0 broken embeds, 0 non-standard images both passes, sole flag the standing linkedin.com/in/dan-hughes 999 anti-bot FP. Staleness head remains cryptoants (2026-06-01, the run-173 KEEP decision, do not reopen); next actionable heads are daffy (2026-07-28, blocked on the vote outcome above), gilesmorris-me and genki (both 2026-07-31). Nothing was mark-verified this run: link liveness was confirmed for the whole subtree but no page's facts were re-checked end to end, and a freshness stamp is a claim about facts.
• DONE (run 200, signal): /contents/tech/research/hyperscale-rs v6.3.1 -> v6.4.0. Milestone 1 of the Xi'an RFC reported complete by flightofthefox on 7 Aug (t.me/hyperscale_rs/10474), with ONE deferred item - splitting shards on fees rather than storage size alone - which waits on the fee system, which waits on the VM. Infobox Status and Execution-layer rows rewritten, the Introduction's 'roughly three-quarters complete at the end of July' sentence replaced, the RFC milestone list marked, and two new subsections added to the Execution Layer section.
• THE ARTEFACT (run 200): github.com/hyperscalers/hyperscale-vm is PUBLIC and has been since 30 July 2026 - the wiki had been carrying 'a purpose-built VM is underway' since 1 Aug. 124 commits, all flightofthefox, by 7 Aug. 12 crates (effects/kernel/hbor/runtime/ref/sdk/stdlib/types/harness/manifest-builder + macros), guest fixtures for account, constant-product pool, order book, staking and transfer, 8 numbered architecture docs, an INV-VM-* invariant register described as the starting point for formal verification, and upgrades.md governing how the engine pin and the deterministic profile move. Design: determinism-by-declaration; route() returns shards + per-shard key-and-mode sets + static call graph with no execution and no state read; undeclared access is unreachable rather than filtered; five access modes with a compatibility relation replace exclusive whole-object locks; the profile is executed twice (version-pinned wasmtime + an independently written reference interpreter, differentially tested, divergence a release blocker).
• PRIORITY HOOK (run 200, UNPOSTED - cadence skip, not a quality judgement; DOES NOT DECAY MUCH since it is a written artefact, not an event). The hyperscale-vm architecture overview lists its NON-GOALS explicitly and one of them is 'Scrypto or EVM compatibility - the effect-typed ABI is not expressible under either; no shim layer.' That is the FIRST place the project has written down that existing Scrypto blueprints will not run on Xi'an's engine and that nothing will be provided to make them run. It does not contradict the 3 Aug 'Scrypto is literally just a couple of Rust macros. Not particularly hard to hit parity' - parity of concepts is not ABI compatibility, and the VM ships its own blueprint/state macros and its own resource, badge and principal types - but the wiki is now the only place the two sit side by side. Angle for the next run: lead with the non-goal line verbatim, then the reconciliation. Compose through radix-studio/VOICE.md; do NOT post a pre-written draft.
• DONE (run 200, contents/history staleness head): /contents/history/validator-subsidy-sunset v1.1.1 -> v1.2.1, oldest page in the category (7 July). It ended on a promise - 'validators now sustain operations through validator fees' - and never measured it. New 'Aftermath: the fee market that replaced it' section built from a live paginated Gateway census at epoch 332862 / state version 546,817,889 (7 Aug 11:06 UTC): 287 components, 188 registered, 4,730,263,018 XRD delegated. Median fee 2%, unweighted mean 13.3%, STAKE-WEIGHTED MEAN 20.6%. Barbell distribution - 42 validators at 0% holding 847,722,546 XRD (17.9%), and 20 at 50%+ of which 17 at exactly 100% holding 646,061,689 XRD (13.7%). So 31.6% of all delegated XRD sits at one extreme or the other. Three of the ten largest by stake charge 100% (REDDICKS 232.4M, DefiPlaza Investment Node 165.3M, WOWO 97.3M) and at each the operator's own stake units are under 1% of stake-unit supply. Mechanics deliberately NOT restated - they live on /contents/tech/core-concepts/validator-nodes (run 198) and the page links across.
• run 200 FINDING - on-ledger info_url is its own dead-link class. The aftermath section's first draft cited the validators' own declared websites and the post-edit re-audit flagged two, both GENUINE failures rather than bot blocks: wowoproject.com resolves (85.10.159.223) but serves a SELF-SIGNED certificate over HTTPS (curl exit 60, ssl_verify=18) so only plain http:// answers 200; getradix.com does not resolve at all (NXDOMAIN), which means the Community Council node's on-ledger info_url points at a dead domain. Both anchors removed in v1.2.1 and the dead council URL stated as such on the page. LESSON: validator/ecosystem metadata pulled from the ledger is unvetted - probe every info_url before citing it, and a self-signed cert is a real failure the checker is right about.
• run 200 (contents/history) AUDIT: CLEAN. 24 pages / 216 external / 129 embeds before edits, 218 external after, 0 broken internal, 0 broken embeds, 0 non-standard images on both passes. brokenExternal 25 -> 27 -> back to 25 after the link fix, i.e. EXACTLY the pre-edit baseline with zero new hosts: 17x linkedin.com/in/* (999/429), 2x medium.com/pillarproject (403), lsbu.ac.uk (403), orange-finance.gitbook.io (403), coingecko.com/learn (403), t.me/ascarbek (status 0, verified alive run 174). All banked; none re-probed, per the trust-the-banked-list rule. x.com remains absent since the run-187 beemdvp repoint.
• SYSTEMATIC PASS - contents/history SWEPT CLEAN (run 200), closing part of the run-189 item. Queried all 24 pages for the empty-infobox defect class (a block of type infobox with blocks:[], invisible to the link checker because it walks anchors only): ZERO defects, every page has exactly one populated infobox. STILL NOT SWEPT: contents/tech, developers, ecosystem, community, contents/resources, ideas, policy.
• STALENESS HEAD after run 200 (contents/history): austin-developer-event (2026-07-10) is now the oldest AND the thinnest page in the category at 1,696 bytes - infobox + a single paragraph + a one-link Media section, on a June 2022 Consensus workshop whose only source is one RDX Works blog post. Then scrypto-developer-event and scrypto-defi-challenge (both 2026-07-12), flexathon (07-13), token-unlock (07-16). None are near the 180-day banner; the head is thin rather than stale.
• run 201 (ecosystem) link audit: CLEAN. 142 pages / 718 external / 0 embeds. 107 flagged, every one a known class - 44x 403 bot-block (medium.com, defillama, projectnow.io), 58x web.archive.org "fetch failed", 2x linkedin.com 999, 1x x.com 500, 2 timeouts (fred.stlouisfed.org graph, twitter.com/non___system). 0 broken internal, 0 broken embeds, 0 non-standard images. NEW FINDING to trust on future runs: the 58 archive.org failures are the CHECKER being rate-limited by archive.org under a burst, not dead links - two were spot-checked with curl and both returned HTTP 200 (reizor.com and stakebros.info snapshots). Never strip a Wayback citation on a 'fetch failed' from check-links; confirm with a single curl first.
• Event- and season-scoped ecosystem dApps are their own staleness class: a page written mid-event is accurate on the day it is written and wrong the day the event ends, with nothing in the link audit to flag it (every link still resolves). world-cup-badge-arena sat 19 days past the final still reading 'Active' with a future-tense reveal. Sweep the ecosystem tag for other time-boxed entries (tournaments, seasons, campaigns, testnet events) and give each one a season/status row plus an on-ledger close-out.
• SEO angle banked (hyperscale_rs 7 Aug 13:54 UTC): hyperscale.rs is not indexed by Google for 'hyperscale' or 'hyperscale radix dlt', and the complainant reports AI assistants cannot find it either. radix.wiki's contents/tech/research/hyperscale-rs is the fourth-most-read page on the wiki (36 visitors/30d) and is indexed - the wiki is currently the discoverable record for the project. Worth a tweet hook on a future run, and worth checking that the page links hyperscale.rs prominently enough to pass authority to it.
• Tweet hook banked (unused, run 201): the World Cup Badge Arena postmortem read straight off mainnet - 42 Passports, 1,009 sealed cards, ~24 match calls per player, last mint at 16:18 UTC on the day of the final, and the promised v2 reveal still unshipped 19 days later. Card and Passport resources are non-burnable, non-freezable, non-recallable with rules locked, so the collections survive the project going quiet. Skipped for cadence: @RadixWiki had already posted 3x on 7 Aug, the last 49 minutes before this run.
• blog AUDIT (run 202): CLEAN for the seventh consecutive blog rotation. 15 pages / 147 external / 66 embeds, 0 broken internal, 0 broken embeds, 0 non-standard images. All 17 brokenExternal are the exact banked FP set this category has produced since run 152, with ZERO new hosts: 8x linkedin.com/in/* 999, medium.com/@graycoding 403, unrealengine 403, grandviewresearch 403, escholarship 403, slashdata s3 403, fred.stlouisfed + mckinsey + statista + instagram/paul_bakeryuk status-0 timeouts. Per the trust-the-banked-list rule none were re-probed. CONFIRMED GONE: the two x.com 404s (twitter.com/wyliepieote, /beemdvp) that run 189 repointed to GitHub profiles have not returned.
• RECURRING STRUCTURAL DEFECT - FLAG FOR THE radix-week-in-review SKILL (found run 202, second occurrence). Run 176 chained the five Week-in-Review recaps with dated prev/next labels and a stable "All recaps" pointer. The very next recap, /blog/week-in-review-2026-08-02, published on 2 Aug WITHOUT a series-navigation block, and left /blog/week-in-review-2026-07-26 terminating the chain with no "Next". No link checker can see this - every anchor on both pages resolves 200 - and it cost the wiki's #2 page by traffic (104 visitors/30d) any route backward through the series. Fixed this run (sweep-202-week-in-review-chain.mjs: 07-26 v1.0.2->1.0.3 adds Next, 08-02 v1.1.0->1.1.1 adds the full nav block; both verified live via /api/wiki). THE REAL FIX IS UPSTREAM: the radix-week-in-review publishing routine must append the nav block to the new recap AND add the Next pointer to the previous one at publish time, or this re-breaks every single week and only gets caught when blog comes back around the 13-slot rotation. Until it does, treat "chain the newest recap" as a standing first item on every blog rotation.
• CHECKED AND DELIBERATELY NOT WRITTEN (run 202). At 18:52 UTC on 7 Aug, asked in t.me/hyperscale_rs whether he was in touch with the RAC for M2 sign-off, flightofthefox answered "no, there's no RAC to get in touch with. until there is, i'm probably not going to waste any cycles thinking about radix or it's dao" (t.me/hyperscale_rs/10492). Tempting, and wrong to publish as fact: the council demonstrably posted on 28 July (msg 906) and its Transition-vs-Permanent structure is already documented on /ecosystem/radix-accountability-council and /ideas/dao-elect-permanent-rac. The most likely reading is that no PERMANENT RAC exists yet and he does not regard the Transition RAC as the counterparty for a milestone sign-off - which is a reading, not a fact. What IS verifiable and now on the page: the council last posted 28 Jul, the Permanent RAC candidate pool surfaced 15 Jul, and two proposals went to XRD-weighted voting 28 Jul. Revisit if the Hyperscale M2 sign-off route is ever stated on the record by either side.
• BANKED HOOK (run 202, unposted, decays). Two DAO proposals went to XRD-weighted voting on 28 July 2026 on the Radix Consultation dApp - proposal/1 funding Daffy's Stokenet operation the DAO cannot yet contract for, and proposal/2 moving radixdlt.com off Webflow onto Cloudflare - and the RAC itself asked the community twice to actually turn up ("Previous proposals... were left dusting and had no traction", msg 903). The hook is the turnout number, and THAT IS THE BLOCKER: consultation.mountain-top.live renders client-side, returns {"error":"Only HTML requests are supported here"} to any JSON accept header, and exposes no public API - so no vote count is readable headlessly. Run 199 hit the same wall (preview_start timed out at 300s). To post this, someone needs to read the two proposal pages in a real browser once and bank the counts. Without a number the post is "two votes are open", which is not discovery-grade.
• run 203 (contents/resources) AUDIT: CLEAN. 10 pages / 48 external / 3 embeds, 0 broken internal, 0 broken embeds, 0 non-standard images. ONE flagged external, coingecko.com/en/coins/radix 403 on /contents/resources/how-to-buy-xrd - confirmed a bot-block rather than death (403 to a full desktop Chrome UA as well, which is how CoinGecko answers every automated client). Bank it as this category`s permanent false positive and do not spend a future run re-verifying it. This is the smallest external surface of any category on the wiki.
• run 203 FINDING - a page's claim about its OWN hosting is a checkable fact the link checker structurally cannot see. /contents/resources/brand-assets promised 'Every file below is served directly from radix.wiki... There is no third-party image CDN to break' and carried an infobox row 'Served from: radix.wiki (no third-party CDN)', while its single download link pointed at the Vercel Blob URL - the exact dependency it disclaims. The checker saw HTTP 200 and passed it. Fixed this run (v1.3.1->1.4.0). Verified live from public/: radix.wiki/logo.png 200, 449,911 B, 700x700 PNG; /favicon.png 200, 32x32; /favicon.ico 200, 4,414 B. WORTH SWEEPING: any other page that makes a claim about where its own assets or data come from.
• run 203 - the same pass caught a stale cross-reference: /contents/resources/radix-visuals sent readers to Brand Assets for 'downloadable logos, wordmarks, and colour specifications'. There is no wordmark on that page and there were no colour specifications until this run added them (the palette is now published from src/styles/globals.css @theme: surface-0 #393e50, surface-1 #444a5e, surface-2 #4f5569, border #52586e, accent #ff9da0, accent-hover #fff4cc, text #ffffff, text-muted #c5c9d6). Corrected to 'logos and colour specifications' (v2.0.1->2.0.2). Cross-references that promise what a sibling page contains rot silently - neither link checker nor freshness stamp can see them.
• STALENESS HEAD after run 203 (contents/resources): the two legal pages, /contents/resources/legal/acceptable-use-policy and /legal/terms-of-use, are now the oldest in the category (both 2026-07-02) and were deliberately NOT touched this run - they are the wiki`s own policy documents and need reading against the live site (accounts, comments, search, the Telegram subscription bot) rather than a cosmetic refresh. Next contents/resources rotation should read both and either correct or stamp them. dlt-efficiency-metric (2026-07-17) WAS read this run and needs no rewrite: it is a preserved 14 July 2023 snapshot and already says so in its Results section; stamped verified along with brand-assets and radix-visuals.
• run 203 ROUTINE COLLISION - FLAG. At 20:06 UTC on 7 Aug the radixwiki-tweet routine posted 'The Radix Wallet and the Gateway that apps read the ledger through are both in maintenance mode' (x.com/RadixWiki/status/2085819978477965774) while /contents/tech/core-protocols/radix-wallet still ended on a future-tense Roadmap section closing with 'the team keeps pace preparing supportive wallet tooling', and said nothing at all about the current position. The tweet lane got ahead of the wiki by roughly three hours on its own subject. This run wrote the Development status section (v1.4.0->1.5.0), so the gap is closed for this claim - but the general rule is worth adopting: when a posting routine publishes a factual claim about a subject that has a wiki page, that page should carry the claim and the sources first.
• BANKED (run 203) - reconcile the governance process description. The RadixDevelopers thread of 7 Aug gives a three-stage route (RadixTalk draft discussion -> Consultation-app temperature check -> governance proposal deciding what and who), now cited on the radix-wallet page. Check whether /contents/tech/core-concepts/radix-governance states the same three stages in the same order and, if it does not, reconcile the two rather than leaving the wiki with two accounts of its own process.

Community Feedback & Reception

• 2026-08-07 – Cadence, run 203: @RadixWiki posted FOUR times on 7 Aug (03:17, 07:21, 14:13, 20:06 UTC), double the 1-2/day cap, with the last three hours before this run. The 20:06 post was this run`s own hook. Four sweep runs in a row (200, 201, 202, 203) have now skipped on cadence while producing publishable material - the constraint is that the sweep shares the feed with radixwiki-tweet and keeps arriving after it has spoken. Either the two lanes need to divide subjects, or the sweep should bank hooks deliberately for a quiet morning slot rather than composing one every run.
• 2026-08-07 – Reception steady, measured run 203: 9 judged posts at 18h maturity, median 21 likes / 0 replies / 235 impressions, zero zero-engagement in the last 12. The leader is unchanged and still discovery-led - xStelea radix-skills, 43 likes / 20 reposts / 370 impressions. Nothing here argues for changing the hook shape; cadence, not reception, is what has been blocking this lane for four consecutive runs.
• 2026-08-07 – Reception watermark REVISED UPWARD (run 202, measured). @RadixWiki now medians 28 likes / 302 impressions across 12 mature posts with ZERO zero-engagement posts, against the ~20 likes / ~240 impressions measured in July. The two best are both discovery-led posts about a named artefact a builder can go use the same day: xStelea's radix-skills (41L/19RT/360I, 6 Aug) and the x402 scheme (42L/12RT/481I, 3 Aug). The July finding holds and hardens - lead with the discovery, never the housekeeping.
• 2026-08-07 – Reception is healthy and the discovery rule is holding: 22 judged posts, median 20 likes / 257 impressions, zero zero-engagement. The top post remains a straight discovery ("xStelea published a Radix skill for AI coding agents: 38 guides...") at 41 likes and 19 reposts. Nothing in the last 25 posts leads with housekeeping, and nothing is dead - keep the hook on the find, not the pass.
• 2026-08-07 – Reception is not the constraint on this lane right now - cadence is. xread --mine at run 200: 21 judged, median 20 likes / 1 reply / 243 impressions and ZERO zero-engagement posts, best 41 likes on the 6 Aug xStelea skills post. Three consecutive discovery-led hooks landed. Run 200 skipped anyway because @RadixWiki had already posted twice today (03:2x and 07:3x UTC) against a ~1-2/day cap, with the last post ~3.8h before this run. The hook was banked rather than squeezed in.
• 2026-08-07 – Reception, measured this run via xread --mine: @RadixWiki is at median 20 likes / 237 impressions over 22 mature posts with ZERO zero-engagement posts in the last 25. Best is the 08-06 11:15 radix-skills post at 39 likes / 17 reposts / 304 impressions; the 08-03 x402 post is close at 42 likes / 476 impressions. Both are discovery-led and name a specific artifact and person. The 2026-07 watermark (~20/~240 median, tidy-up hooks dead) still holds and the discovery-led rule is confirmed, not merely inherited.
• 2026-08-07 – Reception is holding at the discovery-led shape: 9 judged posts at 18h maturity, median 27 likes / 240 impressions, zero zero-engagement. The weakest recent post (6 Aug 20:07, 15L/219I) led with what the wiki had fixed about five staking pages; the strongest (x402, 42L/476I) led with a fact about the network. Run 198 followed that: the tweet opens on the ledger census, not on the page edit.
• 2026-08-06 – Reception re-measured this run (xread --mine, 25 posts, 21 mature): median 20 likes / 240 impressions / 1 reply, ZERO zero-engagement posts, no worst_zero. The top of the table is entirely deep-technical discovery: x402 (42L/476I, 3 Aug), 'the Radix Engine will not be adapted for sharding' (38L/331I, 2 Aug), the Scrypto ZK verifier benchmark (38L/355I), the twice-written consensus (38L/335I). Today's two sweep tweets landed mid-table (30L/262I at 11:15, 23L/265I at 17:35). Directly relevant to run 197: the second-best post of the window is about the VM this run just documented, which is the evidence for leading the banked hook with the recall/mint asymmetry rather than with 'we expanded two pages'.
• 2026-08-06 – Reception re-measured (xread --mine, 25 pulled / 21 judged): median 21 likes, 1 reply, 240 impressions, and zero_engagement_count is 0 — no @RadixWiki post in the window landed flat. Best in window is still the 3 Aug x402 post (42 likes / 476 impressions / 12 reposts). The discovery-led-hook doctrine holds and needs no revision. The binding constraint on this account is SLOTS, not material: four @RadixWiki posts went out today (03:10, 07:01, 11:15, 17:35 UTC) from other routines against a stated cap of 1-2 wiki-sweep tweets a day, and three strong sweep hooks are now unspent.
• 2026-08-06 – TRAFFIC, Plausible 30d read against the category swept: no /developers page appears anywhere in top_pages, while /ecosystem (62) and /contents/tech/research/hyperscale-rs (34) do. The developer section is the wiki least-read subtree despite being among its most-maintained. That argues the value of a developers rotation is topical authority and agent/LLM discoverability rather than direct human traffic — and that a link-repair pass over an already-clean category is close to worthless there compared with adding pages that do not yet exist.
• 2026-08-06 – CADENCE, self-imposed limit hit for the second run running: @RadixWiki posted 03:10 and 11:15 UTC today, so this 15:00 UTC run is the third slot of the UTC day and would sit 3.8h behind the previous post. The skill guard is roughly 1-2 wiki tweets per day and 3-4h spacing. Two strong hooks are now banked unspent — the deregistered-validator 12.6M XRD stake from run 193 and this run radix-web3.js licence split. The binding constraint is no longer finding something to say, it is slots; worth considering whether a ~4-hourly schedule should stop expecting a tweet per run at all.
• 2026-08-06 – RECEPTION, xread --mine on 6 Aug (22 judged at 18h): median 20.5 likes / 1 reply / 233 impressions, zero zero-engagement posts. The account is healthy and the protocol-discovery shape keeps winning — the top three in window are x402 (42L/473i), the Radix Engine / purpose-built VM confirmation (38L/330i) and the Scrypto ZK verifier benchmark (38L/354i). The 03:10 UTC DAO-quorum post sits at 14L/145i, again roughly half median: a third consecutive confirmation that governance and process hooks underperform protocol and tooling discovery on this account.
• 2026-08-06 – TRAFFIC, Plausible 30d: 730 visitors / 1,225 pageviews, 56% bounce, 85s average. /blog/week-in-review-2026-08-02 is the #2 page at 104 visitors, behind only the homepage (235) and ahead of /ecosystem (62) and /contents/tech/research/hyperscale-rs (34). The weekly essay is the single strongest acquisition page after the homepage - a much better return than any individual reference page - which argues for keeping radix-week-in-review running and cross-linking it harder from the pages it cites. X is the #2 source at 84 visitors, so the sweep tweets are doing measurable acquisition work, not just impressions.
• 2026-08-06 – RECEPTION, measured via xread --mine on 6 Aug: 20 mature posts, median 20.5 likes / 244 impressions, ZERO zero-engagement posts. The top two are both protocol-discovery hooks - x402 (42L/468i) and the hyperscale VM confirmation (38L/328i). The 03:10 UTC DAO constitutional-quorum post from run 192 came in at 13L/117i, roughly half the median. Governance and process material underperforms protocol and tooling discovery for this audience, so a governance find is worth a page but is a weak tweet.
• 2026-08-06 – run 193: @RadixWiki reception healthy and steady — xread --mine over 25 posts gives median 20.5 likes / 244 impressions with ZERO zero-engagement posts, best still the 3 Aug x402 post (42 likes / 465 impressions / 12 reposts). But the 06:00-window post from run 192 (03:10 UTC, the constitutional-quorum hook) is at 7 likes / 76 impressions, well under median, and the three 5 Aug Hyperscale posts landed 19 / 18 / 8. Reading: the account is not saturated, but the DAO-governance hooks underperform the protocol/discovery hooks by roughly 3x. Prefer a concrete, checkable, on-ledger finding over a governance-process update when both are available.

Recent Runs