Build with Nullark

Start with one complete flow

Run the browser quickstart

Deposit one note, restore it, and withdraw it before integrating any individual layer.

Choose one boundary

Start with one path: the TypeScript SDK, deposit, or withdrawal guide.

Verify the exact runtime

Match the network, pool, verifier, proving files, public-input order, fee, and submission path before handling value.

Choose a surface

Surface	Public status	Use it for	Important boundary
Browser app	Chromium tested	Learning and using the complete flow	Recovery and proof material stay in the trusted browser session
TypeScript SDK	`@nullark/[email protected]`	Preparing and validating deposit, private balance, recovery, and withdrawal data	Your app still owns proving, chain reads, wallet review, and submission
CLI workspace package	Source distribution	Inspecting runtime and proving-file bindings	It intentionally rejects recovery keys, witnesses, signing, and submission
Direct contract calls	Advanced	Specialized, reviewed integrations	Your application owns calldata, signer, gas, retries, and receipt checks

Follow a build path

Goal	Start here	Completion signal
Wire the package	TypeScript SDK	Clean consumer build plus one restored test deposit
Accept one deposit	Deposit integration	Matching pool event and saved recovery authority
Submit one withdrawal	Withdrawal integration	Matching pool event and spent nullifier read
Review relayer boundaries	Relayer integration	No service is treated as active without a deployment-specific authorization

How the pieces stay consistent

Stage	Required check
Network	Use one supported runtime from recovery through settlement
Recovery	Keep recovery data out of logs, URLs, analytics, flags, and remote services
Proof	Use proving files and public-input order published for that runtime
Review	Recheck recipient, amount, fee, pool, and chain before submission
Submission	Allow only the intended pool, function, value, and deadline
Completion	Confirm the pool event and nullifier state, not only a transport response

Before submitting value

Keep secrets in the trusted client. Never send note secrets, recovery exports, wallet unlock signatures, Merkle witnesses, or proof witnesses to an RPC, relayer, analytics service, or support channel.

Workflows

Setup and recovery

Reference

Build with Nullark

Start with one complete flow

Choose a surface

Follow a build path

How the pieces stay consistent

Before submitting value

​Start with one complete flow

​Choose a surface

​Follow a build path

​How the pieces stay consistent

​Before submitting value

Start with one complete flow

Choose a surface

Follow a build path

How the pieces stay consistent

Before submitting value