Attorney and XRP enthusiast Bill Morgan reveals what he thinks is XRP's biggest strength: its escrow.
Morgan says users only need to understand its escrow to know why XRP will continue to be a successful asset, with all other amendments and capabilities just adding more value. He added that the escrow set up by Ripple on the XRP Ledger is a great example of how it was used to stabilize the price and reassure the market that Ripple would act responsibly in distributing its vast holdings of XRP.
According to XRPScan, 32,444,984,760 XRP is currently in escrow, with 67,526,296,210 XRP now in circulating supply.
In a separate post, Morgan highlighted the decline in XRP escrow as Ripple continues its 1 billion token unlock every month. He noted that about a year ago, the amount of XRP in escrow was just under 36%.
Currently, it is below 32.5% (out of a total of 99,985,640,485 XRP available), which is not surprising given that Ripple does not re-lock about 300 million XRP per month. Morgan predicts that if this trend continues, there will be less than 29% in escrow by next July.
In a recent milestone, nearly a million agent transactions have settled through the XRP Ledger x402 facilitator.
40% to go for XRP Ledger fix upgrade
The fixCleanup3_2_0 amendment, which bundles bug fixes affecting Single Asset Vaults, the Lending Protocol, the permissioned DEX, Multi-Purpose Tokens, and permissioned domains, is currently in voting and has reached 40% consensus according to recent XRPScan data. This means that it still needs another 40% to attain the 80% threshold and achieve the majority required to enter the activation period.
Version 3.2.0 of xrpld, a cleanup and maintenance release, introduces the fixCleanup3_2_0 amendment, which is a collection of fixes for various features.
The fixCleanup3_2_0 amendment adds precision and rounding fixes for Single Asset Vaults and the Lending Protocol. It fixes the 'ValidPermissionedDEX' invariant firing on a valid offer deletion, validates non-canonical Multi-Purpose Token amounts, and adds a zero DomainID check for permissioned domains. The amendment also adds the invariant 'AccountRootsDeletedClean,' which checks that a deleted account does not leave any directly accessible artifacts behind.
