The authority delegation function of XRP ledger was not launched as scheduled...

XRP账本核心升级遭遇“地震级”变动：授权委托与批量交易补丁即将密集激活

后续进展

此前多家媒体报道称，XRP Ledger（XRPL）的“权限委托”（Permission Delegation）升级定于10月5日激活，但该计划并未如期实现。原因在于，该提案在9月下旬重置了为期两周的验证者批准倒计时。目前，名为 PermissionDelegationV1_1 的修正案仍处于禁用状态。

根据10月5日协调世界时（UTC）17:16的最新验证者投票结果显示，在35名受信任的验证者中，有29人支持该提案。这一票数足以维持当前的批准窗口继续运行，但不足以在之前的中断后保留原定的10月5日时间表。如果这种支持率持续高于网络所需的阈值且不再出现中断，PermissionDelegationV1_1 预计将在10月8日协调世界时21:25左右激活。紧随其后的是两项与批量交易（Batch）相关的修正案，它们将在不到18小时内依次上线。

具体而言，fixBatchV1_2 修正案的激活时间预计为10月9日协调世界时14:13左右，而 BatchV1_1 则可能在约14:46激活。这意味着三项独立的XRP Ledger协议变更将在大约17小时的窗口期内集中激活。

为何10月5日的升级未能如期进行？

最初的10月5日预测并非空穴来风。PermissionDelegationV1_1 received enough validators support on September 21, when 29 validators voted in favor, seemingly entering the final two-week countdown. Subsequently, several cryptocurrency media listed October 5 as the most likely activation date.

However, XRP Ledger amendments are not activated once the voting threshold is reached. They must have continued support from more than 80% of trusted verifiers for two consecutive weeks. If the support rating falls back to 80% or below, the previously accumulated time will be cleared and a new two-week cycle will begin only after the amendment regains the required majority. PermissionDelegationV1_1 went through this process in late September. Its majority vote advantage was re-established at around 21:25 UTC on September 24, which postponed the earliest possible activation date from October 5 to the same time period on October 8.

This situation is similar to the vote reset faced by another major XRP Ledger upgrade. Previous reports pointed out that the "Batch" upgrade has been postponed from September 29 to October 9 due to the verifier support rate temporarily falling below the required threshold.

Permission delegation: Let the account distribute specific permissions instead of private keys

PermissionDelegationV1_1Changed the way permissions are allocated between accounts on XRP Ledger. Account owners can grant authority to perform specific operations to other accounts without transferring the private key that provides unlimited control over the original account. For example, a company can allow an operating account to perform defined payment functions while retaining its broader control elsewhere.

The "V1_1" in the version number is important because it is not the first version of this feature. An early "privilege delegation" amendment was discovered to be flawed by developers before activation and was therefore withdrawn. The revised implementation was subsequently introduced in the form of PermissionDelegationV1_1. Previously, the amendment was part of the xrpld 3.3.0 software package and attracted attention in August when six XRP Ledger amendments completed the initial validator voting window. At that stage, passing the initial voting period does not guarantee final activation, as each amendment needs to establish and maintain its own consecutive super majority.

BatchV1_1 and its fixes are coming soon

The most unusual part of the current schedule is that these three potential activation points are closely clustered together. In a real-time verifier read on October 5,BatchV1_1 received support from 30 of the 35 trusted verifiers. It has maintained its latest majority advantage since around 14:46 UTC on September 25, so its earliest activation time is around 14:46 UTC on October 9.

BatchV1_1Allow accounts to package up to eight transactions into one batch transaction. Depending on the execution model, an application can require that all component transactions succeed together, or use other execution rules. This lays the foundation for workflows such as "delivery-versus-payment", where payments and transfers of tokenized assets can be made conditional on each other rather than settled independently.

The accompanying fixBatchV1_2 amendment received wider support in this reading, with all 35 trusted verifiers voting in favor. The amendment was introduced in the emergency version of xrpld 3.4.1 released on September 25 to address security-sensitive issues discovered by developers involving batch implementation. The fix rejects bulk internal transactions that use incorrect transaction wrappers. Its latest majority advantage began shortly before BatchV1_1, so its expected activation time is around 14:13 UTC on October 9, about half an hour earlier than BatchV1_1.

October 8 and 9 are time windows rather than guaranteed release dates

The current sequence looks extremely tight: PermissionDelegationV1_1 is expected to activate at 21:25 UTC on October 8,fixBatchV1_2 is expected to activate at 14:13 UTC on October 9, and BatchV1_1 is activated approximately 33 minutes later. These timestamps should not be regarded as guaranteed start-up times.

Currently, PermissionDelegation V1_1 Just at the minimum level needed to maintain the current validator aggregate majority, obtaining 29 of the 35 votes. If sufficient changes in validator support are made before October 8, its countdown will restart. The same rules apply to both bulk trading amendments. Although their current voting advantage provides more room to allow individual validators to change positions, their activation still depends on the required super majority remaining intact throughout the two-week period.

This is a correction to the October 5 narrative: "Delegation of Rights" is not yet online. Instead, XRP Ledger currently has three pending amendments, which are expected to be activated between the evening of October 8 and the afternoon of October 9 if the verifier consensus is maintained.