Some checks failed
CI/CD Pipeline / Lint and Format (push) Failing after 46s
CI/CD Pipeline / Terraform Validation (push) Failing after 35s
CI/CD Pipeline / Kubernetes Validation (push) Successful in 37s
Deploy ChainID 138 / Deploy ChainID 138 (push) Failing after 1m50s
HYBX OMNL TypeScript & anchor / token-aggregation build + reconcile artifact (push) Failing after 2m19s
Validation / validate-genesis (push) Successful in 51s
Validation / validate-terraform (push) Failing after 39s
Validation / validate-kubernetes (push) Failing after 10s
CI/CD Pipeline / Solidity Contracts (push) Failing after 12m56s
Validation / validate-smart-contracts (push) Failing after 12s
CI/CD Pipeline / Security Scanning (push) Failing after 15m52s
Validation / validate-security (push) Failing after 10m59s
Validation / validate-documentation (push) Failing after 17s
Validate Token List / validate (push) Failing after 30s
OMNL reconcile anchor / Run omnl:reconcile and upload artifacts (push) Failing after 26s
Verify Deployment / Verify Deployment (push) Failing after 56s
805 B
805 B
ZK reserve attestation (optional extension)
On-chain policy uses public inputs (S0, S1, R) from ERC20.totalSupply and ReserveCommitmentStore. For privacy-preserving proof that backing exists without disclosing raw bank balances:
- Implement a verifier contract conforming to
IZkReserveProofVerifier.sol. - Off-chain: generate proofs with your chosen circuit (public inputs: commitment to R, line id, snapshot block).
- Wire: either wrap
commitReservewith a step that checksverifyProofbefore accepting R, or post proofs alongsideevidenceHash/merkleRootfor auditor tooling only.
This repo does not ship a production circuit or verifier bytecode; the interface is the integration boundary for audits.