{"body_html":"<h1 id=\"this-week-on-xrpl-2026-09-13\">This week on XRPL \u2014 2026-09-13</h1>\n<p><em>First edition. Weekly Sunday post pairing the loudest XRP news with the on-chain reality \u2014 each item linked to the on-site page that shows it.</em></p>\n<h2 id=\"1-clarity-act-cloture-vote-tuesday-sept-15\">1. CLARITY Act cloture vote \u2014 Tuesday Sept 15</h2>\n<p>The Financial Innovation &amp; Technology for the 21st Century Act (CLARITY, S. XXX) has a scheduled cloture vote in the Senate on Tuesday. The bill draws the SEC/CFTC jurisdictional line and codifies the \"adequately-decentralized\" test that XRP secondary-market trading has been operating under since the 2023 summary judgment.</p>\n<p><strong>What xrpldashboard shows.</strong> Full bill status + linked hearings + last-reviewed date at <a href=\"https://xrpldashboard.com/regulation\">/regulation</a>. The <code>Last reviewed</code> line on that page is the freshness contract \u2014 as of publish time it reads (fill in from git log).</p>\n<p><strong>Observed at:</strong> 2026-09-13T16:00:00Z \u00b7 <strong>Source:</strong> <code>/regulation</code> page (client-side generated from <code>docs/regulation.md</code> git history).</p>\n<h2 id=\"2-xrpl-token-registry-launched-205-ticker-collisions-found-in-the-first-week\">2. XRPL Token Registry launched \u2014 205 ticker collisions found in the first week</h2>\n<p>The registry (<a href=\"https://xrpldashboard.com/registry/taxonomy\">/registry/taxonomy</a>) opened with a 14-value taxonomy (12 real categories + 2 review-status values) and a curator queue seeded from live ledger data. The top-impact 205 rows in the queue are all <code>ticker_collision</code> \u2014 tokens whose currency codes decode to well-known off-chain tickers (USDT, USDC, BTC, ETH, RLUSD, LTC, \u2026) but whose issuer addresses are not in the canonical whitelist.</p>\n<p><strong>Public wording note.</strong> The registry never renders \"impostor\" or \"scam\" as a verdict. <code>ticker_collision</code> is a mechanical statement about issuer provenance, not character. Full definitions at <a href=\"https://xrpldashboard.com/registry/taxonomy\">/registry/taxonomy#ticker_collision</a>.</p>\n<p><strong>What xrpldashboard shows.</strong> The five-lane live-trade grid on <a href=\"https://xrpldashboard.com/tokens\">/tokens</a> renders collision pulses with an amber-ring overlay independent of category color. Curator review is happening at <code>/admin/token-review</code> (private).</p>\n<p><strong>Observed at:</strong> 2026-09-07T18:00:00Z (registry_state row counts: 16,742 token_facts, 385 category-history rows) \u00b7 <strong>Source:</strong> <code>registry_state</code> metric in the daily signed snapshot leaf.</p>\n<h2 id=\"3-signed-snapshot-chain-fix-undercount-disclosure\">3. Signed-snapshot chain fix + undercount disclosure</h2>\n<p>Two weekend fixes landed. First, a chain-link defect in the daily signed snapshot's <code>previous_root</code> computation (mis-computed on same-day re-runs) was corrected; six historical files carried the defect and are documented in <code>docs/CHAIN_LINK_DEFECT_HISTORICAL_2026-09-04.md</code>. Second, the on-page trade-count on <code>/tokens</code> was corrected from raw stream data to floor-counted totals \u2014 a downward revision of about 8.5%, disclosed on the page with a <code>Correction</code> banner.</p>\n<p><strong>What xrpldashboard shows.</strong> The verification recipe on <a href=\"https://xrpldashboard.com/methodology#signed-snapshots\">/methodology#signed-snapshots</a> still works end-to-end: fetch the day's signed JSON, verify against the pinned pubkey, cross-check the chain root at <code>/.well-known/snapshots/chain.json</code>. Anyone can run it.</p>\n<p><strong>Observed at:</strong> 2026-09-07T22:00:00Z (tonight's snapshot is the first to carry <code>registry_state</code> \u2014 meta metric count moves from 3 to 4) \u00b7 <strong>Source:</strong> <code>/methodology</code> page + <code>docs/anchor_history.md</code>.</p>\n<h2 id=\"4-anchor-6-due-friday\">4. Anchor #6 due Friday</h2>\n<p>The weekly on-XRPL anchor commits the current chain root of the signed-snapshot chain into a Payment memo from the anchor account to the ops account. Cadence is Friday-morning UTC. Anchor #6 will be the first to include the new <code>registry_state</code> in its underlying leaf payload.</p>\n<p><strong>What xrpldashboard shows.</strong> Historical anchors + verification instructions at <a href=\"https://xrpldashboard.com/methodology#signed-snapshots-xrpl-anchor\">/methodology#signed-snapshots-xrpl-anchor</a>. Chain-of-custody unbroken since anchor #1 (2026-08-07 21:49:32 UTC).</p>\n<p><strong>Observed at:</strong> 2026-09-13T00:00:00Z (previous anchor #5 landed 2026-09-04) \u00b7 <strong>Source:</strong> <code>docs/anchor_history.md</code>.</p>\n<h2 id=\"5-receiptregistry-signing-key-online-new-attestation-surface\">5. Receipt/registry signing key online \u2014 new attestation surface</h2>\n<p>An Ed25519 receipt/registry keypair (fingerprint <code>A4:0F:B1:0A:9D:33:64:03</code>) went live this week. It signs both <code>/check.json</code> response envelopes (per-request receipts) and the daily signed XRPL Token Registry snapshot. Pubkey published at three independent surfaces: <a href=\"https://xrpldashboard.com/.well-known/snapshots/receipt_pubkey.pem\">/.well-known/snapshots/receipt_pubkey.pem</a>, <a href=\"https://xrpldashboard.com/.well-known/snapshots/receipt_pubkey.json\">.json</a>, and DNS TXT <code>_xrpld-receipt-key.xrpldashboard.com</code>. All three triangulate.</p>\n<p><strong>What xrpldashboard shows.</strong> Verify-any-past-receipt recipe lives at <a href=\"https://xrpldashboard.com/methodology\">/methodology</a>. Domain separator <code>xrpldashboard/receipt/v1</code> is prepended before Ed25519 verify \u2014 cross-domain replay protection against the historical snapshot key.</p>\n<p><strong>Observed at:</strong> 2026-09-07T18:34:00Z (key generation + publication) \u00b7 <strong>Source:</strong> <code>docs/CREDENTIALS.md \u00a75</code>.</p>\n<hr />\n<p><em>This is the first edition. Weekly cadence \u2014 Sunday 16:30 UTC. RSS/Atom feed: <a href=\"https://xrpldashboard.com/thisweek.xml\">/thisweek.xml</a>. JSON twin: <a href=\"https://xrpldashboard.com/thisweek/2026-09-13.json\">/thisweek/2026-09-13.json</a>. Corrections: <a href=\"https://xrpldashboard.com/contact?purpose=weekly-post-correction\">/contact?purpose=weekly-post-correction</a>.</em></p>","canonical_url":"https://xrpldashboard.com/thisweek/2026-09-13","date":"2026-09-13","front_matter":{"canonical_url":"/thisweek/2026-09-13","edition_number":"1","last_reviewed":"2026-09-13","published_at_utc":"2026-09-13T16:30:00Z","tweet_teaser":"This week on XRPL: CLARITY cloture vote Sept 15, first Token Registry live (205 ticker collisions found), signed-snapshot fix, anchor #6 due Friday."}}
