BLOCH PROTOCOL

A different foundation.

Hybrid lattice signatures at the authorization layer. A proof-of-stake architecture designed around their constraints.

PUBLISHED RECORD REVIEWED 08 SEP 2026 · NOT A LIVE NETWORK FEED

Two signatures, together.

Bloch’s authorization construction requires ML-DSA-65 and Falcon-1024 to verify together. This is the protocol’s design boundary; it does not establish that every application in the ecosystem has the same cryptographic protection.

MODULE LATTICES

ML-DSA-65

The ML-DSA signature scheme is specified in NIST FIPS 204.

NTRU LATTICES

Falcon-1024

The second signature scheme in Bloch’s hybrid construction, with its own signing and verification costs.

The trade-off is larger keys and signatures, additional verification work, and limited hardware-wallet compatibility.

The Genesis-4 architecture.

Proof of stake combines slots and epochs with LMD-GHOST fork choice and a Casper-style finality design.

Published protocol parameters, not live network measurements
ParameterValue
Slot duration30 seconds
Slots per epoch32
Epoch duration16 minutes
ConsensusProof of stake

Use the explorer for current chain observations.

Hash-based privacy research.

Coherence uses SHAKE-256 commitments and a STARK/FRI proving approach. Its published description identifies an unaudited proving scaffold. No anonymity guarantee follows from this design description.

Understand the boundaries.

Protocol design is not an audit.

The published record does not establish a completed independent security audit. Genesis-4 launched with 64 validators under one operator. Neither that launch configuration nor these parameters are a live decentralization measurement.

Postern DEX targets an EVM environment. Its account signatures and permits do not inherit Bloch L1’s post-quantum authorization just by belonging to the same ecosystem.

Node and validator guidance ↗