This page describes the upcoming Bitcoin network events — the BIP-110 proposal and the anticipated eCash network fork — and how Ripple Custody handles them.
This advisory is not tied to a particular version of Ripple Custody. Published August 7, 2026.
If you run on-premise infrastructure, contact your node providers before August 8, 2026 and verify that your Bitcoin nodes will not enforce BIP-110. See On-premise customers: action required.
Ripple Custody maintains a strictly neutral position on BIP-110 and will neither enforce nor reject the upgrade. Our infrastructure runs standard Bitcoin Core and follows the majority chain. We securely process blocks whether or not they contain BIP-110 signaling, so service continues uninterrupted.
If you use on-premise infrastructure, contact your node providers before August 8, 2026 and verify that your nodes will not enforce BIP-110.
Nodes that strictly enforce BIP-110 risk rejecting approximately 97% of blocks. A node that rejects these blocks loses synchronization with the majority chain and diverges from the Ripple Custody view of the network, which can cause significant operational disruptions.
At this time, Ripple Custody will not support the eCash forked asset at launch, pending further internal evaluation of its security and stability.
Network conditions may fluctuate during this transition. To protect your operations from potential chain reorganizations and settlement risks, we strongly recommend that you temporarily increase the required confirmation counts for all incoming Bitcoin transactions.
Our engineering team is actively monitoring the network, including BIP-110 signaling and fork developments, and will continue to do so through mid-September 2026.
If you have questions or need help verifying your node configurations, contact our support team.