Evolver gives a set of mutually-distrusting parties one agreed, tamper-evident, authenticated order of events — and, optionally, disseminates the event payloads for them.
It is not a smart-contract platform. The chain orders your transactions but never runs your application logic and never holds your application's state. You define what an event means and derive state by folding the ordered stream yourself. Applications talk to a node over a small HTTPS wire API.
What it does
- Jolteon BFT consensus
- 2-chain HotStuff-style finality with BLS12-381 aggregate certificates, tolerating f < n/3 Byzantine faults. Idle-quiescent, and leader reputation sidelines dead or slow leaders without lowering the quorum threshold.
- Application ledgers
- Total-ordering of your transactions with opaque bodies, and write-authorization per ledger — open, individual, or group.
- Data availability, managed or bring-your-own
- A ledger can name a DA group and threshold, and consensus then admits a transaction only with enough attestations from that group. Or leave it empty: the chain orders an identifier and you host the bytes yourself.
- Identities, credit and tolls
- On-chain identities with proof-of-possession, node-sponsored so creation is free to clients. Credit transfers between holders, and an optional fixed toll a ledger owner may charge on every authorized write.
Where it is
Evolver is under active development. The public network is a devnet: entry is free and unlimited, no chain here holds value, and chains are replaced rather than migrated. Key handling is dev-grade by decision — the sign/submit split exists so that a production deployment can move where keys live without changing any caller.
Documentation will expand here.