smartsats

Network status · Pre-launch

A new blockchain.Familiar Bitcoin logic.Independent infrastructure.

Created by SmartLedger Technology, SmartSats brings the scalable transaction and scripting model familiar to BSV developers to an independently operated blockchain network.

BSV-compatible · Independently operated · Built by SmartLedger

Pre-launch. SmartSats is in network testing ahead of its official launch. Its genesis is final; no restart is planned, and any change would be announced in advance. SmartSats coins currently have no market price.

Height 0

Genesis

Fixed anchor

Carrying
High Government Debt Is Adding Fuel to the Global Bond-Market Selloff
Genesis hash
1c7c39b927b582cd456e64c9883f467d1e373e85c98c9598975d01b3e1c9117b

Open block 0 in the explorer

Network measurements

Live network

From genesis to the latest block, read from the SmartSats explorer as you watch. Every block links to its full record there: transactions, header data and how it was verified.

  1. 01c7c39b927b582cd…fixed anchor

The newest blocks appear here when your browser can read the explorer. They are always in the explorer itself.

A new chain with familiar logic

SmartSats is an independently operated blockchain created by the SmartLedger Technology team. Its architecture deliberately preserves the transaction model, script behavior and application patterns familiar to developers working with BSV.

So software can be built to target either network without redesigning the application.

  • Familiar transaction model.
  • Independent network.
  • SmartLedger-operated infrastructure.

How SmartSats is built

Transactions and scriptThe same transaction and script rules as BSV.

Developers reuse what they already know: transaction construction, locking and unlocking scripts, UTXO patterns and data protocols.

An application says which chain it is using. The addresses differ, so the choice is always explicit.

Block signingEvery block from block 1 is cryptographically signed by SmartLedger.

That gives the network an independently verifiable record of block production, on top of the usual cryptographic link from each block to the one before.

The signature is carried in the block's coinbase transaction, in an OP_FALSE OP_RETURN "SSIG" output. What is signed covers the block header with the signatures stripped, plus the genesis hash. One of two keys signs: an online key, or its offline backup.

Every 100 blocks, a checkpoint of the chain is anchored on BSV mainnet by NotaryHash, so its history is provable against BSV's proof of work.

ValidationFrom launch, partners run full validating nodes.

A validating node checks every block's signature. Partner signing is planned for a later stage.

Node softwarenewsatoshi, SmartLedger's independently developed node.

A from-scratch implementation, checked case by case against the reference bitcoin-sv node.

Compatibility testing13 of 13 node modules verified against the reference bitcoin-sv node.

1,540 of 1,563 surface items implemented. Both measured 2026-10-06.

Addresses start with m, n or 2, and BSV wallets refuse them, deliberately.

Block cadenceAbout one block a minute.

The explorer marks the chain as overdue when two minutes pass without one.

Build once. Target either chain.

Developers who know BSV do not have to learn a new blockchain architecture. The application keeps one transaction and script model; which network it runs on is a choice underneath.

Make switching chains a configuration choice, not an application rewrite.

An application names the chain it is using. Addresses and key trees differ between the two, so the choice is always explicit.

Designed for scale

SmartSats is being engineered around these principles. They are design aims, not measurements; the measurements are at the top of this page.

  • Large-scale transaction processing
  • UTXO-based architecture
  • Programmable Bitcoin Script
  • On-chain data and application protocols
  • Deterministic transaction verification
  • Simple proofs and auditability
  • Compatibility with BSV-style software
  • Independent node development
  • Observable network behavior

The goal is not another incompatible ecosystem. It is to extend a proven transaction model into an independently operated network that developers can understand immediately.

Anatomy of a SmartSats block

What every SmartSats block carries.

Block
height
Previous hash
the hash of the block before
Time
when it was made
Merkle root
one hash committing to every transaction
Transactions
a count, then the transactions themselves
Signature
in the coinbase, in an OP_FALSE OP_RETURN "SSIG" output
  • Previous hash chains each block to the one before it, back to genesis.
  • Merkle root commits the header to every transaction in the block.
  • SmartLedger signature covers the header with the signatures stripped plus the genesis hash, which binds it to this network: a signature made for this chain is no use on another.
  • Coinbase is the block's first transaction. It carries the SmartLedger signature as data, where every validating node can check it.

For developers

If you already understand Bitcoin transactions, UTXOs, Script, transaction ids, Merkle proofs and BSV application development, SmartSats should feel familiar. That is intentional.

  • One transaction model.
  • Multiple networks.
  • Your application chooses where to run.