docs(digidollar): update exchange integration guide for mainnet activation#431
Open
JohnnyLawDGB wants to merge 1 commit into
Open
Conversation
…ation DigiDollar activated on mainnet at block 23,869,440 on 17 July 2026, but the exchange integration guide still reads as pre-activation: the Key Facts table says features "remain BIP9-gated until activation", section 14 describes the deployment in the present tense as "gated by BIP9 bit 23", and section 13 is titled "Test on Testnet Now!". An exchange evaluating a listing reasonably reads all of that as "DigiDollar is not live yet". Changes: - Add a status banner near the top stating mainnet is live, with activation height and date. - Section 14: rewrite in past tense with the actual outcome; retain the original signaling parameters as background; record the BIP90 burial in v9.26.5 (consensus.DigiDollarHeight = 23869440). - Section 14: note the BIP9 off-by-one. Pre-v9.26.5 nodes report activation_height 23869439 -- the final LOCKED_IN block -- while consensus buries 23869440. Easy to trip over when recording the activation height. - Key Facts: replace the pre-activation wording with live mainnet status and note v9.26.5 as current. - Section 1: recommend v9.26.5 for exchange nodes (oracle startup scan fix). - Section 2 note: scope the "RPCs are gated" caveat to networks where DigiDollar has not yet activated. - Section 13: reframe from waiting for activation to rehearsing the full deposit/withdraw loop on testnet before touching real funds. Documentation only; no behavioural or consensus changes. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
DIGIDOLLAR_EXCHANGE_INTEGRATION.mdstill reads as pre-activation, which is the single most confusing thing about it for its intended audience.An exchange evaluating a DigiDollar listing currently sees:
The reasonable reading of all three is DigiDollar is not live yet. It has been live on mainnet since block 23,869,440, 17 July 2026. This came up while walking a prospective exchange integrator through the guide — they asked whether they were reading a pre-release document.
Changes
consensus.DigiDollarHeight = 23869440,src/kernel/chainparams.cpp).On the activation height
Worth flagging explicitly, because the two available sources disagree by one block:
getdigidollardeploymentinfoon v9.26.4activation_height: 23869439consensus.DigiDollarHeight(chainparams.cpp) + v9.26.5 release notes2386944023869439is the final block of the BIP9LOCKED_INperiod; rules take effect at the following block. The guide now uses 23,869,440 throughout and adds a short note so integrators reading the height off a pre-v9.26.5 node don't record the lock-in boundary by mistake.Verification
Every fact asserted here was checked against a synced mainnet node and against
develop:src/kernel/chainparams.cpp(DigiDollarHeight/AlgoLockHeight=23869440)getdigidollardeploymentinfoon a v9.26.4 mainnet nodeDocumentation only — no behavioural or consensus changes.
🤖 Generated with Claude Code