DigiByte Core v9.26.1-pre2 Release Notes

v9.26.1-pre2 is a one-time DigiDollar mainnet-oracle rehearsal build.

It is not a normal user release. It is not the final DigiDollar mainnet launch. It is a temporary, isolated test build for assigned oracle operators and release coordinators to prove the final mainnet oracle configuration, compressed mainnet activation path, MuSig2 oracle bundle activation, and DigiDollar wallet/RPC behavior before the real mainnet release.

Think of this build as halfway between mainnet and testnet:

• it keeps mainnet identity where oracle keys need it: mainnet genesis, mainnet message magic, mainnet address formats, and the final mainnet oracle keys;
• it isolates itself from public DigiByte mainnet by using PRE-only ports, no seed discovery, no fixed seeds, and a separate data directory;
• it compresses historical DigiByte fork points and DigiDollar activation timing so the full activation path can be tested quickly from a fresh chain.

Development branch: feature/digidollar-v1

Release tag: v9.26.1-pre2 (PRE/oracle rehearsal only)

v9.26.1-pre2 replaces the first PRE rehearsal tag for the current oracle test release. It keeps the same isolated mainnet-PRE network contract while carrying the latest DigiDollar mining/template fixes and updated wallet branding for this second PRE build.

Mining fix summary:

• Non-oracle miners can include DigiDollar oracle price bundles when they use the upgraded DigiDollar-aware block-template path. They do not need oracle private keys.
• Legacy miners can still mine valid normal DGB blocks. They just will not receive oracle-priced DigiDollar mint/redeem work unless they opt in to the new GBT rule.
• CPU mining was updated so patched cpuminer can request DigiDollar-aware templates with --digidollar and preserve the oracle commitment in the coinbase.
• Pool/miner software should request getblocktemplate with {"rules":["segwit","digidollar-oracle"]} and copy default_oracle_commitment exactly when Core returns it.

Required PRE Configuration

Run this build with a fresh PRE data directory. Put digibyte.conf in that fresh data directory, not in an existing normal mainnet ~/.digibyte directory. The node will still report chain=main, but this build stores its chain data under the mainnet-pre network subdirectory.

Example operator digibyte.conf:

# DigiByte Core v9.26.1-pre2 isolated mainnet-oracle rehearsal
# Use this only with a fresh PRE data directory. Do not use normal ~/.digibyte.

server=1
listen=1
txindex=1
digidollar=1

# Mainnet-PRE network ports
port=12046
rpcport=14046

# Join the coordinated PRE network through the bootstrap node.
addnode=digibyte.io:12046

# Keep this PRE build isolated from public DigiByte mainnet peer discovery.
dnsseed=0
fixedseeds=0
discover=0
listenonion=0
onion=0
upnp=0
natpmp=0

# Keep RPC local unless you have a separate trusted tunnel/firewall.
rpcbind=127.0.0.1
rpcallowip=127.0.0.1

Network/firewall requirements:

• Open inbound TCP 12046 for the PRE P2P network if this node should accept peer/oracle connections.
• Do not open or use public mainnet P2P port 12024 for this rehearsal.
• Do not expose RPC port 14046 to the public internet.
• Use addnode=digibyte.io:12046; the PRE bootstrap/oracle node must also listen on TCP 12046.

Read This First

Do not run v9.26.1-pre2 as a normal wallet release.

This build is for a controlled oracle rehearsal. It intentionally changes mainnet startup behavior in order to create a side-mainnet test chain that uses real mainnet oracle keys but does not join public DigiByte mainnet.

Normal users should not install this build for everyday funds, merchant use, mining, exchange use, or public mainnet operation.

Oracle operators should only run it with the coordinated PRE instructions and a fresh PRE data directory. Do not point it at an existing ~/.digibyte mainnet directory.

After this PRE rehearsal is complete, the PRE isolation/fast-activation commit is expected to be reverted before preparing the final mainnet launch build.

Purpose

The goal of v9.26.1-pre2 is to test the final mainnet DigiDollar oracle setup under mainnet-like conditions without touching public mainnet.

This lets us verify:

• the final 35-slot mainnet oracle roster;
• 7-of-35 MuSig2 oracle quorum configuration;
• DigiDollar, oracle, and MuSig2 activation at the same height;
• mainnet address/key handling for oracle wallets;
• BIP9 activation flow with real mined blocks;
• DigiDollar wallet and RPC behavior after activation;
• peer isolation from public mainnet.

The build exists because public testnet does not perfectly reproduce mainnet conditions. This PRE chain keeps the important mainnet identity pieces while using testnet-style fast activation timing.

Mainnet-PRE Network Details

The PRE build deliberately keeps the mainnet genesis and magic bytes so oracle operators test the same mainnet key context. Isolation comes from the PRE data directory, PRE ports, disabled peer discovery, and the public-mainnet-port guard.

Fast Activation Logic

The PRE chain compresses historical DigiByte rule changes so a fresh chain reaches the modern DigiDollar test surface quickly.

Compressed PRE fork schedule:

DigiDollar uses BIP9 bit 23 with a 100-block window and 70-block threshold. The expected PRE flow is:

This is intentionally fast. It is designed to prove activation behavior, not to reproduce years of mainnet elapsed time.

What Changed From RC46

• Mainnet is temporarily configured as mainnet-pre for this rehearsal.
• Mainnet genesis, message magic, address formats, and oracle keys stay mainnet.
• PRE P2P/RPC ports are 12046 / 14046.
• DNS seeds and fixed seeds are disabled so the node does not discover public mainnet peers.
• Public mainnet P2P port 12024 is guarded against accidental outbound use.
• Historical DigiByte fork heights are compressed so a fresh chain can reach the current rule set before DigiDollar activation.
• DigiDollar BIP9 uses a 100-block window, 70-block threshold, and minimum activation height 600.
• DigiDollar, oracle runtime, and MuSig2 oracle bundle format all activate together at height 600.
• The final 35-slot mainnet oracle roster is configured on PRE port 12046.
• getblocktemplate now has a DigiDollar-aware path using the digidollar-oracle rule so non-oracle miners and pools can safely receive oracle commitments and price-dependent DigiDollar mint/redeem transactions.
• Legacy getblocktemplate callers remain safe: they do not receive default_oracle_commitment and they do not receive oracle-priced DigiDollar mint/redeem work they cannot mine correctly.
• Block assembly now checks the same completed MuSig2 session source used to stamp the coinbase oracle bundle, so a miner node can include valid price bundles without being one of the signing oracle wallets.
• Stale oracle-bearing GBT templates are rebuilt instead of being reused after the oracle price ages out.
• The PRE CPU-mining harness can pass --digidollar to patched cpuminer, allowing CPU miners to preserve default_oracle_commitment while mining the normal DigiByte proof-of-work algos.

DigiDollar Mining Fixes In Pre2

The first PRE rehearsal proved oracle signing could complete, but mining needed a clearer handoff between Core, CPU miners, and pool software.

The core issue was simple: DigiDollar mint and redeem transactions need a fresh MuSig2 oracle price bundle in the block coinbase. A miner that builds a block without that bundle can still mine a valid normal DGB block, but it cannot correctly confirm price-dependent DigiDollar mint/redeem transactions.

v9.26.1-pre2 fixes that flow without requiring every miner to become an oracle.

Mining now has two explicit paths:

When Core returns default_oracle_commitment, miner or pool software must copy that script exactly into the coinbase as a zero-value output. Do not invent an oracle commitment if Core does not provide one.

What was fixed:

• Non-oracle miners can mine blocks with oracle price bundles if their upgraded node has the completed MuSig2 bundle at template time.
• getblocktemplate advertises DigiDollar-aware work with !digidollar-oracle in rules and exposes the exact default_oracle_commitment script to preserve.
• GBT caches separate legacy templates from DigiDollar-aware templates so legacy miners do not accidentally receive work they cannot assemble correctly.
• GBT rebuilds stale oracle-bearing templates after the bundle freshness window moves forward, preventing stale price commitments from being reused.
• Block assembly removes price-dependent mint/redeem transactions when no fresh oracle bundle is available instead of creating an invalid block.
• Price-independent DigiDollar transfers can still flow without an oracle price bundle.
• Patched cpuminer can be run with --digidollar so solo CPU mining requests the DigiDollar-aware GBT rule and preserves the returned oracle commitment.

Pool and miner software requirements:

• Use {"rules":["segwit","digidollar-oracle"]} for DigiDollar-aware GBT.
• Preserve default_witness_commitment and default_oracle_commitment as zero-value coinbase outputs when they are present.
• Do not include DigiDollar mint/redeem transactions from outside the returned template when Core did not provide default_oracle_commitment.
• Downstream ASIC/GPU workers do not need oracle private keys. The pool server or solo miner builds the correct coinbase from Core's template.
• See DIGIDOLLAR_MINING_INTEGRATION_GUIDE.md for pool, Stratum, cpuminer, DigiHashV2, and node-stratum-pool integration rules, including public reference-code links to:
  • https://github.com/JaredTate/cpuminer-multi
  • https://github.com/JaredTate/node-stratum-pool
  • https://github.com/JaredTate/digihashv2

This keeps fork risk low: old miners continue producing valid normal blocks, while upgraded DigiDollar-aware miners and pools have a deterministic path to mine mints/redeems with the correct oracle bundle.

What Did Not Change

• The real mainnet genesis hash did not change.
• The real mainnet message magic did not change.
• Mainnet address prefixes did not change.
• The DigiDollar economic rules are not redesigned in this PRE build.
• Oracle quorum remains 7-of-35.
• Testnet26 remains its own network and is not reset by this PRE release.
• Regtest activation behavior is not changed by this PRE release.
• This PRE release does not activate DigiDollar on public mainnet.

Final Mainnet-PRE Oracle Roster

All oracle endpoints use PRE port 12046 for this rehearsal. Public mainnet oracle operation will use the final launch instructions after PRE is reverted and the formal mainnet build is prepared.

Operator Guidance

This release is only for assigned oracle operators and coordinated PRE testers.

Minimum rules:

• Use a fresh PRE data directory.
• Do not reuse normal mainnet ~/.digibyte data.
• Do not copy normal mainnet peers.dat.
• Do not add or connect to public mainnet peers on port 12024.
• Open/use PRE P2P port 12046.
• Confirm getblockchaininfo reports chain=main while the data directory path is mainnet-pre.
• Confirm getdigidollardeploymentinfo reports:
  • min_activation_height = 600
  • oracle_activation_height = 600
  • musig2_format_activation_height = 600
  • oracle_pubkey_count = 35
  • oracle_consensus_required = 7
  • oracle_total_slots = 35
• Start oracle runtime only after the PRE chain reaches DigiDollar/oracle activation.

This PRE chain is allowed to use mainnet oracle keys because it stays isolated from public mainnet.

Validation Status

Known local validation for the PRE code line:

Before publishing binaries, rerun and record:

make -j$(nproc)
./src/test/test_digibyte --show_progress
test/functional/test_runner.py --jobs=8
./src/test/fuzz/test_runner.py <fuzz-bin-dir> -l DEBUG <target-list>
./test_oracle_mainnet.sh

Revert Plan

The PRE changes should stay isolated in an easy-to-revert commit or small commit stack.

After the oracle rehearsal is complete:

1. Save the PRE activation/oracle test results.
2. Shut down PRE nodes.
3. Preserve logs and oracle validation artifacts.
4. Revert the PRE isolation/fast-activation commit.
5. Prepare the final mainnet launch build with normal mainnet ports, normal mainnet peer discovery, and the chosen final activation parameters.

Do not ship this PRE configuration as the final public mainnet release.