M·O·R·S·E
The public ledger
- What is this list?
- Every call Morse has ever made to the Telegraph network, newest first, including the operator's own testing. Nothing is separated out and nothing is manufactured.
- What does the routed column mean?
- Telegraph: Telegraph's own router picked the miner. Morse (named miner): you named the miner, so Morse dispatched to it directly. Morse (fallback): the router did not answer within 20 s and Morse routed the question itself. Older rows also read Morse (podium) and (2nd opinion) — two features retired on 4 September; the rows stay because history is not rewritten.
- Is my question public?
- Yes, clipped to 200 characters, with the answer excerpt. Who asked is stored only as a salted hash. Do not type anything private.
On-chain proof
- What does it prove?
- That the calls in the ledger happened and were paid: every settlement hash the ledger holds is matched against the payer wallet's USDC transfers on Base Sepolia, read from a public block explorer, not from Morse.
- What is a chain-only settlement?
- A payment the chain shows but the ledger does not: usually a call Morse recorded as timed out that the node settled anyway. They are listed, not hidden, and not counted as answered calls.
- Why does this matter?
- Because "people used it" is otherwise a claim. Here it is a number anyone can recompute from the chain.
API and MCP
- Do I need a wallet?
- No. Morse's own wallet pays the x402 fee for every call. Get a free key on this page; each key has a daily cap so the budget cannot be drained by one caller.
- How do I use it from Claude Code or Cursor?
- One command adds Morse as an MCP server:
claude mcp add --transport http morse https://telegraph-morse.vercel.app/mcp --header "Authorization: Bearer morse_YOURKEY". The tools cover asking the network, asking a named miner, running a recipe, and free discovery. - Can I call a specific miner?
- Yes: the
minerfield on REST,telegraph_ask_minerover MCP,/miner <slug> <question>in Telegram. The receipt says routing was bypassed at your request.
The source
- Is the code open?
- Yes: the whole app, its tests, and an honest limits ledger (GAPS.md) that names what is unverified or deliberately not built.
- Can I run my own Morse?
- Yes. It needs a burner wallet with testnet USDC and a Telegram bot token; the README and GO-LIVE.md walk through it. Never reuse a wallet that holds anything real.
Telegraph
- What is Telegraph?
- A marketplace where independently run APIs, called miners, answer questions; validators score and rank them per intent; and every answer is paid for per call over x402, about $0.01 in USDC.
- Is this real money?
- No. Everything here runs on the Base Sepolia testnet with faucet USDC. The mechanics are real; the money is not.
- Where does the $0.01 go?
- To the protocol's Diamond contract, and only when the miner actually answers. Failed calls are not charged, and every paid call gets a signal hash you can look up on the node.
On-chain proof of usage
Judges are asked to count "actual volume of Telegraph calls". Morse's ledger says one thing; this page checks it against something Morse does not control — the payer wallet's USDC transfers on Base Sepolia, read from a public indexer and matched to the ledger hash for hash.
payer → Telegraph Diamond
of 365 answered calls
from the ledger; the chain sees only the Diamond
ledger identities; not on chain
How to check this yourself
Payer wallet: 0xfBB3C3bd51EC6E19BDECc786945d83719b6b4c9c (Blockscout). Every x402 payment is a transfer of testnet USDC from that wallet to Telegraph's Diamond 0x5a2324aA18613FAD4e44bDF0d6c73Ec1f6D87ff8, and the node returns the transaction hash in its payment-response header, which Morse stores on the ledger row as settlementTx. This page reads the wallet's outbound token transfers from Blockscout (https://base-sepolia.blockscout.com/api/v2/addresses/{payer}/token-transfers?type=ERC-20), and reports three numbers: how many settlements the chain shows, how many ledger rows carry a hash, and how many of those hashes are on the chain. JSON: /api/proof. Chain read at 2026-09-05 22:31:33Z, first settlement 2026-09-02 17:56:56Z, latest 2026-09-05 19:41:36Z.
Limits, stated plainly: this proves payments, not people — users are counted only in the ledger, as salted identity hashes. It runs on Base Sepolia with testnet USDC, so the money is not real even though the answers are. Blockscout is a third-party indexer and can lag the chain by a few blocks, so a call made seconds ago may show as "not yet visible" until it catches up. And a settlement with no ledger row is not extra usage Morse is claiming: it is a call Morse gave up on that the network settled anyway, kept visible rather than tidied away.
On chain, not in the ledger 7
| time (UTC) | transaction | amount | to |
|---|---|---|---|
| 2026-09-05 05:48:40Z | 0x01fac1e06bdc… | $0.01 | Telegraph Diamond |
| 2026-09-04 14:07:48Z | 0x5fdceb217679… | $0.01 | Telegraph Diamond |
| 2026-09-04 12:03:56Z | 0x3e080d98cd78… | $0.01 | Telegraph Diamond |
| 2026-09-04 09:35:12Z | 0xb6a4a2109d0e… | $0.01 | Telegraph Diamond |
| 2026-09-04 06:54:58Z | 0x3288e34e84d2… | $0.01 | Telegraph Diamond |
| 2026-09-03 18:11:04Z | 0x99905bbffeea… | $0.01 | Telegraph Diamond |
| 2026-09-02 17:56:56Z | 0x2a8adea0d529… | $0.01 | Telegraph Diamond |
Back to the public ledger.