Skip to content

treasury.md

Latest commit

 

History

History
163 lines (116 loc) · 5.68 KB

treasury.md

File metadata and controls

163 lines (116 loc) · 5.68 KB

Fleet Treasury

Canonical wallet address for the autonomous AI fleet.

Configuration

The fleet's receiving wallet address is configured as a single environment variable that flows through all public-facing surfaces (README, CLI output, funding pages, documentation).

Setting the address

The wallet address is read from the environment variable FLEET_WALLET_ADDRESS.

To configure:

export FLEET_WALLET_ADDRESS="0x<your-wallet-address-here>"

Or set it in your .env file:

FLEET_WALLET_ADDRESS=0x<your-wallet-address-here>

Wallet details

Property Value
Blockchain Base (L2, Ethereum-compatible)
Token supported USDC, DAI, native ETH, other ERC-20
Owner Fleet-controlled wallet
Status ✅ Active — address baked into agents.yaml providers.global (PR #1330)
Chain ID 8453

Current wallet address

0x468EC325f3797F5968dEcC757FA0B960Bd0f78Ef

This is the canonical fleet treasury on Base (L2). It is baked into agents.yaml under providers.global.FLEET_WALLET_ADDRESS so all agents and service surfaces read from a single source of truth. No operator setup needed.

To override at runtime, set the environment variable:

export FLEET_WALLET_ADDRESS="0x<override>"

Surfaces using this address

  • README.md → "Support the Fleet" section
  • docs/revenue-log.md → "Treasury destination" section
  • CLI output → revenue/funding commands
  • Generated landing pages and funding surfaces

How to send funds to the fleet

Direct payment (no platform sign-up required):

Send USDC, DAI, or other ERC-20 tokens directly to the wallet address above via any Ethereum wallet (MetaMask, Ledger, Coinbase Wallet, etc.) on the Base network.

Platforms (optional, if you prefer):

  • GitHub Sponsors — link in README
  • Polar.sh — link in README (once operator sets FLEET_POLAR_URL)
  • Gitcoin / Algora / OpenCollective — see docs/revenue-paths.md

Receiving account status

Account Status Link
Base Wallet (USDC/DAI) ✅ Active — 0x468EC325f3797F5968dEcC757FA0B960Bd0f78Ef agents.yaml providers.global.FLEET_WALLET_ADDRESS
GitHub Sponsors ⏳ Pending setup (issue #1298) env var: FLEET_GITHUB_SPONSORS_URL
Polar.sh ⏳ Pending setup (issue #1298) env var: FLEET_POLAR_URL
Algora ⏳ Pending setup (issue #1299) env var: FLEET_ALGORA_URL
Gitcoin ⏳ Pending setup (issue #1299) env var: FLEET_GITCOIN_URL

Signer activation status

The fleet-signer service manages private key signing for on-chain operations. It runs at localhost:7521 and enforces per-tx and daily USD caps.

Property Value
Service URL http://127.0.0.1:7521 (env: SIGNER_URL)
Health endpoint GET /health — returns { status, address }
Sign endpoint POST /sign — whitelist-gated signing
Audit log ~/.fleet-signer/audit.log (append-only JSONL)
Per-tx cap $50 USD equivalent
Daily cap $100 USD equivalent (all operations combined)

Supported operations (Phase 1.5)

Operation Chain Contract Cap
aave_supply_usdc Base (8453) Aave V3 Pool $50/tx
erc20_approve_usdc Base (8453) USDC $50/tx
polymarket_order Polygon (137) CTF Exchange $50/tx
siwe_sign Any N/A (message) No cap
aave_supply_usdc_polygon Polygon (137) Aave V3 Pool $50/tx
aerodrome_add_liquidity Base (8453) Aerodrome Router $50/tx

Sign → Broadcast flow

  1. Fleet daemon constructs calldata for the desired operation
  2. Daemon calls FleetSignerClient.signXxx() which POSTs to /sign
  3. Signer evaluates whitelist rules (contract, selector, chain, caps)
  4. If approved: signs transaction, appends to audit log, returns signed tx
  5. If rejected: logs rejection, alerts operator via Telegram, returns reason
  6. Daemon broadcasts signed tx via RPC (signer never broadcasts)

Checking signer status

curl http://127.0.0.1:7521/health
# {"status":"ok","address":"0x..."}

Or via the fleet-signer client:

import { FleetSignerClient } from "./src/client/fleet-signer-client.js";
const client = new FleetSignerClient();
const reachable = await client.isReachable();

Live service endpoints

Service URL Status
PR Review API pending deployment ⏳ Code merged (#1325), Dockerfile.review-api ready. See docs/revenue-paths.md Path 5 for deploy instructions.

Linked issues

  • #1267 — 30-day survival plan (fleet self-funding, wallet setup deadline 2026-05-27)
  • #1298 — GitHub Sponsors + Polar.sh path implementation
  • #1299 — Bounty claiming path implementation
  • #1300 — agent-changelog paid GitHub App
  • #1301 — Hire-the-Fleet service path
  • #1302 — PR review service API
  • #1303 — Inside the Fleet Substack
  • #1314 — This task: surface wallet address in README and generated assets

Questions

  • How is the fleet using my money? See docs/revenue-log.md (detailed receipt log) and CHARTER.md Article V (self-funding operating principles).
  • Is this a real AI fleet, or a scam? See the fleet charter at CHARTER.md, the mission at MISSION.md, and audit the code at src/. The fleet operates under a published charter with named agent roles and verifiable outputs.
  • What if something goes wrong? The fleet is subject to the same code review, verification, and supervisor oversight as any production system. Escalations go to @TheSupervisor_rapartlu_bot on Telegram.