SecurityCore release 0.1.0

Validation evidence

Summary of the frozen Core binary identity, fresh Devnet lifecycle, replay/recovery results, page-boundary test and measured costs.

The frozen Core/SDK release gate completed a fresh Devnet lifecycle on 2026-10-07. This page summarizes its evidence without publishing fixture secrets or operational working paths.

Binary and release identity

EvidenceValue
Program IDZkCP47fAJJREdXNKSBvTsgJAuLoTKepgk6opmqsHobm
Core version0.1.0
SDK version@lethenymous/[email protected]
Frozen SBF size906,424 bytes
Frozen SBF SHA-256bb70f41d59660c2f66378f7124ba068a83911746698fbab26236a1e2d447d87b
Fresh Devnet gatePASS, 2026-10-07

The finalized Devnet ProgramData bytes matched the preserved binary. The release manifest records the source and provenance identities.

Lifecycle coverage

The run exercised fresh pool/liquidity setup and public swap baseline, Shield, production-proof Private Swap in both directions, Private Send via Unshield, Unshield, five finalized replay rejections with canonical NullifierSpent, fresh-process account-only recovery followed by a spend, spent-state restart, fail-closed proving interruption and final token accounting.

The 4095→4096 organic page transition passed with a two-output production-proof Private Swap: change appended at index 4095, output at index 4096, both recovered after restart using one 18-account request and zero history calls.

Measured v0 transaction shapes

OperationBytesCompute unitsProof time
Shield66189,678Not applicable
Private Swap A→B with change847639,6165.119 s
Private Swap B→A without change847614,1885.028 s
Private Send1,109351,9262.521 s
Unshield1,077348,7332.400 s
Cross-page 4095→4096 Private Swap756660,9354.918 s

Every submitted SDK transaction in this gate was ≤1,232 bytes. Both measured token supplies reconciled across balances, LP vaults, custody and fee vaults with no unexplained value delta.

Coverage boundary

Real organic Devnet Gen0→Gen1 rollover was not executed. At most one remaining leaf is required before rollover, so the necessary scale was not practical within that run's time/cost budget. Local/runtime evidence is separate and is not represented as organic Devnet history.

The final manifest reports zero known unresolved critical, high or medium findings within the controlled Devnet release gate. The evidence is not an independent third-party production audit. The single-party setup, Token-2022 exclusion, relayer audit status and operational trust limits remain as described in Known limitations.

This summary was checked against the frozen Devnet validation report, Core release manifest, production-prover manifest and production artifact manifest.

PreviousKnown limitationsNext Deployments
Source baseline: frozen Core v0.1.0 / SDK v0.1.1.