// the find
Consensys-inc-archive/quorum
A permissioned implementation of Ethereum supporting data privacy
GoQuorum is a fork of go-ethereum for consortium and enterprise networks. It adds private transactions and contracts, with private state kept separate from public state, plus permissioned peers and non-PoW consensus. It is archived now, so its main use is maintaining an existing deployment or studying how these pieces fit together.
- Private payloads move peer-to-peer through Tessera and are kept out of the public state, while the public chain records only a hash of each private payload. That is a more concrete privacy model than most permissioned Ethereum forks offer.
- Consensus is pluggable. QBFT, IBFT, Raft and Clique are all in the tree, so a network can choose its finality and block-time behaviour instead of inheriting PoW or PoS assumptions.
- While it was maintained, it followed go-ethereum releases, so the EVM and JSON-RPC surface stayed close to upstream and most Ethereum tooling worked unchanged.
- Peer permissioning and the account plugin system, which covers external vaults, address the operational side of running a permissioned network, not just the consensus layer.
- The README says the project is archived, no longer maintained or supported by Consensys, and not recommended for new projects. Any security fix or upstream sync from here on is your job.
- It is a long-lived fork of go-ethereum, so the diff against upstream is large and hard to rebase. Anyone who wants newer EVM features is stuck with whatever upstream version was last merged.
- Privacy depends on a separate Tessera process per node, and private participants must be configured and kept in sync with each node. That is another service to run and monitor, and its failure modes are not obvious from the chain side.
- The documentation the README links to lives on consensys.net and is tied to specific releases. With the project archived, some of those pages are probably stale, so expect to work out gaps by reading the source.