EthSystems completes formal verification of privacy pool, covering specification through Sepolia bytecode
BIBIBI
AT A GLANCE
EthSystems said it had completed the formal verification of the privacy pool from the written specification to the Sepolia bytecode, and identified 6 issues.
Article
EthSystems completes formal verification of a privacy pool, covering everything from specifications to Sepolia bytecode
PANews October 27 reported that Ethereum institutional privacy technology firm EthSystems had completed formal verification of its privacy pool (shielded pool), covering everything from written specifications to Sepolia bytecode running on the testnet. Different tools were used at each layer: Lean for the model, circuits, and hashes; Halmos and Kontrol for the contracts; Aeneas and Verus for the wallet; and byte-by-byte reconstruction checks for the verifier and deployment. Double-spending and value conservation were verified by Lean's theorem prover. The verification identified a total of 6 issues, of which 3 were in the verification tools themselves. The team also listed the assumptions that still remain: hashes are collision-resistant, the verifier will reject forged proofs, and the contract behavior is consistent with the model.
PANews reported that EthSystems announced the completion of formal verification for its privacy pool.
02
The verification scope extended from the written specification to Sepolia the bytecode running on the testnet.
03
Lean was used to verify the model, circuits, and hashes; Halmos and Kontrol were used for the contracts; and Aeneas and Verus were used for the wallet.
04
The verifier and deployment were checked through byte-by-byte reconstruction.
05
Double-spending prevention and value conservation have been verified by Lean theorem proving.
06
The verification identified a total of 6 issues, of which 3 were in the verification tool itself.
07
The remaining assumptions listed by the team include: hash collision resistance, the verifier rejecting forged proofs, and contract behavior being consistent with the model.
AI-assisted interpretation
The following is analysis, separate from reported facts. Verify important claims independently.
Formal verification uses tools to check, according to explicit rules, whether a system conforms to its specification. This work covered the model, circuits, hashes, contracts, wallets, verifier, and deployed bytecode, but the results still rely on several assumptions listed by the team.
Why it matters to readers
The verification claims to cover multiple layers from the specification to the testnet bytecode, and to check issues such as double spending and value conservation; at the same time, the issues found and the remaining assumptions show that verification does not mean all risks have been eliminated.
Beginners should understand this as a claim of a relatively broad technical security review, not as proof that the privacy pool is absolutely secure, nor as confirmation of its mainnet status.
Risks and unknowns
The source text does not provide a formal verification report, code, or independent review materials.
6 The specific nature, severity, and remediation status of the issue have not been specified.
Except for 3 issue(s) from verification tools, the remaining 3 issue(s) are of unclear origin.
The absence of hash collisions, verifier rejection of forged proofs, and consistency between the contract and the model remain assumptions.
The source text only explicitly mentions Sepolia a testnet; it does not state whether deployment on the mainnet has occurred.
Related Developments
Loading event timeline…
Related concepts
privacy pool
This term is not in the glossary yet. Browse related concepts in the glossary.
