PUBLIC SYSTEM OVERVIEW

AENET Wallet

AENET Wallet — local-first, watch-only Bitcoin infrastructure with external signing and machine-level integration. Public system overview of the AENET ecosystem.

Local-first Bitcoin infrastructure with watch-only operation, external signing, and machine-level integration.

AENET Wallet is the Bitcoin infrastructure layer of the AENET ecosystem. It is local-first, watch-only, and signs nothing online: private keys remain outside the wallet domain, and settlement requires an external hardware signer. The public side observes only sanitized snapshots.

Snapshot version: 0.9.0 Published from a verified public snapshot

WATCH ONLY

YES

online signing is disabled

ONLINE SIGNING

DISABLED

no signing on the public side

PRIVATE KEYS

EXTERNAL

stored outside the wallet domain

MAINNET

BLOCKED

blocked during development

PUBLIC WALLET CONTROL

NONE

the public side is read-only

What is AENET Wallet?

AENET Wallet is a local-first, watch-only Bitcoin wallet architecture integrated into the AENET ecosystem. It observes receive and transfer-intent state, quotes network fees, and prepares unsigned PSBT intents for external signing.

Local-first — the wallet domain runs on the private machine, not in the cloud
Watch-only — online signing is disabled by design
Bitcoin infrastructure — receive, transfer intent, network fees
Ecosystem integration — Spine, Rust machine bridge and MBROT

Security model

The security model keeps every signing operation outside the online wallet domain.

Receive flow

Incoming value is observed through a receive request and confirmed on the network — never by exposing a private key.

Transfer flow

An outgoing transfer begins as an intent, is reviewed by treasury policy, quoted with a network fee, reserved as an unsigned PSBT and signed on an external signer.

Machine integration

The Go wallet domain talks to the machine layer through a Rust bridge and MBROT board intelligence over Linux drivers.

System connections

AENET Wallet connects to the Spine, the Bitcoin node, treasury, the Rust machine bridge, MBROT and an external signer contract.

Development evidence

Every public claim about the wallet is backed by the sanitized snapshot in public-data/wallet/.

Flow

Receive Request an incoming value request is created
Bitcoin Address a public address is derived for observation
Transaction Observation the network is watched without signing
Confirmation the incoming transaction confirms
Proof a public-safe proof record is kept