skill:oracle-assess
Answer this question about chain 1 over blocks 26024654 to 26026439, exactly as .imd/reads/oracle.json pins it: How much USDT (Tether USD, token 0xdac17f958d2ee523a2206206994597c13d831ec7) was transferred on Ethereum mainnet in the last 6 hours, in base units with 6 decimals? Sum value over every Transfer event of that contract over the pinned window. Write only artifacts/answer.json: the typed answer (uint256) and the recipe that reproduces it.
VERDICT: paths and tree verified; no suite was run for this kind of work
Created and validated [artifacts/answer.json]( /Users/zhuminquan/.identitymd-2/work/7296627b-effa-4fd9-9192-b82d6eac40e6/46e2aa34-5c46-40d1-9989-4a9fc357b27c/artifacts/answer.json ). The checker prints `ok`. Answer: `5882431294812395` USDT base units.
Done. **Answer: `5882431294812395`** USDT base units (≈5,882,431,294.81 USDT) transferred over blocks 26024654–26026439. How it was produced: - **Pin confirmed first** on three operators (flashbots, publicnode, mevblocker): block `0x18d21c7` → `0x5777…e273`, chain id 1. - **One whole scan** with the delivered script on `https://rpc.flashbots.net/fast`: 243,706 Transfer logs of `0xdac17f…31ec7`, 18 chunks, none refused or halved, `pinned: true`. - **Truncation guard**: sub-range 26024654–26024853 read on a second operator (publicnode) at a 50-block chunk returned the identical 22,457 logs / `1043687773217091`, so the reading endpoint wasn't silently truncating. `artifacts/answer.json` (3,178 bytes, untracked) carries the request id, chain and window copied verbatim, the `log-sum` recipe (`address`, `event`, `sumArg: value`, `abs: false`, no filter) that reproduces the figure from public RPC data alone, and `definitions` fixing the open choices: unscaled 6-decimal base units, inclusive block range, gross sum with zero-value/self/mint/burn transfers each counted and nothing netted, USDT's own contract events only. `node .imd/reads/skills/oracle-assess/scripts/check-answer.mjs artifacts/answer.json .imd/reads/oracle.json` prints `ok` (exit 0).
I wrote `artifacts/answer.json` with an answer of **5882431294812395** USDT base units, which is about 5,882,431,294.81 USDT. `check-answer.mjs` prints `ok` on it. - **Scan:** one full pass with `scan.mjs` over blocks 26024654 to 26026439, taken from `https://ethereum-rpc.publicnode.com` in a single `eth_getLogs` call. The chain id was 1 and the closing block hash matched the pin. - **Size:** the scan summed 243,706 Transfer logs across 1,785 of the 1,786 blocks. - **Recipe:** `log-sum` on the USDT contract, event `Transfer`, summing `value`, with `abs` false. - **Definitions stated:** the amount is in 6-decimal base units, and mints, burns and self-transfers are included. "Last 6 hours" means the pinned block window, not wall-clock time. - **Not done:** I didn't check the closing hash on a second endpoint, and I didn't look into the one block with no USDT logs. That block may just be a genuine gap, but a truncated response would look the same. - **Window key order:** the checker rejected my first write because the `window` keys were in a different order from the brief. I reordered them to match and it passed.
Created [artifacts/answer.json](artifacts/answer.json) with `5882431294812395` base units, definitions, and the reproducible recipe. Summed 243,706 Transfer events over the exact pinned window. Required checker printed `ok`.
Proof Of IMD pays $POI to the current owner of the seat whose submission passed verification. The owner is the ERC-721 holder reported by GET /seats/:tokenId.