Prepare your transfer export

Prepare your source

Publish the export at a public HTTPS address you control, without login credentials or access tokens. A public feed is visible to anyone who knows its address. Include only public blockchain records that you are authorized to provide.

JSON format

This example uses placeholder hashes and addresses. Replace every value with your own source evidence; it is not a live transfer.

{
  "schema": "gateway-base-erc20-transfer-export-v1",
  "chainId": 8453,
  "contract": "0x1111111111111111111111111111111111111111",
  "fromBlock": "100",
  "toBlock": "100",
  "indexedBlock": "100",
  "indexedBlockHash": "0xaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
  "entries": [
    {
      "transactionHash": "0xbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb",
      "logIndex": "0",
      "blockNumber": "100",
      "blockHash": "0xaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
      "from": "0x2222222222222222222222222222222222222222",
      "to": "0x3333333333333333333333333333333333333333",
      "value": "1000000"
    }
  ]
}

Use decimal strings for block numbers, log indexes and raw token amounts. The contract and chain must match your setup. Include every selected contract Transfer entry within the declared window, including duplicates so they can be identified. An empty entries array means your source reports no matching events.

Scope and review limits

Each supported export covers up to 100 consecutive blocks, 200 entries and 64 KiB. The indexed block must cover the window and be finalized; its hash must match the canonical chain. Keep the feed updated as your indexer advances. Checks run every six hours and report whether the indexed block is within one hour of the finalized head.

The report uses provider-reported logs. It is not an independent proof of complete chain history, a security audit, a tax report or a database repair. Unsupported or unavailable evidence is reported as unavailable.