zeekay baddf8096e fix(api): the db package could not import — define the models it declares
`bootnode/db/__init__.py` imported and re-exported three names that models.py
does not define, so `import bootnode.db` raised ImportError on main. Every
consumer died with it: the e2e job's init_db(), the nodes API, the MPC API, the
keys API, the seed. Prod is unaffected only because it runs image 1.0.1, built
before this landed.

It was invisible because test-api ran

    pytest -v --tb=short || echo "No tests yet"

The `|| echo` makes the step exit 0 unconditionally, so CI reported GREEN while
every test module failed to import. That mask is removed; CI can fail honestly.

The consequence was not subtle: docker-release triggers on
`workflow_run: ["CI"] completed`, CI was red, so the image build was SKIPPED
every time — which is why the deployed web image sat at 0.0.1-web from June
while main moved on.

  Cluster        → renamed OrgCluster at some point; call sites updated.
                   The `"kind": "Cluster"` CRD strings are correct and untouched.
  Node           → never existed in ANY revision (checked back to 2026-01-26).
                   Defined here from the contract the code already declares.
  MPCWalletModel → likewise. Distinct from SmartWallet, which is ERC-4337
                   account abstraction, not threshold signing.

Design, in the terms asked for:

DECOMPLECTED — Node stores DESIRED state only. Sync progress, peer count, block
height, cpu/memory, uptime and the backing pod are facts about the cluster, and
fleet_manager already reads them from the Cluster CR. A copy in this table would
be a second source of truth, stale the instant it is written. That split is why
the model is small; it is the spec half of the spec/status pair the CRD layer
already uses, not a new idea.

TYPED — status/node_type/sync_mode are closed Enums at both the Python and the
column level, not free strings. This class of bug was live: the seed wrote
"running" while NodeStatus offers pending/init/starting/bootstrapping/healthy/
unhealthy/terminated — provably DISJOINT sets, so the dashboard's
`filter(n => n.status === "running")` could never match a backend value and
"active nodes" was structurally always 0. One vocabulary now, defined once in
fleet_models and imported everywhere; seed and both frontend call sites moved
onto it.

SMALL INTERFACE — two properties (`is_serving`, `slug`) and a repr. Everything
else is a column read. No cleverness to undo later.

Flagged, not silently reproduced: MPCWalletModel.encrypted_shares holds key
material in the database. It is encrypted, but the standing rule is that secrets
live in KMS. That column is a migration target, documented in the model.

Verified: `import bootnode.db` succeeds, all three enums resolve, every seed
status value is a member of NodeStatus, web tsc 0 errors, web build exits 0.
2026-07-26 13:49:23 -07:00
2026-02-10 14:57:33 -08:00
2026-02-04 23:30:31 -08:00
2026-06-28 20:10:22 -07:00
2026-02-04 23:30:31 -08:00
2026-02-04 23:30:31 -08:00
2026-02-04 23:30:31 -08:00

bootnode

Bootnode

Web3 Backend in a Box - Run locally or deploy to cloud.

Go rewrite (HIP-0106) in progress. The current production service is the Python FastAPI app under api/. A Go scaffold that mounts into superbase per HIP-0106 lives alongside it — api/, cmd/bootnode/, schema/, zap/. See docs/PYTHON_TO_GO_PORT.md for the endpoint-by-endpoint port map and the new Go README section below.

Quick Start

docker compose up -d

Done. Your Web3 backend is running:

Features

API Description
POST /v1/rpc/{chain} Multi-chain JSON-RPC proxy
WS /v1/ws/{chain} Real-time blockchain subscriptions
GET /v1/tokens/{chain}/balances/{address} Token balances & metadata
GET /v1/nfts/{chain}/owned/{address} NFT ownership & metadata
POST /v1/webhooks Event-driven notifications
POST /v1/wallets/create ERC-4337 smart wallets
POST /v1/bundler/{chain} UserOp bundling
POST /v1/gas/sponsor Gas sponsorship

Supported Chains

L1: Ethereum, BNB Chain, Avalanche, Solana, Bitcoin

L2: Arbitrum, Optimism, Base, Polygon, zkSync, Scroll, Linea, Blast

Development

# API (Python 3.12+)
cd api && uv sync && uvicorn bootnode.main:app --reload --port 8000

# Dashboard (Node 22+)
cd web && pnpm install && pnpm dev

Deploy

Self-hosted

docker compose -f docker-compose.prod.yml up -d
# or
kubectl apply -f infra/k8s/

Hanzo Cloud

hanzo deploy

Visit web3.hanzo.ai for managed hosting.

License

Apache-2.0

Go rewrite (HIP-0106)

The Go subsystem mounts into superbase (the unified Hanzo Cloud binary). It exposes a single Mount(r chi.Router, deps api.Deps) error entry point and a public ZAP schema (schema/bootnode.zap) covering every cross-subsystem type.

bootnode/
  schema/bootnode.zap           # public typed surface (ZAP)
  zap/gen/                      # zapc-generated Go (hand-stubs today)
  api/                          # subsystem code (chi handlers + store)
    mount.go                    # HIP-0106 contract
    deps.go                     # IAM/KMS/Base/O11y/Commerce interfaces
    handlers/                   # one MountXxx per FastAPI route group
    middleware/                 # auth, telemetry, rate-limit
    store/                      # per-tenant SQLite via deps.Base
    web3/                       # chain registry + RPC pool
  cmd/bootnode/main.go          # standalone dev shim
  docs/PYTHON_TO_GO_PORT.md     # endpoint-by-endpoint mapping

Build

go build ./...
go vet ./...
go run ./cmd/bootnode    # listens on :8100 (BOOTNODE_ADDR to override)

Generate ZAP bindings

cd zap && make gen       # no-op if zapc isn't installed

zapc lives at ~/work/hanzo/zap/zapc-rs/. Brand policy: no .capnp files, no "Cap'n Proto" references on the public surface (HIP-0106).

S
Description
No description provided
Readme
6.3 MiB
Languages
TypeScript 47.2%
Python 38.2%
Go 6.5%
Rust 4.2%
Shell 1.5%
Other 2.4%