Hybrid signatures
ML-DSA-65 ‖ Falcon-1024 — two independent lattice schemes, so a break in one does not sink an account.
Bloch-SIS-PoW · the ownerless commons
Why the ownerless Bloch protocol matters.
A post-quantum, permissionless, pure-proof-of-work base that no company owns, operates, schedules, or can revoke — built on lattice signatures today, not a classical chain waiting to be broken. This is the commons, not a product pitch.
An independent perspective, by Postern Labs. The Bloch-SIS-PoW protocol is ownerless and is not a Postern Labs product; Postern Labs neither owns, operates, nor speaks for it. Postern builds on Bloch and writes about it. This is one independent party's view of the commons — there is no official Bloch site, node, or explorer, and this page does not claim to be one. See Postern ≠ Bloch and the blochprotocol.com statement.
Post-quantum from the ground up
Lattices today, not a bolt-on tomorrow.
Shor's algorithm breaks classical ECDSA and RSA — the signatures securing essentially every chain in production. Bloch does not wait for that day and does not paper over it with an optional "PQ mode." Every signature on the base is a hybrid ML-DSA-65 ‖ Falcon-1024 lattice signature, and hashing is SHAKE-256 throughout. Post-quantum protection is the ground floor of the design, not a layer added later — a key signed on Bloch today is signed with lattices, so it does not inherit the "harvest now, decrypt later" exposure of classical curves.
SHAKE-256 everywhere
The XOF/hash spine across commitments, addresses, and accumulators — a single quantum-resistant primitive.
Not a bolt-on
No classical fallback to strip off. Shor breaks ECDSA/RSA; Bloch never depended on them.
Ownerless & permissionless
No authority. No dates. No off switch.
Bloch follows the Bitcoin model: no company owns, operates, schedules, or can revoke it. There is no official node, no official site, no official explorer, no foundation, no governance seat, and no roadmap anyone is entitled to enforce — just candidate items any node operator or community member may pursue, the way Bitcoin has BIPs. The base is a self-binding commitment device — a technological Ulysses contract that not even the founder can revoke. From the people, for the people.
That is precisely why Postern Labs — an independent third party — does not own it, and maintains no site for it (including blochprotocol.com). Postern is one independent tool-maker on the commons; it does not speak for the protocol. Read "We, the People" →
Pure proof-of-work, honest finality
Work you can verify — no committee to trust.
The live chain runs standard SHA-256d proof-of-work — double SHA-256, Bitcoin-style hashcash, little-endian target compare since the height-2400 fork. Commodity ASICs and rented hashrate mine it directly over standard Stratum. Finality is PoW depth plus checkpoint reorg-depth — nothing more exotic. There is no FFG, no committee, no BFT finality gadget: a candidate FFG-BFT committee overlay was evaluated and dropped. Validity is deterministic and proof-gated — every node re-verifies the identical rules, so consensus never rests on trusting a quorum of signers.
SHA-256d PoW
Double SHA-256, standard Stratum V1/V2. ASIC- and rented-hashrate-mineable; no bespoke hardware.
Depth-based finality
Confirmation depth + checkpoint reorg-depth. Confirmations are reversible — treated honestly as such.
No gadget, no committee
The FFG-BFT overlay was evaluated and dropped. Pure PoW; deterministic, proof-gated validation.
The trilemma, addressed — not hand-waved
Cheaper nodes → more decentralization, without giving up security.
Scalability, security, decentralization — the standing trade-off. Bloch's answer is the ZK-Ledger groundwork: compact stateless validity. State is committed with SHAKE-256 into a Utreexo accumulator; a STARK/FRI validity proof attests that a block's transitions are correct; and proof-gated pruning lets a node discard bulk state it can no longer be forced to hold. The result is a node cost that trends toward O(log n) instead of O(n) — so the machine needed to fully verify the chain gets cheaper, which means more people can run one, which means more decentralization — and none of it weakens the security model, because every proof is re-checked.
Honestly: this is shipped inert / height-gated groundwork, not a live consensus feature. It is designed and being built, not booted into the base chain's validity rules.
Native contracts, done right
Deterministic, gas-metered, post-quantum — no Turing-tarpit.
Bloch's native-contract layer is built to fit a UTXO, pure-PoW, proof-gated base — not to graft an account-model VM onto it. bloch-euvm is a deterministic, gas-metered eUTXO VM (Cardano/Ergo-style: an output carries a validator + datum, and spending runs the validator) with no global mutable state and no VM Turing-tarpit. Ustav (устав — "statute / charter") is a modular token-charter standard: instead of one monolithic blob of arbitrary code, a token is a signed, versioned charter composing typed modules (Supply, Transfer policy, Compliance/KYC-gate, Vesting, Governance, Custody), committed with SHAKE-256 and its authorities signed ML-DSA-65 ‖ Falcon-1024. Kirpich (кирпич — the "brick" you inspect before laying it) is the fail-closed charter-audit gate: before a charter compiles to a contract it runs a deterministic static audit and refuses to build on any Deny finding — module conflicts, compliance completeness, unsafe parameter combos, supply/mint sanity (BLCH can never be minted), and determinism of the emitted validator set. Findings carry codes (KRP-###) and severities (Deny / Warn / Info).
KRP-### rules across 4 lanes (conflicts / completeness / params / emitted); any Deny finding refuses the compile. Internal static-audit gate, not an external audit — tests-only, not consensus-wired; reduces but does not remove risk. BLCH is not a security.Honest status — designed / tested-reference, NOT consensus-wired. bloch-euvm, Ustav, and Kirpich live today as a tested reference in the isolated bloch-euvm crate (an internal audit has run). They are not wired into the base chain's consensus; doing so is a separate future height-gated hard fork, and the base stays pure PoW until then. When they ship they go live before an external audit exists — and until a third-party audit is done they are not safe; any use is entirely at the user's own risk. BLCH is not a security. Designed ≠ built ≠ booted.
design / spec unaudited
Honest status — read before anything else
Designed ≠ built ≠ booted. Use at your own risk.
- Unaudited mainnet beta. A third-party audit is contracted but not done. This is research participation, not an economy.
- Very few nodes, low hashrate → 51%-attackable. A young SHA-256d chain is cheap to attack with rented hashrate; treat confirmations as reversible. The window until real hashrate accumulates is an open question, not a solved one.
- BLCH carries no value claim and is not a security. No token sale, no listing effort, no price. Disclosed in full: a 17% founder premine (10-year cliff, 40-year vest), structurally passive.
- Native-contract features are designed / tested-reference, NOT consensus-wired. bloch-euvm, Ustav, Kirpich, and the ZK-Ledger groundwork go live before an external audit and are not safe / use at your own risk until a third-party audit exists.
- Designed ≠ built ≠ booted. Hosting or testing a reference is not the same as running it in consensus — this page labels each thing with exactly what it is.
Want to participate? Run a node → · Why Bloch migrated to SHA-256d → · Genesis-2 status report (Markdown) →
Independent perspective, by Postern Labs. The Bloch-SIS-PoW protocol is ownerless and is not a Postern Labs product; Postern Labs neither owns, operates, nor speaks for it. This page is one independent party's view of the commons — not an official protocol site. Postern builds on Bloch and writes about it; it holds no ownership of, representation of, or prerogative over the protocol.