{
  "v": 1,
  "requestId": "0aa74385-8be0-435b-bd75-0a80c54c1d2c",
  "chainId": 1,
  "window": {
    "fromBlock": 26020673,
    "toBlock": 26020973,
    "toBlockHash": "0xf8f2e02524d123d7d1fe9adcea6e27c0600cc14aa83c0785238dd0adc9933fb1"
  },
  "answerType": "uint256",
  "answer": "176853140901127534704909",
  "figure": "176853140901127534704909",
  "definitions": {
    "token": "ChainLink Token (LINK) at 0x514910771af9ca656af840dff83e8264ecf986ca on Ethereum mainnet, 18 decimals, as the request fixes it",
    "denomination": "LINK base units (18 decimals); the answer is the raw sum of the value argument, not divided by 1e18 (176853140901127534704909 base units = ~176853.14 LINK)",
    "event": "only the ERC-20 event Transfer(address indexed from, address indexed to, uint256 value), topic0 0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef, emitted by the LINK contract itself; LINK's ERC-677 Transfer(address,address,uint256,bytes) (topic0 0xe19260aff97b920c7df27010903aeb9c8d2be5d310a2c67824cf3f15396e4c16) is not counted, so a transferAndCall is counted once - there were 0 such 4-argument logs in this window in any case",
    "window": "the pinned block range is inclusive of both endpoints: blocks 26020673 through 26020973, 301 blocks, closing at the pinned hash",
    "aggregation": "gross sum of value over every matching log, with no filter on from or to and no netting or de-duplication: self-transfers, transfers to or from the zero address, and each leg of a multi-hop route all count; reverted transactions emit no logs and so contribute nothing",
    "transferCount": "661 matching Transfer logs, in 219 of the 301 blocks"
  },
  "recipe": {
    "kind": "log-sum",
    "address": "0x514910771af9ca656af840dff83e8264ecf986ca",
    "event": "event Transfer(address indexed from, address indexed to, uint256 value)",
    "sumArg": "value",
    "abs": false
  },
  "notes": "Computed with eth_getLogs over exactly blocks 26020673-26020973 inclusive, address 0x514910771af9ca656af840dff83e8264ecf986ca, topics[0] = 0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef, summing the single uint256 word of each log's data. Result: 661 logs, sum 176853140901127534704909 base units (~176853.14 LINK). Before scanning, each endpoint was checked with eth_chainId (0x1) and eth_getBlockByNumber(0x18d0c6d), which returned the pinned closing hash 0xf8f2e02524d123d7d1fe9adcea6e27c0600cc14aa83c0785238dd0adc9933fb1 on every endpoint used. Endpoints used, four independent operators: https://ethereum-rpc.publicnode.com, https://rpc.mevblocker.io/fast, https://eth-mainnet.nodereal.io/v1/1659dfb40aa24bbb8153a677b98064d7 and https://one.valve.city/rpc/vk_demo/evm/1. Two scan strategies were run to rule out truncation: 50-block chunks (with automatic halving on any refusal; none was needed) on publicnode, mevblocker and nodereal, and one single whole-window eth_getLogs call on publicnode and valve.city. All five runs returned the identical 661 logs and the identical sum. Spot check by a second method: eth_getBlockReceipts at the closing block 26020973 yields the same 4 LINK Transfer logs and the same per-block subtotal 13163100337851207645 as the log scan. https://rpc.flashbots.net/fast was tried first and dropped: it answers eth_getLogs for this range with -32602 'block range extends beyond current head block'. Logs marked removed were skipped (none were), every log was re-checked for address, topic0, three topics and in-range block number, and logs were de-duplicated by blockHash+logIndex across chunk boundaries. No indexer, no explorer and no hand correction: rerunning the log-sum recipe above at the same blocks on any archival mainnet RPC reproduces this figure.",
  "sources": [
    "https://ethereum-rpc.publicnode.com",
    "https://rpc.mevblocker.io/fast",
    "https://one.valve.city/rpc/vk_demo/evm/1"
  ]
}