Amanat

Signed weather intelligence that a contract acts on by itself.

Signed, not "verified": the network's own verified: true cannot be checked from outside (bug report), so every answer here carries an Ed25519 signature over the fields a contract settles on, and anyone can check it with Node and nothing else:

node -e 'const c=require("node:crypto");fetch("https://amanat-miner.vercel.app/forecast?lat=10.32&lon=123.89&hours=6").then(r=>r.json()).then(({attestation:a})=>console.log(c.verify(null,Buffer.from(a.canonical),c.createPublicKey({key:Buffer.from(a.public_key,"base64"),format:"der",type:"spki"}),Buffer.from(a.signature,"base64"))))'

The key it checks against is the one published at /.well-known/amanat.json.

An amanat is a message entrusted to be carried — and, in the language of the old telegraph offices, the dispatch itself. That is the whole shape of this project: a miner sends the amanat, a scoring module tests it, and a contract carries it out without anyone deciding anything by hand.

Built for Telegraph Hackathon Season I. One codebase, three entries:

Live: amanat-miner.vercel.app — read a storm risk for any point, no wallet, no sign-up. It is the same call the contract makes before it spends anything.

In one line, from any MCP client: npx -y amanat-mcp — published to npm and listed in the official MCP registry as io.github.PugarHuda/amanat.

In three minutes: the deck · the film (84 s, cut from live sessions — no mockups) · /api/jobable, which measures how many intents are closed to on-chain jobs, how many are open, and how many cannot be audited at all because their leader publishes its registration at 127.0.0.1. Add ?intent=STORM_ALERT for a verdict on your own.

Track	What	Where
1 — Miner	Weather and storm-risk miner, answers legible to both a text scorer and a smart contract	miner/
2 — Script Author	Measurement-grounded WASM scoring module for Tier A intents	scorer/
3 — Application	Parametric cover settled through ERC-8183 on-chain jobs, a CLI, and an MCP server	onchain/, agent/, app/, mcp/

---

The three problems this is built around

Everything here comes from measuring the live network rather than guessing at it. The numbers below are reproducible with the scripts in this repo.

1. Deterministic intents are scored as if they were prose. In epoch 240 the rank-1 miner on WEATHER_CHECK scored 0.0206 and on STORM_ALERT 0.0067. The miners are not bad; every scoring module on the network compares text, and those miners answer with numbers. A leaderboard built from those scores is noise — and routing follows the leaderboard.

2. The on-chain rail is real but unused. The Diamond answers getJobBasePrice() with 1000000 and, on 21 August, carried 139 miner registrations against 6 ERC-8183 jobs in its entire lifetime — the last two by a single participant, on 17 August. In a 77-hour window there were 44 MinerRegistered events and 2 JobCreated. Meanwhile the organisers name on-chain intelligence pipelines as the highest-value thing to build.

Read again on 31 August: 341 miner registrations, and still only 14 jobs. Eight of the fourteen are ours. Five settled; the last three have not moved.

3. Almost no miner can receive a job at all. A job hands the node raw OnChainData arrays; without an on_chain.request block in its YAML the node cannot turn those into an HTTP call. npm run audit fetches every registered YAML and checks. On 31 August: of 125 live miners, 29 declare an on_chain block at all, and a name-hashable intent has between one and three job-able miners — STORM_ALERT has exactly one, and it is this one. That is the bottleneck under problem 2, and it has loosened rather than closed: on 21 August there were 63 live miners and every name-hashable intent had a single job-able miner.

What the network actually looks like (read from /api/epochs, /api/validators and the Diamond, 21 August): epochs run hourly on testnet, not the 24 hours the docs describe. Each one scores 70 results across 17 intents and 29 of the 66 registered miners — more than half are never scored at all. There is one active validator, telegraph-node-1, so the 43-of-64 BFT threshold is a mainnet property, not something running today.

The shape held; the size did not. At epoch 294 on 30 August the network scored 242 results across 42 intents and all 125 live miners, and epochs had stopped being hourly — the last five landed 3 to 9 hours apart. Still one validator.

---

Track 1 — the miner

miner/server.mjs reads three free, keyless sources and returns every answer in two shapes at once. Open-Meteo's weather model gives the air; its marine model gives significant wave height, which is the thing that actually stops a ship and the one figure the shipping-lane board was missing; and GDACS gives every active named tropical cyclone on Earth with its position and maximum wind, so a reading under Tropical Storm Dolly says so by name rather than reporting "38 km/h wind". Storm risk is the worst of wind, gusts, rain, waves and cyclone proximity — a 4 m sea or a typhoon overhead reaches the ceiling on its own.

This is the beginning of the README. Read the rest at the original. Read the full README ↗