Device Register Process
Step-by-step overview of how App Grove Field documents your family's multisig hardware wallets in a permanent offline register.
What the Device Register Contains
The device register is a bound physical document — not a digital database — that records every hardware wallet in your family multisig arrangement. Each entry includes the device model, serial number, firmware version, assigned custodian, derivation path, and xpub fingerprint for verification purposes.
The register never contains private keys, seed phrases, or passphrases. It describes where recovery materials are stored (safe deposit box, home safe, attorney’s office) without reproducing their contents.
Register Sections
Section 1: Quorum Configuration
Documents your multisig threshold (e.g., three-of-five), the blockchain networks covered, and the date the arrangement was established or last amended.
Section 2: Device Inventory
A table listing each hardware wallet with model, serial number, purchase date, firmware version, and last verified date. Photographs of device labels may be included with serial numbers redacted in copies.
Section 3: Signer Responsibilities
Each signer’s name, contact method, geographic location, and custodial role. Includes backup signer designation if a primary signer becomes unavailable.
Section 4: Derivation Paths & Fingerprints
Records the BIP derivation standard used, account indices, and xpub fingerprints for each signer. Enables offline balance verification without connecting devices to the internet.
Section 5: Geographic Key Distribution
A map or table showing where each signer’s device and recovery materials are physically stored. Identifies concentration risks (e.g., three signers in the same city).
Section 6: Recovery Procedure
Plain-language steps for family members to follow if a signer is unavailable, a device is lost, or a coordinated signature is needed. Written for readers without technical background.
The Registration Timeline
Week 1 — Scoping call (30 minutes): We confirm signer count, device models, existing documentation, and scheduling constraints.
Week 2 — Session one (3 hours): Device inventory, firmware verification, derivation path confirmation. All work performed air-gapped.
Week 3 — Draft review: Each signer receives their section independently for confirmation. Corrections are incorporated.
Week 4 — Session two (2 hours): Test signature, final verification, register binding and delivery. Optional: secure copies deposited with designated family members.
After Registration
We recommend quarterly offline balance verification using the xpub fingerprints in your register. An included follow-up session within 90 days covers your first verification walkthrough.
When devices are replaced or firmware is updated, book a register amendment session to keep documentation current.
Ready to begin? Use the contact form to schedule your registration consultation.