🛰 Flare votes on Confidential Compute — a programmable layer for XRPL assets
Governance vote July 6–13.

Flare has scheduled a community governance vote for July 6–13 (notice posted June 29) to deploy Flare Confidential Compute (FCC) on its Songbird canary network — the first live implementation of the Flare 2.0 architecture (outlined March 2025).

🏗 What it is
▸ FCC pairs trusted execution environments (TEEs) with Flare's data protocols: apps execute on external chains while verification stays decentralized on Flare.
▸ The goal is a programmable confidential compute layer for real-world assets issued on the XRP Ledger — XRPL-issued assets interact with dApps without manual bridging.
▸ It adds protocol-managed wallets (operating on external chains under predefined rules), a faster per-transaction verification path instead of batching, and support for third-party hardware extensions.

⚙️ How it's tested
On Songbird the hardware runs on Google confidential compute under the Flare Foundation; data providers authorize data via weighted consensus, paid from a foundation pool plus attestation fees. Mainnet comes only after the canary run.

💡 Hugo Philion: XRPL is where assets are issued; Flare is the compute layer that adds smart features.

⚖️ To be precise: this is a Songbird (canary) governance vote, not an XRPL protocol change and not a mainnet launch. No token or yield implications — it's ecosystem infrastructure.

🔗 Source: Bitcoin.com · Flare

📡 Tracking XRPL infrastructure & protocol design — @StaticBit_io

#XRP #XRPL #RWA #Flare

⚙️ Batch (XLS-56) is back — atomic multi-transactions on XRPL
Merged to develop; voting comes next.

Denis Angell (the implementer) announced that after an attack-athon, a security audit and 4 reviews, Batch support (V1_1) is officially merged back into xrpld (the develop branch) and will be up for voting in the next release.

🧩 What Batch is
It packages multiple transactions and executes them as a single all-or-nothing atomic unit — no smart contracts. Up to 8 inner transactions, with modes AllOrNothing / OnlyOne / UntilFailure / Independent. Think atomic swap-and-pay, offer + payment, mint + list NFT. It fixes an old pain: if a chain of txs fails midway, the rest break on sequence — Batch removes that.

🔁 Why "back"
The first implementation had an inner-signature issue. Instead of a band-aid (the fixBatchInnerSigs amendment, now deprecated), the feature was reworked as V1_1 and hardened by audit before re-merging.

⚖️ Honest status
This is a code merge into develop, not activation. Next: it lands in a release → becomes an amendment in validator voting → only then mainnet. Batch is not in voting and not on mainnet yet.

🧵 We broke Batch down when it was still in testing — our explainer here.

🔗 PR: rippled#6446 · spec: XLS-56

📡 Tracking XRPL infrastructure & protocol design — @StaticBit_io

#XRP #XRPL #Batch

📊 Why the XRPL lending vote is stuck — it's adoption, not the feature

A month after v3.2.0 shipped (June 15), the network is only half-upgraded: 52% of nodes still run 3.1.3, just 41% are on 3.2.0.

The SingleAssetVault (XLS-65), LendingProtocol (XLS-66) and fixCleanup3_2_0 amendments ship in 3.2.0. A node that hasn't upgraded simply can't vote yes — it doesn't have the code. So consensus is stuck at 20–26% against the 80% threshold (28 of 35 UNL).

⚠️ Fairly: some of this is deliberate — v3.2.0 shipped with migration bugs (pubkey mismatch, sync issues), so part of the caution is 'safety first', not laziness.

💡 The vote hits a ceiling until UNL validators roll to 3.2.0.

🔗 Data: XRPScan, July 2

#XRP #XRPL #Validators

🏛 CLARITY Act: the July 4 deadline is off ⏳

The White House aimed to sign the bill by Independence Day — that's not happening. The Senate left on June 29 and returns July 13, with the first week reserved for the defense bill. The realistic window for a floor vote is late July, before the August recess (from Aug 10).

🧮 The vote math — cloture needs 60 with 53 GOP seats; per Galaxy, two Republicans are expected to vote no → roughly 9 Democrats need to cross over.

⚖️ Two unresolved disputes — ethics provisions around presidential crypto holdings, and Section 604 (developer protections), opposed by law-enforcement associations.

📉 Markets repriced — Polymarket puts a 2026 signing at ~40%, down from 82% in February; Galaxy cut its estimate from 75% to 50%.

💠 For XRPL this is the year's main US regulatory catalyst: the bill would classify XRP as a digital commodity under CFTC oversight.

🇪🇺 The contrast is sharp: MiCA reached full enforcement in the EU on July 1 — Europe finished writing its rules while the US moved its deadline.

⚠️ Senator Lummis: missing the pre-recess window could push the next realistic shot to 2030 — an election year leaves little room for complex financial legislation.

🔗 Sources: coingape.com · cryptotimes.io · Polymarket

📡 Tracking the regulatory picture around XRPL — @StaticBit_io

#XRPL #XRP #CLARITYAct #regulation

🔮 XLS-47: Price Oracles — how XRPL gets data from the outside world

✅ Live since November 2, 2024 — nearly a year before Credentials (XLS-70). Spec author: Gregory Tsipenyuk.

🧩 Why it matters — a blockchain has no native idea what XRP/USD is worth or what a loan rate should be. An oracle bridges that gap: a provider publishes a price on-chain so AMM, DEX, and the Lending Protocol can rely on it.

⚙️ How it works — a new Oracle ledger object holds up to 10 asset pairs per instance. Two transactions: OracleSet (create/update a price), OracleDelete (remove it). Each pair carries BaseAsset/QuoteAsset/AssetPrice/Scale.

🏗 Protocol-native, not L2 — unlike the classic Chainlink model with off-chain nodes and a bridge contract, this oracle lives inside the ledger itself. A provider just submits OracleSet.

🤝 Two providers integrated at launch: Band Protocol and DIA.

📈 Use cases: AMM and DEX get a fair reference price for market-making, the Lending Protocol uses it for rates and liquidation triggers, and the EVM Sidechain syncs data against mainnet.

🩹 A later fix, fixPriceOracleOrder (rippled 3.0.0), addressed a bug where asset-pair order could differ between oracle creation and updates, breaking predictable price lookups.

🔗 Sources: XRPLF/XRPL-Standards (XLS-0047), xrpl.org/docs (Oracle, OracleSet)

📡 Tracking XRPL infrastructure — @StaticBit_io

#XRPL #XLS47 #Oracles #DeFi

🏛️ Ripple secures full MiCA CASP license as EU's transition period closes

✅ Luxembourg's CSSF granted final authorization (not the preliminary green light — the actual license) on July 6. Combined with the existing EMI license (since February), Ripple is now fully MiCA-compliant.

🌍 What it unlocks — passporting crypto services across all 30 EEA countries (27 EU states plus Iceland, Norway, Liechtenstein) through a single regulatory entry point.

⏳ Why the timing matters — MiCA's transitional period ended July 1. Of the 1,200+ companies previously operating in the EU under national regimes, only around 280 secured licenses in time (per ESMA's July 3 register update). The rest are legally required to wind down EU operations.

🚫 Notable casualties: Binance missed the deadline. Tether didn't pursue MiCA compliance at all — USDT is being pulled from European exchanges including Binance and Coinbase.

💬 Cassie Craddock, Ripple's Managing Director for UK & Europe, marked the news on X: the company is now "fully licensed in Europe" and building on recent momentum.

📊 Ripple now holds 75+ regulatory licenses worldwide. The CASP status covers custody, exchange, transfer, and placement of crypto assets — meaning banks and fintechs can work with Ripple Payments through one integration instead of 30 national regimes.

💡 This is about Ripple's regulatory infrastructure, not a direct signal for XRP token demand — but it's meaningful context for institutional trust in Ripple as an operator.

🔗 Source: ripple.com/ripple-press

📡 Tracking the regulatory picture around XRPL — @StaticBit_io

#XRP #Ripple #MiCA #CASP #StaticBit

💵 Nuvion integrates RLUSD — AI banking platform plugs in Ripple's stablecoin

Nuvion, an AI-powered global banking and cross-border payments platform for businesses and fintechs, announced the integration of RLUSD into its infrastructure. The move lets clients move between traditional banking rails and blockchain-based payment networks through a single API — cross-border settlement, treasury and liquidity management across multiple markets.

📈 RLUSD's growth on XRPL (per Evernorth):
▸ XRPL supply — from ~$20M (late 2024) to ~$800M (June 2026)
▸ XRPL's share of total RLUSD supply — ~51% (up from ~17% in April)
▸ Monthly RLUSD transactions — from ~54K to 600K–1.1M

🏛 The announcement landed the same week Ripple secured full MiCA CASP authorization in Luxembourg — regulated access across 30 EEA countries.

"Integrating RLUSD expands the infrastructure available to businesses operating internationally," — Keisha Clark, Managing Director of Nuvion.

🔗 Source: Nuvion/Ripple press release, July 6, 2026 (PR Newswire)

#XRPL #RLUSD #Ripple #Fintech