Conformance with keripy
Three kinds of evidence show how closely libkeri tracks keripy:
| Evidence | What it checks | Where |
|---|---|---|
| Golden vectors | keripy generates events, receipts and messages from fixed salts; libkeri rebuilds each one and must match byte for byte | libkeri/tests/keripy_vectors.rs, generated by libkeri-interop/vectors/gen.py |
| Trace lint | every keripy symbol cited in libkeri’s code exists in the pinned keripy | libkeri/scripts/trace_check.py |
| Interop scenarios | krust and the Rust witness against kli and keripy witnesses, across keripy 1.1, 1.2 and main | Interop scenarios |
Everything libkeri knowingly does differently, and the keripy behaviour the scenarios run into, is in Divergences.