WALLET / ARCHITECTURE
AENET Wallet Architecture
AENET Wallet architecture — watch-only Bitcoin system with a private wallet domain, machine layer, signing boundary and external signer. Public observation reads snapshots only.
AENET Wallet sits behind the private boundary. The public cloud reads sanitized snapshots; the wallet domain, machine layer and signing boundary are never publicly routable.
Public observation
AENET Cloud renders public pages and read-only API responses exclusively from the sanitized wallet snapshot. There is no live query path from the public side into the wallet.
Private boundary
The private boundary separates everything public from the wallet domain. Only verified, sanitized snapshot exports cross it, one way.
Wallet domain
The wallet domain (node, ledger, treasury) manages receive and transfer-intent state. It produces unsigned PSBT intents — never signed transactions.
Machine layer
A Go wallet connects to the machine layer through a Rust bridge and MBROT, observing CPU, memory, storage and network health without exposing machine details.
Signing boundary
An unsigned PSBT crosses the signing boundary to an external signer. Physical confirmation happens on the hardware signer; the signed result returns for validation.
Audit and proof
A public-safe proof record and hash chain support verification without disclosing wallet internals.