Validate recovery data - Nullark

The SDK creates one encrypted recovery envelope for each prepared bundle deposit. Save it before asking the wallet to submit. Restoring the bundle requires both the envelope and its recovery key.

The envelope is secret-bearing recovery authority. Never place a real envelope or recovery key in logs, URLs, analytics, support tickets, tests, or source control.

What the envelope contains

Part	Purpose
Runtime identity	Chain, pool, runtime ID, runtime hash, and template-set hash
External anchor	Bundle commitment prepared for the deposit
Encrypted payload	Fixed 144-byte recovery ciphertext
Payload identity	Encrypted payload hash and byte length

The recovery key lives outside the envelope. Keep both together in your backup.

Restore through the SDK

const bundle = await nullark.recovery.restore({
  envelope,
  recoveryKey
});

The restore path checks the envelope schema, active runtime, pool, template set, payload hash, authenticated-encryption context, and externally anchored bundle commitment. It then recomputes the bundle and child commitments before returning spendable data.

Required order

Parse the expected envelope object without coercing fields.
Match its runtime identity to the active SDK runtime.
Verify the payload shape and hash.
Decrypt with the application-held recovery key and bound context.
Recompute the bundle commitment.
Resolve the bundle commitment’s onchain membership.
Check each selected child nullifier before proving.

Do not write a looser compatibility parser. If a field, hash, runtime, key, or commitment differs, restoration fails and no chain action should follow.