@bitgree 28 January 2026 more from that month

Bitgree now uses Bitcoin Cash double-spend proofs *Bitgree has received an update that reduces the time required to fund an escrow.* How did it work until now? Until now, when the wisher sent a transaction to fund the escrow, at least one blockchain confirmation was required to be considered secure. Until the transaction received that confirmation, the proponent was shown a warning not to purchase the product yet. What has changed? Bitgree now supports Bitcoin Cash double-spend proofs, allowing escrow funding transactions to be considered secure within 5 seconds of being sent, even before receiving any confirmations. How does the implementation work in Bitgree? Bitgree still detects the 0-conf transaction almost instantly (in approximately one second). However, instead of directly displaying a `1 confirmation required` message, it shows a `Transaction received, please wait a few seconds while we make some adjustments` message. It then waits for about 4 seconds and, afterwards, checks via its node whether any double-spend proof for the transaction has appeared on the network. If none is found, the transaction is considered secure and the escrow is funded. What happens if a double-spend attempt is detected? If a double-spend attempt appears during the 4-second waiting period, Bitgree simply displays the `1 confirmation required` message, just as it did before. The same applies if double-spend proofs are not applicable to a specific transaction due to technical criteria, although this only happens in very few cases. What does this update mean in practice? Escrows on Bitgree are now funded almost instantly, without the need to wait for a blockchain confirmation. This makes the user experience smoother for both the wisher and the proponent.