Skip to content

Documentation

Read the system.

The product, security model, architecture, evidence, and release records are documented separately so every important claim can be checked.

Canonical documentsVersioned with the codeClaims tied to evidence
Family wallet

2 of 3 keys can spend

No single device, person, or manufacturer gets the whole wallet.

2signatures requiredof3independent keys

Everyday signerLedger Nano S Plus · verified

Ready

Family signerTrezor Safe 3 · verified

Ready

Offline backupBitBox02 Nova · stored away

Backup

Source of truth

Start with what you need to verify.

  1. 01

    Brand system

    Identity, colors, typography, wordmark construction, components, imagery, and usage rules.

    docs/brand-system.md
  2. 02

    Voice and copy

    The serious-but-cool personality, writing rules, humor boundary, calls to action, and claims checklist.

    docs/voice-and-copy.md
  3. 03

    Product specification

    Canonical wallet behavior, supported flows, invariants, and explicit exclusions.

    docs/product-spec.md
  4. 04

    Security model

    Assets, trust boundaries, required controls, and residual risk.

    docs/security-model.md
  5. 05

    Architecture

    The Svelte, Tauri, Rust, BDK, persistence, network, and hardware boundaries.

    docs/architecture.md
  6. 06

    Implementation status

    Capability-by-capability separation of fixture, native implementation, evidence, and release state.

    docs/implementation-status.md
  7. 07

    Release checklist

    The evidence and review expected for each public release.

    docs/mainnet-release-checklist.md
  8. 08

    Roadmap

    Work ordered by security dependency rather than marketing priority.

    docs/roadmap.md
  9. 09

    Commercial product strategy

    Free, Family, and Business boundaries, non-lock-in rules, revenue model, and licensing proposal.

    docs/commercial-product-strategy.md
  10. 10

    Remote signer coordination

    Threat model and phased plan for end-to-end encrypted, self-hostable proposal exchange.

    docs/remote-signer-coordination-roadmap.md
  11. 11

    Recovery assurance

    Family, inheritance, business-continuity, cosigner, and insurance direction.

    docs/recovery-assurance-roadmap.md

Reading order

Behavior. Boundary. Evidence.

01

What should happen?

Use the product specification for the promised behavior and explicit exclusions.

02

Where is trust placed?

Use the security model and architecture for secret, persistence, hardware, and network boundaries.

03

What is proven today?

Use implementation status and the release checklist before treating a capability as ready.

Your keys.
Your bitcoin.

Groot is new. Start small, verify every address, and rehearse your recovery before holding more.