BizNode — Decentralized Node Network

Node Identity

Every BizNode has a unique cryptographic identity. No usernames, no passwords — just math.

🔑

Ed25519 Keypair

On first boot, your node generates an Ed25519 private/public keypair stored in identity/node_private.pem and identity/node_public.pem. The private key never leaves your machine.

📱

QR Code Identity Card

Your node's public key, name, and endpoint are encoded into a scannable QR code. Share it with other node operators to establish a peer connection instantly.

🔏

Cryptographic Authentication

Every node-to-node request is signed with the sender's private key. The receiving node verifies the signature against the known public key. Impersonation is mathematically impossible.

Identity Endpoints

GET  /api/identity/card        # Export your node's identity card
POST /api/identity/import       # Import a peer node's identity card
GET  /api/mcp-keys              # List all known peer public keys
POST /api/mcp-keys/generate     # Generate a new keypair

Health Monitoring

The MainNode continuously monitors every registered node in the network. If a node goes down, the network knows immediately.

💚

Health Pings

MainNode sends periodic GET /api/health requests to every registered node. Response time, status code, and version are recorded for each ping.

📉

Uptime Tracking

Each node's uptime percentage is calculated from historical pings. Online/offline status, average latency, and last-seen timestamp are available in the admin dashboard.

🚨

Alert System

When a node goes offline, the owner receives an email notification. When it comes back online, a recovery notification follows. Downtime windows are logged for SLA tracking.

Health API

GET  /api/admin/nodes/health    # Health status of all registered nodes
# Response:
{
  "nodes": [
    {
      "node_id": "biz_node_0a3f",
      "name": "Acme Consulting",
      "status": "online",
      "latency_ms": 142,
      "uptime_pct": 99.7,
      "last_seen": "2026-03-09T14:23:00Z"
    }
  ]
}

Service Routing

When one node's customer needs another node's service, the network routes the request, handles payment, and delivers the result — all automatically.

Cross-Node Service Flow

Step	Action	Detail
1	Customer Request	A customer on Node A asks for a service that Node A doesn't offer (e.g., legal review).
2	Service Discovery	Node A queries the network registry for nodes offering "legal review" and finds Node B.
3	DZIT Transfer	Node A's ledger is debited. Node B's ledger is credited. The DZIT price is agreed upon via the service catalogue.
4	Service Delivery	Node B processes the request using its local LLM, knowledge base, and tools. Result is returned to Node A.
5	BZeUSD Settlement	After confirmation, BZeUSD is transferred on-chain to Node B's Polygon wallet as the final settlement layer.

The customer sees a seamless experience. Behind the scenes, two autonomous AI agents coordinated, transacted, and settled — without human intervention.

Admin Dashboard

17 API endpoints give you full visibility and control over payments, credits, nodes, and wallets.

💳

Payment Tracking

View all Stripe payments, filter by category, check processing status. Endpoints: /api/admin/payments, /api/admin/payments/stats, /api/admin/stripe-links.

🪙

Credit Management

Check DZIT balances, add or deduct credits, view transaction history per user. Endpoints: /api/admin/dzit/balance, /api/admin/dzit/add, /api/admin/dzit/deduct.

🖥

Node Monitoring

List all registered nodes, check health status, view latency and uptime metrics. Endpoints: /api/admin/nodes, /api/admin/nodes/health.

💰

Wallet Verification

Check Polygon wallet balances, verify on-chain transactions, audit BZeUSD holdings. Endpoints: /api/admin/wallet/balance, /api/admin/wallet/transactions.

Network Architecture

The MainNode sits at the center of the network, coordinating health checks, service routing, and payment settlement. Child nodes operate autonomously but report to the MainNode for network-wide coordination.

Decentralized Node Network