Skip to navigation
Crypto payment structure with 5 layers.
22.10.26
1. Seed (the wallet itself) 12/24 BIP39 words → one master secret. From it, every key is derived deterministically (BIP32). That's why the same words restore the same addresses on any compatible software. 2. Device (the vault) Ledger/Trezor stores the seed in a secure element, unlocks with a PIN, and signs only what it displays. It exports public keys (xpub/addresses) to the host, never private ones. 3. Derivation (address space) Fixed paths pick the account and coin: BTC m/84'/0'/0'/0/i, ETH m/44'/60'/0'/0/i. Host software uses these to generate receive addresses. 4. Host software (Debian) - Ledger Live / Trezor Suite — GUI/AppImage: balances, send/receive, firmware. - cast / hwi — CLI: build transactions, sign via device, broadcast. - Bitcoin Core — optional full node: your own copy of the chain, watch-only wallet, PSBTs. 5. Chain (the ledger) The actual balances live on-chain. Broadcast goes through your node or a public RPC; the transaction is confirmed by the network. Mechanism of one payment: 1. Host builds a transaction and computes the fee. 2. Device receives it, shows recipient + amount, you confirm on the device screen. 3. Device signs with the private key (never leaves it). 4. Host broadcasts the signed transaction. 5. Chain confirms; balance updates. On Debian concretely: - Minimal install, full-disk encryption, no browser on the signing account. - udev rules + plugdev so the device is reachable without root. - Vendor software from official sources (verified hash), cast for EVM, hwi for Bitcoin. - Optional Bitcoin Core, pruned, as your own broadcaster. - Seed on paper/steel, never in a file, shell history, or password manager.
Reply
Anonymous
Information Epoch 1792718421
Separate policy from mechanism, separate interfaces from engines.
Home
Notebook
Contact us