---
title: "Wiki Maintenance Log"
url: "https://radix.wiki/contents/tech/operations/wiki-maintenance-log"
version: "1.250.0"
updated: 2026-08-28
license: CC-BY-4.0
license_url: "https://creativecommons.org/licenses/by/4.0/"
---

# 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](/policy/verifiability), [neutral point of view](/policy/neutral-point-of-view), [no original research](/policy/no-original-research), [notability](/policy/notability), [conflict of interest](/policy/conflict-of-interest), and [freshness](/policy/freshness) – the last of which sets the 180-day re-verification window this log exists to keep.

## Current Status

|  |  |
| --- | --- |
| **Next category in rotation** | contents/resources |
| **Rotation order** | ecosystem → developers → ecosystem → contents/tech → ecosystem → community → contents/history → ecosystem → blog → contents/resources → ecosystem → ideas → policy |
| **Last run** | 2026-08-28 |
| **Total runs** | 318 |

## Signal Watermarks

|  |  |  |
| --- | --- | --- |
| **Source** | **Last checked** | **Note** |
| telegram | 2026-08-28 | run 318: 122 messages over two days, all of them hyperscale_rs, and not one publishable fact. The overnight thread (10987-11006, 28 Aug 01:5x-02:5x UTC) is a philosophy argument about whether delegators should pick validators at all or press an easy button, with no dated claim, no source and no named mechanism. The three substantive items above the watermark were all already banked at runs 313/315: 10891 on the Charter implying 21-25 days and still in August, 10893 asking flightofthefox about babylon-ledger-app compatibility (still unanswered), 10878 on M2 landing ahead of schedule. RadixDevelopers and RadicalVibing returned nothing in the window. |
| web:miow | 2026-08-15 | run 244 — the ecosystem staleness edit’s spine, read at three public artefacts. sitemap.xml lists eleven published sites, ALL as miow.me/s/ and none as a subdomain; /s/blockspace-capital returns 200 while blockspace-capital.miow.me does not resolve (curl 000); llms.txt gives the 100K-XRD one-time price, the Stripe fiat path, the thirteen Formant parameters and a twelve-type block list that includes gallery and omits footer; /guide is the self-host route (download the Next.js project, Supabase + Vercel + custom domain). |
| plausible | 2026-08-28 | run 318: 1,781 visitors / 1,534 pageviews / 46% bounce / 42s over 30d, the first movement in six reads (+49 visitors, +35 pageviews, bounce 47->46). Order of top_pages unchanged: / 319, /api/mcp 259, /ecosystem 122, /blog/week-in-review-2026-08-02 116, /blog/week-in-review-2026-08-09 76, /contents/tech/research/hyperscale-rs 64. top_sources Direct 1491, X 152, Google 63, Reddit 32, Bing 16, DDG 10. NOTE the rotation alignment: TWO of the six busiest pages are /blog week-in-review issues, so blog is a higher-traffic category than its 19 pages suggest. The visitors-above-pageviews inversion banked at run 316 persists and is still a helper bug, not real traffic. |
| web:3syde | 2026-08-25 | run 304 re-probe, unchanged from run 297 and now dated on the page. www.3syde.com 200 / 22,491 B, still rendering SOON over the same feature copy; 3syde.gitbook.io/3syde 200 / 318,497 B; x.com/3SydedApp 200 / 178,236 B; github.com/3SydeApp 200 / 186,815 B but api.github.com/users/3SydeApp/repos returns an EMPTY ARRAY, so the account holds no public repositories. |
| web:foton | 2026-08-17 | run 261 (NEW SOURCE): foton.is answers 200 / 18,330 B and is a static site — its only outbound destinations are Discord, t.me/FotonMarketplace, @FotonSDK and two Tally application forms; no marketplace application is linked, and foton-token.html / seasons.html / tesseract-nft.html all 308. The Discord invite it advertises resolves live: guild "Foton", 358 members, 21 online. That reachability is what the page’s 🟢 Active now rests on. |
| web:vyrol | 2026-08-24 | run 299 - NEW SOURCE KEY. vyrol.io 302s to www.vyrol.io/landing, 81,632 B: an independent B2B video product ("B2B video software for sales and customer teams") with its own pricing, templates, CRM campaign tooling and blog, no Radix content anywhere. Run Fly carries "Powered by Vyrol" in every page footer, so the render engine is bought in and only the wallet connection, the per-render price and the on-ledger settlement are native. A dependency the token supply does not insulate. |
| web:arkhia | 2026-08-24 | run 297: arkhia.io 200 / 325 KB and arkhia.io/chain-endpoints 200 / 237 KB, 24 Aug 2026. Alive and shipping (x402 facilitator, MCP tools, ZK proofs, BigQuery ETL, Google Cloud Marketplace), and Hedera-specific where it names a network at all - Hedera Explorer and Hedera Metrics in the nav, nine 'hedera' occurrences, ZERO 'radix'. The chain-endpoints page sells bespoke endpoints without naming a chain. This kills the wiki's standing claim that BCW 'built the Arkhia Web3 backend' as a Radix role. |
| web:atomix | 2026-08-23 | atomix.trade is a SvelteKit SPA whose host returns HTTP 404 with a byte-identical 9,607-byte shell for EVERY path, root included (200 only on /). /terms (dated 24 Oct 2025) and /my-apps both render in a browser. Its three check-links "deaths" are false positives. |
| web:hookah | 2026-08-15 | run 244: app.hookah.ing still linked as the live dashboard from a third-party production site. The July-2026 snapshot caveat on the repo is unchanged; what changed is that the HOSTED service now has an outside user on the record. |
| web:runfly | 2026-08-26 | run 310: runfly.app 200, and the site now carries a Play entry in its product nav for the "Pat the Fly" browser game ("Climb while your video renders"). Telegram 999469 (26 Aug 17:16 UTC) announces it as LIVE IN BETA. Not written: /ecosystem/runfly v1.0.0 already records "a browser game" in the arc it took from meme to product, so the beta stamp adds a date rather than a fact. |
| web:clarity | 2026-08-15 | run 246 - NEW SOURCE, and the run's spine. Clarity (clarity.community + the clarity.vote app) read four ways: the SSR marketing site is titled "Governance infrastructure for serious Cardano communities" with zero Radix mentions in 60 KB; the Next.js build manifest declares /cardano-governance, /cardano-dao-metrics, /cardano-treasury-withdrawals and Cardano mainnet/testnet metadata APIs and no Radix equivalent; /radix returns the same 6,387-byte 404 as an invented control path while /cardano-governance returns 200; and the Wayback tagline still read "Cardano, Midnight, and Radix" on 6 Aug 2025 ("Cardano and Radix" in Jan 2024). CDX over the domain: 1,169 archived URLs, Sept 2023 to Jul 2026, every organization route /organizations/cardano/. The 2026 homepage snapshots are client-rendered shells and carry no evidence either way - do not read their zero-Radix as a date. |
| web:igentix | 2026-08-19 | demo.igentix.app 200; /mcp 405 to GET (POST-only, same shape as the banked Gateway 405s). Runs entirely on Stokenet. |
| web:radlock | 2026-08-25 | run 304 follow-up to the run-302 rewrite, and it caught an error that rewrite introduced. x.com/beemdvp, used to credit founder Beem, is a REAL 404: probed from one client with one browser UA, x.com answered 200/209,490 B for /Slysmik and 200/250,716 B for /radixdlt against 404/24,900 B for /beemdvp, so it is an absent account and not the bot-block X normally returns. Repointed to github.com/beemdvp, which is 200, is named "Beem", and forks babylon-node, radixdlt-scrypto, Hyperscale, wallet-sdk, discourse-radix-connect and discourse-rola. |
| web:foton.is | 2026-08-20 | HTTP 200, 18,330 B on 20 Aug 2026. Webflow build stamp reads "Last Published: Tue Apr 25 2023 12:00:02 GMT+0000". /.well-known/radix.json returns the Webflow 404 page - no dApp definition. Site still links t.me/FotonMarketplace. |
| web:hashport | 2026-08-24 | run 297 - NEW SOURCE KEY, and the hardest fact in the rewrite. hashport.network 200 / 391 KB carries a wind-down notice at the top of every page: the bridge was PERMANENTLY DECOMMISSIONED on 31 MAY 2026 at 12:00 UTC, wrapped assets are permanently unredeemable, and no foundation or ecosystem entity can assist with recovery. BCW's own products page still lists and links Hashport as a live product - a live-link/dead-product pair check-links cannot see, because the link resolves 200. |
| web:mayanode | 2026-08-23 | run 279: /mayachain/pools 200 / 10,533 B (26 pools, no XRD). /mayachain/pool/XRD.XRD 404 / 72 B - and that 404 is CITED ON PURPOSE by /ecosystem/maya-protocol as the evidence the pool is gone. Do not repoint or strip it; see the deliberate-error-citation class in backlog. |
| web:nownodes | 2026-08-17 | run 258: NowNodes re-verified ALIVE and correctly key-gated - POST xrd.nownodes.io/core/status/network-configuration returns 401 with body "Unknown API_key" (15 B). nownodes.io apex 200 / 173,704 B. It is now the ONLY documented Core API provider still operating. |
| web:pytrends | 2026-08-26 | run 306 re-verification of /contents/resources/python-scripts/dlt-efficiency-metric's central claim, and all three numbers on the page still hold exactly. api.github.com/repos/GeneralMills/pytrends: archived true, open_issues_count 152, pushed_at 2024-08-10 (the archive push, not a code commit - the page's '22 April 2023' last-commit date is not contradicted by it). pypi.org/pypi/pytrends/json: latest 4.9.2, uploaded 2023-04-13. Page stamped rather than edited. |
| web:supre.me | 2026-08-14 | run 240 — NEW SOURCE. supre.me returns 200 (Wix, footer "©2021 by Supreme Stake"), publishes only the Olympia-format address rv1qt2mpw9j5av508e2f75q2pxhj04m5waerd5eafgrdvkapaxx3v0wxt36584, and states no fee. Its linked status page, supremestake.statuspage.io/api/v2/status.json, reads "All Systems Operational" from a record whose page.updated_at is 2021-09-21T10:24:26-04:00 — five years stale against a node with 70 missed proposals in the trailing month. t.me/SupremeStake resolves but exposes no title, description or member count, so it was not linked. |
| discord:foton | 2026-08-20 | Both invites on foton.is (WggGWQdJXn, Wbv55dEDFE) resolve to guild "Foton", 358 members / 18 online on 20 Aug 2026. Populated, but not evidence anyone operates the marketplace. |
| web:aave-docs | 2026-08-24 | run 298 - NEW SOURCE KEY, and the only real death in the contents/tech audit. docs.aave.com/faq/flash-loans 301s to aave.com/docs/faq/flash-loans and that path returns 404 (255,904 B Next.js 404 shell - note the SIZE, a 404 here is bigger than most live pages, so body size alone does not classify this host). The live equivalent is aave.com/docs/aave-v3/guides/flash-loans, 200 / 316,990 B, linked from the docs home nav. aave.com/sitemap.xml is itself a 404. Repointed on all four wiki pages that cited it. |
| web:bcw-group | 2026-08-24 | run 297 - NEW SOURCE KEY, and the spine of the ecosystem rewrite. bcw.group (WordPress, HTTP 200 / 584 KB) and bcw.group/products (200 / 273 KB) read 24 Aug 2026: 'SOC 2 Type II enterprise solutions firm and venture studio', six verticals (staking, AI, cloud, Web3 infra, ventures, partnerships), footer 'AICPA SOC II COMPLIANT / ISO27001 SELF-CERTIFIED', Google Cloud partner directory entry 200. The products page lists exactly four products - stakeFi, Arkhia, Hashport, HNS - all Hedera-facing. ZERO occurrences of 'radix' or 'xrd' on either page. Blockpour and TOKO are gone from the product list. LinkedIn is now /company/bcw-group2025 (the /bcw-group2019 URL run 108 repointed away from). |
| web:bobby.win | 2026-08-17 | Run 259: 200, 4,430 B, title "Home". info_url of validator_rdx1s0k2g57... (BobbyStake, ex-RADIATOR node). x.com/xrdbobby is "$BOBBY" and live. |
| web:crates.io | 2026-08-25 | run 303, the standing developers-rotation recheck, UNCHANGED from run 296 in every respect. scrypto / radix-clis / scrypto-test / radix-engine are all still 1.3.1, all published 2026-01-20, downloads 36,815 / 9,317 / 30,104 / 35,204. github.com/radixdlt/radixdlt-scrypto's newest RELEASE is still v1.3.1 (Cuttlefish), 2026-01-20; v1.3.0 before it is 2024-11-26. crates.io returns 403 to the link checker with a 247-byte text/plain body and is a banked bot wall, not a death - the JSON API answers fine. |
| web:defiplaza | 2026-08-27 | run 314 - NEW SOURCE KEY, and the run's spine. DeFiPlaza publishes an undocumented public endpoint at defiplaza.net/api/pairs (200 / 105,699 B, also served from radix.defiplaza.net): 156 pairs, TVL summing to $183,418.89, which confirms the wiki's undated 'roughly $183,000' to the dollar. Concentration: 148 pairs above $0, 127 above $1, 50 above $100, 17 above $1,000; newest pair created 20 Jun 2026. Every pair's `volume` field reads 0, so the endpoint gives TVL and nothing else. /api/stats, /api/dex, /api/tokens, /api/info, /api/overview and /api/volume all 404 (6,348 B), so the exchange dashboard's own cumulative figures are not reproducible from any endpoint that answers. api.llama.fi (NOT defillama.com, which is the run-253 Cloudflare wall) answers 200 and carries the per-chain series: Radix TVL $180,367 against Ethereum $7,673 at 06:32 UTC 27 Aug; lifetime volume $855,529,909 split Ethereum $845,994,781 / Radix $9,535,129; 30 days to 26 Aug, Ethereum $801 / Radix $119,685 in volume and $12 / $1,095 in fees. Four live first-party hosts the page never linked: docs.defiplaza.net (200 / 363 KB), stats.defiplaza.net/pools/radixplaza (200 / 129 KB), bridge.defiplaza.net (200), app.defiplaza.net/swap (200, the Ethereum app, still quoting 'Swap the most popular tokens for a 0.1% fee. 65% cheaper than Uniswap'). |
| web:ideomaker | 2026-08-14 | run 240 — WRITTEN, and the banked evidence turned out to be half the story. ideomaker.com is unchanged (200 / 42,080 bytes, Webflow build comment "Last Published: Fri Aug 06 2021"), is a five-page brochure whose Roadmap/Blog/Brandbook/Papers/Developers/Partners/Documentation nav all href="#", whose Log In and Sign Up read "Coming soon with Alpha", and whose staking widget reports "Staked XRD 0 Mil / Stakers 0". But radixnode.html led to the ledger: the team runs the Ideomaker Europe validator, which is registered, in the active set and holding 22.3M XRD. Status moved 🟠 Dormant -> 🟢 Active. Telegram invite live (109 members), Discord invite resolves to guild 461958471349305356 "ideomaker", and the page's only citation, youtu.be/3Wd-mxpU60M, is dead by oEmbed 404 while youtu.be itself answers 200 — which is why check-links never flagged it. |
| web:plausible | 2026-08-23 | run 288: byte-identical to runs 286 and 287 - 1,326 visitors / 1,147 pageviews / 48% / 36 s over 30d. The daily series is the part that moved: 40 and 44 on 14-15 Aug against 110 and 103 on 20-21 Aug. |
| web:radixlist | 2026-08-26 | run 307 - NEW SOURCE KEY, and the measurement that moved the page's status. radixlist.com 200 -> www (58,381 B, a SvelteKit BETA build - /_app/start-*.js and pages/__layout.svelte were removed in SvelteKit 1.0, Dec 2022 - fed by a Sanity CMS backend, project 451f7se3, which is why the catalogue grew long after the front end stopped being rebuilt). Front page reads 'Found 272 results' across 14 pages of 20. Footer credits 'Chris \| pica.finance' (t.me/chris_pica) and 'Kansuler' (t.me/Kansuler), confirming the wiki's creator claim from the site itself. Submission path live: forms.gle/2j8qjK73kywAzoJk9 200 / 34,892 B and /promote 200. pica.finance 200. |
| web:radixtalk | 2026-08-26 | run 307 - the standing watch became the edit. The forum's public Discourse API is a full liveness instrument and this run read four endpoints of it. /about.json: 700 topics, 6,206 posts, 633 accounts; last 30 days 3 topics / 21 posts / 14 people posting; last 7 days ONE post. /categories.json: 13 top-level categories, Chat/Discussion largest at 152/1,500. /categories.json?parent_category_id=46: Governance carries TWO subcategories the wiki had never recorded, Radix Community DAO (id 52) at 32 topics / 575 posts and ILIS DAO (id 51) at 5 / 39 - so governance plus subcategories is 67 topics / 875 posts, 58% of Chat/Discussion's volume and the deepest per-topic discussion on the site. /latest.json dates the newest topic to 17 Aug (2327, a validator reporting node v1.3.0.5 broken, no replies). The clause 8.7 watch reads ABSENT for another rotation. |
| web:rswap-dex | 2026-08-19 | run 273 - NEW SOURCE KEY, and the corroboration behind the reddicks rewrite. dex.reddicks.meme 200 / 166,660 B, title 'RSwap', redirects to /liquidity/add. The interface reports $231K TVL and $15,960.60 of 24h volume across ~10 pools at a 1.0% fee; the pool list names hUSDC/XRD ($88,121), LSULP/DCKS ($39,866), hWBTC/XRD, hETH/XRD, hUSDC/DCKS, hUSDT/XRD, VBT/DCKS, hWBTC/DCKS and DELIVER/DCKS. The page's HTML names Astrolescent 126 times and DefiPlaza 6 - the routing collaboration announced at 998767 is already in the shipped front end, not just in the announcement. |
| wiki:comments | 2026-08-28 | run 318: 4 comments, newest 2026-04-05. Unchanged for the 78th consecutive run. |
| onledger:lsulp | 2026-08-19 | run 273 re-read, and THE SUPPLY IS FALLING. resource_rdx1thksg5ng70g9mmy9ne7wz0sc7auzrrwy7fmgcxzel2gvp8pj0xxfmf at epoch 336,462 / state version 552,173,832 (19 Aug 2026 23:08 UTC): total supply 263,942,458.903028081635868881, down from run 270's 267,774,125.704949386966709152 at 11:06 UTC the same day - 3,831,666.80 units redeemed, about 1.4%, in twelve hours. Authorities unchanged and still locked (freezer/recaller deny_all immutable, mint/burn behind a component badge, rules_locked true). Re-read every ecosystem rotation: this number, not the website, is the wind-down's clock. |
| web:acuiq-llms | 2026-08-27 | run 314 - NEW FALSE-POSITIVE CLASS, and the only probe the ecosystem link list cost this run. check-links flagged acuiq.com/llms.txt at status 0 / timeout, the single flag in the whole category with no banked class. The apex answers 200 / 42,424 B instantly; /llms.txt answers 200 / 19,509 B but takes 18.0 SECONDS, past the checker's timeout, and its headers say why: server Vercel, age 106, a dynamically generated text/plain body with a computed etag. THE CLASS: a DYNAMICALLY GENERATED llms.txt is slow enough on a cold function start to present as a dead link. It matters beyond acuiq because this wiki serves its own /llms.txt the same way. |
| web:caviarnine | 2026-08-21 | run 284 SUPERSEDES the run-282 three-probe wind-down watch, and the answer came from the team rather than from a probe. t.me/caviarxrd/70246 (21 Aug 12:41 UTC, "Tronn \| CaviarNine"): "We are not switching the DEX off. The smart contracts stay live on ledger. What changes is our website: it will be replaced with a simple sunset page, no backend, supporting remove LP only." So the probe that mattered was never going to be a status code on caviarnine.io - the site staying up proves nothing and the site going down would prove less. The component addresses are the thing to watch. |
| web:delphibets | 2026-08-26 | run 310 - NEW SOURCE KEY and the run lead. delphibets.com answers 200 (35,182 B) on 26 Aug 2026, footer still reads V1.5, and the Open-bets filter returns "There are no Open bets" - an EMPTY book, not the "limited active markets" the wiki had. The same page publishes a lifetime figure the wiki never carried: 6,964,221 XRD of total bet volume. Dashboard is wallet-gated. |
| web:grove.city | 2026-08-17 | run 258 - NEW SOURCE, and the run lead. www.grove.city returns 200 / 13,540 B and it is a wind-down notice: "Thank You & Farewell \| Grove ... Grove is winding down. After nine years, this is goodbye." Signed by Arthur Sabintsev (CEO), Fred Teumer (CIO), Daniel Olshansky (CTO). Founded 2017 as Pocket Network Inc.; the Grove Portal "settled more than a trillion requests across 60+ blockchains". ZERO mentions of Radix on the page. DNS is the operative finding: on BOTH 8.8.8.8 and 1.1.1.1, portal.grove.city, rpc.grove.city and radix-mainnet.rpc.grove.city return NO records, while grove.city / www.grove.city resolve to Cloudflare. The Chainstack migration guide dates the farewell note to July 2026 but that is a competitor secondary source and archive.org CDX 503d on three attempts, so no closure month is asserted on the wiki. |
| web:juicystake | 2026-08-17 | run 254: check-links reported https://juicystake.org/ as 'fetch failed' and it is a false positive - the apex 301s to http://www.juicystake.org/ which serves a 70 KB WordPress site, and https://www.juicystake.org/ answers 200 directly under a valid *.juicystake.org certificate (expires 17 Sep 2026). The only real oddity is that the apex redirect drops to plain http; not worth an edit, banked so the next pass does not re-probe. |
| web:liquifyxrd | 2026-08-21 | run 284 SETTLES the second run-282 suspect as a FALSE POSITIVE, using the run-273 vercel-error-headers key. www.liquifyxrd.app and the apex return 403 with a 59-byte body and the header x-vercel-mitigated: deny - Vercel bot mitigation on a LIVE deployment, the opposite of leafnode.info's DEPLOYMENT_PAUSED on the same platform with a near-identical body size. Body size alone would have called these two the same; the header separates them. Do not re-probe. |
| web:notix.live | 2026-08-15 | run 244: the run-242 credit re-read straight out of the served HTML — "Webhook services provided by Hookah" in the footer. Now published on /developers/tools/hookah as its first named production consumer. |
| web:rdap-trove | 2026-08-20 | run 279 - NEW SOURCE KEY, and it REVERSED the banked run-276 call. RDAP (rdap.identitydigital.services/rdap/domain/trove.tools, 20 Aug 2026) shows trove.tools registered through NameCheap 4 Jul 2023, PAID TO 4 JUL 2027, client transfer prohibited, still on nelly/nico.ns.cloudflare.com, and LAST CHANGED 12 AUG 2026 - eight days before the check. A 404 front end plus a renewed, freshly-touched registration is Dormant, not Closed. |
| web:reizor.com | 2026-08-22 | run 286 - NEW SOURCE KEY, and the half of the Reizor finding that is not on the ledger. reizor.com serves HTTP 200 / 43,341 B, title 'Reizor', describing itself as 'A premium music ticketing platform' with Search / My Tickets / My Resale Earnings / Organizer Dashboard routes - the reassignment the page already claimed, now measured rather than asserted. www.reizor.com 301s to the apex. THE FINDING: the token's on-ledger icon_url, https://reizor.com/cryptologo/logo.png, answers 200 with 43,474 bytes of content-type text/html - the new owner's SPA catch-all, served where a PNG should be. `file` confirms HTML, not an image. So every wallet rendering $RZR fetches a stranger's website. |
| web:shardspace | 2026-08-14 | run 242 — NEW SOURCE, and the staleness edit's spine. shardspace.app 200, launch.shardspace.app 200, docs.shardspace.app 200 (GitBook, llms.txt indexes 47 pages of which ELEVEN are still "COMING SOON!" placeholders — the top-level guides for connecting a wallet, staking, swapping and token creation, whose sub-pages do carry instructions). docs/roadmap.md is still the 2023-24 roadmap verbatim ("November 2023 - Babylon MVP Launch" -> "Q2 2024 +"); the two Q1 2024 features (Ecosystem Insights, Network Explorer) have no delivery announcement. Blog newest post 17 June 2025, and its recent posts are guest ecosystem pieces (Felix_xrd), not product news. t.me/ShardSpace 311 members / 15 online. docs/the-team.md spells the founder "Andrew (avaunt)", not "Avant". |
| onledger:lucky8 | 2026-08-16 | run 254: validator_rdx1sw2…ey6g7zam re-read at epoch 335,550/335,551. is_registered true, accepts_delegated_stake true, validator_fee_factor 1 (100%) with validator_fee_change_request null - no divergence, unlike the run-235/251 census cases. stake_xrd_vault 7,972,823.82 XRD, rank 81 of 188 registered and inside the 100-strong active set at 0.167% of active stake. pending_xrd_withdraw_vault 186,287.25 XRD; locked_owner_stake_unit_vault 1,116.43 stake units against 26 queued owner withdrawals of ~1,400 units each, one per ~288 epochs (a day) running out to epoch 343,385 - a rolling ~four-week unlock pipeline, which is what a 100% fee looks like from the ledger side. |
| onledger:whynot | 2026-08-17 | run 261 (NEW): $WHY resource_rdx1t4hz8ag…22220pts3c — fixed supply 999,000,000, minter deny_all, rules locked, epoch 335,887. Last transaction affecting the resource is txid_rdx13s98epl74n5…wlf5q526zmq, 5 Jun 2025, a 1,000,000 $WHY transfer out of one account. Ociswap pool TVL $0.63, price identical at now/24h/7d. |
| web:bondefi.xyz | 2026-08-17 | Run 259 re-probe: api.bondefi.xyz still 502 (6,405 B Cloudflare page). Unchanged since run 251. |
| web:crumbsup.io | 2026-08-16 | run 251 - NEW SOURCE. crumbsup.io 301s to www and serves 1,799 B: a live Stencil single-page app, title 'CrumbsUp', description 'a Hub for DAOs in the Radix ecosystem', with a Google tag. The shell is small because the app is client-rendered, not because the site is a stub - the run-244 route-manifest method's lesson applied in reverse. Platform site alive; the validator's stake is what moved, not the site. |
| web:github-oter | 2026-08-09 | run 211 - NEW SOURCE. github.com/OTER-Labs is a one-repo org: radix-tally-verify, Apache-2.0, created 4 Aug 2026 23:32Z, last push 7 Aug 20:34Z, 7 commits, 0 stars. It is the independent verifier the 8 Aug disclosure promised "within the week" and, in the same post, said had already been open-sourced. The post carries no link to it. Commit fbe48e1c (6 Aug) "Majority Judgment settles at three-fifths, not the median" and a0cd9d51 (7 Aug) "the LSULP leg - tally document v16" date the moving parts. |
| web:mexc-status | 2026-08-23 | run 291 - NEW SOURCE KEY, and it is a WALL rather than an answer. MEXC's own currency/withdrawal-status surfaces refuse automated requests: www.mexc.com/api/platform/spot/market-v2/web/currency/details and /api/operateactivity/announcement/search both return an Akamai 'Access Denied' HTML page, and api.mexc.com/api/v3/capital/config/getall is key-gated. So the CAUSE of the 22 Aug dislocation (a reported wallet-maintenance window) is not verifiable from the venue and was published as attributed community claim only. The market endpoints api.mexc.com/api/v3/ticker/24hr and /depth are open and unauthenticated - the measurement never needed the wall. |
| web:nestfinance | 2026-08-17 | run 261: the domain hunt closed off rather than resolved. nestfinance.xyz now answers 200 as "Nest Pilot", an M-Pesa vendor ledger with no Radix connection (Wayback: 3 captures, the 2025-02 one a 114-byte stub, the 2026-06-11 one already Nest Pilot); nestfinance.io has exactly 2 Wayback captures, both 2022, i.e. before the Radix project; nest.finance still fails TLS. Nest Finance is on no DefiLlama Radix listing and is absent from the official radixdlt.com ecosystem directory. Still no primary source for what it shipped or when it stopped. |
| web:radixplanet | 2026-08-26 | run 307 - NEW SOURCE KEY, and it CONFIRMS the page rather than correcting it. radixplanet.com 200 / 22,051 B renders 'RadixPlanet - Dashboard' with Total Value Locked '---', Total Trades '---', Liquidity Pools 78, Tokens 95, and an Alerts Center whose newest entry is dated 31 DECEMBER 2023. The page's existing status line ('dApp still online but frozen (last activity dated Dec 2023; no live TVL or trades)') is exact. Stamped, not edited. |
| web:radquest.io | 2026-08-20 | run 278 - NEW SOURCE KEY, and THE RUN LEAD. The domain answers 200 with 4,730 bytes, which is why every status-code check has passed it: the body is Namecheap's expired-domain lander (section id="expired-banner", heading "Domain registration has expired", last-modified 30 Jul 2026) and DNS now points at ns1/ns2.lander.d.parity.domains. WHOIS: registrar expiration 2026-08-10T10:36:18Z, updated 2026-08-12, registry expiry rolled to 2027-08-10 under autoRenewPeriod (the .io post-expiry grace, not a renewal by the operator). app.radquest.io does not resolve; /quests 404s. Wayback CDX has nothing after Mar 2025, so the lapse is undated in the archive and only WHOIS carries it. |
| db:banner-census | 2026-08-19 | run 269 - NEW SOURCE KEY, and THE RUN LEAD. One jsonb_path_query over all 363 pages counts editor-placed banner blocks: FIVE, on five pages (1.4%) - stub x2 (contents/tech/core-protocols/application-layer, kernel-layer), promotional x3 (ecosystem/blue-chick-nfts, unisci, unix). FOUR of the six variants have never been placed: unsourced, outdated, cleanup, coi. The [citation needed] span appears on exactly ONE page - /policy/verifiability itself, in its own examples. Not for want of candidates: 40 of 361 non-hub pages hold under 1,500 characters of prose and 25 under 1,000, and the two carrying a Stub notice are not in the shortest ten. Authorship explains it: 1,503 revisions in the 90 days to 19 Aug from 7 accounts, 1,478 of them (98.3%) from AUTHOR_ID cmk5t48vx… , the sweep's own account. A banner is a message to the next editor and the next editor is the same pass. |
| onledger:phoenix | 2026-08-14 | run 242: PHOENIX NODE + $PHNX re-read at epoch 334974/334975 (14 Aug 2026 19:05-19:11 UTC) and it CORRECTED the page. total_supply 529,508,843.548 against 529,758,843.55 on 1 Aug — 250,000 PHNX burned in the fortnight, so "the burn is finished" was wrong. Validator still registered:false; delegated stake 7,595,958.862510990299957534 XRD, down 211,074 from 7,807,033. validator_fee_change_request new_fee_factor 1 (100%) at epoch 297632 against a live fee_factor of 0.1 — inert while unregistered, live on re-registration. |
| web:allnodes.com | 2026-08-22 | run 289 - NEW SOURCE KEY, and the run's finding. allnodes.com/xrd 200 / 3,841,842 B: the protocols table lists Radix XRD at 14.00% APR (market cap $12M, price $0.00088) and the site banner reads "0% fees". On-ledger the same operator charges a 5% validator fee, and 14% is more than double the 6.40% the emission schedule can pay. allnodes.com/xrd/staking 200 / 3,090,729 B is a wallet-select flow that quotes no rate; it is the validator's declared on-ledger info_url. The APR figure is client-rendered into a large protocol table - grep the raw HTML for the row, WebFetch summarises it away. |
| web:curedao-dfda | 2026-08-24 | run 298 - NEW SOURCE KEY, and it settles a status-0 flag as a FALSE POSITIVE with a live successor. app.curedao.org/?utm_source=desci-wiki reads status 0 to check-links but a browser UA follows it to app.dfda.earth/app/public/, HTTP 200 / 20,349 B - CureDAO now presents as dFDA (the Decentralized FDA). The link resolves, so nothing on /contents/tech/core-concepts/decentralized-science-desci is broken, but the anchor text names an organisation that has renamed. Not edited: that page is inside the standing DeSci FLAG FOR A HUMAN (the cluster migrated to the Caper wiki and the page own future is a human call). |
| web:github-muhaj | 2026-08-20 | run 275 - NEW SOURCE KEY, and the only real death in the category. github.com/muhaj/aiin (AI Invest, Advanced Track Silver at Radix Wiki Hackathon #1) returns a genuine GitHub 404 - 304,768-byte body, browser UA, redirects followed. The account is alive: api.github.com/users/muhaj is Jetnor Muhaj, 112 public repos, created 2014, and matches the linkedin.com/in/jetnormuhaj already cited on the same page - but none of the 100 most-recently-pushed repos is a successor, and the Wayback CDX for github.com/muhaj/aiin* returns an EMPTY array, so the URL was never captured. Nothing to repoint to; unwrapped on both pages that carried it. |
| web:midgard-maya | 2026-08-15 | run 244: mayanode.mayachain.info ANSWERED this time (200, 10,527 B) after run 242 timed out twice. /mayachain/pools returns 26 pools and not one is XRD — unchanged from runs 229 and 234, so /ecosystem/maya-protocol stands as written. Bank the corollary: the page cites /mayachain/pool/XRD.XRD, and its 404 IS the citation working, so the checker will flag that URL forever. |
| web:mountain-top | 2026-08-25 | run 300 re-probe, +48h after run 293 and four days before the 29 Aug decision date. UNCHANGED and now three days past expiry: the certificate still reads notBefore 24 May / notAfter 22 Aug 2026 13:47:56 UTC, curl -k still returns 200 / 9,538 B (byte-identical), curl without -k returns 000, and api-consultation.mountain-top.live still 404s at root with a 13-byte body. check-links reports all three consultation.mountain-top.live URLs on /community/daffy as status 0, which is the TLS refusal and not a death. No links rewritten, per the run-293 instruction to leave the 20 citations alone until (1) resolves. |
| web:nest-finance | 2026-08-18 | run 267 - NEW SOURCE KEY, and the whole evidence base for the ecosystem rewrite. Nest Finance read at five artefacts because it has no site. X @NestFinance_ (via r.jina.ai; x.com itself 402s): account joined March 2024, 32 followers, FIVE posts across three days - 4 Mar the four-part "What is Nest Finance?", 5 Mar a GM, the Gitbook announcement and an @XRDdomains name, 6 Mar a Google Form for beta testers. Nothing in the 29 months since. t.me/NestFinancee: 13 members, no posts, and its channel bio is word for word the paragraph this wiki page carried. nest-finance.gitbook.io is ALIVE and is the finding: llms.txt indexes 19 pages and TEN read only "Coming soon" (litepaper, every How To, Risks, rates, referrals, smart contracts, developer docs), and products/liquidity.md is one future-tense sentence - "Automated liquidity vaults will be Nest Finance first product, estimated launch in late Q2." The doc set is a rebrand of Kamino Finance's with two find-and-replace misses left published: nest-finance-points/overview.md heads "Nest Finance Points" over anchor id="kamino-points", and products/borrow-lend.md describes N-Lend then heads its next section "K-Lend Overview" (kamino.com/docs confirms K-Lend, Multiply and eMode as Kamino's). nestfinance.xyz is unrelated - the earliest Wayback capture, 22 Feb 2025, is already a registrar parking lander. api.llama.fi/protocols lists 25 Radix protocols and Nest Finance is not among them. |
| web:radix.stream | 2026-08-23 | run 295 - NEW SOURCE KEY, and the run lead. radix.stream 200 (Webflow, build comment 'Last Published: Mon Apr 24 2023 09:36:35 UTC'); /download-stream-wallet 200 / 12,347 B publishes the FULL release history the wiki had wrong: 1.0.0 (23 May 2022 beta), 1.0.1 (27 May 2022 beta), 1.2.12 (16 Apr 2023, .XRD Domains + RNS integration), 1.2.13 (24 Apr 2023, dApp QR login built for the then-upcoming Foton marketplace). The site was last republished the same day as its last release. The 'Stream Pro' roadmap is still advertised as upcoming three years on. feedback.radix.stream does not resolve (curl 000); t.me/StreamWallet and discord.gg/uZxMPvde9r both 200. Footer credit: Ideomaker SDK BV. |
| web:radixdao.org | 2026-08-18 | run 265 - re-read at the HTML rather than through a summariser, and the summariser got it wrong. The site says "A non-profit DAO, SOON registered in the Marshall Islands" - it does NOT claim registration is complete, so it does not contradict the wiki's pending MIDAO record. generator meta is Astro v7.2.0. /participate publishes the vote-weight rule (liquid XRD + validator LSUs + LSULP + eligible DEX LP, XRD-equivalent at a snapshot taken when each vote opens) and directs voters to vote.radixdao.org. /verify carries the register with the five live entries and five treasury accounts marked not yet deployed. |
| web:radixrolodex | 2026-08-14 | run 242: the standing embed watch, run through the Firebase backend rather than the widget (apiKey AIzaSyA0VhqB7EwtUAGxO1EOtM-yWjKmkgBH1lk, project radix-rolodex). All four deck-id embeds resolve: vf5trPBMoSQqJq4SYBlP "Radix Wiki - FOTON", D7yPu25MGR1GkFrGoBiX "Radix Wiki - ASTRL", ixDFx5ax0ZPvOxSPktBE "Radix Wiki - Ociswap" (all updated 2026-02-10) and l22Bmkh70rxJs6SyU0ut "Radix.Wiki - BlueBalls" (2026-02-14). Clean. |
| web:wider-crypto | 2026-08-01 | run 176: X search "(x402 OR CAIP) (Radix OR XRD)" – @radixdlt ITSELF posted the CAIP/x402 governance proposal on 31 Jul and it was retweeted across the ecosystem (luckynftxrd, JoeyShabadooJr, criptochain, AtlasStaking, Spiiderxrd, UlianovXrd, 3mul4t0r, eltondog123, luckyyxrd). Topic is saturated – see feedback. |
| telegram:ofc3syde | 2026-08-25 | run 304 - NEW SOURCE KEY, and it is a dormancy measurement rather than a signal. A 900-day scrape of t.me/ofc3syde returns 261 messages spanning 10 Oct 2024 to 23 Aug 2026 (ids 20217-20589) and NOT ONE is an announcement from the 3Syde team: the traffic is dice-roll bot commands, greetings, /report calls, recruitment spam and, most recently, Chinese-language data-broker spam posted 23 Aug and left in place. Published on /ecosystem/3syde. |
| web:blockshard.io | 2026-08-17 | Live: 200 / 101 KB, title "Blockshard - Validator and EigenLayer Operator", still lists Radix alongside Tezos, Ethereum, Moonbeam, Moonriver, EigenLayer, SSV and Avail. |
| web:ch-metabridge | 2026-08-27 | Metabridge Ltd 13476191: incorporated 24 Jun 2021 at 7 Bell Yard with Hughes and Ridyard as founding directors, SIC 70221. Jarrett dir 4 Oct 2021 to 14 Feb 2025. Ridyard terminated 17 Jun 2025, Hughes re-appointed the same day and terminated 29 Jul 2025, Hodgson appointed 29 Jul 2025. Compulsory strike-off: GAZ1 2 Dec 2025, GAZ2 dissolved 17 Feb 2026. Already recorded on /ecosystem/radix-foundation - no correction needed. |
| web:ebc-hackathon | 2026-08-25 | run 301 - NEW SOURCE KEY. eblockchainconvention.com/hackathon/ is LIVE (200 / 122,763 B) and still carries the 2024 edition's detail beneath a 2026 masthead: 'Barcelona, Spain / Date: September 25-26, 2024 / Cost: It is free', 48 hours, 250 participants, 'Judging is done by the Radix team', and a prize ladder of 10,000 / 5,000 / 3,000 / 2,000 / 1,000 USDT matching the dollar figures Radix's own recap records as paid in XRD. This is the source that dates the convention to TWO days where the wiki page had one. |
| web:emberflow.org | 2026-08-27 | Wix site, 7 pages / 3,943,265 bytes read 27 Aug 2026: Radix 0, XRD 0, Scrypto 0, blockchain 0. No /.well-known/radix.json. Now an EHR-interoperability pitch. |
| web:gable.finance | 2026-08-27 | HTTP 200, Apache, index Last-Modified Tue 23 Apr 2024 18:06:39 GMT. /.well-known/radix.json -> account_rdx128ku70k3nxy9q0ekcwtwucdwm5jt80xsmxnqm5pfqj2dyjswgh3rm3. |
| web:genkipool-mcp | 2026-08-22 | run 287 re-read of the run-266 baseline, 22 Aug 2026: UNCHANGED. initialize returns protocolVersion 2025-06-18, serverInfo {name radix-community, title "Radix Community Web", version 1.0.0} plus an instructions string naming the three tool families. tools/list returns 34 tools, nextCursor null, readOnlyHint TRUE on all 34 - 3 docs, 13 Gateway reads (lookup_entity, get_account_balances, get_transaction, list_validators, get_network_status, get_xrd_price, get_recent_transactions, get_address_transactions, get_nft_data, get_resource_holders, get_component_state, get_key_value_store, get_component_blueprint), 10 console/manifest builders, 5 address+SBOR utilities, 3 Radix Seal / connector. list_validators is the tool that answers the standing RadixDevelopers 66006 request for a validator MCP. |
| web:google-trends | 2026-08-13 | run 236 - NEW SOURCE, and the run lead. Google Trends NO LONGER REPORTS "XRD Radix": interest_over_time() returns an empty frame, repeatably. Not rate limiting - in the same session and window, Radix returned 1,441, XRD 1,623, ETH Ethereum 895, SOL Solana 1,229, ADA Cardano 1,239, AVAX Avalanche 972, and only the two-word Radix conjunctions ("XRD Radix", "Scrypto Radix") came back empty. "Radix DLT" still registers at 100. Method caveat worth carrying: pytrends calls build_payload with ONE keyword at a time and Trends normalises each series to 100 at its own peak, so cross-term scores compare shape, not volume. |
| web:leafnode.info | 2026-08-23 | Still HTTP 503 (DEPLOYMENT_PAUSED) on apex and www, three consecutive probes, 13 days after the validator deregistered and 7 days after it came back. |
| web:moxstudio.net | 2026-08-15 | Served (153 KB WordPress, lang=tr) but the Sectigo DV certificate expired 2026-06-07, so browsers refuse it. Apple id6498866858 and Google com.moxstd.strangers both 404 against live controls. 2 of 3 itch.io embeds serve. |
| web:nerdsrepublic | 2026-08-26 | run 310 - NEW SOURCE KEY, and it dates a dormancy the wiki could only bracket. nerdsrepublic.net answers 200 (19,134 B) and is a Webflow build whose source comment reads "Last Published: Sat Mar 12 2022 10:34:11 GMT+0000". That converts the infobox's "site frozen (2021-2022)" into a day. The site has not been republished across the entire Babylon upgrade. |
| web:projectnow.io | 2026-08-16 | run 251 - NEW FALSE-POSITIVE CLASS, resolved by body size per the run-250 method. check-links flags four projectnow.io URLs at 403/0 bytes; to a browser UA all four return 403 with a 4,548-byte Cloudflare interstitial. Full body = a wall, not a death. Do not re-probe and do not strip the citations on /ecosystem/project-now. |
| web:radstrike.com | 2026-08-21 | run 282 - NEW SOURCE KEY, reached from a token icon rather than from any link on the wiki. The $ARENA token's on-ledger icon_url is https://radstrike.com/scorpions/img/8151_large.png, NOT anything on abandonedarena.com. That URL answers 200 with a genuine 320x320 PNG, content-type image/png, last-modified Sun 28 Nov 2021 18:07:08 GMT, server LiteSpeed. radstrike.com itself answers 200 / 13,463 B and serves "Radical Strikers", a single-player Radix NFT shooter with About/Mint/Roadmap/Team/FAQ nav, still advertising the game as "coming soon". FROZEN, not active: the Webflow build stamp reads "Last Published: Sat Aug 13 2022 21:27:07 GMT+0000" and the footer is "Copyright 2021 Radical Strikers Team". Outbound: discord.gg/7vtNJ6Hahp, discord.gg/PJ9cJ9v7, t.me/radicalStrikers, twitter.com/radicalStrikers. The site does NOT mention Abandoned Arena or the Scorpions collection anywhere in its markup, so the relationship between the two projects is unstated and was NOT asserted on the wiki. |
| web:rola-examples | 2026-08-25 | run 303 - NEW SOURCE KEY. github.com/radixdlt/rola-examples is ARCHIVED (archived:true on the API), last commit 6621ac36 dated 2023-09-08, 3 stars. apps/client/package.json pins @radixdlt/radix-dapp-toolkit at 0.5.1 and main.ts sets networkId: 13, an id the current Gateway SDK's RadixNetwork map does not contain. The server verifies proofs with a hand-written implementation under apps/server/src/rola/ (blake2b, curve25519, secp256k1, derive-address-from-public-key), because the @radixdlt/rola package did not exist yet. Worth keeping: the archived example's CLIENT pattern is CORRECT - setRequestData(...withProof()) plus provideChallengeGenerator plus dataRequestControl - so the wrong code this run removed from the wiki did not come from here. It was invented. |
| web:staatenlos.ch | 2026-08-22 | run 289 - NEW SOURCE KEY, and the corroboration that made the Allnodes finding safe to publish. staatenlos.ch/staatenlos/radix-staatenlos-node/ 200 / 281,805 B (German), title "Jetzt Radix (XRD) Coin staken". It tells its own delegators "aktuell 6% zusaetzliche Radix-Coins im Jahr" at "eine schlanke Gebuehr von 2,5%" - an operator quoting the real rate. Note the split: the node's on-ledger info_url is node.staatenlos.ch, which returns HTTP 526 (origin TLS failure at Cloudflare), while the maintained guide lives on the main site. On-ledger info_url and the page a project actually maintains can be different URLs, and only the second one is worth citing. |
| web:stakesafe.net | 2026-08-21 | run 284 - NEW SOURCE KEY, verifying the free-tooling claims in the Avaunt announcement rather than repeating them. www.stakesafe.net 200 / 6,617 B, title "Home - StakeSafe.net". validators.stakesafe.net 200 / 450,066 B, title "Radix Network Dashboard - StakeSafe" - the dashboard is real and serving a full validator-set view, not a stub. StakeSafe Alert and the seed/outgoing nodes are stated by the operator and not independently probed. |
| web:t.me-profiles | 2026-08-16 | run 250: t.me USERNAME profiles (as distinct from run 249's t.me message deep links) also serve only to a real UA - t.me/ascarbek returns 0/fetch failed to check-links and 200 / 10,779 B with og:title 'Ascarbek' to a browser UA. Treat every t.me flag from the checker as unverified until probed with a UA. |
| web:thememestudio | 2026-08-26 | run 307 - NEW SOURCE KEY, independently reproducing run 302's reading before acting on it. thememestudio.com 200 -> www, 1,178,196 B, Wix, title 'THE MEME STUDIO \| Meme Coin Marketing Agency'. ZERO occurrences of 'Radix' and ZERO of 'XRD' in the entire document. /blog 200 / 829,151 B. Footer 'Copyright 2024. The Meme Studio.' Homepage now lists AI and RWA among its verticals, so the agency is trading; what is absent is any Radix work. |
| web:triwei-lapsed | 2026-08-24 | run 299 - NEW SOURCE KEY, and THE RUN LEAD: an audit citation can die because the AUDITOR lapsed, not the project. triwei.io read 24 Aug 2026: TLS resets (SSL_ERROR_SYSCALL), which check-links reports as status 0 / ECONNRESET; port 80 answers 200 with a 4,730-byte Namecheap parking lander served from ns1/ns2.lander.d.parity.domains, and the PDF path 404s there. RDAP (rdap.identitydigital.services) dates it to the hour: registered 2023-08-24, expiration now 2027-08-24, status "auto renew period", last changed 2026-08-24T22:05:18Z. So the domain lapsed on its own registration anniversary and the registrar had already repointed the nameservers when this run probed it. The report survives at web.archive.org 20260528021115 (200 / 6,845,039 B) and as a GitBook upload on docs.rootfinance.xyz/introduction/security. Archived homepage 20251014071813: TriWei self-described as "a collective of three solo auditors" covering Solidity, Rust, Vyper, Yul, Scrypto, Tact and Func. |
| web:ttabvue-uspto | 2026-08-20 | run 279 - NEW BANKED FALSE POSITIVE, and the blind-spot-#9 fix uncovered it. /ecosystem/rdx-works cites five ttabvue.uspto.gov proceedings. Probed with the old entity-mangled query they returned 200 (ttabvue ignores an unknown param); probed correctly, four of the five come back status 0 because check-links fires them concurrently and uspto.gov resets the extra connections. Serially with a browser UA they are all 200 with real bodies (pno=91267279 43,929 B, pno=90165249 29,877 B). Same shape as the radixtalk 429 class from run 268: a host rate-limiting the checker, not a dead citation. Do not re-probe or strip. |
| db:link-attributes | 2026-08-20 | blog: 14 absolute radix.wiki self-links under nofollow, a case the earlier regex could not see |
| exchanges:xrd-spot | 2026-08-23 | run 291: ALL SIX venues re-read at their own endpoints 22 Aug 2026 23:06 UTC, plus depth for four, and it is a DISLOCATION not a refresh. MEXC XRD/USDT last 0.00075970, 24h low 0.00062630, spread 2.72%, turnover $83,913. Every other book: BingX 0.00089330 / 0.81% / $68,662, KuCoin 0.000886 / 0.90% / $20,082, Gate.io 0.00089170 / 0.81% / $10,378, CoinEx USDT 0.00088479 / 1.52% / $3,531, CoinEx BTC 0.000000011497 / 2.02% / 0.03892 BTC (~$3,000 at BTCUSDT 77,061). Total ~$189,600/day, MEXC+BingX 80%. MEXC sits ~14% under the median of the other five and its 24h low is 28% under the lowest low any of them printed - a gap arbitrage cannot close, i.e. coins that cannot leave. DEPTH IS THE OTHER FINDING: BingX quotes joint-tightest 0.81% on 289.9 XRD at the ask, about 26 cents of size; Gate.io's identical spread sits on 15,232 XRD (~$13.60). A tight spread is not depth, and this is the sharpest instance yet measured. |
| onledger:mox-token | 2026-08-15 | MOX resource_rdx1thmjcqjnlfm56v7k5g2szfrc44jn22x8tjh7xyczjpswmsnasjl5l9: supply 84,000,000 of 100,000,000 minted 2024-07-01, minter deny_all and immutable, actively swapped against XRD through a native TwoResourcePool (~11.66M MOX / ~538.7k XRD). |
| rpc:solana-mainnet | 2026-08-21 | api.mainnet-beta.solana.com getRecentPerformanceSamples, 10 samples x 60 s to slot 440,790,972: 4,026 tx/s all traffic, 2,192 non-vote. One POST, no key. The repeatable half of any Solana throughput claim. |
| telegram:radix_dlt | 2026-08-27 | run 313: 159 messages, 62 past the run-312 watermark of 999519, and the entire window is one argument between two named participants about Plan A (wait for the DAO transition, then fund adoption) and an intervention. No dated claim, no product news, nothing attributable. Third consecutive run where this channel is high-volume and zero-yield. |
| telegram:radixlist | 2026-08-26 | run 307 - NEW SOURCE KEY, and the decisive one. The directory announces every addition to t.me/radixlist in a fixed 'New listing!' format, which turns the channel into a dated growth record. A 900-day scan returns 15 posts, ids 217-231. Newest is 231, PokerXRD, 23 FEBRUARY 2026. Before it: 230 Shepherd on Radix (20 Feb 2026) and 229 HYDRA (19 Feb 2026), then a NINETEEN-MONTH gap back to 228 NFTwars (28 Jul 2024). Three announced additions in twenty-five months, none in the six months to 26 Aug 2026. This is the class of probe that separates a served site from a maintained one. |
| web:arxiv-cerberus | 2026-08-13 | run 233: arXiv 2008.04450 re-read for the citation - "Cerberus: Minimalistic Multi-shard Byzantine-resilient Transaction Processing", Hellings, Hughes, Primero, Sadoghi, submitted 10 August 2020. Three months before the Flexathon, which is what makes the diary motive checkable. |
| web:blog-externals | 2026-08-28 | run 318 audit of the blog category: 19 pages / 204 external / 66 embeds - 0 broken internal, 0 broken embeds, 0 unverifiable embeds, 0 non-standard images. 16 flagged externals against run 305's 14. FIFTEEN sit in the banked set (9x linkedin.com/in/* 999, grandviewresearch 403, escholarship 403, unrealengine 403, medium 403, fred.stlouisfed.org and mckinsey.com status 0, statista fetch-failed); the linkedin count rose 5 -> 9 because the corpus grew, not because anything died. The SIXTEENTH was new and it was a real death - see the assets.super.so class below. |
| web:foohack-source | 2026-08-20 | run 275 - NEW SOURCE KEY, and it carried a factual correction. radixdlt.com/blog/scrypto-is-as-smooth-as-vegan-butter (29 Jun 2022) says RedFoo "had been introduced to Scrypto only three months earlier" - the wiki had rendered this as "having been coding for only around three months", which the same post contradicts. It also names the Solidity comparison the page carried anonymously (a Technical University of Berlin student project that ran a semester without finishing), gives the crew as RedFoo plus three competition winners, and splits the build into five streams with RedFoo on the auction components. The YouTube link EtRAt3_CHks resolves at oEmbed as 'Smooth as Vegan Butter' - The FooHack Documentary (Radix DLT). |
| web:gilesmorris.me | 2026-08-15 | Personal blog of Giles Morris (WordPress). 285 posts in wp-sitemap-posts-post-1.xml; the Radix material sits under the Crypto$ category. Latest post is still radix-midao-budgeting (28 Jul 2026) — nothing new since run 232. |
| web:github-scrypto | 2026-08-15 | run 247, and the run's spine - the worktop and transaction-processor rewrites read at five files on radixdlt-scrypto main. blueprints/resource/worktop.rs (648 lines): WorktopSubstate is one IndexMap, is_transient true, AllowAll on both function and method auth, nine methods in get_definition plus two added by WorktopBlueprintCuttlefishExtension (ASSERT_RESOURCES_INCLUDE / _ONLY); drop() detaches every bucket and calls drop_empty on each, which IS the no-lost-funds mechanism; WorktopError still carries BasicAssertionFailed with a source comment saying it is unused but kept so the node can serialize legacy errors. blueprints/transaction_processor/{package,blueprint}.rs: one blueprint, one function (Run), no fields/events/hooks, is_transient, FunctionAuth::RootOnly with the comment that it is a precaution that "may be removed if/when the transaction processor is verified to be safe"; MAX_TOTAL_BLOB_SIZE_PER_INVOCATION = 1 MiB applies to V1 minor version One only (version Zero was usize::MAX). system/transaction/{intent_processor,instructions,multithread_intent_processor}.rs: the worktop is allocated + kernel_pin_node'd at init and dropped when the queue empties (including the DoneAndYieldToParent path), returned buckets auto-move to the worktop and returned proofs to the auth zone, ManifestExpression::EntireWorktop resolves to drain(), and the V2 path builds one IntentProcessor per intent per kernel stack, setting each call frame's actor to TRANSACTION_PROCESSOR_PACKAGE/Run directly rather than invoking the export. TRAP RECORDED: radix-engine/src/blueprints/transaction_processor/instructions.rs is an ORPHANED file - that directory's mod.rs declares only `mod blueprint; mod package;` and re-exports the live dispatch from crate::system::transaction::instructions. The orphan still has todo!() arms for the five Cuttlefish assertions and VerifyParent; the compiled file implements all of them. Reading the orphan would produce a false "unimplemented" claim. |
| web:github-xstelea | 2026-08-09 | run 212: re-read xstelea/hookah end to end. Repository is a SNAPSHOT - all six commits dated 5 July 2026, first titled "chore: initial open source snapshot", one contributor, MIT LICENSE present. Public since 17 March 2025. www/docs matches the deployed docs; www/src/pages/index.tsx does NOT match the deployed homepage. radix-web3.js licence caveat re-checked and still accurate (no LICENSE file, GitHub reports license: null, last push 21 June 2026). |
| web:hermesprotocol | 2026-08-13 | run 237 — NEW SOURCE, and the staleness edit's spine. Hermes Protocol read at DNS, GitHub and Telegram rather than at its homepage, because the homepage is what misleads: hermesprotocol.io returns 200 with 150,334 bytes and reads like a going concern. app.hermesprotocol.io — the target of the site's own "Enter App" button — has NO address record: A, AAAA and CNAME all return NOERROR with ANSWER 0 and only the Cloudflare SOA, while the root and docs hosts both resolve to 104.18.10.141/104.18.11.141. t.me/s/Hermes_Protocol newest public post 27 Jun 2023. api.github.com/orgs/HermesProtocol-io: 8 public repos, newest pushed_at 2024-02-23 (hermes-protocol), one archived. The live site also carries three facts the page never had — P2P barter trades, wallet-to-wallet messaging, and a Radix Grant Program '23 first-cohort grant — plus the operator name Momentum One in the footer. THE METHOD GENERALISES to every Dormant ecosystem page: a live marketing site proves nothing; the app hostname, the announcement channel and the newest push do. |
| web:ociswap-runfly | 2026-08-24 | run 299 - NEW SOURCE KEY, and the number that makes the page worth writing. api.ociswap.com/tokens/ read 24 Aug 2026: listed_at 2025-03-20T22:42:29Z (so the curve graduated), rank 64, fully-diluted market cap 428,840 XRD (~$386), TVL 282,429 XRD (~$263), 7d volume 12,948 XRD (~$11.64), cumulative volume since listing 1,289,949 XRD (~$9,866). A service billing per render in this token is billing in a book that traded twelve dollars in a week. Note the /tokens?search= endpoint IGNORES the search term and returns the default page - query by address, never by symbol. |
| web:orange-finance | 2026-08-16 | run 250 - NEW SOURCE. orange-finance.gitbook.io/orange-finance 403s with a 35-byte text/plain body reading 'The organization has been suspended', and the GitBook org root 403s identically - a genuine death, not the banked bot-block class. api.llama.fi/protocol/orange-finance corroborates the wind-down: TVL $557 at 15 Aug 2026, 'url' field empty, and its own audit_links still pointing at the suspended GitBook. orange.finance and app.orange.finance both time out. |
| web:pocket.network | 2026-08-17 | run 258 - NEW SOURCE, and it closes the "is there a successor endpoint" question with a no. api.pocket.network 200 / 185,714 B (Vercel) and docs.pocket.network 200 / 35,597 B (GitHub Pages) both return ZERO matches for /radix/i. pocket.network apex 200. buildintheshade.com and www.buildintheshade.com - the entity Grove named as taking over its RPC infrastructure - DO NOT RESOLVE. So every hop in Grove’s hand-off chain is unreachable for Radix. |
| web:stakefi-anseta | 2026-08-24 | run 297 - NEW SOURCE KEY. stakefi.network 200 now serves ANSETA ('Anseta - Institutional Staking Simplified'); BCW's homepage phrases it as 'BCW Staking with Anseta' and the products page as 'stakeFi ... born out of BCW Group'. Its protocol logo set names Ethereum, Solana, Avalanche, XDC, Hedera, Polygon, Injective, Monad, Cronos, Polymesh, Chromia, Canton, Arc, Tempo, Midnight, EigenLayer, LayerZero, Linera, Morpho, Puffer, Somnia, Space and Time, Sphere, Vanar. Radix is not among them. /protocols and /networks 404 (SPA), so the homepage set is the readable list. |
| web:stakingrewards | 2026-08-22 | run 289 - NEW SOURCE KEY, third-party check on the emission arithmetic. stakingrewards.com/earn/radix publishes 6.01% live APY for XRD, against 6.40% computed from ~300M XRD/yr over the 4.686B-XRD active set and 6.08% net of a 5% fee. Independent agreement to within half a point, which is what let run 289 call the vendor's 14.00% wrong rather than merely unsourced. |
| db:freshness-census | 2026-08-17 | run 256 — NEW SOURCE KEY, the measurement behind the freshness edit. 361 pages total; 164 carry last_verified_at, 197 have never been verified; ZERO are over the 180-day threshold, so no page on the wiki currently renders the synthetic outdated banner. Oldest coalesced reading is ecosystem/xrd-domains, never verified, last edited 28 Mar 2026 (142 days) — and it is LOCKED, so the sweep cannot stamp it. Re-run the four counting queries each time /policy/freshness is refreshed; the stated census is the claim that decays. |
| onledger:blockshard | 2026-08-17 | validator_rdx1svudtxxk… at epoch 335,694: registered, active_in_epoch present, 12,252,454.546924680341858066 XRD, rank 66 of 188 registered, 0.2568% of registered stake, fee_factor 0.01 == effective_fee_factor, pending withdraw 313,400.04, owner stake units locked 14,756.44. |
| onledger:cadwynbloc | 2026-08-24 | run 297 - NEW SOURCE KEY. validator_rdx1sv2rav...tj4fem2p ('Cadwynbloc', description 'Radix Mainnet Validator operated by Cadwynbloc Consulting', info_url cadwynbloc.com which is a three-word splash page naming neither BCW nor Radix). At epoch 337,829 (24 Aug 2026 17:00 UTC): registered, active set, rank 29 of 188 registered, 68,559,800.45 XRD = 1.468% of the 4.67bn securing stake. STORED validator_fee_factor 0.5 with a fee_change_request to 0.75 at epoch 332,966 (long past) - effective_fee_factor.current reads 0.75, so it CHARGES 75%. Owner stake units are queued to unlock in three tranches at epochs 339,314 / 341,906 / 344,379. |
| onledger:dph-supply | 2026-08-26 | run 310 - NEW SOURCE KEY. $DPH (resource_rdx1tk2ekrvckgptrtls6zp0uautg8t34nzl3h93vagt66k49vh757w5px) read live at epoch 338,430 / state version 555,362,914: fungible, divisibility 18, total supply exactly 99,999,999, minter/burner/freezer/recaller all DenyAll and rules_locked true. The 99,999,999 cap in the page's tokenomics section is enforced by the resource, not by the team. |
| onledger:para-token | 2026-08-18 | run 264 - NEW SOURCE KEY. $PARA resource_rdx1tkvnqnrukez9nldufuvgl2ehv84gu4qk0wa67j8666zsuvgysh3wla read live at epoch 336,030 (18 Aug 2026 11:04 UTC): fixed supply 2,500,000,000, minter/burner/freezer/recaller all deny_all, rules locked. Most recent transaction referencing the resource is txid_rdx1zehh5yt7nj8j2mks7fgnnc0lk52ynxd5zq465ra33at3t70cz9dqyrtq08, committed 7 Nov 2025 10:25 UTC - a 20 XRD buy of 667,313 PARA against pool_rdx1c5kf2f8c0myszkufx6lggh9vy583aecp52nw2uedjvkgdlpfr2t482. Ociswap: listed 6 Oct 2023, $2.85 TVL, $0 volume at 24h and 7d, price $0.0000000694. The studio is gone and the token is immutable, so it outlives everyone who made it. |
| onledger:surge-pool | 2026-08-19 | run 269: component_rdx1crezrpxw9ypg6v2panqjqwevnwplg94yeej0rhqq9k7p4kgnltrc9g re-read at epoch 336,270 / state version 551,848,545 (19 Aug 2026 07:07 UTC). Holds 32,562.604282 of resource_rdx1th3uhn69… , confirmed at the resource metadata as symbol sUSD / name "Surge USD". Up from 32,551.37 at epoch 335,646 two days earlier. The pool the DefiLlama adapter reads has held five figures throughout the 148 days DefiLlama has reported zero. |
| telegram:ascent_xrd | 2026-08-25 | run 305: 1862 max, eight past run 304's 1854. ZENITH standings moved (PLAYER67 12,708 > SKRUTEK 11,951 at 25 Aug 20:39 UTC) but /ecosystem/ascent was edited yesterday and a leaderboard that turns over daily is not a fact a wiki page should chase. Contest still closes 30 Aug 12:00 UTC. |
| web:blog-caviarnine | 2026-08-22 | run 286 - BANKED FALSE POSITIVE for the ecosystem rotation, do not re-probe. blog.caviarnine.com is a Medium custom domain: three /floop-tokenomics-* and /product-preview-index-pools URLs all return 403 with a Cloudflare server header, the same wall as medium.com and anthic.medium.com. The CaviarNine wind-down does NOT threaten these citations; the 403 predates it and is Medium bot policy. |
| web:cobrastakes.com | 2026-08-17 | run 254 recheck of the run-251 watch, UNCHANGED: cobrastakes.com and www both return 200 with the same 10,881-byte registrar 'Your domain is expired' page. The validator page already says so; no edit owed. |
| web:defillama-radix | 2026-08-22 | run 291 re-read of api.llama.fi/overview/dexs/radix (supersedes run 270): total24h $26,295, total48hto24h $23,576 (+11.5% d/d), total7d $191,805, change_7d -40.5%. Seven adapters: DefiPlaza, CaviarNine Shape Liquidity, Ociswap Basic, CaviarNine LSU Pool, Astrolescent, Ociswap Precision, CaviarNine Agg - CaviarNine still supplying three of the seven despite the announced wind-down. |
| web:defillama-rswap | 2026-08-23 | api.llama.fi/protocol/rswap, Radix chain: 15 Aug $40,535 -> 19 Aug $63,732 -> 22 Aug $99,564 -> 23 Aug $130,157. Inflection on 19 Aug, the day CaviarNine announced its exit. |
| web:defillama-surge | 2026-08-19 | run 269 re-read of the run-256 series: api.llama.fi/protocol/surge-trade, 200 / 186,369 B, 661 points. Last non-zero is STILL 24 Mar 2026 ($27,844); counting distinct daily points, the trailing zero run is 148 readings, 25 Mar - 19 Aug 2026 inclusive (run 256's "145 as of 17 Aug" was one short of this count). currentChainTvls.Radix = 0. NOTE api.llama.fi/protocol/surge is a DIFFERENT protocol — "Surge", Lending, on Arbitrum, TVL $2,031 — the Radix one is surge-trade. |
| web:github-radquest | 2026-08-20 | run 278 - NEW SOURCE KEY, and it dates the handover posture. github.com/radixdlt/radquest is public, created 5 Dec 2023, TypeScript, 149.6 MB, 0 stars, NOT archived, and carries NO licence file (readable, not open source in the formal sense). Three commits on 4 May 2026 by shambupujar and nothing since: docs/deployment.md (21,694 B, local dev + production K8s), a README link to it, and the rename of both workflows to ci.yaml.disabled / helm-changes.yml.disabled. scrypto-packages/ holds eight packages (radquest, hero-badge-forge-v2, gift-box-opener-v2, card-forge-v2, radgem-forge-v2, quest-rewards-v2, ticket-machine, clam-dex) and packages/common/src/constants.ts commits every Stokenet AND mainnet address - the file that makes the dApp readable after the front end died. |
| web:nft-venue-probe | 2026-08-20 | bullring.auction 200 (11,411 B), foton.is 200, atomix.trade 200, trove.tools 404 (and www.), radket.io DNS failure. TROVE resource resource_rdx1tkl09e0ahgrxpwm4t5frseadp80thu5hm6n0zlzrn6ztddlm60wex8 has exactly ONE affecting transaction ever, 10 Feb 2025. |
| web:on-site-traffic | 2026-08-27 | run 300: flat against run 299 to the visitor. The +59/+54 jump run 299 recorded holds and has not extended. |
| web:web.archive.org | 2026-08-27 | run 297 recheck of the banked class: 43 of the 112 ecosystem flags are web.archive.org status-0, the largest single false-positive family and unchanged since run 254. Not re-probed. |
| code:radix-wiki-auth | 2026-08-16 | run 253 - NEW SOURCE, and the spine of both edits this run: the app's own source read as the primary source for claims the legal pages make about the site. src/ and prisma/schema.prisma contain ZERO occurrences of 'password'; the User model has no credential column at all (radixAddress / personaAddress / displayName / avatarUrl); src/lib/auth.ts:17-18 sets cookie radix_wiki_session with SESSION_DURATION 7 days, :106 sets CHALLENGE_EXPIRATION default 300 s, :122 constructs Rola() from @radixdlt/rola. Comments: POST requires auth, DELETE returns forbidden unless comment.authorId === session.userId, and the Comment model carries no approval or hidden column. Editing goes through requireAuth(request, {type:'edit'\|'create', tagPath}) so balance/author gating is per tag path. |
| db:authorship-census | 2026-08-21 | First run: 364 pages / 2,818 revisions / 16 accounts that ever saved one / 56 registered users. 111 of 147 ecosystem pages authored by ShardSpace Admin in the 6 Feb 2026 Notion import (113 pages in total). Last 90 days 1,554 of 1,579 revisions from Hydrate (98.4%). 5 notice banners wiki-wide: 3 promotional, 2 stub, 0 coi. 4 comments lifetime, last April 2026. |
| gateway:user-tx-rate | 2026-08-21 | mainnet.radixdlt.com /stream/transactions kind_filter User, 100 rows: 22:09:48-23:05:47 UTC 21 Aug = 3,359.6 s, 0.03 user tx/s; state versions 552,958,337-552,976,939 = 5.5 ledger tx/s. Live demand on Babylon in one call. |
| onledger:gnrd-supply | 2026-08-26 | run 310 - NEW SOURCE KEY. Genesis Nerds $GNRD (resource_rdx1tkf56rwzta4qemw5vrrwgf5xlkvdg5huxp26zsfrt6mm3x5frnvzeh) read live at epoch 338,430: supply exactly 10,000, divisibility 18, every authority DenyAll, rules locked. Still a FUNGIBLE resource - the reservation receipt, not the 10,000-avatar NFT collection it was to be swapped for. Supersedes the 21 Jul 2026 epoch-328062 read in the infobox. |
| onledger:juicy-stake | 2026-08-17 | validator_rdx1s0tkjt8… at epoch 335,694: is_registered false, stake_vault 12,087,329.820082095715034029 XRD, pending_xrd_withdraw_vault 661,871.150645647908576531, fee_factor 0.02, no change request. |
| onledger:maya-router | 2026-08-17 | run 256 — NEW SOURCE KEY, and a METHOD CORRECTION worth keeping: component_rdx1cp7hrk7k0pjavnpt5h6dsel096kzlj96r8ukw2ywqgdc5tlvpvn0as holds its XRD across FIFTY-SEVEN vaults, not one. Reading vaults.items[0] alone gives 655,702.78 and looks like the page is wrong by 136k; summing all 57 gives exactly 791,820.9000477125 XRD, which is what /ecosystem/maya-protocol states. Plus 2.5 xUSDC in a single vault. Re-read at epoch 335,647 (17 Aug 2026 03:11 UTC). With aggregation_level=Vault, ALWAYS sum every vault before calling a page’s figure wrong. |
| web:academia-scrypto | 2026-08-27 | run 314: academiascrypto.com has NO DNS RECORD (dig returns an empty answer), so the page's 'no longer resolves' is exact rather than approximate. aprendescrypto.com, which lived only in metadata.website and appears nowhere in the body, IS live: 200 / 21,348 B behind Cloudflare, and it serves an unconfigured template whose  reads 'Home - Accessible Astro Starter'. github.com/AcademiaScrypto is a USER account, not an organisation - api.github.com/orgs/AcademiaScrypto returns 404 while /users/AcademiaScrypto returns id 105361351, and the page's External Links called it an organisation. Both repositories survive and date the death to the day via the search API: Web-AccademiaScrypto-Espanol last pushed 19 May 2022, -Italiano 1 Jun 2022, 0 stars each. |
| web:docs.surge.trade | 2026-08-12 | run 227 - NEW SOURCE and the ecosystem edit's spine. llms.txt indexes the whole doc set as markdown (append .md to any page). welcome-to-surge lists EIGHT pairs against USD (BTC ETH SOL XRD SUI DOGE ADA BNB) and up to 20x - not the "over 100 trading instruments" the wiki carried from the 2024 Medium announcement - collateral sUSDC/xWBTC/xETH/XRD/LSULP, and a Platform Status roadmap on which the referral system is still PLANNED. srg-governance-token/overview: TGE 13 Nov 2024, 100,000,000 supply, 20% of opening and closing trade fees to the SRG treasury, and governance stated only in the future tense ("as the platform matures, the token WILL convey voting rights"), staking merely possible and contingent on a governance vote that does not exist. |
| web:ghproxy-radixdlt | 2026-08-23 | run 296, the standing per-developers-rotation probe, and the mirror is ALIVE. Called with the CLI's own user-agent 23 Aug 2026: /radixdlt/babylon-node returns tag v1.3.0.5, /radixdlt/babylon-gateway and /radixdlt/babylon-nginx both answer with release JSON. Unchanged from run 283. Keep probing every developers rotation - if it goes dark, a 19-month-old installer stops being able to install anything. |
| web:github-radix-dao | 2026-08-09 | run 211: THE REFERENCE LIBRARY IS NOT THE OPERATIVE REPO, and OPERATIVE-REPO.md in Shadaffy/radix-dao says so. The operative documents live in Shadaffy/radix-dao-governance (default branch master, created 18 Apr 2026, last push 7 Aug) - "updated only when a governance proposal passes. If it is there, it is law." Its in-force directories (constitutional/ governance/ legal/ parameters/ transition/ working-groups/) are EMPTY .gitkeeps; the entire framework sits in pending/. The pending documents are also far larger than the reference-library versions the wiki cited at run 209 (operating-agreement 86KB vs 31KB, proposal-and-voting-framework 57KB vs 14KB), so ARTICLE NUMBERS CITED FROM THE REFERENCE LIBRARY MAY NOT HOLD IN THE OPERATIVE TEXT - re-check before repeating run 209s OA citations. |
| web:github-x402-caip | 2026-08-10 | run 217 - NEW SOURCE, and the primary source for this run. BOTH submissions are upstream, no longer forks. ChainAgnostic/namespaces#198 "Add Radix (radix) namespace: CAIP-2, CAIP-10, CAIP-19" opened 2026-08-06T09:10:08Z by AVaunt-consulting - 18 minutes BEFORE the vote citing it closed - 4 files, +512/-0: radix/README.md (CAIP-104), caip2.md (radix:mainnet, radix:stokenet, resolved via network-configuration endpoints), caip10.md, caip19.md. State open, ZERO reviews, one self-comment. x402-foundation/x402#3112 "feat(specs): add Radix exact scheme" opened 2026-08-10T15:38:45Z, 2 files, +741/-1 (scheme_exact_radix.md plus a Radix row in scheme_exact.md Critical Validation Requirements). Spec-only per the spec-first process; SDK follows approval. State open, ZERO reviews; the only comments are bots (vercel deploy auth, and a commit-signing requirement - unsigned commits must be rebased before merge). Re-poll both for merge/review before citing them as pending again. |
| web:hyperscale-proof | 2026-08-24 | run 298 - NEW SOURCE KEY. hyperscale.rs/proof 200 / 35,572 B, title "Hyperscale - how do you know?", posted to the project channel 24 Aug 2026 11:35 UTC (10838). Public explainer for the formal-verification programme: Dijkstra 1970, the FDIV recall as the industry precedent, the ladder (one path / thousands of hostile paths / all paths within bounds / unbounded proof), the model-finds -> simulator-reproduces -> fix-verifies loop, and an honest fine-print section (a worklist not a trophy case; a model is not the code; exhaustive within bounds). Used for framing and dating only - every hard claim on the wiki page is sourced at the repository instead. |
| web:midgard-xrd-pool | 2026-08-20 | run 279 independent re-verification of the run-256 maya-protocol edit, and it HOLDS exactly. mayanode /mayachain/pools lists 26 pools and XRD is not among them; /mayachain/pool/XRD.XRD answers 404 with the body "pool: XRD.XRD does not exist"; midgard /v2/pool/XRD.XRD answers "Bad Request: Unknown pool". Daily depths: last day with runeDepth>0 is 28 Apr 2026, zero on 29 Apr, then a residual assetDepth of -88,508,934 every day since. Monthly swaps: 2,144 in Jan 2026, 509 in Feb, 304 in Mar, ZERO from Apr 2026 onward. Page stamped verified, no edit needed. |
| web:npm-radix-web3js | 2026-08-23 | run 296 - NEW SOURCE KEY, the re-measure behind the radix-web3.js stamp. npm registry + downloads API, 23 Aug 2026. All nine versions UNCHANGED from the 20 June release: radix-web3.js 0.6.3, @radix-effects/gateway 0.6.4, radix-connect 0.3.3, radix-agent-toolkit 0.1.11, rdx-cli 0.2.4, @radix-effects/tx-tool 0.2.4, transaction-stream 0.1.11, sbor 0.3.3, shared 0.0.5. Licence field still MIT on eight and ABSENT on @radix-effects/sbor, matching what the page says. Last-month downloads: 236 / 170 / 83 / 76 / 32 / 105 / 60 / 28 / 126 = 916 total, against 45,317 for @radixdlt/radix-dapp-toolkit (was 46,211 on 6 Aug), a ratio of ~192:1. The four packages the page could not count on 6 Aug now have figures and TWO OF THEM OUT-DRAW rdx-cli and radix-connect. GitHub api unchanged: 8 stars, 3 forks, 20 open issues, not archived, license null, /license 404, last commit 2026-06-21 'Add radix-web3 agent skill', contributors xstelea 172 / github-actions[bot] 15 / turbobot-temp 4 / gguuttss 3. |
| web:radix-blog-posts | 2026-08-22 | run 287: eleven Matthew Hine posts fetched individually for dateline + byline. radix-engine-and-ledger-the-road-to-adoption 14 Nov 2019; moving-past-smart-contracts 3 Dec 2019; on-ledger-recurring-developer-revenue 6 Aug 2020; reducing-defi-hacks 4 Dec 2020; the-problem-with-smart-contracts-today 4 Oct 2021; radix-engine-v2 7 Oct 2021; scrypto-an-asset-oriented-smart-contract-language 12 Oct 2021; how-radix-engine-is-designed-to-scale-dapps 11 Nov 2021; is-scrypto-turing-complete 9 Mar 2022; asset-oriented-soulbound-tokens-done 9 Jun 2022; radixs-asset-oriented-transactions 26 Jun 2023; using-native-pools-and-pool-units 7 Aug 2023; using-transaction-manifests 7 Aug 2023; how-radix-multi-factor-smart-accounts 25 Aug 2023; feedback-wanted-interface-standard 9 Sep 2024. meet-the-team-matt-josh (17 Jul 2021) is the biography source: Head of Product at that date, BSc mechanical engineering Rice University, ~a decade at Texas Instruments where he created the automotive DLP display group, then medical devices / cinema projection / head-mounted displays / 3D scanning / hyperspectral imaging. |
| web:radixdlt-authors | 2026-08-22 | run 287 - NEW SOURCE KEY, and THE RUN LEAD. radixdlt.com/sitemap.xml lists FOURTEEN /blog-author/ records. Read individually 22 Aug 2026: matthew-hine 15 posts (14 Nov 2019 - Jan 2023), matthew-hine-3 10 posts (9 Jun 2022 - 9 Sep 2024), matthew-hine-2 ZERO - one person split across three records, so neither populated page shows the run and the first implies he stopped writing in Jan 2023. Others: piers-ridyard 22 (Jan 2018 - Nov 2023), dan-hughes 26 (Feb 2018 - 13 Jun 2025), adam-simmons 7 (Apr 2021 - 4 Jul 2025), russell-harvey 7, ben-far, jacob-mcatamney, jeremy-epstein, josh-primero, plus the institutional radix (100 shown, latest 28 Apr 2026) and rdx-works (100, latest 1 Mar 2024). METHOD: the newest NAMED byline anywhere is 4 Jul 2025; every 2026 post (2026 strategy, Foundation operational stack, Hyperscale updates) is signed "Radix". An individual absent from 2026 bylines is evidence about the publishing model, not about their role - do not write it as a departure. |
| web:radixdlt-bylines | 2026-08-22 | run 287: Matthew Hine's byline dated at the posts themselves rather than at the author page. Plain "Matthew Hine" through is-scrypto-turing-complete (9 Mar 2022); "Matthew Hine, CPO of RDX Works" from asset-oriented-soulbound-tokens-done (9 Jun 2022) to feedback-wanted-interface-standard (9 Sep 2024). The title change is pinned tighter by the event announcement austin-developer-event-consensus-2022 (31 May 2022), which bills "RDX Works CPO, Matthew Hine". Post dates verified by direct fetch, NOT read off the author-page cards: the card layout puts the date BEFORE the anchor, and reading it after shifts every post by one (that error would have dated on-ledger-recurring-developer-revenue to Dec 2019 instead of 6 Aug 2020, and reducing-defi-hacks to Oct 2020 instead of 4 Dec 2020). |
| web:radixdlt-simmons | 2026-08-25 | run 300 - NEW SOURCE KEY. The adam-simmons author record carries SEVEN posts, all dated by direct fetch rather than off the author-page cards (the run-287 off-by-one trap): radix-website-updated 27 Apr 2021, radix-olympia-mainnet-is-coming 2 Jun 2021, making-xrd-a-cross-chain-token-with-exrd-and-instabridge 3 Jun 2021, designing-governance-with-400-trillion-of-potential 3 Feb 2022, marketing-update-babylon-beyond 24 Nov 2023, radix-rewards-public-test... 2 Jul 2025, how-to-join-the-radix-rewards-public-test 4 Jul 2025. Unlike Hine his record is NOT split across duplicates. Two announcement posts date the arc: a-new-phase-for-radix-adam-simmons-joins-the-radix-foundation-as-cso (29 Nov 2024, bylined DAN HUGHES, and explicit that the CSO role sits outside RDX Works so the community has an advocate that does not report to the technology company) and foundation-update-moving-to-maintenance-mode (28 Apr 2026, "The most senior of these is Adam", quoting him "I am not going anywhere. I am just changing seats"). in-memory-of-dan-hughes-founder-of-radix (29 Jul 2025) is the Foundation-board sentence. |
| web:stokenet-gateway | 2026-08-20 | run 274: POST /status/gateway-status, 20 Aug 2026 03:07 UTC. state_version 425,461,885, epoch 255,095, round 3000, release v1.10.6. THE POINT OF THE CALL: the funding proposal said the Gateway would be decommissioned in mid-August without funding. Mid-August has passed and it is still answering. Published on /community/daffy as the re-dated status line. |
| x:ecosystem accounts | 2026-08-02 | radixdlt + project accounts – no X read creds in this env |
| appstore:radix-stream | 2026-08-27 | run 295 - NEW SOURCE KEY, and the finding the website cannot tell you. Radix Stream is DELISTED FROM BOTH STORES, measured 23 Aug 2026. apps.apple.com/{ro,us}/app/radix-stream/id1596583199 -> HTTP 404, and itunes.apple.com/lookup?id=1596583199 returns resultCount 0 in RO, US, GB, DE and NL (a lookup answering 0 in every storefront is the delisting signal - a region-gated app answers in at least one). An entity search for 'radix stream' returns only unrelated apps. play.google.com for com.ideomaker.radixstream -> 404 in US and RO. The download page still renders both buttons. METHOD worth reusing: for any wiki page listing a mobile app, the storefront lookup APIs are the liveness probe - the project's own download page is not. |
| code:hyperscale-specs | 2026-08-24 | run 298 - NEW SOURCE KEY, and THE RUN LEAD. github.com/hyperscalers/hyperscale-rs/specs holds TEN Quint models (wt_clock, shard_consensus, atomic_commitment, straddler_settlement, beacon_spc, reshape_lifecycle, shard_recovery, witness_fold, reshape_handoff, vm_fee_assurance) plus the SEC-1 statistical companion (committee_security.md/.py). specs/README.md gives model, scope, INV-* IDs and status: all ten read "Verified", at depths 4-13 where a depth is stated. Discipline: properties come from docs/08-invariants.md; transitions name their implementing crate/file/function; every model ships a BROKEN TWIN so quint verify must produce a counterexample; three tiers typecheck -> run -> verify (Apalache, default 10 steps); bounded checking is explicitly NOT proof, inductive invariants named as the upgrade path. Two findings on the record: the Prefix Consensus parent_of divergence (found by the model, replayed by the simulator, fixed, and kept as model E twin) and Finding G-1, an Apalache counterexample showing a beyond-f retained committee drags the QC weighted timestamp and admits an orphan commit, mitigated by the beacon-mandated cross-shard freeze. GitHub commits API: 63 commits touching specs/, first 2026-07-03 ("Add Quint model of the weighted-time clock"), newest 2026-08-24 12:34 UTC. |
| code:radix-auth-model | 2026-08-27 | run 313 - NEW SOURCE KEY, and the spine of both edits. radixdlt-scrypto @ main read across eight files for the authorization model. HARD NUMBERS from radix-common/src/constants/transaction_execution.rs: MAX_ACCESS_RULE_DEPTH 8, MAX_COMPOSITE_REQUIREMENTS 64, MAX_ROLES 50, MAX_ROLE_NAME_LEN 100. GRAMMAR from proof_rule.rs: AccessRule is exactly AllowAll / DenyAll / Protected(CompositeRequirement); CompositeRequirement is BasicRequirement \| AnyOf \| AllOf; BasicRequirement is Require / AmountOf / CountOf / AllOf / AnyOf. AUTH ZONE from auth_zone_substates.rs: three fields of evidence (proofs, simulate_all_proofs_under_resources, implicit_non_fungible_proofs) plus direct_caller_package_address, global_caller and parent; local_implicit_non_fungible_proofs derives the package_of_direct_caller and global_caller badges. BARRIER from auth_module.rs: create_auth_zone runs on every on_call_function and on_call_method, and sets auth_zone_parent to None when is_global_context_change, so proofs do not cross a global-component boundary. RESOLUTION from authorization.rs:332: _self_ resolves to require(global_caller(self)) and is never stored, and an undefined role key falls back to the OWNER role rule rather than denying. RESERVED NAMESPACE from object_modules/role_assignment/package.rs:253: is_role_key_reserved is exactly key.starts_with('_'), and only _owner_ and _self_ are reserved-and-defined. OWNER ROLE from role_assignment.rs: OwnerRole None/Fixed/Updatable, OwnerRoleUpdater None/Owner/Object; updater None writes the field immutable. SECURIFY from blueprints/util/securify.rs: create_presecurified sets updater Object, and securify() sets the securify role to DenyAll, mints the badge, then set_owner_role - the DenyAll is what makes it one-way. RESOURCE ROLES from blueprints/resource/mod.rs: seven roles (MINTER, BURNER, RECALLER, FREEZER, WITHDRAWER, DEPOSITOR, NON_FUNGIBLE_DATA_UPDATER) each with a paired _UPDATER_ROLE. |
| code:scrypto-compiler | 2026-08-21 | run 283 - NEW SOURCE KEY. scrypto-compiler/src/lib.rs documents the flow in a comment at the compile entry point and the code matches it: `scrypto build` compiles TWICE - once with schema producing _with_schema.wasm from which the .rpd is extracted, then once with the scrypto/no-schema feature for the published binary - consulting a local cache keyed on the hash of the with-schema wasm between them, and running wasm-opt on the result by default (cmd_build.rs --disable-wasm-opt turns it off). Both passes are release builds against wasm32-unknown-unknown with -Zbuild-std=std,panic_abort -Zbuild-std-features=optimize_for_size, i.e. std is rebuilt for the target, which is WHY rust-src is in the toolchain template. Artifacts land in target/wasm32-unknown-unknown/release/. --locked / SCRYPTO_CARGO_LOCKED is accepted by build, test AND coverage. cmd_coverage.rs states four preconditions in its own header: system nightly (not chosen by the user), always wasm32-unknown-unknown, always release, and clang + llvm-cov + llvm-profdata already on PATH. |
| onledger:dao-treasury | 2026-08-16 | run 255: the standing two-call check, and it CHANGED for the first time — the reason to keep running it. account_rdx1c9l27suy4nte9ymge5c3eqqnnfepgf9p28d9lcsv3jvmd0f0z8j2fx at epoch 335,598 holds 200 XRD (unchanged, deposited 10 Aug 19:29 UTC) AND ONE NON-FUNGIBLE: the Consultations Master Badge, since 13 Aug. Owner rule re-confirmed CountOf(2) over three Ed25519 signature badges (list length 3) — the 2-of-3 in DAO Parameters §6A. Run 234 read this account with no non-fungible; the badge landed between that read and run 238's, and no run noticed until now because nothing re-ran the non-fungible half of the check. |
| onledger:delay-supply | 2026-08-26 | run 310 - NEW SOURCE KEY. DELAY (resource_rdx1t4dsaa07eaytq0asfe774maqzhrakfjkpxyng2ud4j6y2tdm5l7a76) read live at epoch 338,430: total supply 661,195,247.825631037429292673, minter/freezer/recaller DenyAll, burner ALLOW_ALL, rules locked. The page's "approximately 661 million, minting denied, anyone may burn" is exact. No edit needed; page stamped instead. |
| onledger:runfly-token | 2026-08-24 | run 299 - NEW SOURCE KEY. resource_rdx1t5uyf7s9rpde7pezhthsuygl0sk3gj0e09zzsvsmga69zxdd8y4lvq read at state version 554,435,224 / epoch 337,903 (24 Aug 2026 23:10 UTC): FungibleResource, divisibility 18, total_supply exactly 1,000,000,000, and minter/burner/freezer/recaller ALL DenyAll with every updater role also DenyAll - fixed by construction, only the metadata roles left with the owner. name RUN.FLY, symbol "RUN FLY", tags [rlyfun], info_url https://rly.fun, icon served from runfly.today. The tag and info_url are what tie the product to the launchpad; the exact 1B supply matches rly.fun standard per-coin mint. |
| onledger:topradixnode | 2026-08-18 | run 264: validator_rdx1svvnmmgdr6sl7llxc8sdu32ys7tn8v6k8quh7e6m6ec83fr3pf6d04 read in the full validator list at epoch 336,030 - registered FALSE, rank 48, total_stake 25,347,270.155084587874801481 XRD, fee 25% (raw 1.99%), accepts_delegated_stake TRUE, 1-week uptime 99.16%. Down ~45k XRD from the 25,392,103 read at epoch 331,662 on 3 Aug, so delegators are trickling out. Deregistered-but-staked-and-accepting is dormancy, not closure - this is what corrected metadata.status this run. |
| web:ch-foundation-psc | 2026-08-27 | The Radix Foundation 12106715 PSC register: Jarrett active, notified 10 Feb 2025, nature of control 25-50% of shares AND voting rights, NO right to appoint or remove directors. Ridyard ceased 31 Jan 2025 (25-50% + appoint/remove), Hughes ceased 27 Jul 2025 (25-50% voting). |
| web:docs.radixdlt.com | 2026-08-27 | run 313: the two auth doc pages cited by the rewritten pages both resolve. docs.radixdlt.com/docs/auth and /docs/advanced-accessrules each return 308 to their trailing-slash form and then 200. Kept as citations. |
| web:gateway-endpoints | 2026-08-17 | run 258 - NEW SOURCE KEY, probing the endpoints /developers/infrastructure/02-radix-apis states in  rather than in href (which is why check-links has never touched them). POST /status/gateway-status at 11:06 UTC: mainnet.radixdlt.com 200 (mainnet, epoch 335,742, state_version 550,917,905) and stokenet.radixdlt.com 200 (stokenet, epoch 253,984, state_version 422,125,024), both release_version 1.10.6-v1.10.6. babylon-stokenet-gateway.radixdlt.com returns the byte-identical stokenet response, so it is the same service under a second name. The page’s endpoint table is correct. |
| web:github-hyperscale | 2026-08-10 | run 219 - PRIMARY SOURCE. Verified Milestone 2 week 1 at the manifest rather than the digest. hyperscalers/hyperscale-rs Cargo.toml declares SEVEN hyperscale-vm path crates (hbor, vm-effects, vm-kernel, vm-ref, vm-runtime, vm-stdlib, vm-types) resolving into the vm/ git submodule and NO Radix crate; a repo-wide code search for 'radix-engine' returns 0. crates/engine is now 'Engine integration: the tick-batch execution seam, the executor behind it, and genesis seeding'. PR #141 'Initial VM switch spike' merged 7 Aug 18:24Z; 523c7dbf 'Retire the two-engine material from the system docs' 5 Aug 17:47Z. Counts at 10 Aug: 33 workspace crates, 2,835 commits on main (2,752 lead), 6 contributors, 28 stars / 14 forks, main last pushed 9 Aug 07:05Z. docs/06-resource-economics.md gained the fee and work-budget sections this week (f00d565e 4 Aug, a2791f4b 7 Aug, d09ea58d 8 Aug). NOTE: my own count of commits on main 3-10 Aug is 183, not the digest's 246 - the digest window likely spans the vm submodule or the vm branch, so the page attributes 246 to the digest rather than asserting it. |
| web:github-kangaderoo | 2026-08-13 | run 232 - NEW SOURCE, and the run edit's spine. Read at the GitHub API rather than at the fork the page cited. /users/kangaderoo: account opened 2009-12-18, 14 public repos, Netherlands, 12 followers. search/issues repo:radixdlt/community-scrypto-examples author:kangaderoo type:pr returns NINE pull requests between 29 Jan and 13 Dec 2023 - seven merged (#89, #95, #99, #104, #111, #112, #133), one closed unmerged (#105 Trueblood, Mar 2023), one still open (#131 Coin Dispenser, Aug 2023). Four of the merged blueprints are carried upstream today: games/RaDiceX, defi/trustmore, basic/wrapper, basic/pokerdicebank. #99 and #111/#112 are his own migrations across the v0.7.0 -> v0.8.0 and v0.8.0 -> v0.9.0 breaking releases, not new code. RadixTransactions (3 Nov 2022, Python, 8 commits) is an Olympia-era CSV exporter built on 0xOmarA/RadixLib. rrc-404 is 6 commits 13-31 Mar 2024 and is his newest own commit on any Radix repository. pokerdice.kangaderoo.nl answers 200 / 6,721 B under a browser UA. |
| web:radix-dev-console | 2026-08-14 | run 241 - the developers rotation's lead. console.radixdlt.com 302s path-for-path to console.radixscan.io ('RadixScan Developer Console'), dashboard.radixdlt.com to dashboard.radixscan.io, stokenet-dashboard.radixdlt.com to the MAINNET dashboard root; stokenet-console and stokenet-sandbox return 530 with no origin. Already recorded on /ecosystem/radixscan and /contents/tech/releases/stokenet (30 July run) - what was NOT recorded is that the developers tutorials still routed readers to the old host and to a Stokenet console that does not exist. Wayback brackets the handover: console.radixdlt.com served 200 directly on 20 Apr 2026, dashboard.radixscan.io first archived 13 May 2026. Primary context: the Foundation's operational-stack post of 26 Jan 2026 lists Console/Dashboard/Sandbox as P3, 'prime opportunities for community teams'. |
| web:radixdlt.com/blog | 2026-08-27 | run 301: blog sitemap re-pulled (113,899 B, 618 blog URLs). The APE trail read end to end, all three posts 200 - ape-radix-alexandria-preview-event (30 Sep 2021, the announcement), radix-alexandria-scrypto-is-coming (17 Nov 2021, the post that says 'at APE, we released a preview form of Scrypto and the other Alexandria tools on Github' and links both recordings), alexandria-scrypto-is-here (15 Dec 2021) - plus european-blockchain-convention-event-highlights (18 Oct 2024). NOTE for future history runs: there is NO recap post for the Lisbon Scrypto Developer Event. The 16 March 2022 announcement is the only prose record of that day, which is why the page now attributes its schedule rather than narrating it as fact. |
| web:vandyill-projects | 2026-08-18 | run 262: the four project domains on /community/vandyill probed for TLS before the scheme fix - doubtit.digital (200, 2,380 B), radixrolodex.com (200, 612 B), quack.space (200, 323,203 B), cshwrd.com (200, 36,220 B). All four serve https to a browser UA, so the http:// hrefs were an internal inconsistency, not a site without TLS. |
| web:vote.radixdao.org | 2026-08-23 | run 293 - NEW SOURCE KEY. vote.radixdao.org answers 200 with a valid certificate and the title 'Radix Consultation'. Its app-config.js carries ONLY ENV, DAPP_DEFINITION_ADDRESS (account_rdx128965k8m..., the 'Radix DAO' definition) and NETWORK_ID 1 - no VOTE_COLLECTOR_URL, where the mountain-top build's config.js named api-consultation.mountain-top.live. The only Radix network host in its 996 KB main bundle is mainnet.radixdlt.com. radixdao.org/participate (307 -> /participate/) links vote.radixdao.org and vote.radixdao.org/about/voting-power and names no other venue. Deep paths are client-rendered - /tc/4, /tc/5, /tc/99 all return the same 9,209 B shell - so a URL there proves NOTHING about whether the item exists; check the component, not the path. |
| web:wasmtime-releases | 2026-08-12 | run 227 - NEW SOURCE, one call to corroborate a code comment rather than trusting it. docs.wasmtime.dev/stability-release.html: a new major on the 20th of each month, every release that is a multiple of 12 is an LTS supported 24 months, all others 2 months. So 47 is outside long-term support and 48 (12x4) is the first LTS the VM can sit on, landing 20 Aug 2026 - which is exactly what hyperscale-vm's pin comment says. Cheap check, worth repeating whenever the wiki cites a dated dependency claim. |
| web:wayback-emberflow | 2026-08-27 | 149 CDX snapshots. 23 Jul 2023 homepage: Radix x2, "decentralized" x6. 31 Aug 2025: Radix 0, "decentralized" x5. 11 Mar 2026: both 0. |
| web:wayback-hackation | 2026-08-16 | run 250 - NEW SOURCE, and it closed an item logged as unrecoverable. CDX for github.com/DanoshiFusermoto/hackation* returns exactly two rows: 20201123214521 status 200 and 20221221170007 status 301. Playback 503'd twice before serving the 2020 capture (115,340 B): master, 1 branch, 0 tags, 49 commits, 0 stars / 0 forks / 2 watching, one top-level entry 'core', latest commit 'Added empty atom to genesis block to solve NPE' (Nov 23 2020), Languages Java 100.0%, no description/website/topics, no releases. The tree is NOT in the capture - Wayback archived the landing page - so the source stays lost. |
| web:wayback-slashdata | 2026-08-16 | run 252 - NEW SOURCE, and it saved a citation the checker would have had removed. slashdata-website-cms.s3.amazonaws.com/sample_reports/dsIe6JlZge_KsHWt.pdf returns an S3 AccessDenied XML body (263 B) to a browser UA - a real death, unlike the 403 walls. CDX returns four rows: 200 at 20221116184114 (14,009,887 B, the report itself) and 20230702213751, then 403 at 20250720130436 and 20250721143914 - dating the death to between Jul 2023 and Jul 2025. Repointed to the 2022 capture, which serves 19.4 MB on playback. |
| web:youtube-radixlabs | 2026-08-25 | run 301: four Radix DLT YouTube IDs resolved through oEmbed, all 200. Hn20w1gmpMw 'Alexandria Preview Event - APE Radix - Live Keynote from New York!', he9TunEXgcY 'Scrypto Developer Workshop Recording - APE Radix, Nov 12th 2021', bo5LQW5hATQ 'Lisbon Scrypto Event 2022 Highlights', plus the two EBC panel links on youtu.be. The two APE titles are load-bearing: they date and place the event independently of the announcement, which is what let the new page be written from what happened rather than from a plan. |
| x:@RadixWiki mentions | 2026-08-09 | run 214: xread --mine, 20 judged at 18h maturity - median 21 likes / 0 replies / 288 impressions, ZERO zero-engagement posts. Best remains the 6 Aug xStelea AI-skill post (46 likes / 407 imp / 20 reposts) and the 7 Aug M1 post (46 / 791). Discovery-led hooks keep landing; the tidy-up hook stays retired. 9 Aug is heavily over cap: FOUR originals (03:13, 07:12, 11:17, 14:14 UTC) plus a 16:44 reply. |
| x:RadixWiki reception | 2026-08-28 | run 318 via xread --mine: 22 judged at 18h maturity, median 16 likes / 0 replies / 260.5 impressions, one zero-engagement post at 5% and it is a reply. Best is still the 23 Aug validator-sale post at 39 lk / 604 imp, which is the discovery-led shape: one hard number in the first line, then the mechanism. Healthy and slightly up on run 317 (15.5 / 259). |
| code:editorial-notices | 2026-08-26 | run 309 - NEW SOURCE KEY, the run's spine, measured against the production DB and the live /maintenance index. TWO independent notice mechanisms. (1) Hand-placed banner blocks, six variants in src/types/blocks.ts (stub \| unsourced \| outdated \| promotional \| cleanup \| coi), labels fixed in BANNER_META at src/components/BlockRenderer.tsx:407. FIVE exist across 370 pages: promotional on ecosystem/blue-chick-nfts, /unisci, /unix (all three Dormant or Closed), stub on core-protocols/kernel-layer and /application-layer. unsourced, cleanup and coi have never been used. (2) src/lib/freshness.ts synthesises an outdated notice at >180 days from lastVerifiedAt ?? updatedAt and defers to a hand-placed one (PageContent.tsx:557). 224 of 369 categorised pages carry a stamp; ZERO are past 180 days; the oldest is 150. Separately src/lib/maintenance.ts derives four queues at /maintenance, empty ones unrendered: orphaned 19, unsourced 13, incomplete 2, outdated 0 (absent). The quality grade is set on 6 of 370 pages. |
| code:scrypto-component | 2026-08-24 | run 298 - NEW SOURCE KEY, and the spine of the components deepening. radixdlt-scrypto scrypto/src/component/component.rs (17,807 B): ComponentState::instantiate calls object_new and returns Owned with no address; prepare_to_globalize(owner_role) returns a Globalizing builder taking metadata / roles / enable_component_royalties / with_address(GlobalAddressReservation); globalize() attaches RoleAssignment ALWAYS, Metadata ALWAYS (defaulted when unset), Royalty ONLY when enabled, then calls object_globalize for the address. Royalty amounts are stored per method with a locked flag (royalty_amounts.insert(method, (royalty, !updatable))). radix-common/src/address/hrpset.rs confirms the two prefixes: GlobalGenericComponent -> component_, InternalGenericComponent -> internal_component_. |
| onledger:ascent-supply | 2026-08-25 | run 304 - NEW SOURCE KEY, and the finding is the absence of movement. POST mainnet.radixdlt.com/state/entity/details for resource_rdx1t46jpmzf97s7q5h4tv42hcjyalhq84znevngtsul5wcumxfdprnlp3 at epoch 338142 / state version 554,854,879 (25 Aug 2026 19:07:04 UTC) returns total_supply 888312759.484262, IDENTICAL TO THE LAST DECIMAL to the epoch-334014 read of 11 Aug. Nothing was burned in fourteen days. Roles confirm the framing: minter DenyAll with minter_updater DenyAll, burner AllowAll. Re-read next ecosystem rotation - the moment one cosmetic is bought this decays. |
| onledger:bullring-fees | 2026-08-20 | BullringFeeCollection component_rdx1cqwqdtcv3pakggnyzguzweuc9drytqe3snkrse87h8jckjcz6gfdht, read 20 Aug 2026: fee_rate 0.03, auction_count 108, total_collected 4,924.2609 XRD (~164,100 XRD settled since the 18 Nov 2025 launch, avg ~1,520 XRD). LAST fee deposit 24 Mar 2026 - nothing settled in five months. Admin badge matches the one the dApp definition account holds. |
| onledger:deliver-token | 2026-08-20 | run 279, epoch 336,751: DELIVER resource_rdx1t466mhd2l2jmmzxr8cg3mkwjqhs7zmjgtder2utnh0ue5msxrhyk3t - supply 1,000,000,000, divisibility 18, minter/burner/freezer/recaller ALL DenyAll AND all four *_updater roles DenyAll (so the denials are permanent, not merely current). metadata_setter resolves to Owner. info_url is https://deliverxrd.com, which answers HTTP 404 / 2,516 B off Wix nameservers (ns12/ns13.wixdns.net) on 20 Aug 2026. social_urls: t.me/DELIVER_XRD (preview exists, no title) and x.com/DELIVER_XRD (not probed - x.com 402s). |
| onledger:lsulp-holders | 2026-08-19 | run 273 - NEW SOURCE KEY, and THE RUN LEAD. The holder query the prose grep cannot do: 940 holders of LSULP at epoch 336,462 (19 Aug 2026 23:07 UTC). Weft Finance holds the most by far, across THREE components - Weft Lending Pool V2 (component_rdx1czmr02y...) 51,051,122.67, Weft Lending Market V2 (component_rdx1cpy6put...) 9,883,163.20 and 'C9 LSULP Pool' (component_rdx1cr5cnuz..., described on ledger as the 'Weft C9 LSULP Lending pool') 1,476,638.10 = 62,410,923.97, or 23.6% of supply. Then RSwap's LSULP/DCKS pool (pool_rdx1ch7xn38...) 17,293,134.15 (6.5%), CaviarNine's OWN HyperStake LSULP/XRD pool (pool_rdx1chmckjp...) 9,783,770.32 (3.7%) and Stabilis (component_rdx1cq70cja...) 1,053,413.26. Surge does NOT appear in the top 40, so its LSULP margin acceptance is not a held balance - do not assert one. Re-run each ecosystem rotation while the wind-down is live. |
| telegram:RadicalVibing | 2026-08-27 | run 313: nothing past 475 for a fifth consecutive run. |
| telegram:hyperscale_rs | 2026-08-27 | run 313: 30 messages in the two-day window, six past the run-310/312 watermark and none of them substantive. 10893 (26 Aug 23:58 UTC) asks flightofthefox whether radixdlt/babylon-ledger-app, the Ledger hardware-wallet app, will need changes to stay compatible with the Xi'an work; unanswered at the time of the scrape, so nothing to publish. BANKED as a watch: if it is answered, hardware-wallet compatibility belongs on the Xi'an page. |
| web:consultation-dapps | 2026-08-18 | run 265 - NEW SOURCE KEY, and the method is the finding: A DAPP'S RUNTIME CONFIG NAMES ITS DAPP DEFINITION, SO TWO HOSTNAMES CAN BE TOLD APART WITHOUT LOGGING IN. vote.radixdao.org serves /app-config.js declaring account_rdx128965k8mhauk679vtew96ynq4k43rzd975jak4d5z6cvp0t0c6z7u0; consultation.mountain-top.live serves /config.js declaring account_rdx12y8wqqgpjndcns9m94tjyhmfyx3hujf5snqqqjmu86vrcvg8zsx88y plus VOTE_COLLECTOR_URL api-consultation.mountain-top.live. Different asset bundles too (voteResultsAtom vs temperatureChecksAtom). Both 200, both mainnet. |
| web:defillama-adapters | 2026-08-11 | github.com/DefiLlama/DefiLlama-Adapters projects//index.js names the exact component address a Radix protocol TVL is read from — the way to ground an ecosystem DeFi page in the same numbers the dashboard shows. |
| web:marketplace-vscode | 2026-08-17 | run 258 - BANKED FALSE POSITIVE for the developers rotation, do not re-probe. check-links reports marketplace.visualstudio.com/items?itemName=rust-lang.rust-analyzer as status 0 / fetch failed; with a browser UA it is 200 / 80,156 B. Same UA class as t.me. |
| web:notion-predecessor | 2026-08-25 | run 302, NEW SOURCE KEY and it is this wiki's own ancestor. The eleven notion.so URLs in the corpus resolve to a Notion workspace whose spaceName is literally 'Radix Wiki', spaceDomain 'radixdlt', spaceId 519183ae-9211-4e91-b978-311452f08ddd. Ten sit in /ecosystem (the eleventh, an asteriskdao one-pager on /contents/tech/core-concepts/decentralized-science-desci, is a different space and was NOT touched). Seven are rows of one collection, 4c677f9c-8b6a-4925-8507-a96ca797237e, whose schema is Name / Github / Twitter / Telegram / Discord / Website / Categories / 'Open to work' and which Dan Hughes' row names '🦄 Radix Talent Pool'; six of those seven were last edited within minutes of each other on 29 Nov 2024 and have not moved since. The other three are concept pages - Radix Mainnet Olympia, Radix Developer Environment Alexandria, Cerberus Consensus Protocol - whose titles match this wiki's own articles word for word, which is what dates the lineage. PROBE: POST notion.so/api/v3/getPublicPageData with {type:'block-space',blockId:,name:'page'}. Every one returned publicAccessRole 'read_and_write', requireLogin false, isDeleted false, guestSetting.type 'can_add', isPublicShareLink true. All ten retired this run. |
| web:radicalstaking.com | 2026-08-27 | Operator site. Publishes 125,245,039 XRD active stake and 8,753 delegations, undated, against 148,990,076 XRD on-ledger at epoch 338766. Names its partners as Ociswap, Radix Collection, Delphibets, Cerby, Arcane Labyrinth and SRWA; team Wilson Verardi, Jason Lee, John Buell. |
| web:radix-frontend-npm | 2026-08-25 | run 303 - NEW SOURCE KEY, and the spine of this run's ROLA correction. Read at the registry and inside the published tarballs, not from docs. @radixdlt/radix-dapp-toolkit latest 2.3.0, published 2026-03-02; its dist/index.d.ts is authoritative and says withProof: (value?: boolean), walletApi.sendRequest: () => WalletDataRequestResult (NO arguments), walletApi.provideChallengeGenerator: (fn: () => Promise) => void, setRequestData(...builders), sendOneTimeRequest(...builders) - and requestProofOfOwnership appears NOWHERE in the package. WalletData.proofs entries are {address, type, challenge, proof:{publicKey, signature, curve:'curve25519'\|'secp256k1'}}, byte-for-byte the SignedChallenge type @radixdlt/rola exports. @radixdlt/rola latest 2.1.0, published 2024-11-20, 3,564 downloads in the month to 2026-08-24, 661 in the last week; Rola(input) exposes exactly one method, verifySignedChallenge(signedChallenge) -> ResultAsync. @radixdlt/babylon-gateway-api-sdk latest 1.10.1, published 2025-03-06; its RadixNetwork map is 1,2,10,11,12,14,32-37,240,241,242 - THERE IS NO 13. |
| web:radixtalk-rac-rfps | 2026-08-21 | run 280 - NEW SOURCE KEY. The two Permanent RAC candidacy threads read in full at the Discourse API. 2313 (Timan Rebel self-nomination, 15 Jul, 4 posts, last 20 Jul) names the skill gaps he wants filled - bizdev, fundraising, marketing, governance/compliance, treasury - and drew two further declarations (Leonets/BONDIX, linuxx) plus one non-candidate service pitch (EarthNode GIS). 2312 (Giles Morris, business/finance remit, pro bono, 15 Jul, 7 posts) last moved 13 Aug: he is travelling 14 Aug to 13 Sep and off Telegram, contactable by email. NOT WRITTEN AND DELIBERATELY SO: post 4 of 2312 is a personal political attack on a named candidate. That is forum argument about a person, not a fact about the election, and it stays off the wiki. |
| web:solana-terminology | 2026-08-21 | solana.com/docs/references/terminology 200: "Sealevel - Solana's parallel run-time for onchain programs" and "transactions entry - a set of transactions that may be executed in parallel". Settles the single-threaded error. |
| web:t.me-author-verify | 2026-08-21 | run 284, fifth use and the one that earned it. Five authors resolved via the ?embed=1&mode=tme markup: 998993/998997/998998 = "avaunt > Debix \| Atomix \| Bullring", 998982 = "MAvRe", 998989 = "Daffy", 999003/999004 = "Timan \| Astrolescent", and 999005 = "MAvRe" - which is the catch, because 999005 is first-person CaviarNine team voice REPOSTED by a community member. Position in the transcript would have attributed a co-founder statement to the wrong person. The original is t.me/caviarxrd/70246, authored "Tronn \| CaviarNine". |
| web:wayback-spr-images | 2026-08-18 | run 266 — NEW SOURCE KEY, and it opens a question rather than closing one. /contents/resources/radix-visuals asserts the 79 retired images.spr.so graphics had "no surviving master copies to re-host". One CDX call on images.spr.so* returns 82 MB of 200-status snapshots — but that host was a shared Super.so CDN serving many unrelated sites, so domain-level volume proves nothing about THIS wiki’s 79 URLs. Unresolved; the check needs the 79 URLs recovered from the page’s pre-1-Aug revisions and run through CDX individually. Do not restate the page’s claim as verified until that is done. |
| web:youtube-radixradio | 2026-08-23 | run 295 re-read of the run-286 baseline and EXTENDED with per-video counts. youtube.com/@radixradioontwitter1761/videos, 23 Aug 2026: 30 subscribers, 8 uploads, view counts 96/94/12/63/32/30/96/18 = 441 total, best episode 96. Titles run Episode One..Episode Seven plus 'RadixRadio #24, with Shai S, Founder, Reizor Music' - so the channel is a PARTIAL archive of a show that reached at least 24 episodes, and the figures floor the reposted archive rather than measuring the live Spaces audience. Fetch note: the channel needs -L --compressed and the counts live in metadataParts, not the legacy subscriberCountText key. |
| code:radix-wiki-banners | 2026-08-21 | BANNER_VARIANTS in src/components/BlockEditor.tsx offers all six variants including coi; BANNER_META in BlockRenderer.tsx renders them. The coi variant is producible and has never been used. |
| gateway:fee-destination | 2026-08-23 | run 296 - NEW SOURCE KEY, and the live half of the fee correction. POST mainnet.radixdlt.com/stream/transactions with opt_ins receipt_fee_summary + receipt_fee_destination returns the split per transaction, which is the one-call way to check a costing constant against the ledger instead of trusting source. txid_rdx15gl7urc8kn36mjeq0hwru4mhn9t6uknkh7c7vsnw7tkh6t85zh9q6t3jzn, state version 553,951,096, 23 Aug 2026 23:11:21 UTC: execution 0.3643451 XRD over 7,286,902 cost units = 0.00000005 each EXACTLY; finalization 0.0410076 over 820,152 = 0.00000005 EXACTLY; storage 0.09574889972 / 0.00009536743 = 1,004 bytes EXACTLY. Destination against network fees of 0.50110159972: to_burn 0.25055079986 (50%), to_proposer 0.12527539993 (25%), to_validator_set 0.12527539993 (25%). Three consecutive user transactions returned byte-identical fee summaries, so this is the standard shape rather than one sample. |
| onledger:gable-dapp-def | 2026-08-27 | Gable Finance dApp definition account: last committed transaction 2024-04-22T09:28:54Z. On-ledger name "Gable Finance". |
| onledger:stakesafe-fees | 2026-08-22 | run 289 STANDING-WATCH RE-READ at epoch 337,230, unchanged from the run-284 reading: all three StakeSafe validators still registered at fee 0.15 with the increases still queued and none withdrawn - Amsterdam 75,955,969.31 XRD (rank 23) to 0.25 at epoch 339,608; Rotterdam 81,194,581.99 (rank 21) to 0.25 at 339,609; Seed Node 210,148.86 (rank 94) to 1.0, a 100% fee, at 339,609. /ecosystem/stakesafe states all three as pending, so the page remains correct. ~30 Aug is still the settle date. |
| onledger:trove-resource | 2026-08-20 | run 279, epoch 336,750: TROVE resource_rdx1tkl09e0ahgrxpwm4t5frseadp80thu5hm6n0zlzrn6ztddlm60wex8 is a FungibleResource, total_supply 500,000,000, info_url still https://trove.tools, and /stream/transactions returns exactly ONE affecting transaction in its whole history - txid_rdx19u2rz4ns9kl3kxweaw2nu5yfznwcv074sz73n0d2kmuhauggjrvqxpt2rm, 10 Feb 2025. github.com/ripsource/TROVE created 4 Jun 2023, pushed once 3.5 minutes later, desc "Application for Radix Booster Grant", archived false. |
| web:anza-validator-reqs | 2026-08-21 | docs.anza.xyz/operations/requirements 200: 12 cores/24 threads, 256 GB RAM (ECC suggested), separate NVMe for accounts/ledger/snapshots, voting up to 1.1 SOL/day. Primary source for the Solana hardware floor. |
| web:ch-simmons-officers | 2026-08-25 | run 300 - NEW SOURCE KEY, and the spine of the new page. Companies House officer lists read 25 Aug 2026. RDX Works Ltd (10864928): ADAM LESLIE SIMMONS, director, appointed 18 December 2023, resigned 24 January 2025, British, born September 1991, correspondence address 7 Bell Yard. That is his ONLY appointment anywhere in the UK Radix group. The Radix Foundation (12106715): 5 officers / 4 resignations, and the only ACTIVE one is Andrew John Jarrett, appointed 10 February 2025 - no Simmons, despite the 29 Jul 2025 blog announcing he would join its board. RDX Holdings (14648189): no Simmons either. METHOD, and it is the same one run 287 used for Hine: settle the negative on each company own officer list, then explain the gap rather than assert a contradiction. The gap here has a named cause - control moved to Radix Foundation Limited (Jersey, 156362) in Feb 2025, and Jersey publishes no director list. |
| web:docs.shardspace.app | 2026-08-15 | run 244 re-measure of the run-242 baseline, and NOTHING has moved: llms.txt still indexes 49 entries with exactly 11 carrying a COMING SOON! description, and roadmap.md still lists Ecosystem Insights and a Network Explorer under Q1 2024 undelivered. Byte-for-byte the same measurement two runs apart — no restart, no rewrite due yet. |
| web:github-babylon-node | 2026-08-12 | radixdlt/babylon-node @main - GenesisConsensusManagerConfig.java carries the mainnet genesis consensus config and the developer comment explaining the 100% reliability requirement. |
| web:radixdlt-post-paths | 2026-08-22 | run 288 - NEW SOURCE KEY, and it clears a whole legacy citation class. A wiki-wide census counted 30 occurrences of radixdlt.com/post/ over 7 pages (token-unlock 14, partnerships 8, homepage 3, tempo-consensus-mechanism 2, radix-mainnet-olympia 1, rcnet 1, blog/ten-10x-moments 1), 21 distinct URLs. Probed all 21 with a browser UA following redirects: 20 answer HTTP 200 after a 301 to the identical /blog/ slug. The 21st, radix-partners-with-argent-the-worlds-easiest-to-use-defi-wallet, 301s to /blog/ and then 404s - and it is ALREADY Wayback-wrapped on /contents/history/partnerships, which is why check-links reports the category clean. So /post/ is a live redirect, not a death: rewrite it for canonicality, never because it is broken. |
| web:youtube-tokenunlock | 2026-08-22 | run 288: youtube.com/watch?v=RvZRPs_rOgg oEmbed 200, "Radix \| Unlock Tokens Update", author Hashfield Technology (a community channel, not a Radix account). The video /contents/history/token-unlock cites in its infobox is alive; the embed now sits at the end of that infobox. |
| code:radix-fee-constants | 2026-08-23 | run 296 - NEW SOURCE KEY, and THE RUN LEAD: the fee model read at the constants rather than at the knowledge-base article, and it CORRECTED this wiki. radixdlt-scrypto@main radix-common/src/constants/transaction_execution.rs: EXECUTION_COST_UNIT_PRICE_IN_XRD and FINALIZATION_COST_UNIT_PRICE_IN_XRD both 0.00000005; STATE_STORAGE_PRICE_IN_XRD and ARCHIVE_STORAGE_PRICE_IN_XRD both 0.00009536743 (commented '1 MB = 6 USD'); EXECUTION_COST_UNIT_LIMIT 100,000,000; FINALIZATION_COST_UNIT_LIMIT 50,000,000; EXECUTION_COST_UNIT_LOAN 4,000,000; PREVIEW_CREDIT_IN_XRD 1,000,000 (commented '$60000'); MAX_PER_FUNCTION_ROYALTY_IN_XRD 166.666...; USD_PRICE_IN_XRD 16.666... i.e. 1 XRD = $0.06. THE SPLIT: NETWORK_FEES_PROPOSER_SHARE_PERCENTAGE 25 and NETWORK_FEES_VALIDATOR_SET_SHARE_PERCENTAGE 25, TIPS_PROPOSER_SHARE_PERCENTAGE 100 and TIPS_VALIDATOR_SET_SHARE_PERCENTAGE 0. radix-engine/src/system/system_modules/costing/fee_summary.rs computes to_burn_amount() as (tips + network_fees) - to_proposer - to_validator_set, so the burn is a RESIDUAL of exactly 50%, not a first cut of 50% followed by a 25/75 split of the rest - which is what /developers/transactions/03-transaction-fees had said. Also decisive: CostingParameters::latest() in radix-engine/src/transaction/transaction_executor.rs still returns babylon_genesis(), so no protocol update since Babylon has moved any of these numbers. |
| github:official-examples | 2026-08-14 | run 241 - NEW SOURCE, and the sharpest finding of the run. docs.radixdlt.com delegates its Stokenet deployment step to radixdlt/official-examples step-by-step/08-ledger-ready-gumball-machine README, whose 'Deploy the package to Stokenet' opens 'Go to the Stokenet Developer Console Website' linking stokenet-console.radixdlt.com/deploy-package - HTTP 530, no origin, checked 14 Aug 2026. The same README is the source for two things the wiki was missing: the exact wallet faucet path (account name > three dots > Dev Preferences > Get XRD Test Tokens) and the 'Owner role' / 'Owner role updatable' dropdowns the deploy form requires. |
| onledger:atomix-dapp-def | 2026-08-20 | account_rdx16yfhd6hf6ffcutzxmrxvqzh4ag9fs2j0x00skz5wtkpv6mkmt4f68n last on-ledger activity 23 Mar 2026, the same week Bullring last settled. Not proof of Atomix status - a dApp definition account is not the operating component. |
| onledger:radquest-assets | 2026-08-20 | run 278 - NEW SOURCE KEY, epoch 336,703 / state version 552,583,231, 20 Aug 2026 19:11 UTC. RadQuest Hero Badges resource_rdx1n2mvky7na57d832lypd9xy5ftxt7lynu3flyn084gfncayshmmdwga total_supply 200,158 (one per quester, so it is a headcount); RadMorphs resource_rdx1nt2q2rks2xgus6etcpeq4c8ysuj0l5pwhs9r3cxw6qtly5kxqddp2e total_supply 10,984, about one in eighteen. LAST ACTIVITY: last RadMorph minted 2026-04-27T06:24:15Z (burning 2 RadGems + 1 Morph Energy Card); last tx against questRewardsV2 component_rdx1cpklwp2zr6padewcxdkvnqydwp6mlzquyuuvlsztm8agdjdpmfzkxc 2026-04-27T06:38:07Z; one further Hero Badge tx 2026-05-01T06:59:53Z, then nothing. The dApp stopped 15 weeks before the domain did. |
| telegram:RadixDevelopers | 2026-08-27 | run 313: unchanged, nothing past 66055 for a tenth consecutive run. |
| web:ch-rdxworks-officers | 2026-08-22 | run 287: RDX Works Ltd (10864928) officer list read 22 Aug 2026 - 8 officers / 6 resignations, and no Hine among them. The Companies House officer INDEX returns four people named Matthew Hine (born Sep 1982, Oct 1985, May 1974, Feb 1996), none connected to a Radix company. Current directors are Christopher Frank Hodgson and Claire Elaine Tait, both appointed 29 Jul 2025. METHOD: settle a negative on a company's own officer list, not on a name search - the search alone cannot distinguish "no appointment" from "filed under a different name spelling", which is exactly the trap the seven Ridyard officer records set. |
| web:cloudflare-403-class | 2026-08-24 | run 298 - NEW BANKED FALSE-POSITIVE CLASS for the contents/tech rotation, do not re-probe. Six unrelated hosts flagged 403 by check-links (bitcointalk.org, aibc.world, axieinfinity.com, cepr.org, stanford-jblp.pubpub.org, coinvise.mirror.xyz) all return 403 with a 5,313-5,816 B body to a browser UA, and axieinfinity.com identifies it: title "Just a moment...", five cloudflare markers in the body. It is the Cloudflare interstitial, not a death. The narrow 5.3-5.8 KB band IS the signature - a real 404 on a modern framework host runs an order of magnitude larger (see web:aave-docs at 255 KB). |
| web:defillama-caviarnine | 2026-08-19 | run 270 - NEW SOURCE KEY, the measurement behind 'the economics no longer work'. api.llama.fi/protocol/caviarnine, 875,721 B, 1,038 daily points: PEAK $42,087,970 on 9 April 2024, LATEST $452,231 on 19 August 2026 - a fall of about 99% over 28 months. The series is continuous, so this is a decline rather than a tracking break (contrast the surge-trade adapter, zero since 25 March 2026). |
| web:github-gable-finance | 2026-08-27 | 2 public repos, neither archived. Last pushes: gable 2023-12-13, gable-v1 2023-11-07. |
| web:github-hyperscale-rs | 2026-08-18 | run 262 census: 2,978 commits total, 2,895 flightofthefox (was 2,752 of ~2,900 on 9 Aug). The key-man reading HOLDS and gets sharper: the only other substantial contributor, kaldeberger (68 commits, CI/deployment/terraform), ran 15 Dec 2025 - 31 Jan 2026 and has committed nothing since; every other contributor has 3 commits or fewer. Newest commits are post-quantum: aa1adef93009a751e176ae3435b0c7ef5485d8d9 (16 Aug) adds transaction signing and verification under ML-DSA-65, with f9a4ced3 and ba81891c adding the securify upgrade flow and a virtual ML-DSA-65 account scenario. |
| web:github-hyperscale-vm | 2026-08-18 | run 262 contributor census + commit read, the spine of the /community/flightofthefox refresh. hyperscalers/hyperscale-vm is 293 commits, ALL flightofthefox (was 133 on 9 Aug, so 160 in nine days). Two fronts read at the commits: authorisation moved off raw signatures on 13 Aug (fc4ce4065af566a08b8a6b542fa52a3759ac619d "Let a signature sign in and nothing else; guarded methods take badges"), and from 16 Aug the run is making value linear - 04f790e8d0abda0dcd2788c265bf3f9966a3465c (value crosses as a handle the guest cannot open), e3bbbb88f5ec8a39db3883b850c5427f06de65a0 (a cell types the resource it holds), 5f26ec0dcd868edc73aea7db16c04c0dd4c60568 (a body that lets go of value is refused). |
| web:github-radixdlt-core | 2026-08-08 | run 205: read the four core repos through the GitHub + npm APIs. babylon-wallet-ios last commit 30 Jul 2026 (PR #1513) / release 1.18.4 (25 Nov 2025); babylon-wallet-android 31 Jul 2026 (PR #1447) / 1.22.1 (9 Jun 2026); babylon-gateway 20 May 2026 (PR #840, docs) / v1.10.6 (7 Apr 2026); radix-dapp-toolkit last main commit AND last release both 2 Mar 2026 (v2.3.0, npm latest unchanged since), pushed_at across all branches 24 Mar 2026, not archived. The toolkit is the outlier: no volunteer upkeep at all. |
| web:github-vm-comparison | 2026-08-19 | run 272 — NEW SOURCE KEY, and THE RUN LEAD. api.github.com/repos/hyperscalers/vm-comparison: public, created 2026-08-19T17:34:11Z, ONE commit 20a2ef88 "Initial bench." by flightofthefox at 17:36:02Z, description "Throughput comparison between HS-VM and RE". README 9,696 B read whole. Result, Apple M-series, 1000 transfers, best of 3: total 39.35 us/tx hyperscale against 797.91 Radix Engine = 20.3x, 25,412 vs 1,253 transfers/second; execute is the whole gap (29.58 vs 792.55, 26.8x) and hyperscale is SLOWER at validate (7.95 vs 2.88) where it pays for admission and shard routing. Self-checked against radixdlt-scrypto's own criterion bench (833 us; harness reports 798-826). Constraints the harness publishes itself: RE's Account is native Rust and hyperscale's is wasm (the fast side pays a wasm bill the slow side does not), RE must lock_fee and hyperscale has no fee concept, no signature verification and no merkleization on either side, in-memory maps both. The 4-core "up to ~102,000 tx/s / 81x" column is EXTRAPOLATED and the README says so — do not publish it as a result. What IS structural: Babylon's column is flat because the committer executes one ledger sequentially and a manifest's references are a visibility grant, not a conflict set, so there is nothing to schedule on. |
| web:linkedin-adamsimmons | 2026-08-25 | run 305 - THE RUN-300 CONTROL HAS GONE BEHIND THE WALL. Run 300 established /in/adamsimmons1 as a known-good LinkedIn slug at HTTP 200 / 652,091 B, which is what made the 999 wall on /in/adamsimmons meaningful. Re-probed 25 Aug 2026 23:0x UTC, one client, browser UA, redirects followed: /in/adamsimmons1 now returns 999 / 1,530 B, identical to /in/richardjarram/ (which check-links had flagged 404 / 9,169 B), /in/richard-jarram and /in/thomas-starzynski/. The sibling method settles it the same way it settled x.com/beemdvp at run 304, but with the opposite conclusion: the wall now answers EVERY path, so no linkedin.com/in/* citation on this wiki can be confirmed or refuted from here. Wayback is no help either - the CDX for both richardjarram spellings returns an empty array, because LinkedIn is excluded from the archive. Keep every LinkedIn citation; stop spending probes on them. |
| web:vercel-error-headers | 2026-08-19 | run 273 EXTENDS the run-267 key with the two headers that separate a dead site from a firewalled one, and both classes appeared in this rotation. x-vercel-error: DEPLOYMENT_PAUSED (503, 99 B, text/plain) = the deployment is off - leafnode.info, already documented on its page. x-vercel-mitigated: deny (403, 59 B) = Vercel's firewall denying the automated request while the site is alive - www.liquifyxrd.app and its apex, both. Read the header, not the status: the link checker reports 503 and 403 and cannot tell these apart. |
| code:radix-wiki-freshness | 2026-08-20 | src/lib/freshness.ts reads the last_verified_at COLUMN; four pages had been stamped into metadata instead |
| db:ecosystem-status-index | 2026-08-24 | run 297 STANDING CHECK, second run of it, and there is NO DRIFT this time. 147 ecosystem pages bucket as 62 Active / 43 Dormant / 33 Closed / 4 Testnet / 3 In development / 1 Pre-launch / 1 Departed; /contents/resources/radix-ecosystem-operational-status heads read Operational (62), Testnet-pre-launch-in-development (8), Dormant (43), Closed and departed (34) and every one of the 147 slugs is listed. Note for the query: the index stores hrefs as \"/ecosystem/\", so a JSON.stringify'd haystack needs the escaped quote or every page reads as missing. |
| onledger:avaunt-validator | 2026-08-22 | run 289 STANDING-WATCH RE-READ at epoch 337,230, six days before the announced 28 Aug handover: validator_rdx1sd9uhhpml8vjz8uz0tut9jzv2mx326jdusfxjpccccj2904s8ndhqq still registered, still named Avaunt/ShardSpace, still 2% with no fee change queued, still accepting delegated stake, rank 8 of 188 - and stake has ticked DOWN for the first time, 148,944,934.79 (epoch 337,087) to 148,940,582.25. The ledger has not moved on the transfer. |
| onledger:dao-quorum-basis | 2026-08-23 | run 293 - NEW SOURCE KEY, and the sharpest thing in the run. The five on-ledger quorums are FIXED XRD amounts, not percentages the contract computes at the snapshot, and the four distinct figures sit in an exact 10 : 7 : 5 : 3 ratio to one base of 13,508,325,920 XRD. That base is NOT eligible voting power. XRD total supply read at the state version of the first parameter write (549,111,658, 12 Aug 17:23:20, epoch 334,377) is 13,508,342,408.66 - the same number to within ~16,500 XRD, about half an hour of issuance. So DAO Parameters SS3.2's 10/7/7/5/3% were struck against TOTAL SUPPLY while SS3.2 itself defines quorum against eligible voting power at snapshot and SS8A defines that as a strict subset (liquid XRD + LSU + LSULP + eligible LP). Against the smaller base each deployed threshold is a LARGER share, i.e. harder, than the registry's own percentage reads. And nothing tracks inflation: supply grows ~300M XRD/yr, so an untouched figure drifts down as a share of supply until an owner-gated update_governance_parameter_set call moves it. Two registry tests are not encoded at all - SS3.3A Minimum Affirmative Support and the 50-unique-address Treasury floor - because StandardProposalParameters has only voting_days, quorum, approval_threshold. |
| onledger:fee-change-queue | 2026-08-24 | run 297 - NEW SOURCE KEY, and THE RUN LEAD. One paginated /state/validators/list read gives every pending fee change with effective_at_epoch, and at_ledger_state {epoch:N} on /state/entity/details gives that validator's stake vault AT that epoch - so a before/after stake series across a fee change costs one call per point. Measured at epoch 337,829: Radstakes 15->25% at 335,294 went 99,869,766 -> 93,028,935 XRD (-6.9%, rank 16); Cadwynbloc 50->75% at 332,966 went 68,350,833 -> 68,559,800 XRD (+0.3%, rank 29). Queue today: StakeSafe Amsterdam 15->25% at 339,608, StakeSafe Rotterdam 15->25% at 339,609 (157.1M XRD combined), StakeSafe Seed Node 15->100% at 339,609 (210,242 XRD), Leaf Node 1->100% at 341,223 (25,670,173 XRD). Active-set validators at >=50%: 15, of which 10 charge exactly 100%. |
| web:code.visualstudio.com | 2026-08-20 | run 278: TRANSIENT, not a class. check-links reported status 0 (fetch failed) on the second pass over /contents/resources/python-scripts/proof-of-work and had passed it clean twenty minutes earlier; a direct probe returns 200 / 246,786 B. Do not unwrap on a single 0 - re-probe first. |
| web:docs.google-flexathon | 2026-08-13 | run 233 - NEW SOURCE, and the run lead. The Google Doc the wiki has cited as "Flexathon Documentation" since the page was written exports to 4,214 characters of plain text and its last diary entry is "Day 3: Nov 25th" - three days into a nineteen-day hackathon whose stated deadline was 11 December 2020. It carries the mission statement, the motive (the UC Davis-co-authored Cerberus paper had been public three months and "some in the crypto community has been spreading doubt"), Hughes own caveats ("it WILL be buggy, it WILL crash, it will NOT be commercial grade"), the four follow-along sources, and Days 1-3 in a Good/Challenges two-column format. Nothing public covers the remaining sixteen days or whether the deadline was met. |
| web:github-buildwithgrove | 2026-08-17 | run 258 - NEW SOURCE, the hard artefact behind the wind-down. api.github.com/orgs/buildwithgrove: 195 public repos, org updated 2026-08-10, description "Get paid to create anywhere." Both repo pages read (100 + 95): ALL 195 are archived:true, and 112 of them carry pushed_at 2026-08-14T16:13:xxZ - a bulk archive sweep on 14 Aug 2026. For contrast pokt-network is 187 repos, org updated 2026-01-09, not archived - the protocol continues, the company does not. |
| web:github-flightofthefox | 2026-08-09 | run 214 - NEW SOURCE. The hyperscale-rs lead's public artefacts, read via the GitHub API on 9 Aug: account created 17 Feb 2022, company @proven-network, 3 personal repos. Commit record 1,692 proven-node / 345 proven-2pc / 2,752 hyperscale-rs / 133 hyperscale-vm. jellyfish-verkle-tree (24-25 Mar 2026) is a standalone experiment - JMT storage design plus verkle proof aggregation, Bandersnatch/IPA/Dankrad Feist, 576-byte constant proof - and is NOT wired into hyperscale-rs, which ships its own plain hyperscale-jmt crate. Re-read the commit counts before quoting them again; they move weekly. |
| web:github-wallet-gateway | 2026-08-12 | run 228: the two recurring developers-pass checks, both unchanged. radixdlt/radix-dapp-toolkit PR #326 is still open, created 2026-03-24T11:50Z, updated_at identical to created_at, zero comments and zero review comments in 141 days; last commit on main remains 2026-03-02 (Alex Stelea, release merge). npm @steleaio/radix-engine-toolkit registry modified 2026-03-04, still 6 versions, dist-tags latest=2.0.0-dev / dev=2.0.0-dev.5, so wallet-agent-ai 2.0.3 pinning 2.0.0-dev.5 exactly is unchanged and still the dependency risk banked at run 221. |
| web:radixtalk-p3-services | 2026-08-20 | run 278 - NEW SOURCE KEY. radixtalk.com/t/2238.json "Action on P3 Foundation Services", opened 17 Feb 2026 by Farah_Foundation, 7 posts, last 22 Feb 2026. Lists all ~25 P3 services verbatim and singles out RadQuest as the one carrying "ongoing monthly costs", with shutdown framed as reducing recurring opex. Sibling services with no wiki page and the same exposure: Gumball Club, IDOS Proof-of-Personhood, Radix Rewards, wallet.radixdlt.com, academy.radixdlt.com (explicitly "live but not maintained"), Olympia-explorer, Sandbox, dApp Catalog Service, XRD Supply API. |
| web:t.me-recycled-handles | 2026-08-20 | Full re-run 20 Aug 2026 over every t.me handle cited on the 146 ecosystem pages, metadata.telegram included: 56 distinct handles, all 200. Nine from the 1 Aug sweep already corrected. ONE new: @FotonMarketplace, created 18 Aug 07:11:55 UTC, 1 subscriber, gate button to @Collabslands_bot. Two others carry "verify you are human" gates but are genuine-age channels (@ROOTfinanceradix 301 subs, created Jun 2024; @DOGECUBE 55 subs, created Nov 2024) - not recycled, no action. |
| code:hyperscale-invariants | 2026-08-24 | run 298 - NEW SOURCE KEY. docs/08-invariants.md is 32,915 B and defines 75 stable IDs in eight families: INV-SEC 21, INV-EXEC 21, INV-BEACON 19, INV-SHARD 15, INV-RESHAPE 15, INV-DET 8, INV-STATE 6, INV-ECON 6. INV-VM-* IDs live in the VM own register at vm/docs/09-invariants.md, so the protocol register does not own them. INV-SEC-1 is the premise every other property is conditional on and it is stated in tiers: below f+1 unconditional, f+1..2f recoverable degradation rather than guaranteed safety, 2f+1 terminal and therefore prevented. |
| code:radix-wiki-mcp-server | 2026-08-17 | run 260 — NEW SOURCE KEY. This wiki own MCP server verified live: POST https://radix.wiki/api/mcp initialize returns serverInfo {name radix-wiki, version 3.1.0}, protocolVersion 2025-03-26, capabilities tools+resources. src/lib/mcp-tools.ts declares 11 tools (search_wiki, get_page, list_pages, get_categories, get_recent_changes, get_full_corpus, get_ideas_board, get_challenge, login, create_page, edit_page); the last three are the ROLA write path. https://radix.wiki/AGENTS.md 200 / 9,499 B, /agents-md 200. |
| code:radixdlt-scrypto-pool | 2026-08-19 | run 272 — NEW SOURCE KEY, and the spine of the second edit. radix-engine/src/blueprints/pool read at the source rather than at docs.radixdlt.com/docs/pool. v1/constants.rs: three blueprints (OneResourcePool/TwoResourcePool/MultiResourcePool) in one native package, one role, pool_manager_role. Instantiate rejects non-fungible resources (NonFungibleResourcesAreNotAccepted), mints a divisibility-18 pool-unit resource whose minter/burner require the component's global caller badge with BOTH updaters deny_all (permanently), and writes locked two-way metadata (component: pool_vault_number / pool_resources / pool_unit; pool unit: pool). calculate_amount_owed rounds ToNegativeInfinity to the reserve's divisibility — always down. package.rs carries PoolV1MinorVersion Zero\|One and dispatches every export by protocol version. updates/anemone.rs generate_pool_math_precision_fix_state_updates: PoolCode1 -> PoolCode2 code-substate swap, no schema change, logic only — v1_1 computes redemption in PreciseDecimal and converts back at the end, and contribute gained a ResourceDoesNotBelongToPool check. |
| dns:closed-project-domains | 2026-08-21 | run 282 - NEW SOURCE KEY, and it CORRECTED this wiki. dig A/NS/SOA over the four closed-project domains, 21 Aug 2026. THREE are genuinely gone: farbo.me, radket.com (and www.), nftwars.app all return NXDOMAIN - the registration itself has lapsed. ONE IS NOT: abandonedarena.com returns NOERROR with NO A and NO AAAA record, a live zone delegated to ns1/ns2/ns3.digitalocean.com with a valid SOA (hostmaster.abandonedarena.com). Only www.abandonedarena.com is NXDOMAIN. /ecosystem/abandoned-arena had asserted since July 2026 that "the domain no longer resolves"; it does resolve, it just serves nothing, and somebody is still paying for and delegating the name. Fixed this run. |
| onledger:asset-fund-wallet | 2026-08-27 | run 310 recheck of the Ecosystem Asset Fund wallet (account_rdx1297vs7up584rkwensy0jwzxq6g0xua67ca9trxdyr45cjnmzdak5x3) at epoch 338,431: it still holds 12,497,490.37 DELAY, unsold, confirming the /ecosystem/delay infobox figure to the token. Also visible and NOT yet on any wiki page: 204,395.44 DPH, so the fund bought the prediction market too. 37 fungible positions in all, including 590,060 XRD. |
| onledger:lsu-holder-census | 2026-08-27 | Stake-unit holder counts for the 12 largest validators at epoch 338766. Radical Staking 8,700, Jazzer9F 8,654, SRWA 3,051, Ocinode 2,176, CaviarNine-1 1,608, Weft 1,423, XSEED 982, Astrolescent 939, Cobra Stakes 758, Avaunt 429, RadixStaker 344, WOWO 342, Radix-Pipeline 226, Reddicks 82 — and Radstakes 121,414, dominated by dust last touched at state versions 9-10 (Olympia migration). |
| onledger:protocol-activity | 2026-08-12 | run 227: SRG read live at epoch 334255. total_supply 98,894,000 against the 100,000,000 minted at the 13 Nov 2024 TGE, so 1,106,000 SRG (~1.1%) has been burned. Authorities: minter deny_all but MUTABLE, burner allow_all and IMMUTABLE - the right to burn cannot be withdrawn, which is what makes the community-triggered buy-back real rather than a UI affordance. The SRG treasury component_rdx1czwd96pvxsuy2ydd25fulz242x36h257thn45tscp4rkxkrfy99958 is a FeeDistributor 1.0.0 holding treasury_virtual_balance 353.97. |
| telegram:dexter_discussion | 2026-08-05 | run 162: scanned 400d of t.me/dexter_discussion for the DeXter status check – retirement proposal 2026-02-18 (msg 27547), wind-down confirmation 2026-03-08 (msg 27603), contributor farewells 2026-03-09, last user report of the exchange UI 2026-03-16. Channel effectively quiet since. Note: t.me/community_project_x (announcements) no longer resolves as a username. |
| web:arxiv-prefix-consensus | 2026-08-24 | run 298 - NEW SOURCE KEY. arXiv 2602.02892 "Prefix Consensus For Censorship Resistant BFT", Xiang / Tonkikh / Spiegelman, 2 Feb 2026, 200. This is the algorithm hyperscale-rs beacon agreement implements and model E checks against, including the paper own Algorithm 7 soundness boundary (n >= 5f+1) mechanised as a broken twin at n = 3f+1. |
| web:ch-radix-publishing-uk | 2026-08-27 | Radix Publishing (UK) Ltd 14955990: Active, incorporated 23 Jun 2023, registered 234 Victoria Road Stoke-on-Trent, SIC 62090. Two officers ever - Jarrett (active) and Hughes (terminated 27 Jul 2025). Jarrett is its sole serving director. |
| web:github-babylon-nodecli | 2026-08-21 | run 283 - NEW SOURCE KEY, and the second edit’s spine. radixdlt/babylon-nodecli: NOT archived, but the newest release is 2.2.4 published 2025-01-13 and main’s newest commit is 2025-03-12 "ci: remove snyk (#132)" - 19 months frozen. Assets are babylonnode-ubuntu-20.04 and -22.04 only (272 downloads of the 22.04 binary), no 24.04 build; the wiki’s wget URL to /releases/latest/download/babylonnode-ubuntu-22.04 does 200 (redirects to the 2.2.4 asset), so the link checker was right and the page was still incomplete. The CLI carries NO node version: node-runner-cli/github/github.py latest_release() resolves the tag at run time and sys.exit(1)s if the lookup fails, with per-component overrides named in config/EnvVars.py (RADIXDLT_APP_/NGINX_/CLI_/GATEWAY_VERSION_OVERRIDE). |
| web:github-wallet-agent-ai | 2026-08-11 | run 221 - NEW SOURCE. wallet-agent-ai/wallet-agent-ai read end to end. Created 2026-05-16, default branch is 'v2.0' (NOT main; master and main-old also present - the fourth default-branch trap banked in a fortnight), 2 stars, 0 GitHub releases, last commit 2026-06-16T21:51:29Z. LICENSE is verbatim GNU GPL v3 and package.json declares GPL-3.0, though GitHub's detector reports NOASSERTION - the wiki's licence claim is correct. CHANGELOG dates 0.1.0 to 4 May, 1.0.0 to 10 May, 2.0.0 to 29 May 2026. npm 'wallet-agent-ai' has five versions, latest 2.0.3 on 2026-06-08T20:54:20Z, 119 downloads in the month to 9 Aug. Stack: LangChain/LangGraph with OpenAI, Google GenAI, Groq and Ollama adapters, plus an MCP server; src/mcp/known-pools.ts is 68KB (~130 pools, 32 tokens); src/cli carries init/derive/unlock/recover against a local keystore. It does NOT use the Radix dApp Toolkit - since 2.0.1 it pins @steleaio/radix-engine-toolkit at exactly 2.0.0-dev.5, a prerelease of 2026-03-04 drawing 35 downloads/month whose npm 'latest' dist-tag points at the OLDER 2.0.0-dev. |
| web:park.io-lapsed-domains | 2026-08-18 | run 264 - NEW SOURCE KEY, and the evidence class behind both rewrites. Two ecosystem project domains have been caught by park.io, a drop-catch registrar that buys names as they expire: stakebros.info publishes NO A record and has its nameservers delegated to park.io (nothing loads), and parabox.io resolves and serves the Park.io for-sale page verbatim ("parabox.io - a really cool domain parked on Park.io", 4,036 B over http; https fails TLS because the certificate does not cover the name). This is a stronger death signal than a 404 and check-links cannot see it - a parked domain answers 200. Wayback dates the stakebros.info death precisely: last working capture 13 Dec 2025, none after. parabox.io has captures only from 2021-2022. |
| web:radix-wiki-brand-files | 2026-08-26 | run 306 - the /contents/resources/brand-assets infobox re-measured against the files it describes, and every figure is right. radix.wiki/logo.png 200 / 449,911 B / 700x700 (page says 700x700, 440 KB), favicon.png 200 / 3,341 B / 32x32, favicon.ico 200 / 4,414 B (page says 4 KB). The colour table matches src/styles/globals.css token for token across all eight rows (surface-0 #393e50, surface-1 #444a5e, surface-2 #4f5569, border #52586e, accent #ff9da0, accent-hover #fff4cc, text #ffffff, text-muted #c5c9d6). Page stamped rather than edited. |
| web:radixdlt-booster-gable | 2026-08-27 | radixdlt.com/blog/babylon-booster-grants-gable, 21 Nov 2023, HTTP 200. Confirms the grant. Does NOT state $15,000. |
| web:radixdlt-booster-posts | 2026-08-27 | All 21 posts the funding table links, fetched and searched 27 Aug 2026. $15,000 appears only from ShardSpace (8 Dec 2023) onward: Weft 5 Jan, Fibonacci 11 Jan, XRD Domains 18 Jan, InfiniteLabs 24 Jan, RadLand 2 Feb 2024. The nine posts dated 3 Nov to 5 Dec 2023 state no amount. Launch post 11 May 2023 says "up to $10k USD". Reshape post 7 Feb 2024 (not March) sets MVP $5,000 / Launch "now $15,000" / Refine up to $50,000 / Growth up to $140,000, capped $160k per project. |
| code:radix-wiki-check-links | 2026-08-27 | run 310 ecosystem audit: 148 pages / 989 external / 39 embeds. 0 broken internal, 0 broken embeds, 0 non-standard images, 5 banked unverifiable embeds, 100 flagged externals. The count rose 87 -> 100 against run 307 entirely inside the web.archive.org class (43 -> 46 as UND_ERR_CONNECT_TIMEOUT) plus medium/defillama variance; NOT ONE flag sits outside a banked class, so zero probes were spent on the list. |
| github:radix-dao-governance | 2026-08-26 | run 308, and this is the arbiter the /ideas board should have been reading all along. Shadaffy/radix-dao-governance is the OPERATIVE repo; Shadaffy/radix-dao is the reference library and its own OPERATIVE-REPO.md says the operative one is updated only when a proposal passes. State read 26 Aug 2026: constitutional/, parameters/, governance/, legal/ and working-groups/ each hold one empty .gitkeep, so NOTHING is ratified; everything sits under pending/. Charter v1.0.0 last updated 2026-08-25 (commit 'pre-ratification quality pass across the policy library', 08:35:41Z), 29,866 B, zero [TBD]. GP-PRE-1-Framework-Ratification.md same commit; GP-ELECT-1-Permanent-RAC-Election.md 2026-08-05 (draft scaffold, 7 unticked TODOs); PROPOSALS.md 2026-07-29 (stale on the election mechanism); pending/README.md 2026-08-25T18:23Z. Re-read this repo at the head of every ideas rotation. |
| onledger:leafnode-validator | 2026-08-23 | Leaf Node validator_rdx1swzn5… at epoch 337,470: is_registered true, active set rank 45/100, 25,719,752.92 XRD active + 8,550,966.92 XRD pending withdrawal, fee 0.01 with a request for 1 at epoch 341,223. Owner badge [83853a5d…0793] proved from account_rdx1697zj… on 10 and 16 Aug, from account_rdx12ykjn… on 22 Aug, and held by the latter now. |
| onledger:validator-metadata | 2026-08-27 | Run 259: read name + description + info_url + effective_fee_factor for all 25 validator addresses published across the 24 ecosystem validator-operator pages. One mismatch (radiator -> BobbyStake). Cheap: two /state/entity/details batches plus one /state/validators/list walk. |
| onledger:validator-register | 2026-08-22 | run 289: full /state/validators/list read at epoch 337,230 (22 Aug 2026 15:06 UTC, state version 553,299,026). 287 validators, 188 registered, 4,685,936,982.82 XRD staked across them and 4,685,788,128.24 XRD across the top-100 active set - so at the ~300M XRD annual emission the GROSS network staking rate is 6.40%. The #100 cutoff is 45,500 XRD. This one read settled both staleness-head pages and re-confirmed two standing watches; it is the cheapest high-yield call in the ecosystem rotation and should open every one. |
| web:blockchain-expo-jarrett | 2026-08-27 | blockchain-expo.com/global/speaker/andy-jarret/ (Blockchain Expo Global 2023): CEO Radix Tokens (Jersey) Ltd, board of Instabridge and Instapass, in crypto from 2014, and the self-described claim "responsible for driving the crypto currency legislation in Jersey in 2015" - published on the page as his own bio, no independent corroboration found. |
| web:ch-jarrett-appointments | 2026-08-27 | Companies House officer record 7SX3GxdNZi1skxY7IsgQb3pg06w (Andrew John Jarrett, b. Jan 1967, resident Jersey): 3 current appointments - Radix Foundation 12106715 (dir 10 Feb 2025, active), Metaverse (Radix) FC040852 (dir 5 Sep 2023), Radix Publishing (UK) 14955990 (dir 23 Jun 2023, active). A second officer record YM-hOX9lO-_xdNkeDeegNWslsGw holds the fourth: Metabridge 13476191, 4 Oct 2021 to 14 Feb 2025. |
| web:companies-house-ridyard | 2026-08-18 | run 262 - NEW SOURCE KEY, the verification behind the /community/piers-ridyard freshness stamp. Officer record xNMnsQ-3_DNiimtW6aqDexwWSi4 re-read 18 Aug 2026: 7 appointments, UNCHANGED since the page was written on 7 Aug. Four carry resignation dates that match the page exactly (Metabridge 17 Jun 2025, RDX Works 17 Jun 2025, Radix Foundation 31 Jan 2025, GoodFi 1 Dec 2024); the three without resignations - Radix Publishing, Radix Tokens, Xoo Holdings - are all Dissolved, which is why the page carefully says he resigned every directorship held in a company STILL ON THE REGISTER. No new appointment. Stamped rather than edited. |
| web:dao-parameters-registry | 2026-08-19 | run 268 - NEW SOURCE KEY, 59,496 bytes at pending/parameters/dao-parameters-registry.md, and it settles every value the /ideas cards asked the community to settle. Quorum §3.2: Constitutional 10% / GovProcess 7% / Treasury 7% / Executable 5% / TC 3%, measured as Participation (YES+NO+ABSTAIN) against ELIGIBLE VOTING POWER at snapshot, plus a 50-unique-address absolute floor on Treasury. Approval §3.3: 66/60/50/50/50 against Decisive Votes (YES+NO). §3.3A Minimum Affirmative Support is NEW and has no Round-2 counterpart: YES floors of 3.5/2/1.5/1% of eligible voting power because ABSTAIN counts to quorum but not approval. §8A eligible sources: liquid XRD + LSU->XRD at snapshot are an ENTRENCHED constitutional floor (Charter §12.1 item 4); LSULP, Ociswap/CaviarNine/DefiPlaza LP units, precision and shape pools are RAC-governed tier 2 on 30-day notice. Delegation recorded "not yet enabled - pending platform support". §3A activation: ratification + activation both 66%/10%/3.5%; election opens within 90 days of ratification; >=5 KYC-verified Permanent RAC seats before the Activation Statement; advisory outcomes recognised at >=7% participation and >=50% YES. §7 WG: 1-3 stewards, 6-month terms, monthly reporting, $2,500 RFP threshold, $10,000 independent review panel, all effective from the Activation Date and binding ANY body with treasury-spending authority. |
| web:docs-core-api-providers | 2026-08-17 | run 258 - NEW SOURCE, read with a browser UA because WebFetch gets 403 from docs.radixdlt.com. docs.radixdlt.com/docs/core-api-providers 200 / 25,044 B, UNCHANGED and still wrong: "The foundation does not provide a public Core API", then Grove offering "immediate access ... for free using the following Grove-powered public endpoint as a base URL: https://radix-mainnet.rpc.grove.city/v1/326002fc/core", free "up to a total of 5m request per day", plus portal.grove.city for private endpoints. Both hosts are absent from DNS. NowNodes is listed at xrd.nownodes.io. Second instance of the run-241 class (Radix docs sending a developer to a dead host) and the one this run spent as a tweet. |
| web:github-danoshifusermoto | 2026-08-13 | run 233 - NEW SOURCE. github.com/DanoshiFusermoto/hackation, source #3 in the Flexathon diary, returns 404 at both the HTML and the API. The account (created 2019-04-18, Dan Hughes) has exactly TWO public repos today: Hyperscale (created 2025-03-11, pushed 2025-07-27, 27 stars) and incubator-milagro-java (2021-04-10). No public copy of the Flexathon prototype survives. |
| web:github-scrypto-releases | 2026-08-25 | run 301 - NEW SOURCE KEY, and it is the corroboration the whole run turns on. radixdlt/radixdlt-scrypto releases read through the GitHub API: v0.1.0 published 2021-11-12T16:26:06Z (created 16:00:17Z, author iamyulong, empty body), v0.2.0 2021-12-15T14:49:13Z with the body 'This is for Alexandria release', v0.3.0 2022-02-16T13:53:47Z, v0.4.0 2022-04-27T20:19:16Z. The tags endpoint confirms v0.1.0 is the EARLIEST tag in the repository - there is no v0.0.x - and the repo was created 2021-07-19T16:54:24Z, so it carried no tagged release at all for its first four months. v0.1.0 therefore lands on the afternoon of the Alexandria Preview Event in New York, which is what turns a retrospective sentence in a blog post into a dated fact. |
| web:radixdlt-group-entities | 2026-08-27 | learn.radixdlt.com 302s to radixdlt.com/articles-learn/what-is-the-radix-foundation-and-its-group-of-entities. Names Jarrett as CEO of Radix Tokens Jersey working with compliance and the local regulator; lists Foundation Ltd, Radix Tokens (Jersey), Radix Publishing Ltd, Radix Publishing (UK), Archetype Ltd. |
| gateway:effective-fee-factor | 2026-08-25 | run 305 - NEW SOURCE KEY, and THE RUN LEAD. The Gateway answers 'what fee does this validator charge' twice, and one of the two answers is a fossil. /state/validators/list gives every ValidatorCollectionItem an effective_fee_factor object: current is the fee actually charged, pending appears ONLY while a request is genuinely queued. /state/entity/details - the endpoint you reach for when you have one validator's address - returns NEITHER, only the raw validator_fee_factor and validator_fee_change_request. The schema at github.com/radixdlt/babylon-gateway/blob/main/src/RadixDlt.NetworkGateway.GatewayApi/gateway-api-schema.yaml declares effective_fee_factor required on ValidatorCollectionItem (current required, pending nullable) and declares it in exactly one other place, the required-fields list of the same type. Measured at epoch 338,190 (25 Aug 2026 23:08 UTC): CaviarNine-1 stored 0.0175 charges 0, CaviarNine-2 stored 0.017 charges 0, Cadwynbloc stored 0.5 charges 0.75, Radstakes stored 0.15 charges 0.25, all four with pending ABSENT; StakeSafe Amsterdam/Rotterdam/Seed Node and Leaf Node stored 0.15/0.15/0.15/0.01 charge the same, with pending 0.25 at 339,608, 0.25 at 339,609, 1 at 339,609 and 1 at 341,223. Avaunt is the only one of the nine whose request field is null. |
| web:learn-radixdlt-redirects | 2026-08-27 | run 296 - NEW SOURCE KEY, and it settles a whole citation class rather than one link. check-links flagged learn.radixdlt.com/article/what-is-radix-engine as status 0 / ETIMEDOUT on /developers/scrypto/01-fundamentals. It is a FALSE POSITIVE: with a browser UA it 200s, redirecting to www.radixdlt.com/articles-learn/what-is-radix-engine. A wiki-wide census then found 117 occurrences of learn.radixdlt.com across 42 distinct URLs on 20+ pages, and ALL 42 were probed: every one returns 200 through a path-for-path 301 to www.radixdlt.com/articles-learn/, and the bare host redirects to /learn/knowledge-base. Note www.radixdlt.com/articles-learn itself (no slug) is a 404, so the redirect is per-article, not a directory. ZERO deaths. Same shape as the run-288 radixdlt.com/post/ -> /blog/ class: a legacy host that works, not a broken link. Do not re-probe the set; do not mass-rewrite. |
| web:linkedin-jarrett-handles | 2026-08-27 | linkedin.com/in/andrewjarrett1 is the Radix CEO ("Andrew Jarrett - Radix Tokens (Jersey)", chartered director). linkedin.com/in/andyjarrett is a DIFFERENT person - Andy Jarrett of Kinexio, formerly Mallcomm, UK proptech. Both answer 999 to automated requests, so check-links cannot separate them. X handle is @andrewjarrett ("Andy.xrd"). |
| web:radix-wiki-agent-surface | 2026-08-26 | run 306 - NEW SOURCE KEY, the wiki measuring itself. Every figure on /contents/resources/mcp-server, probed live 26 Aug 2026. POST /api/mcp initialize returns serverInfo radix-wiki 3.1.0, protocolVersion 2025-03-26, plus an instructions string; tools/list returns ELEVEN tools (search_wiki, get_page, list_pages, get_categories, get_recent_changes, get_full_corpus, get_ideas_board, get_challenge, login, create_page, edit_page), of which only create_page and edit_page carry auth: 'rola' in src/lib/mcp-tools.ts; resources/list returns radix-wiki://llms.txt and radix-wiki://categories; get_categories totalPages 369 (llms-index.txt's header says 368, so the static header lags the live count by one). GET /api/mcp 405, OPTIONS 204 with Access-Control-Allow-Origin *. Flat files: llms.txt 15,365 B, llms-index.txt 86,020 B, llms-full.txt 3,105,600 B, AGENTS.md 9,499 B (also at /agents-md), openapi.json 10,545 B, server-card 499 B, agent-card.json 3,295 B, a .md twin 1,947 B for brand-assets. llms.txt returns a weak ETag and answers If-None-Match with 304. robots.txt disallows /api/ for * and re-allows /api/mcp, /api/wiki/ and the three llms files for the named assistant agents. Registry: registry.modelcontextprotocol.io lists wiki.radix/radix-wiki at 2.0.0, 2.1.0, 3.0.0 and 3.1.0, the last published 2026-08-15T19:10:41Z and the only isLatest. |
| web:radixecosystem-directory | 2026-08-24 | run 297 - NEW SOURCE KEY, and it supplied the only Radix tie BCW has. radixecosystem.com/projects/ is the community-run project directory; its BCW entry carries a live 'Validator details' panel naming Cadwynbloc, validator_rdx1sv2rav2zqvufxs9dk5yu92t00ncrcw3dfu64pxxz29vvq3tj4fem2p, with stake/fee/uptime read live (its 68,559,549 XRD matched the ledger to five digits). Community-submitted with an explicit accuracy disclaimer, so it is an attribution source, not a fact source - useful for finding a project's on-ledger entity when its own site names none. |
| code:consensus-manager-config | 2026-08-22 | run 286 re-read at radix-engine-interface/src/blueprints/consensus_manager/invocations.rs (raw.githubusercontent, main). ConsensusManagerConfig::mainnet_genesis(): max_validators 100, min_round_count 500, max_round_count 3000, target_duration_millis 300000, num_unstake_epochs 2016 (= 7 days at the 5-minute epoch target), total_emission_xrd_per_epoch 2853.881278538812785388, min_validator_reliability 1, num_owner_stake_units_unlock_epochs 8064, num_fee_increase_delay_epochs 4032 (= 14 days), validator_creation_usd_cost 1000. CAVEAT recorded rather than published: these are the GENESIS values in source; a protocol update could have moved them and the consensus manager component returns no state to the Gateway, so do not publish num_fee_increase_delay_epochs as live without corroboration from an observed validator_fee_change_request epoch gap. |
| code:radix-wiki-agent-cluster | 2026-08-17 | run 260 — NEW SOURCE KEY, and the primary source that dated the run first edit. The DMAIC agent cluster the two oldest contents/tech pages describe was removed in commit 895228b (27 Jun 2026, "Remove retired agent-cluster routes"): it deleted src/app/api/metrics/route.ts plus moltbook/scout/sentinel/pulse/twitter/status/mend/backup, and DROPPED vercel.json. vercel.json at 895228b^ carried nine crons with /api/metrics on "0 6 * * *" — exactly the "Daily 6 AM UTC" cadence the Control Chart published. There is no agents/ directory and no cron declaration in the repo today. |
| code:scrypto-package-template | 2026-08-21 | run 283 - NEW SOURCE KEY, and the spine of the first edit. radixdlt-scrypto@main radix-clis/src/scrypto/cmd_new_package.rs writes SEVEN files, not the three this wiki listed: Cargo.toml, Cargo.lock, .gitignore, rust-toolchain.toml, src/lib.rs, tests/lib.rs (plus the src and tests dirs). assets/template/rust-toolchain.toml_template pins channel 1.92.0 with components rustfmt + rust-src and target wasm32-unknown-unknown - the pin travels inside the CLI binary, which is the mechanism behind the install page’s Version Pins section. Cargo.toml_template: opt-level z, lto, codegen-units 1, panic abort, strip, overflow-checks = TRUE (release builds panic on overflow rather than wrapping), crate-type ["cdylib","lib"], and a trailing empty [workspace] stanza that hides the package from an ancestor workspace. tests/lib.rs ships BOTH harnesses pre-wired (LedgerSimulatorBuilder and TestEnvironment). Also settled a non-finding: NonFungibleGlobalId::from_public_key takes P: HasPublicKeyHash and public_key_hash.rs:17 carries a blanket impl for &T, so the wiki’s `&public_key` sample compiles - do not "fix" it. |
| onledger:closed-token-markets | 2026-08-22 | run 286 - NEW SOURCE KEY, and THE RUN LEAD. The run-282 method extended to the next two closed pages carrying metadata.assets, read at epoch 337,086 / state version 553,058,752 (22 Aug 2026), and the two answers are opposites. $NOW (resource_rdx1th42ay5...p3u48l2q): 1,000,000,000 minted, 0 burned, all four authorities AND their updaters DenyAll, 833 holders, top holder 348,759,188.52 (34.9%) unmoved since 11 Oct 2024. Its market is ONE Ociswap native TwoResourcePool (pool_rdx1c5vzrppel06...pflypu6r, dapp_definition = Ociswap) holding 119,764,938.30 NOW against 5,169.995 XRD, balance last changed 8 Aug 2026 - still trading. Its metadata stake_component resolves to component_rdx1cz2t6hl05...r0t92d8, blueprint PlazaStaking v1.0.0 (DeFiPlaza), named 'NOW Staking', on-ledger description still advertising '350,000 will be distributed each week'; its OneResourcePool holds 41,291,785.74 NOW (4.1% of supply) unchanged since 16 Feb 2026. $RZR (resource_rdx1t5w44wm9...2yas2xm0e): symbol is 'rzr', NOT the 'REI' the wiki said; 525,000,000 minted, 0 burned, all authorities DenyAll, 1,213 holders, top holder 485,537,120 (92.5%) unmoved since 26 Dec 2024; four pools hold it, the two Ociswap XRD pairs carrying 2,741.41 + 1,645.18 = 4,386.60 XRD of depth and both last changed 14 Feb 2026. State-version dates confirmed one by one through /stream/transactions. |
| onledger:governance-component | 2026-08-23 | run 293 re-read LIVE at epoch 337,473 / state version 553,710,407 (23 Aug 11:20 UTC) and THE PARAMETER STORE WAS READ FOR THE FIRST TIME. component_rdx1cp90ys... ('Radix DAO Consultations', package_rdx1p49s244...) still reads temperature_check_count 0, proposal_count 0, majority_judgment_election_count 0, and its newest transaction of any kind is 12 Aug 17:33 UTC (8 transactions total, instantiate 6 Aug 16:57). But its parameter_sets KVS holds FIVE live GovernanceParameterSet entries written 12 Aug 17:23-17:33: dao-constitutional (7d/1,350,832,592/0.66), dao-governance (7d/945,582,814/0.60), dao-treasury (7d/945,582,814/0.50), default 'Standard Executable' v2 (7d/675,416,296/0.50) and dao-election (TC 3 days; election 7d/945,582,814, minimum_median_grade Good, 14-day rerun same terms, 90-day reserve list). TC stage is 5 days / 405,249,777 / 0.5 in all but dao-election. Its blueprint has 20 methods against the old component's 11 - named parameter sets, record_temperature_check_outcome, and a five-method majority-judgment subsystem. A census for 'dao-constitutional' returned ZERO wiki pages before this run. |
| onledger:master-badge-custody | 2026-08-23 | run 293 CORRECTS THE IMPLICATION of run 255 without contradicting its facts. The Consultations Master Badge (resource_rdx1nt4gug..., #1#) is still in the RAC 2-of-3 multisig account_rdx1c9l27suy... - but find-entities-by-badge returns total_controlled 0: it is named in NO role assignment on ANY entity on the ledger. The badge that actually operates the DAO's ballot box is the Consultations ADMIN Badge, resource_rdx1ng4c5k87..., which controls SIX entities (packages package_rdx1ph2gyym... and package_rdx1p49s244..., and Governance components cz8tzcyy 'Radix Consultation V2', czs6rhvd, cpg8ehts 'Radix DAO Consultation v3' and cp90ys55 'Radix DAO Consultations'). The live component's owner role Requires that resource and its updater is None - LOCKED, unreassignable for the life of the component. The badge sits in single-signature account_rdx12yu55zy... (it moved there 12 Aug at state version 549,113,728; the parameter writes were signed from account_rdx129yk8vd... presenting #1#). So the RAC holding the master badge does not give the RAC control of the ballot box. |
| web:awesome-radix-mcp-servers | 2026-08-26 | run 306 - NEW SOURCE KEY. raw.githubusercontent.com/xstelea/awesome-radix-mcp-servers/main/README.md is 465 bytes and lists exactly THREE servers under 'Available Servers': Attos World, SBOR EZ Mode, Astrolescent. It lists neither radix.wiki's own MCP server nor the RadixScan Agent Layer, both of which /developers/radix-developer-resources already links. The wiki cites the index as a community resource on the new page and states its three entries nowhere, so nothing on the wiki depends on the count; re-read it before quoting. |
| web:coingecko-defillama-walls | 2026-08-16 | run 253 - the two flagged externals on /contents/resources/how-to-buy-xrd, re-settled by the run-250 body-size method rather than by re-probing blind. coingecko.com/en/coins/radix returns 403 with 1,451,841 bytes and defillama.com/dexs/chain/radix returns 403 with 5,665 bytes of a Cloudflare 'Just a moment...' interstitial. A 403 with a full body is a WALL, not a death. Both citations kept. Do not re-probe on the next resources rotation. |
| web:github-genkipool-rust-sdk | 2026-08-23 | run 296 recheck: UNCHANGED since run 247. 9 releases, newest connector-v0.3.1 published 2026-08-02, pushed_at 2026-08-02, 1 star, 0 forks, Apache-2.0, not archived. |
| web:github-scrypto-challenges | 2026-08-18 | run 263 - NEW SOURCE KEY, and it closed the run-250 banked gap. radixdlt/scrypto-challenges is NOT archived (last push 23 Dec 2025, 67 stars / 173 forks). 7-defi-devpost holds exactly 17 directories, matching the submission count the page infobox has always carried: AlkyneFi, CupPerps, DefiFunds, Optlend, RadInsurance, Tokenvest, [SRWA_lending], coupon, flashyfi, fleet-vehicle-lending, investor_companion, kaupa, kl_protocol, mojitoswap, scrilla_lending, scrypto-lend-marketplace, stoichiometric. READMEs read for the nine that did not place. investor_companion has no README (API returns no content field). |
| web:grove-moving-up-the-stack | 2026-08-19 | run 258 - NEW SOURCE and THE PRIMARY SOURCE that corrected this run’s own first edit. medium.com/decentralized-infrastructure/groves-next-chapter-moving-up-the-stack-fd7ecaf0a184, Arthur Sabintsev, 10 November 2025: Grove is "stepping away from directly operating or developing the protocol and our gateway, the Grove Portal"; "throughout the month of November, the vast majority of Grove’s paid and public endpoint traffic will migrate to new public endpoints infrastructure hosted on https://api.pocket.network"; RPC and validator infrastructure transferred to BuildInTheShade.com. No hard shutdown deadline given. THIS is the date that matters to a Radix developer - the gateway stopped being Grove’s in Nov 2025, nine months before the company closed. |
| web:telegram-handle-integrity | 2026-08-01 | run 178 (NEW source): swept all 62 Telegram handles cited under /ecosystem via the public t.me/s/ previews. 9 are recycled squats (see the advisory page); 51 are groups whose previews are not public, which the probe cannot judge either way; 2 are alive and real (radix_genkipool 2021, ROOTfinanceradix 2024, DOGECUBE 2024 all show genuine history). Re-run the probe when auditing ecosystem again – the campaign is ongoing (Radixnode was taken 30 Jul, three weeks after the 29 Jun batch). |
| onledger:caviarnine-validators | 2026-08-25 | run 305 - NEW SOURCE KEY, and it is the measurement that invalidated a published check. CaviarNine-1 (validator_rdx1sd8c8v9...ds85rkv) and CaviarNine-2 (validator_rdx1sv7zpyu...fxv9j5pqx) at epoch 338,190: registered, accepting stake, 113,615,542.04 and 119,632,220.27 XRD, effective_fee_factor.current 0 on both, no pending. Both carry validator_fee_change_request {new_fee_factor 0, epoch_effective 282893}, and reading at at_ledger_state {epoch: 282890} shows why: CaviarNine-2 held {0.017, epoch_effective 40245} while its stored factor still read 0.0175, so the field is REWRITTEN by the next request, never cleared by the one that lands. It has been non-null since epoch 282,893, roughly seven months before the 23 Aug prediction that treated a non-null request as its hit condition. Stake ticked down from the 23 Aug reading on both (113,954,257 -> 113,615,542; 120,987,192 -> 119,632,220). |
| onledger:closed-project-tokens | 2026-08-21 | run 282 - NEW SOURCE KEY, and THE RUN LEAD. The four stalest unverified ecosystem pages are all marked Closed and all four carry a metadata.assets resource that no run had ever read. Read at epoch 336,894 / state version 552,775,691 via /state/entity/details + /extensions/resource-holders/page. ALL FOUR are fully minted, zero burned, with minter/burner/freezer/recaller AND all four updaters set to DenyAll - permanently immutable. The distributions are what differ. $ARENA (resource_rdx1thwqzplv7...): 100,000 supply, 2,266 holders, top 47,425.64 = 47.4%. $FARBO (resource_rdx1thlrdezdr9h...): 100,000,000 supply matching the published maximum exactly, but only 357 holders and 82,416,955.18 = 82.4% in ONE account, against a plan that allocated 75% to an airdrop plus presale. $WARS (resource_rdx1tk450x27z...): 1,000,000,000 supply and exactly TWO holders - one account with 999,999,999.999999995 and a native TwoResourcePool paired with XRD drained to dust on both sides (0.000000005 WARS / 0.000000000000043 XRD, pool_rdx1ch4zq4kj78xsrml7jfps05s76a3my7hcj550qr06zvft6lagl3vzl8). $RDK (resource_rdx1t4zrksrzh7u...): 50,000,000 supply matching the published 26m/10m/10m/4m allocation exactly, and 27,869 HOLDERS - more than most launched Radix projects reach - with the #2 holder a FUNDED native pool (pool_rdx1ckvw8yleumnj5tk3ued5cxg7tmtgfmysfc3c60nc6w4utqhl8ywjgh) holding 6,944,719.26 RDK against 68,618.84 DFP2 (DefiPlaza governance, resource_rdx1t5ywq4c6nd2lxkemkv4uzt8v7x7smjcguzq5sgafwtasa6luq7fclq, supply 67,941,915). CAVEAT for a future run: /stream/transactions with affected_global_entities_filter returned zero items for three of the four resources and a single 24 Jan 2025 creation for $WARS, which cannot be right given thousands of holders - treat that endpoint's ABSENCE as uninformative, never as "no activity since". |
| onledger:mountaintop-validator | 2026-08-18 | run 263 - NEW SOURCE KEY, verifying the funding model of the cheapest P1 proposal. validator_rdx1sv9gp89vf89dmlr5uuhquvggyrrsew5mjfykyf868ja70ukst3jsug read live at epoch 335,982 / state version 551,351,291: name "MountainTop", is_registered true, accepts_delegated_stake true, 20,783,653.11 XRD staked, 100% uptime (1w). The fee shows the run-235/259 divergence again - stored validator_fee_factor 0, effective fee 5%. |
| onledger:validator-name-census | 2026-08-18 | run 264 - NEW SOURCE KEY, and the method that settles "did this validator ever exist / does it still". The mainnet validator list read whole at epoch 336,030 returns 287 records (188 registered) INCLUDING unregistered validators that still hold stake, each with its on-ledger name. Grepping the names is a one-call existence check: no record publishes StakeBros or StakeBroz, which is what closed that page. Note two names worth knowing: "Blockshard CH\|BG RadixUID" (rank 71, registered, 12.25M XRD) is the validator the /ecosystem/radixuid page is about, and "Discontinued due to no longer being in top 100" (rank 150) is a validator whose operator wrote the wind-down into the name field. |
| onledger:consultation-dapp-defs | 2026-08-18 | run 265 - NEW SOURCE KEY, and it settles the venue question at the ledger. Both dApp definitions resolved live at epoch 336,079 / state version 551,519,980 (18 Aug 2026 15:12 UTC): account_rdx128965k8... is named "Radix DAO"; account_rdx12y8wqqg... is named "Radix Consultation V2", described "Governance on Radix, by the Radix community". Two distinct deployments, not one app at two hostnames. Every proposal and temperature-check URL the wiki cites points at the older one. |
| web:github-radix-dao-governance | 2026-08-21 | run 280 re-read at the TREE rather than at named files, and one call settled three cards. api.github.com/repos/Shadaffy/radix-dao-governance/git/trees/master?recursive=1 returns 38 blobs, untruncated. pending/governance/ holds 19 policies including conflict-of-interest-policy.md (16,206 B) and code-of-conduct.md (13,068 B), both last substantively committed 5 Aug 2026 ("close the workbook review findings for ratification"). pending/legal/ holds operating-agreement.md (95,064 B), the Certificate of Formation (filename carries 130826_v1_01) and a BOIR template. pending/README.md (last touched 16 Aug, "align formation documents with MIDAO filing forms") is the index: GP-PRE-1 ratifies 21 documents in ONE constitutional vote and is "Ready for review"; GP-ELECT-1 and GP-ACTIVATE-1 are both marked "Draft scaffold". The four-step sequence is ratification -> formation -> RAC election -> Activation Vote, and community governance is ADVISORY until the last of those. |
| web:ch-foundation-filing-history | 2026-08-27 | RADIX FOUNDATION 12106715 filing history. GAZ2 dissolved 29 Apr 2025; RT01 administrative restoration 17 Nov 2025, on which day it also filed CS01 (made 15 Jul 2025, no updates), AA to 31 Dec 2024, AD01 off the CH default address, AP01+PSC01 Jarrett dated 10 Feb 2025, TM01+PSC07 Hughes dated 27 Jul 2025, TM01 Lindsey Tan Lim dated 10 Feb 2025. CS01 of 23 Jun 2026 also no updates. |
| web:github-atlantis-desktop-tool | 2026-08-19 | api.github.com: pushed_at 2024-04-05, archived false, 21 stars — the page’s dormant-since-April-2024 claim is exact. Stamped, not edited. |
| web:github-babylon-node-releases | 2026-08-21 | run 283, the standing recheck: newest release is STILL v1.3.0.5 (1 Jun 2026), with v1.3.0.4 (2 Apr 2026) and v1.3.0.2 (3 Jan 2025) behind it. |
| web:radix-dao-integrity-policies | 2026-08-21 | run 280 - NEW SOURCE KEY. Conflict of Interest Policy: no numeric materiality threshold and none in DAO Parameters (a figure "would authorise non-disclosure beneath it"); SS4.1 requires ALL financial interests disclosed with no threshold, so the >10% mandate the wiki carried as an open deliverable was considered and refused. Scope is role-based (RAC, Treasury Signers, WG stewards with budget authority, decision-making contractors); ordinary token holders are outside it. SS3.5 treats delegated-function consolidation as a declaration duty rather than a recusal trigger, because a recusal reading would drop the RAC below its own non-recused floor. SS7 makes a 3-year predecessor-entity affiliation a standing conflict. SS10 gives the RAC 30 days to find, with the accused heard first. Code of Conduct: SS5 reporting path (RAC, or Governance & Legal WG where a RAC member is implicated), SS6.3 graded sanctions at graded thresholds, SS6.4 refers an unappealed permanent exclusion to arbitration anyway. SS6.3 also states that NO sanction reaches the vote - Charter SS12.1 entrenches XRD and LSU as eligible voting power for all DAO votes and SS13 voids a conflicting policy, so disenfranchisement would be unenforceable rather than severe. |
| web:radix-dao-operating-agreement | 2026-08-21 | run 280 - NEW SOURCE KEY, and the spine of two of the three edits. 95,064 B, 14 articles and 6 schedules. Art. IX.2 creates the LEGAL SIGNATORY, designated by Transition RAC written resolution, empowered to execute contracts/transfers/custody/filings and expressly NOT a manager of the Company by virtue of the office. IX.11 sets 2-of-3 for ordinary transition treasury actions and unanimity for protected matters; IX.12 lists those (material asset disposal, movement outside approved custody, transfer/assignment/exclusive licensing of core IP, repos, domains, web2 credentials, and any change that would defer the Activation Vote). IX.4 lists what may be transferred; IX.5 has the Company rely in good faith on the transferor representations with NO independent verification step. IX.8 names PrimeVault as a possible initial custody solution and allows the custody arrangement to be documented CONFIDENTIALLY where the Founding Transferor requires - relevant to /ideas/dao-xrd-custody and to the published-balance deliverable. Schedule 5 is a 10-condition activation checklist, 6 with a third-party dependency: Registrar (1), Registrar+agent (2), KYC provider (3), custody provider (4), and the FOUNDATION twice (8 continuity statement, 9 principal transfers "completed OR FORMALLY INITIATED"). Clause 8.5 gives the Transition RAC no discretion to delay the Activation Statement or the vote once evidence is in hand, on pain of breach. Clause 8.7 is titled "Foundation-Dependency and External Delay - Safe Harbour": Foundation-attributable delay is not a breach, but the RAC must publish an explanation within 14 DAYS and update at least every 30 DAYS while the dependency runs. Waiver of any condition needs the entrenched-provision threshold and must be recorded in the Activation Statement. |
| telegram:RadixAccountabilityCouncil | 2026-08-25 | run 301: no new posts past 911. |
| web:assets.super.so | 2026-08-28 | NEW CLASS banked at run 318, and it is the FIRST 403 this routine has confirmed as a genuine death rather than a bot wall. https://assets.super.so/2a0d12a5-9454-4417-b17e-d51617137fb6/files/* returns HTTP 403 with an application/xml body reading AccessDenied from server AmazonS3 via CloudFront, and the bucket root 403s identically. That is an S3 authorization failure, NOT the Cloudflare/HTML bot wall the other banked 403s are; a browser User-Agent and a Referer both make no difference. Run 313 audited contents/tech at 27 Aug 07:12Z, recorded ZERO real deaths and listed no super.so class, so the lock-down happened inside the following ~20 hours. Wiki-wide census: 7 link instances, 4 distinct objects, 2 pages (contents/tech/research/tempo-consensus-mechanism x6, blog/rgh2024-debrief x1). Three of the four are recoverable from the Wayback Machine and one is not. DO NOT re-probe individual keys: the whole bucket is gone, test the root. |

## Open Backlog

- MEASURED, run 317, and it is a STATE-INTEGRITY problem rather than a wiki one: THE RUN DIARY AND THE FEED DISAGREE ABOUT WHETHER A TWEET WENT OUT. runHistory records run 316 (contents/history) as "tweet: skipped - cadence", and x.com/RadixWiki carries an original at 2026-08-27T20:09:18Z whose text is run 316 subject matter ("Radix ran its first hackathon in July 2018, in a breakout room at the Pillar Unconference in Vilnius"), 2093068358065193367. The skill allows writing state in step 4 and posting in step 5, with a re-write afterwards to carry the URL; run 316 evidently posted and never re-wrote. The consequence is not cosmetic: the NEXT run reads runHistory to count the day s originals and undercounts by one, which is exactly the gate that protects reception. Either write state after posting, or have the posting step patch the last runHistory entry. FLAG FOR A HUMAN if the fix belongs in the skill rather than a run.
- FLAG FOR A HUMAN (run 309, code change, one line, and it is now visible to search engines): the `policy` node in src/lib/tags.ts names FIVE policies in its description - 'verifiability, neutral point of view, no original research, notability, and freshness' - and the category holds SEVEN, having gained conflict-of-interest earlier and editorial-notices this run. That string renders as the category page's meta description, so the omission is what Google reads off /policy. It also carries an em dash, which is the run-292 VOICE flag in the same line.
- BANKED, run 306, and it is an outreach call rather than an edit: THE COMMUNITY INDEX OF RADIX MCP SERVERS DOES NOT LIST THIS WIKI'S. github.com/xstelea/awesome-radix-mcp-servers is 465 bytes and names three servers (Attos World, SBOR EZ Mode, Astrolescent). radix.wiki has run a spec-correct Streamable HTTP server since at least Aug 2026, is published in the official MCP registry as wiki.radix/radix-wiki, and is absent from the index; so is the RadixScan Agent Layer, which /developers/radix-developer-resources also links. Adding either is a pull request to someone else's repo, which this routine does not open. FLAG FOR A HUMAN if the listing is wanted.
- MEASURED, run 308: THE LEDGER AND THE RULEBOOK DISAGREE ON A FIELD NAME AND ONLY ONE OF THEM IS AUTHORITATIVE. The deployed governance component's election parameter set carries minimum_median_grade. The framework it implements settles grades at the Grade Quantile, three-fifths of the voting power cast, and DAO Parameters 6B records that quantile as 'fixed in Proposal & Voting Framework 6.2.4; not a parameter' and calls the floor the MJ Minimum Qualifying Grade. GP-ELECT-1 says in terms that grades are settled at the quantile 'not at the median'. This wiki repeated the median reading from 14 Aug to 26 Aug and it is now corrected on /ideas/dao-elect-permanent-rac. Watch: if the contract is redeployed, see whether the field is renamed. The same median wording also sits in an exemplar in radix-studio/VOICE.md 2, which is a human's file - FLAG FOR A HUMAN rather than an edit.
- FLAG FOR A HUMAN (run 305, housekeeping and it is measurable): THE MAINTENANCE-LOG STATE IS GROWING WITHOUT A CAP ON ITS LARGEST SECTION. state reads 346,357 bytes at run 305, of which sources is 155,601 (45%) across 231 keys, backlog 55,470, runHistory 100,393 and feedback 25,973. The write path caps backlog at 60, runHistory at 30 and feedback at 40, so those three are bounded; sources is not, and it grows by two to four keys a run because most new keys are one-off probes (web:bobby.win, web:notix.live, onledger:mox-token) that will never be read again. The skill's own history records this state reaching 722 KB before the caps were added. A cap on sources needs a rule about WHICH keys are durable - telegram:*, plausible, x:* and the banked false-positive classes must survive; a single-page probe key need not - so it is a human's call, not a run's.
- FLAG FOR A HUMAN (run 305, and it is a scheduling decision rather than a maintenance one): THE HOOK PIPELINE IS BACKING UP FASTER THAN THE CAP CAN DRAIN IT. Seven runs in a row have now skipped the tweet on cadence (297, 298, 299, 301, 303, 304, 305) and SEVEN priority hooks sit banked and unposted - runs 297, 298, 299, 301, 303, 304 and this one. The arithmetic is structural, not bad luck: wiki-sweep runs roughly every four hours (six times a day), each run is expected to produce something worth sharing, and the @RadixWiki feed is shared with the radixwiki-tweet routine, all against a 1-2 originals/day cap. On 25 Aug the day's three originals were 03:11, 11:16 and 20:12, and only two of the three came from this routine. Two of the banked hooks have already had a decay date pass or approach (run 297's StakeSafe beat, 30 Aug; run 304's ZENITH beat, 30 Aug). The decision a human owns: either lift the cap, or give wiki-sweep a reserved slot in the shared feed, or accept that most of what this routine finds is never posted and stop scoring runs on whether they tweeted. Do NOT resolve it by tweeting more inside the current cap - reception is healthy precisely because the feed is not crowded (22 judged, median 15.5 lk / 250.5 imp, one zero-engagement post and it is a reply).
- FLAG FOR A HUMAN, opened run 292, and it is a VOICE decision rather than a maintenance one, measured before being raised: radix-studio/VOICE.md absolute #1 bans the em dash on EVERY surface and names wiki articles as a public-facing surface, and this wiki carries 982 em dashes across 115 of its 365 pages. This is not one drifted page. It is the house style of the corpus, written that way by this routine over many runs, and run 292's own three edits added more before the census was taken. Two coherent resolutions and this routine should not pick between them alone: (a) amend VOICE to exempt long-form wiki prose from the em-dash absolute, which is the smaller change and matches what both wikis actually publish, or (b) keep the absolute and add a bounded en-dash pass to each rotation - roughly 8 pages a run at the current cadence, mechanical, and every one of them needs a revision row. What must NOT happen is the third option this run declined: fixing only the pages a sweep happens to touch, which leaves the corpus half-converted and the rule half-enforced with no record of which half. Census query: SELECT count over pages where content::text matches an em dash or —.
- FLAG FOR A HUMAN (run 265, code change, and without it the data fix above decays): the TipTap Link extension stamps every hand-typed link with target="_blank" rel="noopener noreferrer nofollow". That is right for an outbound citation and wrong for a link to another page of this wiki, and it is why 271 internal anchors carry nofollow. The editor should choose per-href: internal (starts "/" or radix.wiki) gets rel="noopener" and no target; external keeps the current default. One conditional in the Link extension config. Until it ships, every page edited in the browser reintroduces the defect.
- FLAG FOR A HUMAN (run 256, code change, and it is the smallest of the standing flags): there is no way for an editor to record that they re-checked a page. lastVerifiedAt is read in five places in src/ and written in none — only scripts/mark-verified.mjs sets it — so every verification the wiki displays comes from the sweep, and a human editor who confirms a page is still correct leaves no trace but a revision. /policy/freshness now says so plainly (v1.3.0), which is the honest fix, but the real fix is a "mark verified" control on the editor or an API field on PUT /api/wiki/[...path]. Pairs with the run-239 flag on BANNER_META hrefs: both are small edits to make the policy cluster describe a system that exists.
- FLAG FOR A HUMAN (run 253, and it is a governance decision rather than a maintenance one): /contents/resources/legal/terms-of-use asserts THREE mutually exclusive licences in one section. Under 'Intellectual property rights and copyright' it says contributors 'formally and completely release all rights to the work as soon as it is uploaded' and it is 'then owned by the public as a whole' (CC0/public domain); the very next paragraph says content may be redistributed 'if and only if the copied version is made available on the same terms to others and acknowledgment of the authors is included' (share-alike with attribution, i.e. CC BY-SA); and under 'Rights you licence' it says 'You retain all of your ownership rights in your content' and grants us a non-exclusive licence (all rights reserved by the contributor). A reuser cannot comply with all three. The same section opens with a dangling subordinate clause that never resolves ('While we are the owner or the licensee of all intellectual property rights in our site'). Picking one regime binds every past contribution, so this sweep deliberately did not choose - it fixed only the auth section, which was verifiable against the code.
- FLAG FOR A HUMAN (run 239, code change — this closes run 226's open question with a measured answer). The maintenance banners do NOT link to the policies they enforce. BannerBlockView in src/components/BlockRenderer.tsx (BANNER_META at line 408) renders a fixed label and message as plain text with no anchor, so a reader who meets a 'Written like an advertisement' or 'May be outdated' notice has no route to /policy/neutral-point-of-view or /policy/freshness. The same is true of the synthetic freshness banner built in src/lib/freshness.ts. That is the natural inbound the policy cluster is missing, and the fix is six one-line hrefs in BANNER_META, not sprinkled prose links. Measured this run: exactly ONE non-policy page on the wiki links to any /policy/* page (the maintenance log) — DOWN from the two run 226 measured, because a later rewrite of /ecosystem/oter dropped its policy link. MITIGATED IN CONTENT, NOT IN CODE, run 309: /policy/editorial-notices now names every variant next to the policy it enforces and is linked from all six sibling policy pages, so a reader who meets a notice can at least find the mapping by search. The anchor in the banner itself is still the fix.
- FLAG FOR A HUMAN (run 232, community rotation): /community/cryptoants is the last surviving auth-route shell and it survived because the 27 July prune misclassified it. scripts/prune-community-shells-2026-07-27.mjs listed cryptoants in KEEP as "self-authored bio, 850B" - ranked by byte size, which put it above the 296B/591B shell signatures the script matched on. It is not a bio. The content is the auth route default template verbatim ("This is your personal community page. Edit it to share your thoughts..." / "Tell the community about yourself..."), the auto-generated infobox reads Status: Placeholder / Not yet customized, and the page has exactly two revisions, both machine-written: "Initial community page" (31 May 2026) and "Auto-fix: generated infobox" (1 Jun 2026). The wallet holder (display_name CryptoAnts, account_rdx168lx667y0fq8a6rtra06tjandyj2xmmnavljyl4r33gcwrp900m7sh) has authored 1 page and 2 revisions wiki-wide, all of it this. Deleting it re-applies the approved 38-shell class decision, but KEEP was an explicit recorded human choice, so reversing it is a human call, not an unattended one. No prose invented in the meantime - there is nothing public to write about this member.
- FLAG FOR A HUMAN (run 236, this wiki's own legal text): /contents/resources/legal/privacy-policy is generic e-commerce boilerplate that does not describe this site. It names advertising networks, credit reference agencies, and payment and delivery sub-contractors as parties it may share data with - a wiki with no ads, no payments and no deliveries. Run 223 asked whether the legal pages still describe how the wiki works; read this run, the answer is that they never did. The acceptable-use-policy (6,491 chars) and terms-of-use (13,144 chars) contain no stale wiki-mechanics claim - neither mentions community pages, auto-creation, points or the leaderboard - so nothing there is wrong, only generic. All three are the operator's own legal undertakings, so narrowing them is a human decision, not an unattended edit. Both untouched pages were stamped via mark-verified so they stop counting as stale.
- 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.
- 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.
- 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.
- 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.
- 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/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.
- 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).
- STALENESS HEAD after run 318 (blog): the category holds 19 pages and its head is two bulk-touch blocks, not real neglect - four week-in-review issues sharing updated_at 2026-08-18T18:37 and nine pages sharing 2026-08-20T14:11. Cleared this run: /blog/rgh2024-debrief (v2.6.4 -> v2.6.5, dead slide-deck link repointed and STAMPED). The head is now the four 18 August week-in-review issues, which are DATED RECAPS and should be verified rather than rewritten - a past week does not go stale. The one genuinely open item in the category is /blog/week-in-review's state.predictions: four predictions open, earliest due 2026-09-06 (StakeSafe three-validator fee rise), then 2026-09-20 x2 and 2026-10-04. None overdue at this run, so nothing to score. The next blog rotation that lands after 6 September MUST score the StakeSafe one off effective_fee_factor, not validator_fee_factor.
- BLOG LINK AUDIT, run 318 (supersedes the run-305 audit): 19 pages / 204 external / 66 embeds - 0 broken internal, 0 broken embeds, 0 unverifiable embeds, 0 non-standard images. 16 flagged externals, 15 banked and 1 real death (assets.super.so, fixed this run). The internal chain is healthy in a way worth recording because it is the category readers actually land in: every week-in-review issue links its predecessor, its successor and the /blog/week-in-review hub, and the hub links all nine issues, so a reader arriving on the 2 August issue from search can walk to the current one. The apparent /blog/* internal links to foundation-update-moving-to-maintenance-mode, hyperscale-completing-the-interim-phase and six others are NOT wiki pages and NOT broken: they are path fragments inside www.radixdlt.com/blog/... URLs. Do not "fix" them.
- ACTIONABLE for any rotation, opened run 318 and NOT resolved: THE RADIX PUBLIC NODE INCENTIVES PAPER (24 December 2017, 199.3 KB) HAS NO PUBLIC COPY LEFT. It lived at assets.super.so/.../3cc28606-2bad-496f-a997-59f7ad3d85b9/2017-12-24_Radix_Public_Node_Incentives_White_Paper.pdf, which is inside the bucket that went dark. The Wayback CDX has ELEVEN captures from that bucket and this is not one of them; a wildcard on the 3cc28606 prefix returns nothing, and papers.radixdlt.com is NXDOMAIN. www.radixdlt.com/whitepapers now serves only Cerberus (assets.website-files.com/...Cerberus-Whitepaper-v1.01.pdf) and the DeFi white paper (uploads-ssl.webflow.com/...v2.05.pdf); there is no Tempo or node-incentives entry and /whitepapers/tempo 404s. The tempo page now names the paper without a link. If anyone in the ecosystem still holds the PDF it is worth re-hosting; ask in hyperscale_rs or RadixDevelopers.
- MEASURED, run 318, and it is a citation-integrity finding rather than a link one: THIS WIKI CITED ONE DOCUMENT AS TWO FOR AS LONG AS THE PAGE HAS EXISTED. /contents/tech/research/tempo-consensus-mechanism linked "Tempo" (intro + infobox, key e4f934ff-25c3-4ffe-a6dd-2bbb82714e64.pdf) and "170925 Radix Tempo Whitepaper-v1.1.pdf638.0KB" (Further Reading, key 4258f4f2-.../RadixDLT-Whitepaper-v1.1.pdf) as separate papers. Both archived snapshots download to md5 7328a6430973ea762e094ba9f5c0eea4, 653,332 bytes, 8 pages, /Title "Microsoft Word - RadixDLT-Whitepaper-v1.1.docx" - and 653,332 B is exactly the 638.0KB the page already printed next to one of them. Same file, two Super keys. GENERALISABLE: check-links dedupes by URL, so one document under two URLs reads as two healthy citations forever. Worth a pass that hashes what the wiki links to, not only what status it returns.
- METHOD, run 318, and it is the thirty-seventh in the family - it is also the first CORRECTION to a standing rule rather than an addition to it: A 403 IS NOT ALWAYS A BOT WALL, AND THE BODY IS WHAT SEPARATES THEM. This routine banks 403s as false positives on the grounds that SSRN, Medium, ResearchGate, LinkedIn and Cloudflare-walled hosts all refuse automated requests while serving humans, and that rule has been right every time it fired until now. assets.super.so returns 403 too, and the body is application/xml AccessDenied from server AmazonS3 - an object-store authorization failure, not a bot policy. The separator is cheap and should be applied to every NEW 403 before banking it: read the body. text/html plus a Cloudflare or LinkedIn server header is a bot wall; application/xml plus AmazonS3 (or any object-store error code) is a dead object. Second cheap tell: probe the HOST ROOT. A bot wall serves its front page to a browser UA; a locked bucket 403s at the root too.

_35 older open items held in state._

## Community Feedback & Reception

- 2026-08-28 – Run 318 broke a ten-run tweet drought and every gate said post independently: the 28 Aug UTC day held ZERO @RadixWiki originals against the 1-2 cap, and the previous original went out 27 Aug 20:09:18Z, 7.3 hours before the gate, clear of the 3-4 hour brand-feed rule. The 12-hour same-wiki rule was the only one leaning skip and it is a lean, not a bar; the run-305 human flag about the hook pipeline backing up argues the other way. Reception supports the call: 22 judged, median 16 lk / 260.5 imp, best-ever post is the discovery-led validator-sale one at 39 lk / 604 imp, and this run's hook has the same shape (a founding document went offline, and two of the links to it were the same file).
- 2026-08-27 – @RadixWiki reception measured at run 317: 22 judged posts, median 15.5 likes / 0 replies / 259 impressions, one zero-engagement post at 5% and it is a reply, not an original. Healthy and flat against run 315 (16 / 0 / 255). The best post in the window is discovery-led and on-ledger: "Radix's eighth-largest validator changed hands on Friday for 1,456,311 XRD, in a single transaction. The 149 million XRD delegated to it never moved. A badge did" (23 Aug, 39 lk / 603 imp / 11 reposts) - the highest repost count in the window by a factor of three. The shape that earns reposts is a mechanism nobody had published, stated as a number. Confirms the standing instruction: lead with the discovery, never the housekeeping.
- 2026-08-27 – Unprompted third-party citation of this wiki inside the project it covers. hyperscale_rs message 10869 (25 Aug 2026 20:01 UTC) posts "Also a digest here: https://radix.wiki/contents/tech/research/hyperscale-rs" into the project's own Telegram channel, where the project's lead developer reads. That page is the wiki's sixth-busiest at 63 visitors/30d and it is the only contents/tech page in top_pages. Being cited as the digest by the community of the thing being documented is the reception signal this routine has been looking for in tweet metrics.
- 2026-08-27 – run 315, wiki comments: 4 total, newest 5 April 2026, all four on the DAO charter discussion. Seventy-eighth consecutive run with no new comment. The on-site comment surface remains dead as an inbound channel; X replies are the only live one.
- 2026-08-27 – RECEPTION, run 315, measured cold before the gate: 21 judged at 18 h maturity, median 16 lk / 0 rp / 255 imp, one zero-engagement post at 5% and it is the same 2-impression reply as every read since run 306. The median has now ticked up from 15 to 16 and impressions from ~250 to 255. Best in window remains the validator-badge sale (39 lk / 600 imp, 23 Aug), which is mechanism-led discovery - the shape the banked hooks are.
- 2026-08-27 – RECEPTION, run 314, measured cold before the gate: 22 judged at 18 h maturity, median 15 lk / 0 rp / 249.5 imp, one zero-engagement post at 5% and it is the same 2-impression reply as every read since run 305. Best in window is 23 Aug's validator-badge sale at 39 lk / 598 imp. The account is healthy and the shape that wins is unchanged: a hard number attached to a mechanism, led by the discovery. The two originals immediately before this run scored 6 and 5 likes and both opened on a project rather than on a number, which is the case for leading run 314's post with $846 million against $801.
- 2026-08-27 – UNSOLICITED PRAISE FOR A PAGE, and the first of its kind logged: radix_dlt 999381 (25 Aug 14:15 UTC) reads 'Whoever put this together for RunFly, thank you so much! 🖖 https://radix.wiki/ecosystem/runfly if you want a banner, let Pat know!' Someone in the main Radix chat found a page this routine created, thanked it publicly, and offered artwork for it. Two things follow. The ecosystem stubs are read by the projects they describe, which raises the accuracy bar on them. And /ecosystem/runfly has a banner image available for the asking, which is an outreach action rather than an edit - see the run-310 RunFly item.
- 2026-08-27 – run 313, wiki comments: 4 total, newest 5 April 2026, all four on the DAO charter discussion. Seventy-seventh consecutive run with no new comment. The on-site comment surface remains dead as an inbound channel; the wiki's actual reader contact is Telegram and X replies.
- 2026-08-27 – run 313 reception, measured cold before the tweet gate: 22 judged at 18h maturity, median 15 likes / 0 replies / 249.5 impressions, one zero-engagement post (5%) and it is still the same 2-impression reply. The actionable part is not the median, which has now held at 15 for six consecutive reads, but the spread. The two most recent originals both scored 4 likes - the run-312 Emberflow ecosystem-status correction (71 impressions) and a Hyperscale transaction-composition post (95) - while every one of the five best posts in the window leads with a mechanism a reader can act on. Combined with the standing 27 Aug guidance to post less about dormant projects, this reads as a direct instruction: ecosystem status corrections are the weak shape, engine and protocol mechanics are the strong one.
- 2026-08-27 – Reception re-measured before posting, 22 judged at 18h maturity: median 15.5 likes / 0 replies / 254.5 impressions, one zero-engagement post out of 22 and it is the same 2-impression reply. Discovery-led hooks continue to carry the account; the best of the window is the validator-sale post at 39 likes / 597 impressions. Four @RadixWiki originals landed on the 26 Aug UTC day against a 1-2/day cap, which is why runs 309, 310 and 311 all skipped, and the 21:38 radixwiki-tweet run held a fifth. The cap is being enforced by skipping, not by scheduling.
- 2026-08-26 – run 310 reception read: 23 judged posts at 18h maturity, median 15 likes / 0 replies / 251 impressions, one zero-engagement post at 4%. The median has now held at 15 likes across runs 307-310 while impressions drifted 247 -> 250 -> 251, so the discovery-led hook is not fatiguing. No @RadixWiki mentions and no new wiki comments (4, newest 5 April, 75th consecutive run). Traffic reception is unreadable for the eleventh consecutive run: Plausible has returned a byte-identical 30-day payload since run 300, which means no page touched in the last ten runs can be shown to have moved.
- 2026-08-26 – Wiki comments: 4 total, newest 5 April 2026, all four on the DAO charter discussion. Seventy-first consecutive run with no new comment. The wiki's actual inbound conversation is on X and in Telegram, not in the comment threads, and the 219 visitors a month arriving at /api/mcp are not people who can leave one.
- 2026-08-26 – Reception re-measured cold before the gate (--mine, 22 judged at 18h): median 15.5 lk / 0 rp / 252 imp, one zero-engagement post at 5% and it is still the same 2-impression reply to @coinhold_wallet. best is still the 23 Aug validator sale, now 39 lk / 580 imp / 11 reposts. Eight-run skip streak BROKEN this run on a clean gate: zero @RadixWiki posts on the 26 Aug UTC day, the last brand post 7.2 h earlier (25 Aug 20:12Z, radixwiki-tweet) against the 3-4 h rule, and the last sweep tweet 16.2 h earlier (run 302, 11:16Z) against the 12 h rule.
- 2026-08-25 – run 305, recorded because run 304 logged only the RunFly message and these two are separate and earlier. radix_dlt 999346 (25 Aug 08:28 UTC) and 999352 (09:29 UTC) are the same reader posting twice, addressed to @bayesien: 'I was browsing the Radix wiki earlier and wanted to say what a great job you (and others?) are doing maintaining it' - once asking 'Are you using any AI for it?' and once 'Are you using spell-check for it?'. Two things worth keeping. (1) '(and others?)' is a reader trying to work out whether this is one person or a group, which is a question the wiki does not answer anywhere; there is no page or footer describing who maintains it or how. (2) The spell-check question is not idle - it is the second reader in three days to raise language quality, after the 25 Aug ESL feedback that changed how run 303 wrote its developer prose. There is no spell-check in the edit path and no linting of stored HTML. A dictionary pass over the corpus would be a cheap, bounded, one-off script and it is the kind of thing a reader has now asked for twice.
- 2026-08-25 – run 305, and it is the THIRD unprompted reader signal in three days, the first one that is not a thank-you but a referral. hyperscale_rs Telegram 10869, 25 Aug 2026 20:01 UTC: a channel regular answering a newcomer who had asked whether hyperscale.rs and its GitHub were the whole reading list replies 'Also a digest here: https://radix.wiki/contents/tech/research/hyperscale-rs'. That is this wiki being used as a reference INSIDE the project's own channel, by someone who is not us, to onboard someone who is not us - a different and better signal than being thanked, because it is a use rather than a compliment. It also matches the traffic: that page is the wiki's sixth most-visited over 30 days at 61 visitors and the only non-home, non-blog, non-/ecosystem page in the top six. What follows for the routine: the hyperscale-rs page is now load-bearing for newcomers, so its accuracy and its internal links deserve the strongest maintenance in the corpus, and the run-298 banked item on the formal-verification programme should be written INTO it rather than saved for a tweet.

_25 older entries held in state._

## Recent Runs

|  |  |  |  |
| --- | --- | --- | --- |
| **Date** | **Category** | **Summary** | **Tweet** |
| 2026-08-28 | blog | blog rotation (run 318), and the lead is that Radix's 2017 whitepaper stopped being downloadable inside the last twenty hours and this wiki's three links to it died together - two of which turned out to be the same file. LINKS: 19 pages / 204 external / 66 embeds - 0 broken internal, 0 broken embeds, 0 unverifiable embeds, 0 non-standard images, and 16 flagged externals of which FIFTEEN sit in the run-305 banked set (the linkedin.com/in/* count rose 5 -> 9 on corpus growth alone). The sixteenth was new and it broke this routine's oldest rule: assets.super.so 403s, and the body is application/xml AccessDenied from server AmazonS3, not the Cloudflare HTML wall every previously-banked 403 carries. A browser UA and a Referer changed nothing and the bucket ROOT 403s too, so it is the whole tenant that went dark. Run 313 audited contents/tech at 27 Aug 07:12Z with ZERO real deaths and no super.so class, which dates the lock-down to the following ~20 hours. CENSUS: 7 link instances, 4 distinct objects, 2 pages. THE DISCOVERY came from downloading the archived copies rather than trusting the labels: the intro/infobox "Tempo" link and Further Reading's "170925 Radix Tempo Whitepaper-v1.1.pdf638.0KB" are md5 7328a6430973ea762e094ba9f5c0eea4, 653,332 bytes, 8 pages, /Title "Microsoft Word - RadixDLT-Whitepaper-v1.1.docx" - one document the page had been advertising as two, and 653,332 B is exactly the 638.0KB the page itself printed. EDIT 1, /contents/tech/research/tempo-consensus-mechanism v1.2.5 -> v1.3.0, 13,236 -> 12,989 B: all three Tempo-whitepaper references now resolve to the Internet Archive capture of 23 Oct 2025 (verified 200 application/pdf, 8 pages); the Public Node Incentives paper has NO capture at its URL and no public copy found, so its three anchors were unwrapped to plain text with a note saying why; and the infobox Consensus Mechanism row, which read "HotStuff" over a hackernoon link, now reads "Tempo (lazy consensus, logical clocks)" - HotStuff is what Cerberus adopted AFTER Tempo failed on finality, which this page's own Problems section says. EDIT 2, /blog/rgh2024-debrief v2.6.4 -> v2.6.5: the RadixStats hackathon deck repointed to its 11 Dec 2024 capture. A write-order bug was caught in the dry run and fixed before any write - the archive URL embeds one of the two keys it replaces, so replacing them in the wrong order double-prefixed the URL; both pages now carry a doubled-prefix assertion. Both verified at the new versions through the uncached API and both STAMPED. Script retained as scripts/sweep-318-super-so-bucket.mjs. SIGNAL: 122 Telegram messages, all hyperscale_rs, all philosophy about validator choice, zero publishable. Plausible moved for the first time in six reads (1,781 / 1,534) and put TWO week-in-review issues in the top six pages. Comments 4, newest 5 April, 78th consecutive run. TWEET posted after ten consecutive skips; no video. | https://x.com/RadixWiki/status/2093177304029548547 |
| 2026-08-27 | ecosystem | ecosystem rotation (run 317), and the lead is that a validator advertising itself as number one by delegators is measuring something the ledger does not store. REWROTE /ecosystem/radical-staking (v2.2.1 -> v3.0.0, STAMPED): it was 8,624 bytes of which two thirds was generic advice addressed to the reader - eleven headings under Benefit and Security and Trust telling the reader to "Look for information about the reputation of Radical Staking validator" and to "Evaluate the experience and expertise of the team". A template, not an article, and it sent the reader off to check facts one Gateway call settles. Replaced with figures measured at epoch 338766: 148,990,075.76 XRD staked (rank 8 of 188), 1% fee, 100% uptime over a month, 8,700 stake-unit holders. The operator publishes 125,245,039 XRD and 8,753 delegations undated on its own homepage, so its stake figure is ~19% below the ledger while its participant count sits 53 above the closest on-ledger measure. Reported the "#1 by delegators" claim as the operator's, with the proxy stated and its limit shown: 8,700 leads Jazzer9F 8,654 by 46 accounts, while Radstakes stake unit is held by 121,414 accounts of mostly genesis-era dust. Also fixed the opening sentence, which called the network "the Radical Network", replaced the invented one-line partner descriptions with the operator's current list, and removed Maya Protocol, which the page described as a stablecoin platform and which is a cross-chain liquidity network. CLOSED THE RUN-315 OPEN QUESTION on /ecosystem/radix-foundation (v4.1.0 -> v4.2.0, STAMPED): the filing history for 12106715 says the PSC shortfall is a filing gap, not an unrecorded transfer. The company was struck off 29 Apr 2025 and administratively restored 17 Nov 2025, and on the restoration date filed nine months of record at once - Jarrett AP01 + PSC01 dated 10 Feb 2025, Lindsey Tan Lim TM01 dated the same day, Hughes TM01 + PSC07 dated 27 Jul 2025, accounts to 31 Dec 2024, a move off the Companies House default address, and a confirmation statement made 15 Jul 2025. No PSC statement covers the remainder, and both confirmation statements since (15 Jul 2025, 23 Jun 2026) were filed with no updates. LINKS: 148 pages / 1,004 external / 39 embeds - 0 broken internal, 0 broken embeds, 0 non-standard images, and 106 flagged externals of which one class is new and is the checker throttling itself: 49 web.archive.org ECONNREFUSED/ECONNRESET that answer 200 on a serial request. Zero real unrecorded deaths, eleventh consecutive ecosystem rotation. SIGNALS: hyperscale_rs 10918 (27 Aug 20:15 UTC) is the project lead on validator fee policy under Hyperscale - the software will not mandate a fee, "the power sits entirely with those running the nodes", and even a validator-imposed floor loses to reimbursement. Banked, unattributable as scraped. Traffic 30d: 1,781 visitors, top pages / 319, /api/mcp 259, /ecosystem 122. | skipped - cadence, and every gate said skip independently. The 27 Aug UTC day already held FOUR @RadixWiki originals (03:26:38Z, 11:13:53Z, 14:13:49Z, 20:09:18Z) against a 1-2/day cap, and the gate came at 23:15Z, 3.1 hours after the last - inside the 3-4 hour brand-feed rule and far inside the 12-hour same-wiki rule. Reception healthy and flat (22 judged, median 15.5 lk / 0 rp / 259 imp, one zero-engagement post at 5% and it is a reply). The hook is a genesis distribution and a published mechanism, so it cannot decay; banked PRIORITY. No video. Tenth consecutive skip. |
| 2026-08-27 | contents/history | contents/history rotation (run 316), the category's FIRST recorded link audit, and the lead is that this wiki had a page about the event where Radix ran its first ever hackathon and the page did not mention the hackathon. LINKS: 25 pages / 253 external / 131 embeds - 0 broken internal, 0 broken embeds, 0 unverifiable embeds, 0 non-standard images, ZERO real deaths, and all 23 flagged externals sit in bot-block classes (17 linkedin, 2 medium.com/pillarproject, coingecko, coindesk, lsbu.ac.uk) which are now banked. REWRITTEN: /contents/history/pillar-unconference v2.2.1 -> v3.0.0, 1,271 -> 7,310 bytes. It had been one sentence, two photographs and a single date, '20 July 2018'. The Unconference ran 15-22 July 2018, a full week at the Vilnius Grand Resort, confirmed at two independent sources. Radix took a breakout room for three days of coding on the alpha's radixdlt-java and radixdlt-js-lite libraries and then ran the tail event of the week: six teams, $3,000 and a handful of Ledger Nanos, won by Hack.Funding (post-hackathon micro-lending, viable only at Radix's fee level) ahead of RadiXign (a Docusign competitor built in two days), with Rad Property Raffle, Podium, Podiloto and Personal Data Locker also fielded. The whole finding came out of URLs check-links had been flagging as 403 for 316 runs; the Wayback raw-bytes form read both of them. FIXED: /contents/history/pillar-hackathon-1 v2.2.2 -> v2.2.3, which said Pillar and Radix 'crossed again later that year at the Pillar Unconference' when the Unconference was six months earlier and in the previous year. Both pages stamped; both edits verified through /api/wiki. TELEGRAM: 33 messages, nothing new to write, one reception signal logged. TWEET SKIPPED on cadence, the day already holding three originals against a 1-2 cap with the last 4.9 hours before the gate; the hook is banked PRIORITY and cannot decay. Reception measured cold first: 22 judged at 18h, median 15.5 lk / 0 rp / 256.5 imp, one zero-engagement post (5%) and it is the same 2-impression reply. No video. | skipped - cadence |
| 2026-08-27 | community | community rotation (run 315), the category's first recorded link audit, and the lead is that this wiki linked its own CEO's name to a stranger. The homepage pointed "Andy Jarrett" at linkedin.com/in/andyjarrett - Andy Jarrett of Kinexio, formerly Mallcomm, a UK proptech - while the Radix CEO is andrewjarrett1. LinkedIn 999s every bot, so check-links could never tell them apart. NEW PAGE: /community/andy-jarrett v1.0.0, closing the run-300 shortlist item; six blocks off the Companies House officer and PSC registers, the Foundation group-entities article, the RTJL board post of 4 Mar 2024, the Blockchain Expo 2023 speaker bio and the announcements of 29 Jul 2025 and 28 Apr 2026. The spine: he is the sole serving director of BOTH live UK companies on the Foundation side of the group, sole active PSC of the Foundation at 25-50% with no appoint/remove right, has never carried a Radix blog byline, and is the counterparty on the sending side of the treasury handover. EDITS: homepage v8.6.7 -> v8.6.8 (link corrected, both name occurrences wired to the new page), /ecosystem/radix-foundation v4.0.2 -> v4.1.0 (linked, plus the nature-of-control qualification the PSC register carries). STAMPED: adam-simmons, piers-ridyard. LINKS: 11 pages / 184 external / 4 embeds - 0 broken internal, 0 broken embeds, 0 non-standard images, 3 flagged externals all confirmed bot-block classes and alive, so 0 genuinely dead. Metabridge's dissolution and its founding directors were re-checked against the register and the wiki already had them right. | skipped - cadence, and every gate said skip independently. The 27 Aug UTC day already held THREE @RadixWiki originals (03:26:38Z run 312, 11:13:53Z run 314, 14:13:49Z) against a 1-2/day cap, and the gate came at 15:11Z, 57 minutes after the last one - inside the 3-4 hour brand-feed rule and far inside the 12-hour same-wiki rule. Reception is healthy and improving (21 judged, median 16 lk / 0 rp / 255 imp, up from 15/250). The hook is a public register and cannot decay, so it is banked. No video. |
| 2026-08-27 | ecosystem | ecosystem rotation (run 314), and the lead is that a DEX which has settled $846 million on Ethereum now trades eight hundred dollars a month there while its Radix deployment does a hundred and twenty thousand. LINKS: 148 pages / 995 external / 39 embeds - 0 broken internal, 0 broken embeds, 0 non-standard images, 5 banked unverifiable embeds, and 99 flagged externals of which exactly ONE was outside a banked class. That one (acuiq.com/llms.txt at status 0) is settled and banked as a NEW class: a dynamically generated llms.txt takes 18.0 seconds on a cold Vercel start and times the checker out while answering 200 with 19,509 bytes, which matters because this wiki serves its own the same way. The run-312 t.me class retired itself, flagging zero. Tenth consecutive ecosystem rotation with zero real deaths. SIGNAL: dry and off-topic. 182 Telegram messages, ~40 past the run-313 watermarks, almost all of it the continuing radix_dlt argument about unpaid Foundation work; the two keepers are banked, not written. Plausible byte-identical for the fourth consecutive read. Comments 4, newest 5 April, unchanged for the 72nd run. EDITS: two pages, both at the true staleness head once the two LOCKED pages are skipped, both rewritten against live sources and both stamped. /ecosystem/defiplaza v3.1.2 -> v3.2.0: its Status & Metrics section carried three undated figures attributed to 'mid-2026' with no source. The $183,000 TVL HOLDS to the dollar (the project's own undocumented /api/pairs endpoint returns 156 pairs summing to $183,418.89; DefiLlama measures $180,367 the same morning), but the cumulative $10.9M/$69k are not reproducible from any endpoint that answers, so they are replaced by the api.llama.fi per-chain series rather than restated. That series is the finding: Ethereum produced $845,994,781 of the protocol's $855,529,909 lifetime volume and traded $801 in the thirty days to 26 Aug against Radix's $119,685, collecting $12 in fees against $1,095, with Radix now holding 95.9% of protocol TVL. The Ethereum app is still live and still quotes its 0.1% fee. Four live first-party links added that the page never carried (docs, analytics, bridge, Ethereum swap app). /ecosystem/academia-scrypto v3.1.1 -> v3.2.0: metadata.status said 🟢 Active while the page's own infobox and body said the academy died in 2022, so the ecosystem status facet counted it as live. Corrected to 🔴 Closed and dated to the day (both repositories last pushed 19 May and 1 Jun 2022, academiascrypto.com has no DNS record at all); dropped metadata.website, which pointed at aprendescrypto.com, a live domain serving an unconfigured template titled 'Home - Accessible Astro Starter'; added metadata.github; and corrected 'organisation' to 'account' (api.github.com/orgs 404, /users 200). A wiki-wide sweep for the same defect found THREE contradictions in 148 pages, the other two banked. TWEET: posted. Gates cleared: one original on the 27 Aug UTC day against the 1-2 cap, the last (03:26Z) 7.8 h before the gate and clear of the 3-4 h brand-feed rule, and the 12 h same-wiki rule was overridden on merit because the finding is discovery-led with two hard numbers, which is the shape the account measures best on. No video. FEEDBACK: the first unsolicited praise for a page logged in this state - the main Radix chat thanked whoever wrote /ecosystem/runfly and offered a banner for it. | https://x.com/RadixWiki/status/2092933615147520096 |
| 2026-08-27 | contents/tech | contents/tech rotation (run 313), and the lead is that this wiki taught Radix's authorization model with the one behaviour that can bite you left out: a role a blueprint declares but nobody assigns is not denied, it is owner-gated. LINKS: 86 pages / 610 external / 39 embeds - 0 broken internal, 0 broken embeds, 0 unverifiable embeds, 0 non-standard images, ZERO real deaths, and all 29 flagged externals sit inside classes already banked for this category at run 285 (SSRN, Medium, ResearchGate, LinkedIn 999, the six-host Cloudflare 403 class, crates.io, notion, IMF, CEPR, pubpub, web.archive.org status-0, and the run-298 app.curedao.org false positive), so ZERO probes were spent on the list. The rise from run 285's 27 flags on 582 checks to 29 on 610 is entirely growth in the corpus. SIGNAL: high volume, zero yield. 189 Telegram messages over two days, 69 past the run-312 watermarks, and not one publishable fact - hyperscale_rs is five 'gm' plus one unanswered Ledger-app question (banked as a watch), radix_dlt is one continuous Plan-A-versus-intervention argument with no dated claim in it. Plausible byte-identical for the third read since it moved at run 311 (1,732 / 1,499 / 47% / 41s), with /contents/tech/research/hyperscale-rs at 63 visitors the only page of this category in top_pages, breaking the staleness tie toward it. Comments 4, newest 5 April, 77th consecutive run. THE RUN took the two oldest pages in the category, both 30 June and NEITHER EVER VERIFIED, and they turned out to be the same topic split across two one-paragraph stubs. EDIT 1, /contents/tech/core-concepts/access-rules-and-auth-zones v1.3.3 -> v2.0.0, 2 blocks / 2,481 B -> 7 blocks / 12,802 B, rewritten against radixdlt-scrypto @ main. The page asserted that engine-level enforcement makes authorization errors 'structurally impossible' and drew an uncited EVM comparison to say so; both are gone. The claim is wrong in a specific way the source names: authorization.rs resolves an undefined role key by reading the object's OWNER role and testing that rule, so an incomplete role assignment fails OPEN toward the owner rather than closed, and _self_ is never stored at all - it resolves to require(global_caller(self)). Replaced with the mechanics: the three AccessRule variants and the five basic requirements including CountOf as the N-of-M form, the caps that reject an over-complex rule when it is SET rather than when it is tested (depth 8, 64 nodes), the auth zone as a per-call-frame object holding three distinct kinds of evidence, the implicit badges nobody creates (the signature virtual badge, package_of_direct_caller, global_caller), the barrier that sets the parent to None when a call crosses into another global component so proofs do not leak, the ten-method AuthZone interface with its three separate drops, and a closing section that states what the model does NOT do instead of overclaiming. EDIT 2, /contents/tech/core-concepts/role-assignment-module v1.0.2 -> v2.0.0, 3 blocks / 1,705 B -> 6 blocks / 9,321 B, deepened from a single paragraph: the stored shape (one owner field, one role-to-rule collection), OwnerRole None/Fixed/Updatable against OwnerRoleUpdater None/Owner/Object, the reserved namespace measured rather than described (is_role_key_reserved is exactly starts_with('_'), and only _owner_ and _self_ are reserved-and-defined), the 50-role and 100-byte caps, assignment-time rule validation, the four MethodAccessibility values, and the securify path traced through securify.rs - create_presecurified sets the updater to Object, and securify() sets the securify role to DenyAll BEFORE minting the owner badge, which is the step that makes the conversion one-way. Both pages verified through the uncached API at v2.0.0 and both STAMPED. Script retained as scripts/sweep-313-auth-model.mjs, idempotency sentinel corrected after the write so a re-run is a no-op. TWEET skipped on cadence, matching the run-307 precedent almost exactly: the previous @RadixWiki original went out 27 Aug 03:26:38Z and this gate came at 07:12Z, 3.75 hours later (run 307 skipped at 4.0), inside both the 12-hour same-wiki rule and the 3-4 hour brand-feed rule; the 1-2/day cap still had a slot free. The owner-fallback hook is banked PRIORITY and cannot decay. No video. | skipped - cadence |
| 2026-08-27 | ecosystem | ecosystem rotation (run 312), and the lead is that this wiki listed a company as a Radix project for a year after its own website stopped saying so. LINKS: 148 pages / 990 external / 39 embeds - 0 broken internal, 0 broken embeds, 0 non-standard images, 5 banked unverifiable embeds, and 97 flagged externals, one class of which is NEW: five t.me URLs at ETIMEDOUT that flagged zero times at run 310 three hours earlier. One probe settled it (t.me/gable_finance returns 200 with the project in its og:description) and the class is banked with the web.archive.org family, so one probe was spent on the list rather than none. gable.finance retired its own run-310 single by not flagging. SIGNAL: high volume, near-zero yield. 170 Telegram messages over two days, 64 past the run-311 watermark, and almost all of it one radix_dlt argument about Plan A and Plan B for the DAO transition; the single dated keeper is 999519, "Happy 200 days Temporary RAC as of today", back-dating the temporary council to about 8 February 2026, banked because the scrape carries no attribution. Plausible held at the run-311 read (1,732 / 1,499 / 47% / 41s) with /ecosystem at 121 visitors, breaking the staleness tie toward this category for the third run running. Comments 4, newest 5 April, 76th consecutive run. TWO EDITS, both on never-verified pages, both now stamped. EDIT 1, /ecosystem/emberflow v2.1.1 -> v3.0.0, the discovery: the page carried promotional biography of three named private individuals with ZERO citations of any kind in the body, and asserted a Radix connection the company itself no longer makes anywhere. Seven pages of emberflow.org read 27 Aug, 3,943,265 bytes, contain "Radix" zero times, along with zero "XRD", zero "Scrypto" and zero "blockchain", and the site serves no /.well-known/radix.json. Wayback dates the turn: the 23 Jul 2023 homepage names Radix twice and "decentralized" six times, the 31 Aug 2025 homepage names Radix not at all while keeping "decentralized" five times, and by 11 Mar 2026 the second word is gone too. LifeBand is now sold to healthcare providers as an EHR interoperability layer. Rewritten to six blocks: the founder biographies are now marked as company claims against /policy/verifiability rather than stated as fact, the 2023 and 2026 presentations of the product sit side by side, and the page has its first external citations. Status stays 🟠 Dormant because none of the four values in src/lib/tags.ts means "still trading, no longer on Radix", and the page now says so. EDIT 2, /ecosystem/gable-finance v2.1.1 -> v3.0.0: it said "The Gable team applied for a Radix Babylon Booster grant." Gable won one, announced 21 Nov 2023, and this wiki's own funding page has carried the link for months. The Features and Future Plans sections were 2023 forward-looking statements presented as the present ("The first iteration of the Gable will be released shortly after the launch of Radix Babylon in August 2023"; a native token "planned" for 2024 when the Foundation's Nov 2023 post already describes decentralising GAB distribution). Replaced with the dated targets from that post and a Status section dating the dormancy from three artefacts that agree to within a day: the homepage carries Last-Modified 23 Apr 2024, the dApp definition it publishes at /.well-known/radix.json has no committed transaction after 22 Apr 2024, and the GitHub org was last pushed 13 Dec 2023. The $15,000 the funding page attaches to the Gable row is NOT in the post it links, so this page records the grant without a figure and the discrepancy is banked. The fund-wallet census asked for at run 310 was re-run and came back byte-identical, with a method correction banked for the funding page (22 of 36 match, not 20). FOLLOW-UP, same day, after the run was reported: the $15,000 discrepancy banked above was taken rather than left. /contents/history/radix-ecosystem-funding v2.2.1 -> v2.3.0. Every one of the 21 posts the grants table links was fetched and searched, and the defect turned out not to be one row. The programme launch post of 11 May 2023 announces "XRD with a value of up to $10k USD", and the section lead attributed $15,000 to that exact post; $15,000 first appears in the ShardSpace announcement of 8 Dec 2023 and in every later one (Weft, Fibonacci, XRD Domains, InfiniteLabs, RadLand); the nine announcements dated 3 Nov to 5 Dec 2023 state no amount at all. Seven sourced cells keep the figure with the anchor relabelled to "announcement", nine unsourced cells now read "Not stated" and keep the link, the lead records the rise with the reshape post's own word ("now $15,000 in XRD"), and the reshape date is corrected from March 2024 to 7 February 2024. The MVP $5,000 figures were left alone: the Grant Tracks list above the table already matches the programme page. The fund census sentence went from twenty matches to twenty-two in the same edit. Page STAMPED. | https://x.com/RadixWiki/status/2092816028099072454 |
| 2026-08-26 | developers | developers rotation (run 311), and the lead is that this wiki taught two operations it never said how to perform. LINKS: 34 pages / 297 external / 2 embeds - 0 broken internal, 0 broken embeds, 0 unverifiable embeds, 0 non-standard images, ZERO real deaths, and all four flags sit in banked bot-block classes (two crates.io, two medium.com), so zero probes were spent. Third consecutive clean sheet for this category. SIGNAL: 27 Telegram messages, all hyperscale_rs, one keeper and it is developer-facing but unattributable (banked). Plausible MOVED for the first time in eleven reads, to 1,732 / 1,499 / 47% / 41s, which retires the run-303 stalled-ingest suspicion. Comments 4, newest 5 April, 71st consecutive run. TWO EDITS, both on never-verified pages, both now stamped. EDIT 1, /developers/scrypto/09-permissioned-and-regulated-assets v1.0.1 -> v1.1.0, the run's discovery: the page said a freeze 'suspends withdrawals from a particular vault' and stopped there. VaultFreezeFlags is a three-flag bitfield - WITHDRAW 1, DEPOSIT 2, BURN 4 - so an authority can stop a vault paying out while still letting deposits land, or block a burn without touching transfers, and every flag is cleared again by unfreeze, which the page never mentioned at all. Worse, the page declared freeze_roles! and recall_roles! and then left the reader to guess the call: the Scrypto Vault trait has no freeze, unfreeze or recall method, so a blueprint cannot do either. A new section states what actually does - four manifest direct vault aliases (RECALL_FROM_VAULT, RECALL_NON_FUNGIBLES_FROM_VAULT, FREEZE_VAULT, UNFREEZE_VAULT), each addressed by an internal_vault_ id rather than the account or the resource, so recalling from a holder needs a Gateway vault lookup first, and both recalls return a Bucket that lands on the worktop and has to be disposed of before the transaction ends. The two wallet PRs the page tracks were re-checked and have not moved: sargon #452 (126/-29, 10 files) and babylon-wallet-android #1446 (2,625/-26, 30 files) are both still open, neither a draft, untouched since 27 and 26 July, four days after they were opened. EDIT 2, /developers/transactions/05-addresses-and-entity-types v1.0.1 -> v1.0.2: 21 KB of address mechanics that had never been verified, re-read line by line against radixdlt-scrypto @ main - all 21 EntityType discriminants, the 14 entity HRPs and 7 transaction-part HRPs in HrpSet, and the eight network ids and suffixes - and every claim held, including the awkward ones (locker 104 -> d, the three preallocated families, the readable-prefix derivation). The one thing that had aged was its supporting census, taken at epoch 330462, so it was re-run at epoch 338479 / state version 555,449,706 and came back stronger: 287 validator components on mainnet, 188 of them registered, and ALL 287 begin validator_rdx1s followed by one of v, d, w or 0 - the claim holds for every validator entity that exists, not just the registered ones. NON-FINDING kept: nine developers pages carry no infobox block, which looks like a quality-bar breach and is not - their metadata renders the facts table through buildMetadataBlock, so there is nothing to fix. | skipped - cadence, and both gates said skip independently. Two @RadixWiki originals already sat on the 26 Aug UTC day (03:15:41Z run 306, 11:23:14Z run 308) against a 1-2/day cap, and this gate came at 23:11Z, 11.8 hours after the second, inside the 12-hour same-wiki rule by twelve minutes. Reception healthy and unchanged (22 judged, median 15.5 lk / 0 rp / 252.5 imp, one zero-engagement post at 5%). The hook is a published trait definition and a manifest grammar and cannot decay, so it is banked PRIORITY. Ninth consecutive skip. No video. |
| 2026-08-26 | ecosystem | ecosystem rotation (run 310), and the lead is that this wiki described a live prediction market's book as thin when it is empty. LINKS: 148 pages / 989 external / 39 embeds - 0 broken internal, 0 broken embeds, 0 non-standard images, 5 banked unverifiable embeds, and 100 flagged externals with NOT ONE outside a banked class, so zero probes were spent on the list; the rise from run 307's 87 is entirely web.archive.org connect-timeout variance (43 -> 46) plus medium/defillama noise. SIGNAL: high volume, low yield. 115 Telegram messages over two days and 45 past the run-309 watermark, almost all of it one radix_dlt argument about who does the Foundation's unpaid non-technical work now; the only product news is the Run Fly game beta (999469, 17:16 UTC), banked because the page already lists the game. Plausible byte-identical for the ELEVENTH read (1,657 / 1,441 / 47% / 42s), /ecosystem at 116 visitors breaking the staleness tie toward this category for the second run running. Comments 4, newest 5 April, 75th consecutive run. THE RUN cleared three more of the never-verified 21 July cluster. EDIT 1, /ecosystem/delphibets v2.1.4 -> v2.2.0: the page carried one undated sentence for the project's entire present - 'As of 2026 the web app remains live (v1.5) but shows limited active markets'. Read 26 Aug, the app is served, the footer still says V1.5, and the Open filter returns 'There are no Open bets'. Not a thin book, an empty one. The app also publishes 6,964,221 XRD of lifetime volume, which the wiki had never carried, and $DPH read live at epoch 338,430 is 99,999,999 fixed with minter, burner, freezer and recaller ALL DenyAll and the rules locked - so the cap in the tokenomics section is enforced by the resource rather than maintained by the team. Replaced with a dated Status-as-measured section; infobox status now reads 'app served at v1.5, no open markets (26 Aug 2026)'. EDIT 2, /ecosystem/nerds-republic v3.1.1 -> v3.2.0: marked Dormant in the infobox and then written entirely in the present tense below it, with no External Links section at all. Two probes dated it. The site is a Webflow build whose source comment reads Last Published Sat Mar 12 2022 10:34:11 GMT, which turns 'site frozen (2021-2022)' into a day and shows nothing was published across the whole Babylon upgrade. And $GNRD read live at epoch 338,430 is still a FUNGIBLE resource of exactly 10,000 units with every authority DenyAll and rules locked - the reservation receipt, not the 10,000-avatar collection it was to be swapped for, so the swap the page describes in the future tense never happened. Added a Status section and the missing External Links; infobox status and on-ledger rows redated from the 21 Jul epoch-328062 read. STAMP, /ecosystem/delay: no edit needed and that was measured, not assumed. Supply reads 661,195,247.825631037429292673 against the page's 'approximately 661 million', minting denied and burning open to anyone exactly as written, and the Ecosystem Asset Fund wallet still holds 12,497,490.37 DELAY unsold against the infobox's 12.5M. Stamped with mark-verified. The fund read also turned up 204,395.44 DPH, a second undocumented relationship between the same treasury and DelphiBets, banked ACTIONABLE. TWEET skipped on cadence: two originals already on the 26 Aug UTC day against a 1-2/day cap, the most recent 7.7 hours before this gate and inside the 12-hour same-wiki rule. Reception healthy and flat (23 judged, median 15 lk / 0 rp / 251 imp). Hook banked. No video. | skipped - cadence |
| 2026-08-26 | policy | policy rotation (run 309), the category's first recorded audit, and the lead is that this wiki named a notice as the enforcement for three of its policies and had never said what a notice is. LINKS: 6 pages / 6 external / 0 embeds - 0 broken internal, 0 broken embeds, 0 unverifiable embeds, 0 non-standard images, and both flagged externals sit in banked classes, so zero probes were spent: defillama.com/protocol/surge-trade is the run-253 Cloudflare wall and leafnode.info is the run-273 Vercel DEPLOYMENT_PAUSED, both already documented on /policy/verifiability as the worked examples they are. SIGNAL: the driest on record - 42 Telegram messages, hyperscale_rs only, not one past the run-308 watermark; two of the three channels silent for two days; Plausible byte-identical for the tenth read; comments still 4, newest 5 April, 71st consecutive run. EDIT 1, NEW PAGE /policy/editorial-notices v1.0.0, 8 blocks: the six banner variants next to the policy each enforces, the synthetic 180-day freshness notice that no editor places, and the four derived queues at /maintenance, every figure measured rather than described. FIVE notices exist across 370 pages (3 promotional, all on Dormant or Closed ecosystem projects; 2 stub); three variants have never been used; 224 of 369 pages carry a verification stamp and ZERO are past 180 days, the oldest at 150; the queues read orphaned 19, unsourced 13, incomplete 2, and outdated absent because an empty queue is not rendered. EDIT 2, sweep-309-policy-see-also.mjs, all six existing policy pages patch-bumped (conflict-of-interest 1.2.1, freshness 1.3.2, neutral-point-of-view 1.3.1, no-original-research 2.0.1, notability 1.2.1, verifiability 1.5.1) so each still names all of its siblings. Both NPOV worked examples re-checked and still true: radix-rolodex and hermes-protocol both read Dormant. All seven pages verified through /api/wiki and /policy regenerated with the new entry. | skipped - cadence. Two @RadixWiki originals already sat on the 26 Aug UTC day (03:15:41Z run 306, 11:23:14Z run 308) against a 1-2/day cap, the second 4.3 hours before this gate and inside the 12-hour same-wiki rule. Reception is healthy and unchanged (23 judged, median 15 lk / 0 rp / 250 imp, the sole zero-engagement post the same 2-impression reply). The hook is a standing measurement of this wiki and cannot decay, so it is banked PRIORITY. No video. |