docs(tap): update GraphTally guide for post-Horizon

   - Remove legacy V1 content (contracts,
   separate escrow subgraph)
   - Add Graph Horizon context and link to
   overview
   - Simplify to Horizon-first configuration with
    horizon.enabled = true
   - Add GraphOps gateway aggregator endpoint
   - Document operator_mnemonics for key rotation
   - Streamline architecture overview and getting
    started
   - Remove migration framing in favor of current
    setup guide

Author: suchapalaver

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

@@ -2,182 +2,149 @@
 title: GraphTally Guide
 ---
 
-Learn about The Graph's new payment system, **GraphTally** [(previously Timeline Aggregation Protocol)](https://docs.rs/tap_core/latest/tap_core/index.html). This system provides fast, efficient microtransactions with minimized trust.
+Learn about The Graph's payment system, **GraphTally** [(previously Timeline Aggregation Protocol)](https://docs.rs/tap_core/latest/tap_core/index.html). GraphTally provides fast, efficient microtransactions with minimized trust.
 
 ## Overview
 
-GraphTally provides the following key features:
+GraphTally is the payment system for The Graph, integrated into the core protocol through [Graph Horizon](/graph-horizon/overview). It enables efficient pay-per-query payments between gateways and indexers.
 
-- Efficiently handles micropayments.
-- Adds a layer of consolidations to onchain transactions and costs.
-- Allows Indexers control of receipts and payments, guaranteeing payment for queries.
-- Enables decentralized, trustless gateways and improves indexer service performance for multiple senders.
+Key benefits:
 
-### How It Works
+- **Efficient micropayments**: Pay-per-query without high transaction costs
+- **Reduced onchain costs**: Receipts aggregate into single blockchain transactions
+- **Payment guarantees**: Indexers control receipt aggregation, ensuring payment for served queries
+- **Trustless operation**: Decentralized gateways with cryptographic verification
 
-GraphTally allows a sender to make multiple payments to a receiver through **Receipts**, which are then aggregated into a single payment called a **Receipt Aggregate Voucher (RAV)**. This aggregated payment can be verified on the blockchain, reducing the number of transactions and simplifying the payment process.
+## How It Works
 
-For each query, the gateway sends a signed receipt that is stored in your database. The `indexer-tap-agent` aggregates these receipts into RAVs through periodic requests. You can update a RAV by sending it with newer receipts, which generates a new RAV with an increased value.
+GraphTally enables a sender (gateway) to make multiple payments to a receiver (indexer) through **Receipts**, which aggregate into a **Receipt Aggregate Voucher (RAV)**. RAVs can be verified and redeemed on the blockchain.
+
+**Payment flow:**
+
+1. Gateway sends a signed receipt with each query
+2. `indexer-service-rs` validates and stores receipts in your database
+3. `indexer-tap-agent` periodically aggregates receipts into RAVs
+4. RAVs accumulate value as new receipts arrive
+5. After allocation closure, the final RAV is redeemed onchain
 
 ### RAV Details
 
-- RAVs represent money waiting to be sent to the blockchain.
-- The system continuously aggregates receipts to ensure that the total value of non-aggregated receipts does not exceed the configured `max_amount_willing_to_lose_grt`.
-- Each RAV can be redeemed once in the contracts, which is why they are sent after the allocation is closed.
+- RAVs represent pending payments waiting for blockchain redemption
+- The system aggregates receipts continuously, keeping unaggregated value below `max_amount_willing_to_lose_grt`
+- Each RAV redeems once onchain, so final RAVs are created after allocation closure
 
 ### Redeeming RAVs
 
-The redemption process is fully automated when running both `indexer-tap-agent` and `indexer-agent`:
+RAV redemption is fully automated when running `indexer-tap-agent` and `indexer-agent`:
 
-1. An Indexer closes an allocation.
-2. After the `recently-closed-allocation-buffer` period, `indexer-tap-agent` takes all pending receipts for that allocation and requests aggregation into a final RAV, marking it as `last`.
-3. `indexer-agent` takes all the last RAVs and sends redeem requests to the blockchain, updating the `redeem_at` value.
+1. Indexer closes an allocation
+2. After the `recently-closed-allocation-buffer` period, `indexer-tap-agent` aggregates remaining receipts into a final RAV marked as `last`
+3. `indexer-agent` submits redeem transactions to the blockchain
 4. During the `finality-time` period, `indexer-agent` monitors for blockchain reorganizations:
-   - If the transaction was reverted, the RAV is resent to the blockchain.
-   - If not reverted, it gets marked as `final`.
-
-## Blockchain Addresses
+   - Reverted transactions are resubmitted
+   - Confirmed transactions are marked `final`
 
-### Contracts
+## Gateway Addresses
 
-| Contract            | Arbitrum Mainnet (42161)                     | Arbitrum Sepolia (421614)                    |
-| ------------------- | -------------------------------------------- | -------------------------------------------- |
-| TAP Verifier        | `0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a` | `0xfC24cE7a4428A6B89B52645243662A02BA734ECF` |
-| AllocationIDTracker | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` |
-| Escrow              | `0x8f477709eF277d4A880801D01A140a9CF88bA0d3` | `0x1e4dC4f9F95E102635D8F7ED71c5CdbFa20e2d02` |
-
-### Gateway
-
-| Component  | Edge and Node Mainnet (Arbitrum Mainnet)      | Edge and Node Testnet (Arbitrum Sepolia)      |
+| Component  | Arbitrum Mainnet                              | Arbitrum Sepolia (Testnet)                    |
 | ---------- | --------------------------------------------- | --------------------------------------------- |
 | Sender     | `0xDDE4cfFd3D9052A9cb618fC05a1Cd02be1f2F467`  | `0xC3dDf37906724732FfD748057FEBe23379b0710D`  |
 | Signers    | `0xfF4B7A5EfD00Ff2EC3518D4F250A27e4c29A2211`  | `0xFb142dE83E261e43a81e9ACEADd1c66A0DB121FE`  |
 | Aggregator | `https://tap-aggregator.network.thegraph.com` | `https://tap-aggregator.testnet.thegraph.com` |
 
-## Prerequisites
-
-In addition to typical indexer requirements, you'll need a `tap-escrow-subgraph` endpoint to query escrow information. You can use The Graph Network to query or self-host on your `graph-node`:
-
-- [Graph TAP Arbitrum Sepolia Subgraph (for The Graph testnet)](https://thegraph.com/explorer/subgraphs/7ubx365MiqBH5iUz6XWXWT8PTof5BVAyEzdb8m17RvbD)
-- [Graph TAP Arbitrum One Subgraph (for The Graph mainnet)](https://thegraph.com/explorer/subgraphs/4sukbNVTzGELnhdnpyPqsf1QqtzNHEYKKmJkgaT8z6M1)
-
-> Note: `indexer-agent` does not currently handle the indexing of this Subgraph like it does for the Network Subgraph deployment. You must index it manually.
-
-## Migration Guide
+## Getting Started
 
 ### Software Requirements
 
-#### Required Versions
-
-- **indexer-agent**: [Latest version supporting TAP](https://github.com/graphprotocol/indexer/releases)
+- **indexer-agent**: [Latest version](https://github.com/graphprotocol/indexer/releases)
 - **indexer-service-rs**: [Latest release](https://github.com/graphprotocol/indexer-rs/releases?q=indexer-service-rs)
 - **indexer-tap-agent**: [Latest release](https://github.com/graphprotocol/indexer-rs/releases?q=indexer-tap-agent)
 
-#### Docker Images
+### Docker Images
 
 ```bash
-# Indexer Service
 docker pull ghcr.io/graphprotocol/indexer-service-rs:latest
-
-# TAP Agent
 docker pull ghcr.io/graphprotocol/indexer-tap-agent:latest
 ```
 
-### Migration Steps
+### Architecture Overview
 
-#### 1. Update Indexer Agent
+Your indexer stack consists of:
 
-- Continue using your existing `indexer-agent`
-- Add the `--tap-subgraph-endpoint` argument to enable TAP functionality and RAV redemption
-- Example: `--tap-subgraph-endpoint https://api.thegraph.com/subgraphs/name/graphprotocol/tap-mainnet`
+- **indexer-service-rs**: Handles incoming queries, validates receipts, routes to graph-node. Stateless and horizontally scalable.
+- **indexer-tap-agent**: Aggregates receipts into RAVs. Run exactly **one instance**.
+- **indexer-agent**: Manages allocations and redeems RAVs onchain.
 
-#### 2. Replace Indexer Service
+All three components share the same PostgreSQL database.
 
-- Fully replace your TypeScript indexer-service with `indexer-service-rs`
-- The new service is stateless and can be scaled horizontally
-- Use the same database as your existing setup
+### Configuration
 
-#### 3. Deploy TAP Agent
+Both `indexer-service-rs` and `indexer-tap-agent` use a shared TOML configuration file. Pass it with `--config /path/to/config.toml`.
 
-- Run exactly **one instance** of `indexer-tap-agent`
-- This component manages receipt aggregation and RAV creation
-- It must have access to the same database as other indexer components
-
-#### 4. Configuration
-
-Both `indexer-service-rs` and `indexer-tap-agent` share a TOML configuration file. Create a configuration file and pass it with `--config /path/to/config.toml`.
-
-##### Minimal Configuration Example
+#### Configuration Example
 
 ```toml
-# Essential configuration for indexer-rs components
-# All values below must be updated to match your setup
-
 [indexer]
 indexer_address = "0x1111111111111111111111111111111111111111"
 operator_mnemonic = "your twelve word mnemonic phrase here ..."
 
+# For key rotation, you can specify multiple mnemonics:
+# operator_mnemonics = [
+#     "current mnemonic phrase here",
+#     "previous mnemonic if you rotated keys"
+# ]
+
 [database]
-# Use the same database as your indexer-agent
 postgres_url = "postgresql://user:password@localhost:5432/indexer_db"
 
 [graph_node]
-# Your graph-node endpoints
 query_url = "http://graph-node:8000"
 status_url = "http://graph-node:8000/graphql"
 
 [subgraphs.network]
-# The Graph Network Subgraph (use query_url OR deployment_id, not both)
+# The Graph Network Subgraph (includes escrow data)
+# Use query_url for hosted service, or deployment_id for local indexing (recommended)
 query_url = "https://api.thegraph.com/subgraphs/name/graphprotocol/graph-network-arbitrum"
 # deployment_id = "QmUVskWrz1ZiQZ76AtyhcfFDEH1ELnRpoyEhVL8p6NFTbR"
 
-[subgraphs.escrow]
-# TAP Escrow Subgraph (use query_url OR deployment_id, not both)
-query_url = "https://api.thegraph.com/subgraphs/name/graphprotocol/tap-arbitrum-one"
-# deployment_id = "QmPcbDomKwfsmVBNbvncU8gdWTvUiH9zVFYxDMc5ohpjvU"
-
 [blockchain]
-# For Arbitrum mainnet
 chain_id = 42161
 receipts_verifier_address = "0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a"
 
-# For Arbitrum Sepolia testnet, use:
+# For testnet:
 # chain_id = 421614
 # receipts_verifier_address = "0xfC24cE7a4428A6B89B52645243662A02BA734ECF"
 
 [tap]
-# Maximum GRT amount to risk before requiring aggregation
-# Use string format to prevent rounding errors
 max_amount_willing_to_lose_grt = "0.1"
 
 [tap.sender_aggregator_endpoints]
-# Gateway endpoints for RAV aggregation
-# Mainnet
+# Mainnet gateways
 "0xDDE4cfFd3D9052A9cb618fC05a1Cd02be1f2F467" = "https://tap-aggregator.network.thegraph.com"
+"0xDD6a6f76eb36B873C1C184e8b9b9e762FE216490" = "https://tap-aggregator-arbitrum-one.graphops.xyz"
 
-# For testnet, use:
+# For testnet:
 # "0xC3dDf37906724732FfD748057FEBe23379b0710D" = "https://tap-aggregator.testnet.thegraph.com"
+
+[horizon]
+enabled = true
 ```
 
-##### Environment Variable Overrides
+#### Environment Variable Overrides
 
-You can override any configuration value using environment variables:
+Override any configuration value using environment variables:
 
 ```bash
 # Pattern: [PREFIX]__[SECTION]__[KEY]
-# PREFIX can be INDEXER_SERVICE or TAP_AGENT
+# PREFIX: INDEXER_SERVICE or TAP_AGENT
 
-# Examples:
 export INDEXER_SERVICE__DATABASE__POSTGRES_URL="postgresql://..."
 export TAP_AGENT__TAP__MAX_AMOUNT_WILLING_TO_LOSE_GRT="0.5"
-export INDEXER_SERVICE__BLOCKCHAIN__RECEIPTS_VERIFIER_ADDRESS="0x..."
 ```
 
-##### Advanced Configuration
-
-For all configuration options, see:
+#### Advanced Configuration
 
-- [Full configuration example](https://github.com/graphprotocol/indexer-rs/blob/main/crates/config/maximal-config-example.toml)
+- [Full configuration reference](https://github.com/graphprotocol/indexer-rs/blob/main/crates/config/maximal-config-example.toml)
 - [Default values](https://github.com/graphprotocol/indexer-rs/blob/main/crates/config/default_values.toml)
 
 ### Logging
@@ -190,9 +157,6 @@ export RUST_LOG=indexer_service=info,indexer_tap_agent=info
 
 # For debugging
 export RUST_LOG=indexer_service=debug,indexer_tap_agent=debug
-
-# TAP-specific debugging
-export RUST_LOG=indexer_tap_agent=debug,info
 ```
 
 ## Monitoring
@@ -213,9 +177,9 @@ Key metrics to monitor:
 
 ### Grafana Dashboard
 
-Import the [official Grafana dashboard](https://github.com/graphprotocol/indexer-rs/blob/main/docs/dashboard.json) for comprehensive monitoring of:
+Import the [official Grafana dashboard](https://github.com/graphprotocol/indexer-rs/blob/main/docs/dashboard.json) for monitoring:
 
-- TAP receipt flow and aggregation status
+- Receipt flow and aggregation status
 - RAV creation and redemption lifecycle
 - System performance and error rates
 - Database query performance
@@ -230,7 +194,7 @@ Common issues and solutions:
    - Review debug logs for specific error messages
 
 2. **Receipts not aggregating**:
-   - Ensure `tap-agent` is running (only one instance)
+   - Ensure `indexer-tap-agent` is running (only one instance)
    - Check database connectivity
    - Verify `max_amount_willing_to_lose_grt` is not too high
 
@@ -243,17 +207,15 @@ Common issues and solutions:
 
 ### Docker Compose
 
-Example compose configuration for both services:
+Example compose configuration:
 
 ```yaml
-version: '3.8'
-
 services:
   indexer-service:
     image: ghcr.io/graphprotocol/indexer-service-rs:latest
     ports:
-      - '7600:7600' # Service port
-      - '7300:7300' # Metrics port
+      - '7600:7600'
+      - '7300:7300'
     volumes:
       - ./config.toml:/config.toml
     command: ['--config', '/config.toml']
@@ -264,7 +226,7 @@ services:
   tap-agent:
     image: ghcr.io/graphprotocol/indexer-tap-agent:latest
     ports:
-      - '7301:7300' # Metrics port (different host port)
+      - '7301:7300'
     volumes:
       - ./config.toml:/config.toml
     command: ['--config', '/config.toml']
@@ -291,7 +253,7 @@ For Kubernetes deployments, see the [Graph Launchpad charts](https://github.com/
 
 2. **High Availability**:
    - Run multiple `indexer-service-rs` instances behind a load balancer
-   - Keep `tap-agent` as a single instance with proper monitoring
+   - Keep `indexer-tap-agent` as a single instance with proper monitoring
    - Use database connection pooling
 
 3. **Security**: