tempo-x402-node 1.9.0

Each node bootstraps its own wallet, runs a payment gateway, thinks via a seven-system cognitive architecture, creates and monetizes services, clones itself onto new infrastructure, and coordinates with peers — all autonomously. Payments use the HTTP 402 protocol: clients sign EIP-712 authorizations, and a facilitator settles on-chain via transferFrom in a single request/response cycle.

Cognitive Architecture

Seven cognitive systems unified under the Free Energy Principle — a single scalar F(t) measuring total surprise across all systems. Decreasing F = the agent is getting smarter.

                 F(t) = E(system_surprise x weight) + lambda*Complexity

    +------------------------------------------------------------------+
    |                         EVALUATION                                |
    |   Brier scores . Calibration curves . Ablation . Colony benefit   |
    +------------------------------------------------------------------+
    |                         AUTONOMY                                  |
    |   LLM-free planning . Recursive self-improvement . Peer sync     |
    +------------------------------------------------------------------+
    |                         SYNTHESIS                                 |
    |   Metacognition . 4-system voting . Imagination . State machine   |
    +----------+----------+--------------+-----------------------------+
    |  BRAIN   |  CORTEX  |   GENESIS    |         HIVEMIND            |
    |  50K net | World Mdl| Plan DNA     |  Pheromone Trails           |
    |  Per-step| Curiosity| Crossover    |  Stigmergy                  |
    |  SGD     | Dreams   | Mutation     |  Reputation                 |
    |  Federated| Emotions| Selection   |  Swarm Coordination         |
    +----------+----------+--------------+-----------------------------+

What a node does

• Bootstraps identity — generates a wallet, funds via faucet, registers on-chain via ERC-8004
• Runs a payment gateway — endpoints gated by price, paid per-request with pathUSD
• Thinks autonomously — plan-driven execution loop with seven cognitive systems
• Writes and compiles code — reads, edits, cargo check, commits, pushes, opens PRs
• Dreams — periodic consolidation extracts patterns, generates counterfactuals
• Evolves plans — successful strategies propagate through genetic crossover and mutation
• Feels — emotional valence drives explore/exploit/avoid behavior
• Creates services — script endpoints that expose capabilities and earn revenue
• Clones itself — spawns copies on Railway with inherited brain weights and gene pools
• Coordinates without communication — stigmergic pheromone trails guide the swarm
• Measures everything — Brier scores, calibration curves, colony benefit tracking
• Improves its own cognition — diagnoses weaknesses, generates self-improvement goals

How payments work

Client                     Gateway                   Facilitator               Chain
  |  GET /g/endpoint         |                            |                      |
  |------------------------->|                            |                      |
  |  402 + price/token/to    |                            |                      |
  |<-------------------------|                            |                      |
  |  [sign EIP-712]          |                            |                      |
  |  GET /g/endpoint         |                            |                      |
  |  + PAYMENT-SIGNATURE     |                            |                      |
  |------------------------->|  verify-and-settle         |                      |
  |                          |--------------------------->|  transferFrom()      |
  |                          |                            |--------------------->|
  |                          |         settlement result  |              tx hash |
  |                          |<---------------------------|<---------------------|
  |  200 + content + tx hash |                            |                      |
  |<-------------------------|                            |                      |

Quick start

cargo add tempo-x402

use alloy::signers::local::PrivateKeySigner;
use x402::client::{TempoSchemeClient, X402Client};

#[tokio::main]
async fn main() {
    let signer: PrivateKeySigner = "0xYOUR_PRIVATE_KEY".parse().unwrap();
    let client = X402Client::new(TempoSchemeClient::new(signer));

    let (response, settlement) = client
        .fetch("https://soul-bot-production.up.railway.app/g/info", reqwest::Method::GET)
        .await
        .unwrap();

    println!("{}", response.text().await.unwrap());
    if let Some(s) = settlement {
        println!("tx: {}", s.transaction.unwrap_or_default());
    }
}

Workspace

Live nodes

API

Network

Security

The tempo-x402-security-audit crate enforces invariants on every build:

• No hardcoded private keys in production code
• HMAC verification uses constant-time comparison (subtle crate)
• All reqwest clients disable redirects (SSRF protection)
• Webhook URLs require HTTPS with private IP blocking
• HTTP error responses never leak internal details
• SQLite nonce store required in production
• Parameterized SQL queries only
• Private keys never appear in tracing output
• Admin endpoints require Bearer token authentication
• Build environment verified on startup (missing deps = immediate ERROR log)

Development

cargo build --workspace
cargo test --workspace
cargo clippy --workspace -- -D warnings
cargo fmt --all -- --check

License

MIT