BTC $84,096.38 -2.76%
ETH $2,687.34 -2.53%
BNB $772.29 -2.48%
XRP $1.51 -7.74%
SOL $114.94 -3.57%
TRX $0.3430 -0.28%
DOGE $0.0946 -7.92%
ADA $0.2409 -6.96%
BCH $340.52 -1.54%
LINK $12.42 -5.01%
HYPE $92.79 -4.68%
AAVE $140.24 -7.76%
SUI $0.9638 -6.86%
XLM $0.2033 -8.48%
ZEC $1,524.06 -5.39%
AAPL $336.30 -1.25%
AMZN $248.09 -3.12%
GOOGL $338.94 -3.95%
MSFT $498.08 -0.50%
META $735.37 -0.68%
NVDA $224.23 -2.11%
TSLA $377.83 -0.42%
SNDK $1,776.62 -5.94%
INTC $120.74 -2.95%
SPCX $148.38 -3.87%
MU $1,056.82 -3.78%
AMD $606.90 -2.83%
BTC $84,096.38 -2.76%
ETH $2,687.34 -2.53%
BNB $772.29 -2.48%
XRP $1.51 -7.74%
SOL $114.94 -3.57%
TRX $0.3430 -0.28%
DOGE $0.0946 -7.92%
ADA $0.2409 -6.96%
BCH $340.52 -1.54%
LINK $12.42 -5.01%
HYPE $92.79 -4.68%
AAVE $140.24 -7.76%
SUI $0.9638 -6.86%
XLM $0.2033 -8.48%
ZEC $1,524.06 -5.39%
AAPL $336.30 -1.25%
AMZN $248.09 -3.12%
GOOGL $338.94 -3.95%
MSFT $498.08 -0.50%
META $735.37 -0.68%
NVDA $224.23 -2.11%
TSLA $377.83 -0.42%
SNDK $1,776.62 -5.94%
INTC $120.74 -2.95%
SPCX $148.38 -3.87%
MU $1,056.82 -3.78%
AMD $606.90 -2.83%

upgrade

All
Article
Flash

first_img XRP Ledger restarts upgrade, allowing accounts to split payment and compliance permissions

The PermissionDelegationV1_1 upgrade of the XRP Ledger entered a 14-day activation countdown on September 21, having received support from 29 of the 35 trusted validator nodes. If the support rate remains above 80% during this period, the upgrade could officially activate as early as October 5 at 11:18 UTC; at least 28 validator nodes must continue to support it, or the countdown will reset.This feature allows accounts to split permissions by role. For example, a stablecoin issuer can allow a connected compliance system to approve customer accounts holding its tokens while keeping the keys with full control offline; operational accounts can gain payment permissions but cannot change keys or delegate authority to others. Each trustee can have up to 10 permissions, and the main account can modify or revoke them at any time.This is the network's second attempt to introduce this feature. The original version had vulnerabilities that attackers could exploit to make others pay transaction fees with improperly signed transactions, and by repeatedly submitting high-fee transactions, they could deplete the victim's XRP balance. This vulnerability was reported by community testers on September 15, 2025, and validator nodes were advised to reject the amendment, so it was never activated. The fixed version was released with xrpld 3.3.0, changing the way unauthorized transactions are rejected, ensuring that fees are not deducted before signature verification.

first_img Ripple: Asset management institutions are preparing for the payment upgrade Batch V1.1 of the XRP Ledger

According to CoinDesk, Ripple stated that asset management companies and other commercial projects are preparing to use the Batch V1.1 feature of the XRP Ledger. This feature allows up to eight transactions to be combined into a single operation and ensures that all transactions either succeed or fail in an all-or-nothing manner, avoiding situations where one party completes settlement while the other fails.This upgrade is expected to support Delivery Versus Payment (DVP) transactions, allowing asset transfers and payments to be completed simultaneously, while also enabling exchanges, wallets, and market platforms to directly attach service fees to customer transactions for processing.RippleX Engineering Director Ayo Akinyele mentioned that some projects are already being developed around Batch, and once activated, it will bring related work closer to a production environment. Specific partners and launch times will be announced once plans are finalized. The amendment has received support from 30 of the 35 tracked validators on the XRP Ledger, exceeding the 28 votes required to enter the activation countdown. The countdown began on September 15, and if the validator support rate remains above 80% within 14 days, Batch V1.1 is expected to be activated shortly after September 29.Previously, researchers discovered serious flaws in the Batch V1 signature verification process in February, which could prematurely stop checking signatures under certain conditions, allowing attackers to unauthorizedly include transactions from other accounts. The developers subsequently withdrew the original version. Since the amendment had not yet been activated at that time, the vulnerability code did not run on the live ledger, and no funds were exposed.

first_img Ethereum Glamsterdam upgrade passed the rehearsal, scheduled to launch Sepolia on October 6

According to CoinDesk, the Ethereum Glamsterdam upgrade has continued to confirm blocks after adopting new block construction rules this week, passing key tests and paving the way for its planned launch on the Sepolia public testnet on October 6. The Nethermind client subsequently completed performance tests involving one of the biggest changes in Glamsterdam, with all 2,302 tests passing, processing 57.07 billion gas in 3 minutes and 15 seconds, averaging about 2.9 billion gas per second.The benchmark measures the speed of the Nethermind execution software rather than the entire network, testing block-level access lists. This mechanism informs Ethereum nodes in advance about which accounts and storage data will be used in the block, allowing nodes to fetch data and check unrelated transactions simultaneously, whereas the current Ethereum mostly processes related work sequentially, limiting the amount of activity each block can accommodate. About an hour after the testnet launch, Glamsterdam raised the block gas limit from 60 million to 200 million, freeing up space for more payments, token swaps, and other activities per block.The 200 million gas limit allows Ethereum to absorb more activity before users start bidding for block space, thereby alleviating fee spikes during transaction surges or when popular tokens are launched. Larger blocks are also harder to verify, which may make it difficult for small-scale operators to keep up. Glamsterdam aims to gain additional capacity without excessively increasing chain operating costs. This upgrade also extends the block data propagation time from about 2 seconds to 9 seconds and plans to incorporate the handover and payment of block construction and verification into Ethereum's own rules, reducing reliance on external relay services.

first_img XRP Ledger upgrade Batch V1.1 is just one vote away from activation

The Batch V1.1 upgrade for the XRP Ledger is just one vote away from initiating the activation process. The RippleX team has fixed 11 software defects in the latest review. The Batch feature allows users to combine up to eight related transactions into a single operation, ensuring that both parties complete the transfer simultaneously when two people exchange tokens, thus avoiding the situation where one party pays while the other fails.In Tuesday's snapshot, the upgrade received support from 27 out of 35 trusted validators, accounting for approximately 77%, while changes to the XRP Ledger require an 80% support rate. Therefore, currently, one validator's vote can determine success or failure, and obtaining one more vote will initiate a two-week activation countdown. The support rate must remain above this threshold for 14 days, during which validators can change their votes.Previously, researchers discovered vulnerabilities in the original Batch proposal, allowing attackers to initiate transactions using others' accounts without authorization under specific conditions; this version was not deployed on the mainnet. The new version was released with xrpld 3.3.0 on August 6, and the latest review found 11 issues related to signatures, authorization checks, and server crashes. Among these, a serious vulnerability rated by the security company Common Prefix could allow attackers to reuse user signature permissions to execute transactions beyond expectations. RippleX stated that the review involved four senior engineers, audits from Halborn and Common Prefix, public security competitions, and automated testing, and mentioned that commercial projects using Batch have been signed or are in development.
app_icon
ChainCatcher Building the Web3 world with innovations.