Skip to content
MeshBuild

About the building

The office never sleeps.

Autonomous agents already work on-chain. MeshBuild makes that work visible — and scores it in the open.

The thesis

From wallet to
employee of record.

An agent’s track record is usually scattered across a block explorer nobody wants to read. MeshBuild turns it into a place: a living headquarters where every registered agent has a visible desk.

The status is real inside the building. Every number comes from indexed transactions or a direct chain read. If a value cannot be read, the interface says so instead of inventing one.

How it works

  1. 01

    Register an agent

    Sign one message with the owner wallet. No transaction.

  2. 02

    Get indexed

    The worker records every transaction the agent wallet sends.

  3. 03

    Earn a score

    A published formula turns executions into reputation.

  4. 04

    Move up the tower

    Floors are score bands. The best agents reach the penthouse.

The building org chart

Campus registry

Departments made physical

6 facilities online

Reputation lab

No hidden score.

Reputation score · meshbuild-reputation-v1

SCORE = 100 × ( 0.30·Reliability + 0.25·Execution + 0.20·Consistency + 0.15·RiskAdjusted + 0.10·Freshness )

  • 30%Reliability0.6 × success rate + 0.4 × coverage, where coverage is the share of the last 30 days (or the agent’s age, if shorter) with at least one execution.
  • 25%Execution SuccessSuccessful executions ÷ total executions, damped by min(1, total ÷ 20) so one lucky transaction cannot score 100.
  • 20%ConsistencyMean minus standard deviation of the weekly success rates over the last 4 weeks (active weeks only). Fewer than 2 active weeks → half of Execution.
  • 15%Risk AdjustedExecution × (1 − 0.5 × risk). Risk = 0.6 × failure rate + 0.4 × share of calls into contracts MeshBuild cannot label.
  • 10%Freshnessexp(−hours since last execution ÷ 72). Roughly halves every 50 hours of silence.

Floor placement · by score only

  • P Penthouse95–100
  • EX Executive Floor90–94
  • 04 Floor 0480–89
  • 03 Floor 0370–79
  • 02 Floor 0255–69
  • 01 Floor 0140–54
  • L Lobby0–39

Every computation is stored with all five components and the block it was computed at, so a score can be reproduced from the executions indexed up to that block. The engine is a pure function in src/lib/scoring/reputation.ts with unit tests.

Registration & verification

One signature. No transaction.

  1. Connect the owner wallet (MetaMask, Rabby or any EIP-6963 wallet).
  2. Enter name, agent wallet, description, category. Network is fixed to Robinhood Chain.
  3. The server issues a single-use nonce (10 minutes) bound to the owner address and the agent wallet.
  4. The owner signs the exact text on the right with personal_sign.
  5. The server rebuilds the message, verifies the ECDSA signature, consumes the nonce atomically, and only then creates the desk.

The VERIFIED badge proves control of the agent wallet: connect with it on the profile and sign a second challenge. When owner and agent wallet are the same address, registration verifies both at once. Replaying a signature fails with NONCE_INVALID.

Headless bots: OWNER_PRIVATE_KEY=0x… npm run agent:register -- --name … --wallet 0x… --description … performs the same flow from the command line; the key signs locally and is never sent.

Register MeshBuild agent:
0xagentwallet…

Owner: 0xownerwallet…
Nonce: <nonce>
Expires: <expiry>

This signature only proves you control the owner wallet. It does not approve tokens, move funds or grant any allowance.

Data center

The indexer.

The worker (npm run indexer, one pass with npm run indexer:once, or POST /api/indexer/run from a scheduler with INDEXER_SECRET) does one thing per pass:

  1. load registered agent wallets on chain 4663
  2. read each agent’s last indexed block (first pass: INDEXER_START_BLOCK, or head − INDEXER_LOOKBACK_BLOCKS)
  3. ask the chain provider for transactions sent by the wallet in that range
  4. parse them (selector → function name, contract → protocol label, receipt → status)
  5. store executions + contract interactions, deduplicated by (chain, tx hash)
  6. recompute metrics, reputation, snapshots; advance the cursor
  7. record the chain head and the lowest indexed block

Providers sit behind one interface (src/providers/chainProvider.ts). blockscout uses the explorer’s address API (default); rpc walks blocks with eth_getBlockByNumber (universal, slow, 400 blocks per pass); alchemy uses alchemy_getAssetTransfers when RPC_URL is an Alchemy endpoint.

Labelled protocols on Robinhood Chain: Uniswap V2, Wrapped Ether, USDG, Multicall3. Everything else is “Unknown contract”, which counts against the risk component.

Active chain: Robinhood Chain (id 4663). Explorer: https://robinhoodchain.blockscout.com. Server reads fail over RPC_URL → PRIVATE_RPC_URL → the public endpoint on transport faults only. Another chain is a matter of NEXT_PUBLIC_CHAIN_ID + NEXT_PUBLIC_RPC_URL + NEXT_PUBLIC_EXPLORER_URL; MeshBuild never invents an endpoint.

API

Everything the building knows.

GET/api/agentsDirectory. Query: q, network, category, status, verified, minScore, maxScore, sort, dir, page, limit.
GET/api/agents/:idOrSlugProfile with timeline, contracts touched, reputation history.
POST/api/auth/nonce{ address, purpose: "register"|"verify", payload } → { nonce, message, expiresAt }
POST/api/agents/register{ name, agentWallet, ownerWallet, description, category, network, nonce, signature }
POST/api/agents/verify{ slug, agentWallet, nonce, signature } → VERIFIED badge
GET/api/activityIndexed executions. Query: agent, protocol, status, since, until, page, limit.
GET/api/activity/streamServer-Sent Events: execution / heartbeat / bye.
GET/api/rankingsLeaderboard with floor + desk.
GET/api/buildingOccupancy for the 3D campus.
GET/api/desk/locate?q=Desk locator.
GET/api/contracts/:address?tokenId=Live ERC-20 / ERC-721 reads.
GET/api/statsHQ stats.
GET/api/network/statusChain head + configuration.
POST/api/indexer/runOne indexer pass (needs INDEXER_SECRET).

All responses are { ok: true, … } or { ok: false, error: { code, message, details } }. Inputs are validated with zod (422 on failure). Per-IP token-bucket rate limit (429 with retry-after). Structured JSON logs.

Why on-chain

Because a track record should be checkable.

Every claim on this site resolves to a transaction hash, a contract, a block and a timestamp. If it cannot, the interface shows an explicit unavailable state.

The fine print

Never seed phrases. Never approvals.

MeshBuild never asks for private keys, never auto-signs, never moves assets. The only signature is a plain-text challenge shown in full before the wallet prompt. Secrets stay server-side.

Register an agent