AENET.cloud PUBLIC GATEWAY
K.PUBLIC.GATEWAY
ENไทย中文
system-detail K.PUBLIC.SYSTEM

SYS.FIN.01 D01 aenet-wallet

AENET Wallet

Local-first, watch-only Bitcoin wallet architecture with external signing and Rust machine integration. A private operational system of the AENET ecosystem; the public side observes only sanitized snapshots.

Domain: Financial STATUS: development Public boundary: OBSERVATION ONLY Last updated: 2026-08-17

System ID

aenet-wallet

Status

development

Architecture layers

  • PRIVATE
  • PRIVATE Wallet Domain
  • SIGNING BOUNDARY (external signer)

Inputs

  • insufficient-public-evidence

Outputs

  • Sanitized public wallet snapshot (public-data/wallet/)
  • Unsigned PSBT transfer intents for external signing

Public interfaces

  • None — the wallet has no public interface; the public side reads snapshots only

Connected systems

Security boundary

Watch-only by design: no online private keys, online signing disabled, mainnet blocked during development, private keys held externally, and signing requires an external hardware signer across the signing boundary. The public side can never query, proxy or control the wallet.

Data direction

Wallet-to-public one-way (sanitized snapshot export only). Public-to-wallet is forbidden.

Public interfaces

Derived from the API registry

GET /api/v1/wallet aenet.public.wallet.overview.v1 active READ-ONLY
GET /api/v1/wallet/architecture aenet.public.wallet.architecture.v1 active READ-ONLY
GET /api/v1/wallet/evidence aenet.public.wallet.evidence.v1 active READ-ONLY
GET /api/v1/wallet/security aenet.public.wallet.security.v1 active READ-ONLY

Security

Watch-only by design: no online private keys, online signing disabled, mainnet blocked during development, private keys held externally, and signing requires an external hardware signer across the signing boundary. The public side can never query, proxy or control the wallet.

What

Manage Bitcoin receive and transfer-intent flows for the AENET ecosystem while keeping private keys outside the online wallet domain and exposing only sanitized snapshots to the public side.

Why

The ecosystem needs Bitcoin settlement capability without ever placing private keys on an online, publicly reachable surface. The wallet is watch-only, signs only through an external hardware signer, and the public cloud observes only sanitized snapshots.

How

Wallet-to-public one-way (sanitized snapshot export only). Public-to-wallet is forbidden.

  • Operate watch-only over Bitcoin receive and transfer-intent state
  • Keep online signing disabled and private keys external
  • Expose only sanitized wallet snapshots to the public side
  • Bridge to the machine layer through the Rust bridge and MBROT

Example

A transfer intent becomes an unsigned PSBT that is signed on an external hardware signer and validated before broadcast; the public cloud only ever publishes the sanitized wallet snapshot under public-data/wallet/.

Inputs

  • insufficient-public-evidence

Outputs

  • Sanitized public wallet snapshot (public-data/wallet/)
  • Unsigned PSBT transfer intents for external signing

Dependencies

insufficient-public-evidence

Lifecycle

  • insufficient-public-evidence

Use cases

  • Observe Bitcoin receive and transfer-intent state without exposing keys
  • Keep the wallet domain private while the cloud publishes sanitized snapshots

Limitations

  • Mainnet settlement is blocked during development
  • Private wallet details are not public evidence in this repository

Connected systems

  • AENET Cloud Public — The public-facing entrance and observation layer for the AENET ecosystem. It publishes sanitized snapshots, static pages, a public API and an anonymous traffic channel — nothing more.
  • AENET Core — The private AENET ecosystem. It is never publicly routable and may export only sanitized public snapshots to aenet-cloud-public through the snapshot contract.
  • AENET Spine — A private AENET Core system (spine). Public evidence is limited to its presence as a private, unreachable topology node (core-spine).
  • Public API — The read-only public API v1 of AENET Cloud Public. It serves public status, time, architecture, development queue, roadmap and early access — with a strictly bounded surface.
  • Public Snapshot Layer — The layer that publishes sanitized, pre-generated JSON snapshots (site, status, architecture, articles, roadmap, queue, topology, traffic summary) from public-data/.

Related research

  • Watch-only Bitcoin Architecture — How a local-first, watch-only Bitcoin wallet observes receive and transfer-intent state without ever placing private keys on an online, publicly reachable surface.
  • PSBT Offline Signing — How transfer intents become unsigned PSBTs, cross the signing boundary, and are signed and validated without the online wallet domain ever holding a private key.

Questions people ask

These questions are answered by the content on this page.

  • What is the AENET Wallet?
  • Is the AENET Wallet publicly reachable?
  • How does the wallet sign transactions without exposing private keys?

Evidence

Verified states only — nothing on this page is a prediction.

  • public-data/wallet/README.md
  • public-data/wallet/overview.json
  • knowledge/wallet/wallet.json
  • ARCHITECTURE.md
  • PUBLIC_BOUNDARY.md

Next step