A local wallet that stays inside the vault boundary.
Core keeps the signing path local and explicit: prepare -> confirm -> broadcast.
When it fits
Use the wallet path when you want local signing and explicit previews before broadcast.
Preview first
Build and inspect the transaction before any signature leaves the device.
Multi-chain wallet
Keep BTC and ETH flows in the same encrypted vault.
Explicit broadcast
Nothing reaches the network until the user confirms the preview.
Transaction lifecycle
No transaction leaves the device without explicit confirmation. Core assembles, you verify.
Prepare
Core assembles the transaction and derives the right signing context.
Preview
Fees, amount, and warnings appear before anything can leave the device.
Confirm
The explicit user action authorizes the signature and broadcast.
Broadcast
The signed transaction is sent to the network only after confirmation.
Security boundaries
Keys stay local
Seed phrases and standalone keys stay in Core or on disk inside the vault boundary.
No blind send
The preview stage is mandatory before broadcast is even possible.
Explicit approval
A transaction only signs after the user confirms the preview.
Limits and scope
The wallet is intentionally narrow rather than feature-complete.
- It focuses on the listed supported chains and basic signing flows.
- It is a local wallet, not a remote custodial service.
- It is built around explicit confirmation, not automatic blind sending.
Not a custodial exchange
The wallet is local signing infrastructure inside the vault, not a trading platform.
Keep wallet signing inside the same vault boundary.
The preview and confirm stages keep transaction flow explicit before the network ever sees it.