> FETCHING JOB RECORD
skill:oracle-assess
Answer this question about chain 56 over blocks 123188258 to 123196252, exactly as .imd/reads/oracle.json pins it: How much USDT (Tether USD, token 0x55d398326f99059ff775485246999027b3197955) was transferred on BNB Smart Chain in the last 1 hours, in base units with 18 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
Wrote `artifacts/answer.json` with the reproducible recipe. Total: **434347604440932709557643337** base units across **904,392 Transfer events** in the exact pinned range. Required checker returned `ok`.
Created [artifacts/answer.json](/Users/peterhucik/.identitymd/work/992562b4-2924-49ff-b894-5f185cd1b05b/7fae9eea-e6e9-4a56-87aa-f5ea92b1da8b/artifacts/answer.json). Answer: `434347604440932709557643337` base units. Validation passed: `check-answer.mjs` printed `ok`.
Answer: **434347604440932709557643337** USDT base units (≈434,347,604.44 USDT) over 904,392 Transfer logs in blocks 123188258–123196252, pin confirmed. Checker: `ok`.
I wrote `artifacts/answer.json`, and `check-answer.mjs` prints `ok` for it. **Answer:** `434347604440932709557643337` USDT base units, about 434.35M USDT. That is the sum of `value` over all 904,392 `Transfer` logs from `0x55d398326f99059ff775485246999027b3197955` in blocks 123188258–123196252 on chain 56. **Recipe:** `log-sum` on that address, with event `Transfer(address indexed from, address indexed to, uint256 value)`, `sumArg: value` and `abs: false`. **How I checked it:** - I ran `scan.mjs` against `https://bsc-rpc.publicnode.com`. It confirmed chain id 56 and the pinned closing block hash. - The scan script can't tell when an endpoint silently cuts a response short. So I ran the scan a second time with smaller ranges (20 blocks per call instead of 50). The log count and the sum were identical. - I confirmed the closing block hash on a second provider, `https://bsc.drpc.org`, which returned the same hash. - The first `check-answer.mjs` run failed only because my `window` keys were in a different order from the brief. I reordered them to match, and the rerun printed `ok`. **Definitions I set, stated under `definitions`:** - The pinned block range stands in for "the last 1 hours". - Every `Transfer` log counts, including mints, burns and self-transfers. - Values are summed raw, with no netting or deduplication. No other file was changed; `git status` shows nothing, so `answer.json` is not committed and is left for the daemon to upload.
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.