22 Votes for Lending Protocol and 23 for Vaults on XRP Ledger in Nov. 10 Vote
Key Facts
The proposed lending protocol on the XRP Ledger received support from 22 of 35 validators, while the Single Asset Vault amendment received 23 votes, according to the network’s amendments ledger dated Nov. 10, 2026. The ledger showed that neither amendment had been activated and that neither gained nor lost a majority that day. The number required for activation was 28 votes in the ledger, leaving the lending protocol 6 votes short and the vaults 5 votes short. The tally means recorded support had not yet reached the required voting level, despite the similar number of votes in favor of the two amendments. The proposals concern adding lending and asset-pooling tools to the network’s protocols.
Activation of XRP Ledger amendments is governed by a rule requiring support from more than 80% of trusted validators for two weeks. Network documentation says reaching the required support level does not lead to immediate activation, as the percentage must remain above the threshold throughout the specified period. If support falls below 80%, the amendment is temporarily rejected and the two-week period starts again. The activation process is therefore tied to sustained support, not simply reaching a certain number of votes in a single reading. This requirement sets a time frame for determining whether the amendments will take effect on the network.
The governance mechanism provides that votes from trusted validators count toward amendment support. XRP Ledger documentation says only validators vote, and that votes counted are those cast by validators trusted by the network. An individual server does not have the authority to activate or deactivate an amendment across the network. This makes the activation decision the result of a collective vote that meets the trust and duration requirements. These rules place the Nov. 10 tally in the context of a governance process that cannot be decided by a single operator.
The Single Asset Vault proposal would allow a pool to be created that collects assets from multiple depositors and then makes them available to other protocols on-chain, including the lending protocol. Network documentation says assets that vaults can hold include XRP, trust-line tokens and multi-purpose tokens. The design puts the pooling and availability of funds within the network’s own infrastructure, rather than limiting them to separate depositor balances. The proposed vaults are linked to the lending protocol, as pooled funds could serve as a source of financing. The vote therefore covers two amendments that complement each other in their proposed function: the asset pool and the lending mechanism that could use it.
The lending proposal describes fixed-term, uncollateralized loans funded by pooled assets. Under the proposal’s specification, credit assessment and risk management take place off-chain, while loans are executed within the protocol on the network. This separation means the loan design does not rely on crypto collateral held on-chain, but on assessments and risk management conducted off-chain. The proposal also includes a first-loss capital mechanism for when a loan defaults. The specification says this mechanism absorbs part of the losses in the event of default, without stating that it covers all losses.
The reference server software release 3.4.0, available in September 2026, added the LendingProtocolV1_1 amendment as a proposed amendment. The release notes say the software provided the necessary code, but its release did not itself activate the rules. The proposal adds closed vaults with a defined cycle through underwriting, investing and redemption phases, and changes interest recognition to a cash basis. In a performance report published by RippleX developers in October 2026, the company said tests of the amendment detected no decline in throughput across about 20 comparisons between test groups. These results remain part of the amendment’s technical background, while the validator vote and sustained-support process determine whether it will be activated on the network.