Published security status - Nullark

This page separates the current SDK-pinned deployment from work still in progress. Public records cover exact identities and bounded checks. Private operational controls stay outside those records.

Current SDK-pinned deployment

Current deployment publishes chain, contracts, fee policy, and proving identities as one set. Approved relayer endpoint: pending. Operator custody, frontend provenance, and privacy each need their own evidence.

Separate work in progress

Development work stays separate from the published runtime. Deployment approval and production status require the complete release evidence set.

Field	Published status
Formal work	In progress
Deployment	Not deployed
Source commit	Not published
Deployment approved	No
Production ready	No
Privacy claims approved	No

Published runtime changes only through a reviewed release with matching evidence.

What evidence means

Evidence	Direct result	Next evidence
Unit or integration test	Tested behavior passed for reviewed source	Broader security and deployment review
Formal theorem	A stated property follows for the modeled relation	Source, circuit, verifier, and deployment refinement
Artifact SHA-256	Exact file bytes match	Circuit soundness and setup integrity
Contract codehash	Deployed bytecode matches expected bytes	Initialization, roles, and live operations
Runtime record	Values belong to one named deployment	Service availability and origin integrity
Smoke record	One bounded execution occurred	Ongoing safety, availability, and privacy evidence

What still needs explicit evidence

Production readiness and privacy claims require explicit release evidence. Authorization comes from that evidence set, never from prose, one local test, one hash, or one theorem. For now, amounts, destinations, timing, and submitters stay public. Nullark will publish any stronger privacy guarantee with the deployment it covers.