ShieldBit
A new chapter in
peer-to-peer money.
Your node. Your wallet. Your work. Join a proof-of-work network with ML-DSA-65 spending signatures and rules you can verify.
Built block by block. Open to miners, node operators and reviewers.
Why ShieldBit
Built for the Post-Quantum Era
Ordinary payments, explicit ownership rules, and post-quantum spending signatures. Mainnet is producing blocks. Independent human security review and broader network testing remain outstanding.
ML-DSA-65 Signatures
NIST FIPS 204 spending signatures designed to resist known classical and quantum attacks. Security still depends on implementation, review, and protecting wallet keys.
Proof-of-Work Mining
Standalone double-SHA256 proof of work and bounded Bitcoin auxiliary proofs. Live Bitcoin pool and ASIC integration still requires testing.
Ordinary Payments
Send SBT directly to another wallet through signed on-chain transfers. Ownership, amounts, fees, and mining-reward maturity are checked before funds move.
Fork Recovery
Validated accumulated-work selection and atomic UTXO rollback keep ordinary payments consistent through chain reorganizations. Equal-work forks retain the active tip.
Wallet Protection
Encrypted wallet keys, checked recovery against the original address, and owner-only local node submission. Payments are transparent, not anonymous.
Validation Safeguards
Bounded decoding, amount checks, coinbase-height commitments, median-time-past rules, and 64-bit timestamps. Tests and review provide evidence, not immunity from bugs.
Under the Hood
Pure Python Reference Implementation
A Python reference implementation with explicit network-bound signatures and full 32-byte address commitments. Review the assumptions, not just the claims.
-
ML-DSA-65 (NIST FIPS 204) Post-quantum digital signatures via the
cryptographylibrary (≥50.0.2) -
SHA3-256 + double-SHA256 SHA3 for all internal hashing, double-SHA256 for standalone proof of work
-
Bech32m Addresses (sb1…) BIP-350 encoding with custom HRP, implemented from scratch
-
Shamir Secret Sharing k-of-n recovery over GF(2^8) — built-in key backup without third parties
-
asyncio P2P Node Full compact block relay, GCS filters, and peer discovery
-
AES-256-GCM Keystore PBKDF2-encrypted wallet keys, never stored in plaintext
Release: c5cb5568c549
Signing format: v2
Address commitment: tagged SHA3-256, 32 bytes
# Monetary rules
Initial subsidy: 40 SBT
Halving: every 250,000 blocks
Reward maturity: 100 blocks
# Mining compatibility
Single-thread CPU reference miner
No turnkey GPU or Stratum/ASIC miner
Bitcoin pool interoperability not yet proven
Join the Network
Your node. Your wallet. Your work.
Mainnet is live and early contributors are welcome. You need your own computer and payout address, not access to our cloud account.
Public mining is open. The founder-signed Linux x86-64 release is available below, including for Ubuntu 24.04 on Windows WSL2. Mainnet launch authorization: true. Do not run unofficial miners or send anyone a seed, private key or wallet password.
Download signed Linux / WSL package · Release checksum · Download and inspect installer · Review native source · Source checksum. No wallets, private keys, cloud configs or private Git history are included.
The current signed package requires x86-64, glibc 2.34 or newer and CPython 3.12 with venv/pip. Ubuntu 24.04 and Windows WSL2 Ubuntu 24.04 have been tested; other distribution recipes below have not been end-to-end tested. Be the first to test mining on your distribution and report your results. Include your distribution/version, architecture, Python version and sanitized results; never send wallet files, passwords or private keys. Start with 4 GB RAM, 10 GB free disk and reliable internet as startup reserves, not full-load guarantees. Use administrator access only for OS prerequisites. GPU mining is not included.
Ubuntu 24.04
sudo apt-get update sudo apt-get install python3.12-venv python3.12 --version uname -m getconf GNU_LIBC_VERSION
Expect Python 3.12, x86_64 and glibc 2.34 or newer. Continue with the shared steps below. Debian's default Python may not be 3.12: use a separately managed, trusted CPython 3.12 with venv/pip, or an Ubuntu 24.04 VM. Do not replace Debian's system Python or assume its repositories contain python3.12.
Fedora with Python 3.12 available
dnf info python3.12 sudo dnf install python3.12 python3.12 --version python3.12 -m ensurepip --version uname -m getconf GNU_LIBC_VERSION
Use the versioned interpreter, not Fedora's newer default Python. Confirm venv/pip support before proceeding. If the package is unavailable in your enabled official repositories, stop and use the tested Ubuntu setup. Fedora package reference.
RHEL 9.4+ / compatible CentOS Stream
dnf info python3.12 python3.12-pip sudo dnf install python3.12 python3.12-pip python3.12 --version uname -m getconf GNU_LIBC_VERSION
Proceed only if these packages are available in your enabled official repositories and venv/pip works. CentOS Stream must meet the same runtime requirements; older CentOS 7/8 cannot use this bundle. No subscription purchase or repository changes are required by ShieldBit. Red Hat Python reference.
Windows 11 / WSL2 Ubuntu 24.04
In PowerShell, install Ubuntu only if it is not already installed:
wsl --install -d Ubuntu-24.04 wsl --list --verbose
Confirm Ubuntu-24.04 uses version 2, open it and run:
sudo apt-get update sudo apt-get install python3.12-venv python3.12 --version
Download the two official files above. Move them from /mnt/c/Users/YOUR_WINDOWS_USERNAME/Downloads into your Linux home folder, then run the shared steps below inside Ubuntu. Keep node state on the Linux filesystem. This is a WSL miner, not a native Windows executable.
Other Linux distributions
uname -m getconf GNU_LIBC_VERSION python3.12 --version python3.12 -m ensurepip --version
CPU mining is not restricted to one Linux brand, but this bundle is not universal. Proceed only on x86_64 with glibc 2.34+ and CPython 3.12 supporting venv/pip. ARM/Raspberry Pi, Alpine/musl and older glibc need separately built and verified artifacts; do not force-install these wheels. Use Ubuntu 24.04 if your platform does not qualify.
Bitcoin ASIC / pool integration
Not yet a plug-and-play mining option. SHA-256d work and AuxPoW validation exist, but TCP 9333 is a node P2P port, not a Stratum endpoint. Do not point an ASIC at either seed or expose node RPC publicly.
Both sides need to participate. A ShieldBit Stratum V1 adapter exists in development; the current public source snapshot contains the deployed core and does not yet include that adapter. It has not been qualified with a live Bitcoin pool or physical ASIC. The miner operator provides compatible hardware and firmware and tests it with a consenting pool operator. Existing Bitcoin pools do not automatically support SBT.
- Identify the hardware.
Record the SHA-256 ASIC model, firmware, supported Stratum version and a consenting pool/operator. Keep credentials private.
- Review the pool adapter.
The development preview translates ShieldBit work into Stratum V1 jobs, validates shares, submits candidates and constructs AuxPoW proofs. It has fixed difficulty, no automatic SBT payment and no Bitcoin miner payout accounting; independent review and capacity tests remain necessary.
- Validate before production.
Test real hardware on an isolated test network, including rejected shares, job changes, recovery and canonical block propagation. Bitcoin Core regtest checks do not establish live ASIC compatibility.
- Configure only a qualified pool.
No qualified public ShieldBit Stratum endpoint or device recipe is available. Do not connect an ASIC yet. Pool operators can review the public mining support and adapter release steps; miners should use only a later independently tested endpoint.
- Get the official release and verify it.
No GitHub account or cloud credentials are needed. Download both the package and installer to your Linux home folder, inspect the installer before running it, then execute the following with CPython 3.12. Do not use sudo. The installer verifies the archive, pinned wheels, ML-DSA production signature and installed-source fingerprints; it does not create a wallet or start mining.
cd "$HOME" python3.12 install_public_release.py \ --archive shieldbit-linux-x86_64-c5cb556.tar.gz \ --sha256 1477b0ff77406f023bb40575974f5cd6cf6b059a666510be93c3baa0e4fb2a20 PY="$HOME/.shieldbit-release/c5cb556/venv/bin/python"
Set PY in each new terminal. The software-signature check reports mainnet_launch_authorized: false because its scope is software authentication only; the separate founder launch approval and final installer receipt report true. Private repository collaboration still requires an invitation.
- Create your own encrypted wallet and test its backup.
After verification, use the release's Python environment. Keep your wallet offline where practical and back up both wallet.json and wallet.salt in encrypted storage. Record your complete public payout address beginning sb11r. Never use the founder's payout address for your mining.
"$PY" -I -m shieldbit.cli.main --network main --data-dir "$HOME/.shieldbit-wallet" wallet create
- Start a node and check the mainnet identity.
Connect outward to the two official P2P seeds on TCP 9333. You do not need inbound ports for initial outbound participation. Keep RPC local; a publicly reachable node needs a separately secured inbound P2P rule. Use a fresh mainnet state directory.
"$PY" -I -m shieldbit.cli.main --network main --data-dir "$HOME/.shieldbit-mainnet" node start \ --bind 127.0.0.1 --port 9333 --prune 288 \ --peer 132.145.170.224:9333 --peer 129.80.6.228:9333
In a second terminal, verify network
main, connected peers and genesis0000094862883b548e8e5262f7b7fabd35188d25ddae0c82438cd031e8b3bdbd."$PY" -I -m shieldbit.cli.main --network main --data-dir "$HOME/.shieldbit-mainnet" node status
- Mine to your own public address.
Leave the node running. Replace YOUR_OWN_PUBLIC_ADDRESS with your wallet's address; set PY to the verified release environment in each terminal. The current miner supports one CPU thread, not a GPU or automatic ASIC connection.
"$PY" -I -m shieldbit.cli.main --network main --data-dir "$HOME/.shieldbit-mainnet" mine \ --threads 1 --address YOUR_OWN_PUBLIC_ADDRESS
Stop with Ctrl+C. A locally accepted block must propagate and remain canonical. Subsidy is currently 40 SBT plus fees; reward outputs mature after 100 blocks. Ten minutes is the difficulty target, not a promise for every block or a fixed wall-clock maturity period.
Bitcoin miners and pool operators: standalone SHA-256 and AuxPoW validation exist, but a generic Bitcoin ASIC cannot simply be pointed at this Python miner. Help validate a pool/Stratum adapter and real ASIC interoperability before committing production hash power. Discuss integration.
Roadmap
Where We Are
Honest, transparent progress tracking — no vaporware.
Ordinary UTXO transfers, ML-DSA-65 signing, fork recovery, encrypted wallets, compact filters and a live P2P node. Independent review remains outstanding.
The deployed merged source passed 487 local tests with two platform-specific skips. Fresh installed releases passed seven authorization and six deployment checks. Tests are not an independent audit.
shieldbit.org registered on Cloudflare. Email routing active. CDN configured.
Whitepaper 1.3: deployed 20M supply ceiling, 40 SBT subsidy, 250,000-block halvings, 32-byte addresses, network-bound signatures and launch-distribution disclosures.
Founder-signed merged release installed on two OCI nodes. Matching genesis/chain state, clean restarts, integrity checks and backups verified. Mining on Windows/WSL is propagating to both nodes.
Public P2P access and founder-signed sanitized downloads are available. New miners, independent node operators and reviewers are welcome.
Founder-authorized mainnet is producing blocks. Independent human review, sustained hostile WAN load, physical power/media-loss and live pool/ASIC validation remain unproven. No established exchange price is claimed.
Open Source
Help Build the First Chapter.
Community participation starts with running nodes, verifying blocks and sharing reproducible results. ShieldBit is Apache-2.0 licensed. Reviewed source snapshots and founder-signed releases are public; private development access remains by invitation.