Skip to documentation
Reality-grade bankingDocumentationOpen implementation
Documentation contents

Identity & protection

Back up identity and proof originals

Save the right files separately, restore verified evidence, and understand what a backup does not carry.

Reviewed 2026-10-25 · SDK 129.0.0Read Markdown ↗

Save two different backups

  1. Save your identity

    Open the identity panel and choose Back up my Identity Record. Save the actual original.

  2. Protect any phrase

    If the Record uses a recovery phrase, save it separately and privately. Do not include it in a support message or public proof.

  3. Save proof evidence

    Expand Account proofs & receipts and choose Save private proof backup.

  4. Keep current originals

    Save updated Vault/Note originals as their operation requires; an older file cannot contain an unsaved later result.

What the proof archive contains

The bankeiz.proof-backup.v1 collection preserves supported exact owned originals, asset definitions, verified recovery evidence, retained Note images and completed deposit receipts held on the device. Each original is reopened under the existing verifier before export. A filename, amount or claimed digest does not qualify it.

Backup scope
IncludedExcluded
Complete supported proof originals and evidenceSigning keys, unlock phrases and permission tokens.
Supported retained Note images and completed receiptsHardware-bound Note credentials.
Exact byte originals and their identity/application bindingUnfinished payment attempts and their local execution checkpoints.

Protect the downloaded archive

The private archive is not the public account-proof feature. Sharing it can disclose sensitive originals and history. Keep a separate copy before removing storage or retiring the device. Do not send the archive to support just to report an operation reference.

Restore evidence under the matching identity

  1. Open the matching identity

    Use its supported original recovery path first.

  2. Choose Import backup or proof

    Select the archive, supported original, complete recovery JSON, Note PNG or completed deposit receipt.

  3. Review verified sources

    Inspect filenames, source results and transaction coordinates. Invalid or foreign sources must be refused.

  4. Choose Import verified proofs

    The complete batch is retained atomically; cancel leaves storage unchanged.

Limits and recovery boundaries

The collection supports up to 1,000 sources, 32 MiB per source, 64 MiB of original bytes and a 90 MiB encoded download, with cumulative stored-proof checks. Keep the original files if a limit is exceeded. Exact originals deduplicate; a concurrent identity or storage change prevents a partial import. Import retains evidence. It does not execute a payment, credit a balance, redeem a Note, replace pending work or restore hardware-bound custody. Resolve unfinished operations on the original device before destructive changes.

Implementation sources

Inspect the exact path.

Source links retain revision 6c5d582. Read the documented operation and assessment scope alongside its code.