{
  "v": 1,
  "requestId": "7d89e084-d45a-435b-9e97-ffe98075b2ac",
  "chainId": 56,
  "window": {
    "toBlock": 123196255,
    "fromBlock": 123188260,
    "toBlockHash": "0x83085dab5d565e70767e214710aeb088208df9ec6c81e46f178609605298d5c7"
  },
  "answerType": "uint256",
  "answer": "57749965339546136106174413",
  "figure": "57749965339546136106174413",
  "definitions": {
    "token": "Only logs emitted by 0x8ac76a51cc950d9822d68b83fe1ad97b32cd580d (Binance-Peg USD Coin on BNB Smart Chain) are counted; no other USDC representation and no wrapper or bridge contract is included.",
    "event": "ERC-20 Transfer(address indexed from, address indexed to, uint256 value), topic0 0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef. Transfers made without emitting this event are not observable and are not counted.",
    "transferred": "The gross sum of the value argument over every such log. No netting, no deduplication of the legs of one transaction, no exclusion of self-transfers, and no exclusion of mints or burns (transfers from or to 0x0000000000000000000000000000000000000000); abs is irrelevant because value is a uint256.",
    "denomination": "Base units of the token, 18 decimals, as the question states; this token's decimals() is 18, so the figure is also the raw on-chain value. 57749965339546136106174413 base units is about 57,749,965.34 USDC.",
    "window": "Blocks 123188260 through 123196255 inclusive on both ends, exactly as pinned: 7996 blocks, timestamps 2026-09-21T13:21:18Z to 2026-09-21T14:21:18Z, one hour. Nothing outside the pinned range was read, and the phrase \"the last 1 hours\" was taken to mean exactly this pinned range.",
    "logs": "Logs marked removed were dropped and any log repeated by the provider was counted once, keyed by block number and log index."
  },
  "recipe": {
    "kind": "log-sum",
    "address": "0x8ac76a51cc950d9822d68b83fe1ad97b32cd580d",
    "event": "event Transfer(address indexed from, address indexed to, uint256 value)",
    "sumArg": "value",
    "abs": false
  },
  "notes": "Computed with the delivered scan script, once, whole:\n\nnode .imd/reads/skills/oracle-assess/scripts/scan.mjs --rpc https://public-bsc-mainnet.fastnode.io --from 123188260 --to 123196255 --pin 0x83085dab5d565e70767e214710aeb088208df9ec6c81e46f178609605298d5c7 --address 0x8ac76a51cc950d9822d68b83fe1ad97b32cd580d --event \"Transfer(address,address,uint256)\" --sum data:0 --chunk 1000 --concurrency 3\n\nIt reported chainId 56, toBlockHash 0x83085dab5d565e70767e214710aeb088208df9ec6c81e46f178609605298d5c7 with pinned true, 107408 logs over 7901 blocks in 8 chunks of 1000 blocks with no refusal or halving, and sum 57749965339546136106174413. value is the first (and only) data word of the event, so --sum data:0 is the recipe's sumArg \"value\".\n\nEndpoints used. https://public.1rpc.io/bnb was tried first from the catalogue row and abandoned: it caps eth_getLogs at 50 blocks and then answers \"limit exceeded\", which is exactly the truncation-and-refusal case the reference warns about. Endpoints probed and rejected for the scan: https://rpc.swiftnodes.io/rpc/bsc (500-block cap), https://api.zan.top/bsc-mainnet (429), https://bsc.rpc.sentio.xyz (too many results), https://bsc.drpc.org (400), https://bsc-mainnet.public.blastapi.io (429), https://bsc.meowrpc.com (429), https://bsc-dataseed1.bnbchain.org and https://binance.nodereal.io (limit exceeded). The scan ran wholly on https://public-bsc-mainnet.fastnode.io, which refuses an over-large query rather than truncating it (its cap is 20000 results per query; the largest chunk here stayed under it, and no chunk was refused). Before trusting the figure I checked the chain id and the pinned closing block on two endpoints from other operators, https://bsc-rpc.publicnode.com and https://rpc-bsc.48.club: both returned chain id 0x38 and the same hash for block 123196255, with timestamp 2026-09-21T14:21:18Z against 2026-09-21T13:21:18Z for block 123188260, so the pinned window is the stated hour. As a cheap consistency check during endpoint probing, the first 1000 blocks of the window returned an identical log count of 12352 on five independent endpoints (thirdweb, fastnode, publicnode, pocket, 48.club, nodereal), which is what a truncated read would not do. No second full scan was run: the deployer reruns the recipe.\n\nThe question left nothing material open beyond the sense of \"transferred\"; the gross, non-netted reading stated under definitions is the obvious one for \"sum value over every Transfer event\" and is what the log-sum recipe reruns."
}