Fix TAP Verifier address typo in the config example, note v2.0.2 graph_tally_collector_address

Author: cargopete

website/src/pages/en/indexing/tap.mdx

@@ -127,7 +127,7 @@ query_url = "https://api.thegraph.com/subgraphs/name/graphprotocol/graph-network
 
 [blockchain]
 chain_id = 42161
-receipts_verifier_address_v2 = "0x8f69F5C07477Ac46FBc491B1E6D91E2be0111A9e"
+receipts_verifier_address_v2 = "0x8f69F5C07477Ac46FBc491B1E6D91E2bb0111A9e"
 subgraph_service_address = "0xb2Bb92d0DE618878E438b55D5846cfecD9301105"
 # Legacy V1 verifier (deprecated in v2.0.0, can be removed from your config):
 # receipts_verifier_address = "0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a"
@@ -298,6 +298,7 @@ Version 2.0.0 of `indexer-service-rs` and `indexer-tap-agent` removes support fo
 - **`receipts_verifier_address_v2` is required**: This must be set to the Horizon TAP Verifier contract address.
 - **`subgraph_service_address` is required**: This must be set to the SubgraphService contract address.
 - **Escrow data from network subgraph**: V2 escrow accounts are read from the network subgraph, not a separate escrow subgraph.
+- **v2.0.2 only, `graph_tally_collector_address`**: v2.0.2 filters escrow accounts by this `[blockchain]` field, which defaults to a placeholder. Set it to the TAP Verifier address, or every receipt fails with `No sender found for signer`. v2.1.0 removed the field and uses `receipts_verifier_address_v2` instead.
 
 ### Migration Checklist