zkPI is a zero-knowledge payment instruction.
Proof-carrying instructions: a venue's decision, provable without the inputs that produced it.
flowchart LR
subgraph known["what the quorum computes over"]
direction TB
R["the request<br/>asset, size, side"]
P["each maker's<br/>pricing policy"]
W["the winner<br/>and its price"]
end
subgraph published["what is published"]
direction TB
C["committed<br/>instruction"]
N["nullifier"]
D["deadline"]
S["quorum<br/>signature"]
end
subgraph venue["what a settlement venue checks"]
direction TB
V["in range<br/>unspent<br/>in time<br/>signed by the quorum"]
end
R --> C
P --> C
W --> C
C --> V
N --> V
D --> V
S --> V
known -. "never crosses" .-> venue
classDef secret fill:#F3E4E3,stroke:#B08C89,color:#3A2A29
classDef wire fill:#E8EFE6,stroke:#8FA88A,color:#243024
class R,P,W secret
class C,N,D,S,V wire
flowchart TB
subgraph audited["used, not rewritten"]
DALEK["curve25519-dalek<br/>ristretto255"]
BP["bulletproofs<br/>range proofs"]
FROST["frost-ristretto255<br/>threshold signatures"]
end
subgraph zk["zkfmi-zk"]
PED["pedersen<br/>commitments, asset tags"]
SIG["sigma<br/>opening, cross-generator, product"]
RNG["range"]
OOM["oneofmany<br/>Groth-Kohlweiss"]
ORD["or_dleq"]
ADP["adaptor<br/>pre-sign, adapt, extract"]
end
subgraph pi["zkpi"]
ISS["issuer<br/>KYB credentials"]
INS["instruction<br/>commit, bound, nullify"]
QUO["quorum<br/>who signed it"]
HAN["handles<br/>one seed, an unrelated point per venue"]
end
DALEK --> PED
DALEK --> HAN
BP --> RNG
FROST --> QUO
PED --> SIG
PED --> OOM
PED --> ORD
SIG --> ADP
SIG --> INS
RNG --> INS
OOM --> ISS
ORD --> ISS
INS --> QUO
HAN --> INS
Generated from one shared research tree, which is why the layout is regular across the three repositories. This repository is nevertheless self-contained: its tests, locks, measurements and source do not require the private working tree.
Rust crates:
rust/zkfmi-zkrust/zkpirust/zkpi-proofsrust/zkpi-committeerust/qomm-dslrust/qomm-simrust/qomm-mpcrust/qomm-auditrust/zkfmi-measurerust/zkpi-harness
Measurement binaries carried by zkpi-harness:
run_quote_proofrun_voleithzk_benchzk_compare
zkpi-proofs and zkpi-committee are shared by DeFMI and multiple venues.
The QOMM-only rule/policy/state/liquidity audits, venue transport modules and
run_state_audit now live in QOMM, as
qomm-proofs, qomm-transport and qomm-harness. Neither zkPI nor DeFMI
depends on QOMM. Historical transcript labels and recorded artifacts retain
their original names.
artifacts/ holds the measurements the numbers in the paper are taken from, as
the binaries wrote them. Each carries the host it ran on as a label (host-a,
host-b, host-c) rather than a machine name; the private mapping back
to real machines is not published.
POSITION.md--- what is new here and what is not, stated line by line against the nearest prior workACCOUNTABILITY.md--- what happens when a node misbehaves: the five rungs from abort to guaranteed output delivery, and which one each mechanism here reachesZKPI_WIRE.md--- the bytes an instruction travels as, the vectors to check an implementation against, and where it can runREVIEW.md--- what two rounds of review found, including what was checked and found sounddoc/ja/DEFMI_ZKPI_USE_CASES.md--- non-QOMM uses for proof-carrying instructions and decentralized settlement, with prior art and an implementation order
Cargo resolves these repositories from the checked-in lock file.
Enterprise PoC guide (Japanese) explains the installation, role separation, failure cases, evidence to retain and acceptance criteria for a company-run evaluation.
cd rust
cargo test -j 4 --locked --workspaceEvery reported number has an artifact and a Rust binary that produces it. Where a measurement needs something not shipped here --- MP-SPDZ, a second host, a market data feed --- the binary says so and fails rather than substituting a default.
MIT. See LICENSE.