When I posted almost one year ago the amount of XRP in escrow was just under 36%. Almost one year later it is now below 32.5%, which is not surprising given that ripple does not re-lock about 300 XRP million per month. What is surprising is how many people lazily post that the amount of XRP locked in escrow is 35% or 40% or total supply. If the trend continues, there will be less than 29% in escrow next July. Some Bitcoin maxis still think it is over 50%.
Here is my projection on the US Senate vote on Clarity Act H.R.3633 ๐ ๐บ๐ธ ๐ณ
YAY - 60 โ ๏ธ
NAY - 40
Last year, July 17, 2025 the US House passed the Clarity Act by a bipartisan vote of 294-134. โ ๏ธ
The Clarity Act has 16+ illicit finance safeguards, not loopholes:
โ Sec 201: BSA/AML applies to crypto
โ Sec 303: new sanctions to hit Iran
โ Sec 305: exchanges can freeze dirty money
If you donโt like crypto, then say it, but stop these baseless attacks.
๐๏ธ RIPPLE IS OFFICIALLY MiCA COMPLIANT. ๐จ
@Ripple secured their CASP license in Luxembourg on June 23.
30 European countries.
Full regulated payment services.
One $XRP infrastructure.
83% of EU crypto firms couldn't even get licensed.
Let that sink in..
#CLARITYAct will it actually pass by July 4th?
BlackRock's Joseph Chalom just put the odds at sub-50% for that deadline, but stays optimistic it lands by year-end if not before August recess.
His sharper point: if the US stalls, Asia won't wait. He's been to Korea and Hong Kong 4x in 9 months and expects local regulators there to pass their own frameworks first, possibly leapfrogging the US.
The future of payments will be multichain, interoperable, and built on institutional-grade blockchain infrastructure.
Our focus is simple: continue making the XRPL the leading blockchain for institutional payments โ and a natural home for the next generation of key regulated stablecoins โ while growing the utility and adoption of $RLUSD and $XRP around the world.
๐จ๐๏ธNEW: The Next Two Weeks Could Decide the Fate of the Clarity Act
With the Senate out until July 13, staff, the White House and industry stakeholders are racing to resolve the issues standing between the Clarity Act and a Senate floor vote.
https://t.co/LAhB5sXzhM
THE WAIT IS ALMOST OVER..
According to an undisclosed source, the clarity act final text could be release by US Senate this Friday, July 3. ๐ ๐บ๐ธ
Concerns have been raised about the possibility of front running or transaction sandwich attacks on XRPL payments and offer crossing.
For the reasons I've explained, I'm not that concerned about this issue. But I have a proposal for a fairly simple scheme that would eliminate this attack. It's a transaction reservation scheme that can ensure that a transaction executes before any transaction that was formed after it was disclosed.
This is the scheme, and it eliminates concerns about front running or sandwich attacks.
Reserving Transaction Slots
A new ledger object is proposed, ReservedTxns. It contains a ledger sequence number and an array of transaction IDs. It is stored at an index that is formed from a hash of a fixed string and the ledger sequence number.
A new transaction is proposed, TxnReserve to reserve an execution slot for a transaction. It takes a ledger number and transaction ID as parameters.
It succeeds if:
1) It pays a fee of at least twice the normal transaction fee.
2) It meets all the normal transaction execution requirements.
3) The ledger sequence number specified in the transaction is greater than that current ledger sequence number and not more than 16 ledgers greater than the current ledger sequence number. The transaction TECs if this test fails.
4) The ReservedTxns object for the specified ledger sequence number either does not exist or if it exists it contains fewer than 32 transaction IDs and does not contain the specified transaction ID. The transaction TECs if any of these tests fail.
If it succeeds, it creates a ReservedTxns object for the specified ledger index if one does not exist. It then adds the specified transaction ID to the end of the array of transaction IDs in the object.
Broadcasting Reserved Transactions
If a transaction has a reserved slot in ledger X, the transaction should be broadcast as soon as it is known ledger X-1โs initial proposals are all received or the final consensus transaction set is known. The XRPL software should be modified to provide a feature to disclose when that occurs and, if desired, to hold a list of transactions to broadcast when, and only when, that happens.
The XRPL software should always broadcast a transaction with a reserved slot if that transaction has not been broadcast recently. This should apply even if the server thinks the transaction will not succeed. Its relaying has already been paid for by the doubled fee for the reservation transaction, so this is not an attack.
A transaction that is intended to execute as a reserved transaction should have its last valid ledger set to the ledger it is expected to execute in. This ensures that if it is somehow delayed, it still cannot be sandwiched or front run.
Execution Mechanics
As each ledger executes, the following steps are added prior to the execution of any transactions in the transaction set:
1) The ledger object containing the reserved transactions for this ledger sequence number is retrieved. If there is none, skip the rest of these steps and execute transactions normally.
2) For each transaction ID in the set of reserved transactions, that transaction is executed if it is in the consensus set and removed from the consensus set so it will not execute again.
3) The reserved transactions object for this ledger sequence number is removed from the ledger.
DoS Attack Resistance
There is a theoretical attack on this scheme where an attacker could fill up all reservation slots for many ledgers as a denial of service to others to prevent them from being able to use this scheme to protect their transactions. This is mitigated by the fact that they would have to pay continuously and others could simply wait the attack out. However, the cost is low enough that someone could theoretically do this indefinitely.
A simple fix is to ratchet up the fees for the reservation transaction as the object starts to get full. For example, when we hit 16 reserved slots, we could begin to raise the fee linearly up to the base reserve. By the time we hit 30, the fee could go up to three times the base reserve.
If needed, we could even raise the limit to 64 if people are willing to keep paying fees. Itโs likely that this would never result in such fees being paid and simply make the attack impractical. An attacker would have to pay, every five seconds, several times the most anyone would be willing to pay to protect their transaction.
From an undisclosed source..
CLARITY ACT H.R.3633 FULL SENATE FLOOR VOTE COULD HAPPENS BETWEEN.. ๐ ๐บ๐ธ
July 20 - July 30 ๐
Please do not ask me for sauce and sausage.. โ ๏ธ
Lock in.. ๐