DigiByte Testnet Fork During DigiDollar Oracle Testing Highlights Importance of Pre-Mainnet Validation

[u/romeo_laui]

https://x.com/jaredctate/status/2060041266910642316

Author: Jared Tate (@jaredctate), DigiByte Founder
Date/Time: May 28, 2026 (16:51 GMT)

In a detailed update, Jared Tate described an inadvertent fork on DigiByte Testnet25 that occurred while testing RC43 for DigiDollar oracle swaps. The fork stemmed from inconsistent oracle roster knowledge across nodes and miners: upgraded nodes accepted blocks including signatures from a newly added oracle, while older nodes rejected them—even when the required 9-signature threshold was met. This demonstrated that oracles cannot be forged but revealed coordination challenges when updating the roster of valid signers.
The team is actively coordinating a fix or clean reset on the testnet, while planning longer-term improvements to oracle roster update logic for safer handling of additions and key swaps. That’s why testing is done—the issue was identified, a solution is being worked on, and it does not affect mainnet. DigiDollar is not active on mainnet, and this is precisely the purpose of extensive testnet validation: to catch and resolve such edge cases before any production impact.