Skip to content

Learn · V1

Understand the wallet you depend on.

Keys, policies, recovery, and privacy in plain language. Start here before deciding which setup fits you or your family.

Nine essentialsNo account requiredBitcoin only
Recovery rehearsal

Prove the way out

A backup is useful when it rebuilds the same wallet without Groot.

JSON

Groot public backupDescriptors, labels, and policy

Saved
BSMS

Multisig backupPortable policy material

Saved
PDF

Recovery guideHuman-readable QR document

Saved
✓

Recovery drill passedSame wallet · Same first address

The essentials.

01

Wallet and signer are different jobs.

A wallet tracks addresses, coins, balances, and transaction proposals. A signer controls a private key and approves a transaction. Groot can keep both jobs on one device for a software wallet, or coordinate independent hardware signers without receiving their keys.

02

Multisig removes one fragile key.

A 2-of-3 wallet can spend when any two of three independent keys sign. The policy, signer identity, and recovery descriptor matter as much as the threshold. Groot uses standard descriptor policies so another compatible coordinator can rebuild the wallet.

03

Descriptors describe. PSBTs propose.

A public descriptor records how addresses and signing policy are derived without containing private keys. A Partially Signed Bitcoin Transaction carries a proposed transaction and its collected signatures. Together they make portable, offline, and remote workflows possible.

04

Recovery is a path. Inheritance is a process.

Recovery answers how you regain control after losing a device or key. Inheritance also needs people, instructions, evidence, timing, and rehearsal. A good plan minimizes today’s theft surface while remaining understandable to a spouse, parent, helper, or business successor.

05

Your node defines what the wallet reveals.

A wallet backend learns the addresses and transactions it is asked about. Groot therefore uses the local or remote Bitcoin Core node selected by each wallet and never silently falls back to a public wallet backend. Remote access requires HTTPS.

06

Remote coordination should move ciphertext, not trust.

Planned Groot Family coordination will exchange encrypted invitations, proposals, and signatures between enrolled devices. The relay must not be able to read or alter a PSBT, sign, reconstruct a wallet, or become necessary for recovery. Standard offline exchange remains the escape path.

07

Paid service must have a sovereign exit.

Free covers creating, signing, reviewing, exporting, and recovering the wallet. Family and Business add coordination, assurance, support, approval, and accounting workflows. Ending a subscription must never strand a wallet or prevent a user from moving bitcoin.

08

New software deserves small first steps.

Start with a small amount. Verify addresses on the signer. Rehearse recovery. Increase responsibility only after the full path makes sense.

09

Verify software before you trust it.

Download Groot from the official GitHub Releases page. Compare the file with the published checksum, then verify that checksum with the release signature and key information included with the release. Stop if any part does not match.

Go deeper

Verify the details.

The public security model explains current trust boundaries. The documentation map points to canonical, versioned product and release records.

Your keys.
Your bitcoin.

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