🤖[ANN][BIS]Bismuth is Back in 2026

[bit-signal]

This Bismuth Explorer has received an update. You can see the live application at Bismuth.im

Key Changes:
- 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

Github Repo Link:
Bismuth Explorer

[bit-signal]

This Tornado Bismuth Wallet has been updated to version 0.1.47. You can download the app at Github!

Key Changes:
- Generate RSA, ECDSA or ED25519 based addresses from within the app
- 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.


Github Repo Link:
https://github.com/bismuthfoundation/TornadoWallet/releases/tag/v0.1.47

[bit-signal]

This BIS-Paper Wallet has been updated to version 0.3. Download link is at Github!

Key Changes:
- v0.3: Add ED25519 deterministic address generation support

This lets you import private keys from the BIS-Paper Wallet into Tornado Wallet if needed.


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

[bit-signal]

Tornado Bismuth Wallet has been updated to version 0.1.48. Download link is at Github!

Key Changes:
- the wallet now loads its interface even when no wallet server is reachable, instead of blocking startup on API connectivity.
- users can optionally configure their own API host and port
- added a one-click Copy Address icon for faster address copying
- updated the BIS token API integration with an active, working API endpoint
- QR codes for receive addresses are now generated locally, removing the dependency on an external service

Github Repo Link:
https://github.com/bismuthfoundation/TornadoWallet/releases

[bit-signal]

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

Guiding Principles:
1. Consensus does not change. The same blocks must produce the same hashes and validate identically. The exact signing-buffer and block-hash byte forms are frozen in bismuth_serialize.py and characterization-locked; everything else (storage, transport, APIs) is free to change behind that boundary.

2. Replay-verified. Every storage/representation change is validated by re-hashing the chain end-to-end through the frozen boundary (replay_verify.py, tests/test_replay.py) and must produce byte-identical block hashes. No silent drift.

3. Incremental and reversible. Small, test-gated changes — not a big abstract rewrite. New behaviour is opt-in (config-flagged, default off) until validated on regnet and by independent replay. Old peers keep working.

4. Modernize at the edges, freeze the core. New, clean modules at the seams; surgical edits to the legacy monoliths; the consensus core is touched only through the frozen layer.

Github Repo Link:
https://github.com/hclivess/Bismuth/blob/main/doc/17-roadmap.md

[bit-signal]

Bismuth will add support for post‑quantum crypto schemes.

- ML‑DSA‑65
- ML‑DSA‑44
- ML‑DSA‑87

These crypto schemes remain inactive on consensus until a signalled pq fork.

Source Link:
https://github.com/hclivess/Bismuth/blob/main/doc/09-crypto-wallets-keys.md#addresses--keys

[bit-signal]

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.

Core thesis: Bismuth was not merely an old proof-of-work chain. It was a long-running architectural testbed for ideas the wider industry later rediscovered, renamed, and popularized.

Source: https://bismuth.cz/10-years-of-bismuth.html

[HCLivess]

1. Consensus does not change. The same blocks must produce the same hashes and validate identically. The exact signing-buffer and block-hash byte forms are frozen in bismuth_serialize.py and characterization-locked; everything else (storage, transport, APIs) is free to change behind that boundary.

We're gonna nuke consensus - but make a more robust one, leaving behind a lot of technical debt from the early days. A lot of big abstract changes in the end, but best to have done it in one go and fine tune while the chain is underused, if people decide to use it again.

[chrysophylax]

1. Consensus does not change. The same blocks must produce the same hashes and validate identically. The exact signing-buffer and block-hash byte forms are frozen in bismuth_serialize.py and characterization-locked; everything else (storage, transport, APIs) is free to change behind that boundary.

We're gonna nuke consensus - but make a more robust one, leaving behind a lot of technical debt from the early days. A lot of big abstract changes in the end, but best to have done it in one go and fine tune while the chain is underused, if people decide to use it again.

Hmmm ...

Any details at all?

#crysx #cwi

[HCLivess]

- API interface
- Complete rework of serialization
- BTC/ETH RPC calls
- RISC-V smart contracts before Ethereum - no more relying on middlemen and their infra
- Fully decentralized DEXes across all bridges
- A set of fun smart contracts
- Peer-to-peer bootstrap syncing

Bismuth is moving and it is moving fast
Make sure to read 10 years of Bismuth and the new white paper

[chrysophylax]

- API interface
- Complete rework of serialization
- BTC/ETH RPC calls
- RISC-V smart contracts before Ethereum - no more relying on middlemen and their infra
- Fully decentralized DEXes across all bridges
- A set of fun smart contracts
- Peer-to-peer bootstrap syncing

Bismuth is moving and it is moving fast
Make sure to read 10 years of Bismuth and the new white paper

I watched ...

Since the Very Beginning when You guys were just talking about a Python Based Coin.



#crysx #cwi

[HCLivess]

Yes because Python is the most accessible programming language and the most popular one

[bit-signal]

Bismuth: A Peer-to-Peer Settlement Layer
for Programmable Value

Github Link: https://github.com/hclivess/bismuth/blob/main/doc/wp/bismuth.pdf