DigiByte v9.26.0-rc12 Release Notes

WARNING: This is a TESTNET-ONLY release. DO NOT use on mainnet.

Development Branch: https://github.com/DigiByte-Core/digibyte/tree/feature/digidollar-v1

Join the Developer Chat: https://app.gitter.im/#/room/#digidollar:gitter.im

What's New in RC12

🔮 Phase 2: Multi-Oracle Consensus (3-of-5 Schnorr Threshold)

The headline feature of RC12 is the activation of Phase Two oracle consensus on testnet. This moves from the single-oracle (1-of-1) system used in RC11 to a decentralized 3-of-5 Schnorr threshold system.

Key changes:

• 3-of-5 consensus: Any 3 of 5 authorized oracle operators must provide valid signed price messages for a bundle to be accepted into a block
• Phase Two activation at block 100: Testnet activates multi-oracle consensus early for testing
• 5 oracle nodes enabled: Oracle operators 0–4 are now active (previously only oracle 0)
• Phase Two compact format (v0x02): New on-chain encoding for multi-oracle bundles, maintaining the same 22-byte footprint
• Phase-aware block validation: ValidateBlockOracleData() now routes to Phase One or Phase Two validation based on block height

🔑 Wallet-Based Oracle Key Management (New!)

RC12 introduces two new RPC commands that make oracle setup dead simple — no manual key handling required:

createoraclekey — Generate your oracle keypair

digibyte-cli -testnet -rpcwallet=oracle createoraclekey <oracle_id>

• Generates a Schnorr keypair and stores the private key securely in your wallet
• Returns both the X-only public key (32 bytes, used in chainparams) and compressed public key (33 bytes, for reference)
• The private key never leaves your wallet

startoracle — Start your oracle with your ID

digibyte-cli -testnet -rpcwallet=oracle startoracle <oracle_id>

• Automatically loads the private key from your wallet — no raw hex needed
• Starts the oracle price feed thread
• Optional: pass private_key_hex as second parameter for manual key injection

⚠️ After restarting digibyted, you must run startoracle again. The key persists in the wallet, but the oracle thread does not auto-start.

📋 Quick Oracle Setup (2 Commands!)

# 1. Create your oracle keypair (one-time)
digibyte-cli -testnet -rpcwallet=oracle createoraclekey 5

# 2. Start your oracle (after every node restart)
digibyte-cli -testnet -rpcwallet=oracle startoracle 5

That's it. Send the X-only public key from step 1 to the DigiByte Core maintainer. Once your key is added to chainparams.cpp, step 2 is all you need.

See DIGIDOLLAR_ORACLE_SETUP.md for the complete oracle operator guide.

🐛 Critical Bug Fix: BIP9 DigiDollar Activation

• Fixed BIP9 activation state machine — In RC11, ALWAYS_ACTIVE combined with an early return in ReadRegTestArgs() prevented -digidollaractivationheight from working. RC12 ensures DigiDollar activation progresses through the full DEFINED → STARTED → LOCKED_IN → ACTIVE state machine on all networks.

Other Changes

• Oracle ID validation fix — Now correctly uses 0-based indexing (0–29)
• Oracle unit test fixes — 5 bugs fixed in oracle test suite
• Phase Two RegTest support — RegTest now configured for 3-of-5 oracle consensus
• Phase Two integration tests — New multi-oracle RegTest integration script
• Pending message lifecycle tests — Tests for Phase Two oracle message handling
• Wallet splash image — Updated from RC11 to RC12 branding
• DD Transactions auto-refresh — DigiDollar Transactions tab now refreshes automatically
• Consolidated oracle docs — Single source of truth in DIGIDOLLAR_ORACLE_SETUP.md, old docs moved to docs/

Technical Changes

Known Issues

• Testnet oracle keys (oracles 1–4) use known test values (SHA256 hash-derived). Real operator keys will be swapped before mainnet.
• Mainnet oracle consensus remains disabled (nDigiDollarPhase2Height = INT_MAX)
• startoracle must be re-run after every digibyted restart

Upgrade Notes

RC12 uses testnet13 network (port 12030). This is a new testnet — fresh chain, no data carries over from RC10/RC11.

If Upgrading from RC9 or Earlier:

1. Close your old wallet
2. Delete old testnet data:
   • Windows: Delete %APPDATA%\DigiByte\testnet10\ and testnet11\
   • macOS: Delete ~/Library/Application Support/DigiByte/testnet10/ and testnet11/
   • Linux: Delete ~/.digibyte/testnet10/ and ~/.digibyte/testnet11/
3. Download and install RC12
4. Launch with -testnet flag

What is DigiDollar?

DigiDollar is a USD-pegged stablecoin built natively into DigiByte. It uses an over-collateralized model where users lock DGB to mint DUSD at the current oracle price of DGB.

The world's first truly decentralized stablecoin native on a UTXO blockchain, enabling stable value transactions without centralized control.

DGB becomes the strategic reserve asset (21B max, only 2.23 DGB per person on Earth right now). Everything happens inside DigiByte Core wallet. You never give up control of your private keys. No centralized company, fund or pool. Pure decentralization.

Learn more: https://digibyte.io/digidollar

Current Status

• Phase 2 Multi-Oracle Testing — This release activates 3-of-5 Schnorr threshold oracle consensus on testnet.
• Testnet Only — All DGB and DUSD on testnet have no real value.

Quick Start Guide

Step 1: Download

Download the appropriate file for your platform from the Downloads section below and extract it.

Step 2: Create Config File

Create the config file in your platform's data directory with the following contents:

# DigiByte Configuration
# Global settings (apply to all networks)
testnet=1
server=1
txindex=1

# Testnet-specific settings
[test]
digidollar=1
digidollarstatsindex=1
algo=sha256d
addnode=oracle1.digibyte.io
rpcuser=digibyte
rpcpassword=digibyte123

Windows Setup

Step 1: Download and Install

Download digibyte-9.26.0-rc12-win64-setup.exe and install normally.

Step 2: First Launch (Testnet Mode)

You must launch in testnet mode. Open PowerShell and run:

& "C:\Program Files\DigiByte\digibyte-qt.exe" -testnet

The wallet will start in testnet mode and create the data directory automatically.

Step 3: Create Config File

1. Press Win + R, type %APPDATA%\DigiByte and press Enter
2. Create a new text file named digibyte.conf (remove the .txt extension)
3. Paste the config contents from Step 2 above and save

Step 4: Restart

Close the wallet and launch again from PowerShell:

& "C:\Program Files\DigiByte\digibyte-qt.exe" -testnet

Verify It's Working

• Title bar should say "DigiByte Core - Wallet [testnet13]"
• You should see a DigiDollar tab in the sidebar

Data Directory Reference

• Config: %APPDATA%\DigiByte\digibyte.conf
• Testnet data: %APPDATA%\DigiByte\testnet13\

macOS Setup

Step 1: Download and Extract

Download the .dmg file for your Mac and open it. Drag DigiByte-Qt to your Desktop.

Step 2: First Launch (Testnet Mode)

You must launch in testnet mode. Open Terminal and run:

cd ~/Desktop
./DigiByte-Qt.app/Contents/MacOS/DigiByte-Qt -testnet

If you get a security warning, right-click the app and select "Open", or run:

xattr -cr ~/Desktop/DigiByte-Qt.app

Then try the launch command again.

The wallet will start in testnet mode and create the data directory automatically.

Step 3: Create Config File

In Terminal:

mkdir -p ~/Library/Application\ Support/DigiByte
cat > ~/Library/Application\ Support/DigiByte/digibyte.conf << 'EOF'
# DigiByte Configuration
# Global settings (apply to all networks)
testnet=1
server=1
txindex=1

# Testnet-specific settings
[test]
digidollar=1
digidollarstatsindex=1
algo=sha256d
addnode=oracle1.digibyte.io
rpcuser=digibyte
rpcpassword=digibyte123
EOF

Step 4: Restart

Close the wallet and launch again from Terminal:

cd ~/Desktop
./DigiByte-Qt.app/Contents/MacOS/DigiByte-Qt -testnet

Verify It's Working

• Title bar should say "DigiByte Core - Wallet [testnet13]"
• You should see a DigiDollar tab in the sidebar

Data Directory Reference

• Config: ~/Library/Application Support/DigiByte/digibyte.conf
• Testnet data: ~/Library/Application Support/DigiByte/testnet13/

Ubuntu/Linux Setup

Data Directory

~/.digibyte/

Config file: ~/.digibyte/digibyte.conf

Testnet data stored in: ~/.digibyte/testnet13/

Steps:

1. Open Terminal and create config:

mkdir -p ~/.digibyte
cat > ~/.digibyte/digibyte.conf << 'EOF'
# DigiByte Configuration
# Global settings (apply to all networks)
testnet=1
server=1
txindex=1

# Testnet-specific settings
[test]
digidollar=1
digidollarstatsindex=1
algo=sha256d
addnode=oracle1.digibyte.io
rpcuser=digibyte
rpcpassword=digibyte123
EOF

1. Extract and run:

cd ~/Downloads
tar xzf digibyte-9.26.0-rc12-x86_64-linux-gnu.tar.gz
./digibyte-9.26.0-rc12/bin/digibyte-qt

Verify It's Working

• Title bar should say "DigiByte Core - Wallet [testnet13]"
• You should see a DigiDollar tab in the sidebar

Getting Testnet DGB

Option 1: GUI Console Mining

Mine testnet DGB directly using the GUI console:

1. Go to the Receive tab and create a new address (copy your dgbt1... address)
2. Go to Window > Console
3. Type: generatetoaddress 1 dgbt1qYOURADDRESSHERE
4. Press Enter to mine 1 block
5. Wait for 8 confirmations before spending mined coins (reduced from 100 in testnet)

Option 2: CPU Miner (Recommended for Continuous Mining)

Use cpuminer to mine testnet DGB in the background. Make sure your wallet is running and synced first.

Download cpuminer: https://github.com/pooler/cpuminer

Build from source or download a release for your platform.

Run cpuminer:

Linux/macOS:

./minerd -a sha256d -o http://127.0.0.1:14026 -O digibyte:digibyte123 -t 4 --coinbase-addr=dgbt1qYOURADDRESSHERE

Windows (PowerShell):

.\minerd.exe -a sha256d -o http://127.0.0.1:14026 -O digibyte:digibyte123 -t 4 --coinbase-addr=dgbt1qYOURADDRESSHERE

Parameters explained:

• -a sha256d — Use SHA256d algorithm (matches algo=sha256d in config)
• -o http://127.0.0.1:14026 — RPC endpoint (testnet RPC port)
• -O digibyte:digibyte123 — RPC credentials from your config (user:password)
• -t 4 — Number of CPU threads to use (adjust based on your CPU)
• --coinbase-addr=dgbt1q... — Your testnet receive address

The miner will continuously mine blocks and send rewards to your address.

Testing DigiDollar Features

Once your wallet is synced and you have testnet DGB:

1. View Network Status — The DigiDollar Overview tab shows oracle price and network collateralization
2. Mint DUSD — Lock DGB as collateral to create DigiDollars
3. Send DUSD — Transfer DigiDollars to other testnet addresses
4. Redeem DUSD — Burn DigiDollars to unlock your DGB collateral (full position only)
5. View History — DD Transactions tab shows complete transaction history (now auto-refreshes!)
6. Coin Control — Use manual DD input selection for advanced redemptions
7. Address Book — Save frequently used DD addresses for quick sending
8. Export History — Export DD transactions to CSV for record keeping

Oracle Operator Setup (Phase 2 Test)

Want to run an oracle node for the Phase 2 multi-oracle test? Here's the simple version:

Prerequisites

• DigiByte Core RC12 built from source with curl support
• An assigned oracle ID (0–4 for testnet, contact the maintainer)

Two-Command Setup

# Step 1: Create wallet and generate oracle key (one-time)
digibyte-cli -testnet createwallet "oracle"
digibyte-cli -testnet -rpcwallet=oracle createoraclekey <your_oracle_id>

# Step 2: Start your oracle (after every node restart)
digibyte-cli -testnet -rpcwallet=oracle startoracle <your_oracle_id>

Step 1 generates a Schnorr keypair, stores the private key in your wallet, and returns the public key. Send the X-only public key (32-byte hex) to the maintainer for inclusion in chainparams.cpp.

Step 2 loads the private key from your wallet and starts the oracle price feed thread. Your node will automatically fetch DGB/USD prices from multiple exchanges (minimum 2 sources required) and broadcast signed price messages to the network.

For the complete guide including configuration, security, troubleshooting, and RPC reference, see DIGIDOLLAR_ORACLE_SETUP.md.

Network Information

Fork Schedule (Testnet12)

Emission Schedule (Testnet12)

Commits Since RC11

• Implement createoraclekey wallet RPC for oracle keypair generation
• Implement wallet-based startoracle with automatic key loading
• Add oracle key persistence in descriptor wallets
• Activate Phase Two multi-oracle consensus (3-of-5) on testnet
• Enable oracle nodes 0–4 for testnet Phase Two
• Set Phase Two activation height to block 100 on testnet
• Configure RegTest for Phase Two 3-of-5 oracle consensus
• Add Phase Two compact format (version 0x02) to CreateOracleScript
• Add Phase Two decoding to ExtractOracleBundle
• Add Phase Two bundle creation from pending messages in AddOracleBundleToBlock
• Update ValidateBlockOracleData with phase-aware consensus validation
• Fix BIP9 DigiDollar activation state machine (ALWAYS_ACTIVE + ReadRegTestArgs early return)
• Fix oracle ID validation to use 0-based indexing
• Fix 5 oracle unit test failures
• Add Phase Two multi-oracle RegTest integration script
• Add pending message lifecycle tests for Phase Two
• Update existing oracle tests for Phase Two activation height
• Add oracle wallet key tests and update validation tests
• Add Phase Two bundle lifecycle and test helpers
• Consolidate oracle setup guides into DIGIDOLLAR_ORACLE_SETUP.md
• Add ORACLE_OPERATOR_GUIDE.md for third-party oracle operators
• Comprehensive accuracy pass on DIGIDOLLAR_ORACLE_SETUP.md (ports, data dirs, exchange sources, price ranges, outlier filtering)
• Clarify dual public key formats in createoraclekey docs
• Update wallet splash image from RC11 to RC12
• Add auto-refresh to DD Transactions tab
• Version bump to v9.26.0-rc12

Troubleshooting

"DigiDollar tab not appearing"

• Verify digidollar=1 is under [test] section in config
• Verify testnet=1 is at the top of config (not under any section)
• Restart the wallet after config changes

"Not connecting to network"

• Check your firewall allows port 12030
• Verify addnode=oracle1.digibyte.io is under [test] in config

"Oracle price shows 0 or N/A"

• Wait for sync to complete
• The oracle broadcasts price updates every few minutes
• Check Window > Console: getoracleprice

"Mining not working"

• Ensure algo=sha256d is in your config under [test]
• SHA256d is recommended for fastest CPU mining

"No wallet is loaded" when running oracle commands

• Add -rpcwallet=oracle to your createoraclekey and startoracle commands

"Oracle not configured" from startoracle

• Run createoraclekey first to generate and store the key in your wallet

"Transaction fee too high"

• DigiDollar transactions require 0.1 DGB minimum fee — this is expected
• This ensures reliable network propagation

"Old testnet data causing crashes"

• Delete your testnet10 and testnet11 folders completely (see Upgrade Notes above)
• RC12 uses testnet13 blockchain (new chain, bumped from testnet12 in RC10/RC11)

Downloads

Feedback & Community

Please report issues and feedback to help us prepare for mainnet launch.

• Developer Chat (Gitter): https://app.gitter.im/#/room/#digidollar:gitter.im
• GitHub Issues: https://github.com/DigiByte-Core/digibyte/issues