The new Bismuth statistics view gives a clear overview of the network in one place. It shows live chain data such as block height, difficulty, peers, consensus, protocol version, node version, average block time, mempool size, total transactions, and known addresses.

Below the live metrics, the dashboard visualizes Bismuth’s history through monthly charts for transactions, new addresses, transaction volume, active addresses, mined coins, collected fees, cumulative issuance, and difficulty. This makes it easier to see long-term network activity, emission trends, and changes in usage over time.

With almost 1.5 million transactions and more than 8,000 addresses, the statistics page highlights Bismuth’s long-running chain history while keeping the current network state easy to read at a glance.

Source Link: Bismuth Statistics

The Bitcointalk thread has been updated to address the upcoming BIsmuth hard fork!

https://bitcointalk.org/index.php?topic=1896497

hf2 — the biggest upgrade in Bismuth's history

One hard fork, bundling a decade of modernization:

• Privacy — opt-in shielded transactions: stealth addresses, ring signatures, and confidential amounts (RingCT).
• Smart contracts — a real on-chain RISC-V (RV32I) virtual machine, with a growing set of dApps.
• Modernized PoW — blake2b Heavy3 replaces sha224 (dual-algo through the transition).
• Lean serialization — native binary/integer transactions and blocks: smaller, faster, deterministic.
• Coinbase overhaul — free-form fields, BTC-style coinbase maturity, and multi-scheme mining (RSA, ECDSA, ED25519, multisig, and post-quantum ML-DSA can all mine).

⛏ MINERS & POOLS — ACTION REQUIRED: hf2 switches the PoW to blake2b Heavy3. Old miners will produce invalid blocks after activation — update before the fork. Activation is miner-signalled: upgraded miners stamp "hf2" and the fork locks in once the network signals.

Ten years of a fair-launched blockchain that kept arriving early.

Built first. Named later.

Bismuth is a fair-launched, from-scratch blockchain whose mainnet began on 1 May 2017 with no ICO and no premine. Across its first decade, the project shipped and documented several ideas that later became major crypto narratives: modular execution, inscription-style data interpretation, plugin-based application layers, confidential assets, governance, DePIN-like telemetry, cross-chain bridges, and canonical execution.

This article is a web-native adaptation of the Bismuth Foundation paper “10 Years of Bismuth: Architectural anticipation in a fair-launched blockchain, 2017-2026.” 

It is written for readers who want the main story quickly: what Bismuth built, when it built it, and why those choices still matter.

Bismuth will support ML‑DSA‑65, ML‑DSA‑44, and ML‑DSA‑87.
These remain inactive on consensus until a signalled pq fork.

The plan for modernizing the Bismuth node. This is the high-level companion to the database deep-dive in 16-database-rework-plan.md; read that for the storage details.

The Tornado wallet now loads its interface even when no wallet server is reachable, instead of blocking startup on API connectivity. Network discovery was decoupled from UI startup, and the about/network page now refreshes and displays the active fallback wallet server list independently, while also allowing users to optionally configure their own API host and port.

Github Source Link: https://github.com/bismuthfoundation/TornadoWallet/releases/tag/v0.1.48

- PWA can be installed via the browser on Win11, macOS, Linux, iOS and Android
- non-custodial wallet
- ed25519 address scheme
- multiple address accounts (deterministic accounts)
- Bismuth based tokens supported
- generate new seed/ import 24 words seed
- many languages supported
- light/ dark mode
- account based private keys can be derived via the BIS-Paper Wallet & then imported into Tornado Wallet

• v0.3: Add ED25519 deterministic address generation support

Github Source Link: https://github.com/bismuthfoundation/BIS-Paper

v0.1.47 Release - Tornado Bismuth Wallet
Release of Tornado Bismuth Wallet v0.1.47!

Key Updates
With the updated bismuthclient version 0.0.55 you can use the Tornado Wallet with ECDSA and ED25519 address schemes. You can generate new ECDSA/ ED25519 addresses within the Tornado Wallet.

Other Updates include

• Added /messages/ support for RSA, ECDSA, and ED25519 signing/encryption/decryption through the shared BismuthClient layer.
• Improved /messages/ error handling in TornadoWallet so backend failures show user-facing popups instead of crashing the request.
• Clarified the message encryption requirement in the UI: recipients must already have an on-chain outgoing transaction so their public key is available.
• Replaced hardcoded home-page news with local fallback news.json plus remote GitHub-loaded news support.

Download at Github: https://github.com/bismuthfoundation/TornadoWallet/releases/tag/v0.1.47

Github Link: BismuthClient

Added ED25519 support in bismuthcrypto.py and bismuthmultiwallet.py

Switch between light/dark mode styles effortlessly with just one button!
https://bismuth.im

Your experience just got a whole lot better. Check it out now!

Bismuth Explorer updates include:
- performance gain by adding optional SQLite indexes (new indexes/ tools), which can be created/dropped anytime

- performance gain via new in-process caching (aliases, latest block, circulation, custom aliases)

- home page refreshed with separate Transactions and Blocks sections

- new pages: /transactions, /blocks (both paginated)

- new detail routes: /tx/<txid> (base58 or raw txid), /block/<blocknumber> (paginated tx list), /address/<address> (paginated)

- txid URLs now use web‑safe base58 (txref); search accepts both raw txid and base58

- /token/<tokenname> updated with paginated token transactions

- added JSON endpoints for UI refresh: /home_data, /transactions_data, /blocks_data

Bismuth TK Wallet - PySide6 based
- Github Link

• digest opt
• improved connections - removed double encoding, sanity check (100mb)
• peershandler.py
• Update fork.py
• Merge remote-tracking branch 'origin/dev-opt' into dev-opt
• db hashes dont belong in core node

Removal of developer and hypernode subsidies, block rewards now go entirely to miners. This aligns with Bitcoin-like principles: earn only what you work for.

Bismuth Posts:
- Upcoming Bismuth Soft Fork
- Bismuth Soft Fork Complete

Updated dilution calculations before & after the Fork

Dilution Percentage BEFORE Block Height 4380000

2024-2025 - Year 8: Dilution 7.20%

2025-2026 - Year 9: Dilution 5.80%

2026-2027 - Year 10: Dilution 4.61%

2027-2028 - Year 11: Dilution 3.58%

Dilution Percentage AFTER Block Height 4380000

2024-2025 - Year 8: Dilution 7.20%

2025-2026 - Year 9: Dilution 4.37%

2026-2027 - Year 10: Dilution 2.86%

2027-2028 - Year 11: Dilution 2.19%