# [CONSTITUTIONAL] AIP: Authorize Priority Gas Auctions and Establish the Fast Feed

- Space: [Arbitrum Core](https://snapshot.box/arb1:0xf07DeD9dC292157749B6Fd268E37DF6EA38395B9.md)
- Author: 0xb4c064f466931B8d0F637654c916E3F203c46f13
- State: Executed
- Voting type: Basic
- Start: 2026-08-20 20:18 UTC
- End: 2026-09-04 07:57 UTC
- Votes: 281
- Open in Snapshot: https://snapshot.box/#/arb1:0xf07DeD9dC292157749B6Fd268E37DF6EA38395B9/proposal/104933844856336554027758452704713321330340501652892001249184191934279866979282

## Results

- For: 100.0%
- Against: 0.0%
- Abstain: 0.0%

## Proposal

## Abstract

This AIP proposes to combine two separate actions into a single on-chain vote for the ArbitrumDAO to consider:

1. transitioning Arbitrum One's ordering policy from Timeboost to Priority Gas Auctions and sunsetting Timeboost on Arbitrum Nova; and
2. establishing the Fast Feed, a paid and authenticated data streaming product for Arbitrum One.

Both component proposals have completed separate Snapshot temperature checks:

- PGA Snapshot
- Fast Feed Snapshot

As a recap, adopting PGA would begin with disabling Timeboost on Arbitrum One, then activating priority fee collection and enabling the PGA ordering policy based on per-transaction priority fees. On Nova, Timeboost would simply be sunset, with no adoption of PGA.

Meanwhile, the Fast Feed activation would establish a paid, permissionless feed through which authenticated subscribers receive transactions and related metadata after those transactions have been ordered by the sequencer but before a complete block is published through the existing sequencer per-block feed.

This consolidated AIP preserves the mandates approved through the two temperature checks and incorporates the implementation updates identified after those votes. The on-chain proposal is atomic: delegates are voting on both components through one proposal and one combined execution payload.

## Motivation

### Priority Gas Auctions

Timeboost was launched on Arbitrum One in April 2025, a novel transaction ordering policy designed to put user fairness and spam reduction at the forefront while, for the first time, creating additional revenue to the ArbitrumDAO via Timeboost auction fees. While Timeboost has delivered meaningful benefits including user fairness, and a new revenue stream for the DAO, some structural considerations have also come to light that are worth addressing:

- Timeboost's architecture represents a large barrier of entry with emerging DeFi primitives such as Proprietary Automated Market Makers (propAMMs), which require cheap and frequent, low-latency, priority-ordered inclusion to update onchain parameters.
- Timeboost participation remains limited as many builders that entered the auction at launch exited. Additionally, the overhead to build a custom tool that would participate in an ahead-of-time auction increased the difficulty of adoption.

A fundamentally different model is needed and the more familiar ordering policy: Priority Gas Auctions (PGA) stands out as a clear option. PGA addresses the challenges above by making ordering determined by per-transaction `priorityFeePerGas` bids rather than a periodic, ahead-of-time express lane auction:

- Competition is distributed across every transaction and every block, making collusion structurally harder.
- PGA mechanics are well-understood by CEX-DEX arbitrageurs and MEV searchers operating on other chains (Ethereum, Solana, Base, OP Mainnet, Unichain), and propAMMs, lowering the barrier to entry for these participants.
- Additionally, we introduce an anti-starvation mechanism that helps facilitate that non-priority paying or low priority transactions get included within a couple of blocks. The exact wait time for a transaction is dependent on the selected parameters for the PGA round and the priority fee expressed in a transaction.

While ArbOS 61 Elara introduced the capability for Arbitrum chains to collect priority fees (via the `maxPriorityFeePerGas` field in EIP-1559 type 2 transactions), it deliberately did not enable this feature on Arbitrum One or Nova. It was clearly noted that enablement would require a separate Constitutional DAO vote. This proposal would enable the collection of priority fees.

### Fast Feed

The Fast Feed is designed to serve any ecosystem participant that benefits from earlier visibility into ordered transaction flow (including MEV searchers, Market Makers, propAMMs and latency-sensitive DeFi applications). Access to the Fast Feed is provided on a paid subscription basis, with the goal of using the proceeds to help ensure reliability and consistent feed performance for all subscribers.

The net revenue will be split between the ArbitrumDAO Treasury and the Arbitrum Developer Guild pursuant to the RewardDistributor contract deployed on-chain, following the same revenue split framework established by the Timeboost AIP (described further below).

## Rationale

### Priority Gas Auctions

A new transaction ordering policy offers the ArbitrumDAO an opportunity to continue to capture additional revenue that should not come at the expense of users; with the introduction of an anti-starvation mechanism that helps transactions with 0 or low priority fees get included. Transactions remain subject to paying the latest base fees.

Rather than capturing arbitrage opportunities by having the fastest hardware or bidding ahead-of-time, participants can win these opportunities by bidding in a just-in-time auction to gain priority ordering.

The priority auction is permissionless and participation is open to everyone, where transactions with the highest bids get included earlier within a 125ms PGA round, and ties are broken by arrival timestamp.

The ArbitrumDAO can configure all aspects of PGA, including enabling or disabling it, the auction's design, and how to handle proceeds.

#### Priority Fee Collection

A new contract, the `TipCollectionToggler`, will be deployed to grant Offchain the permissions needed to enable and disable priority fee collection. Through this contract, the ArbitrumDAO authorizes Offchain to activate PGA and priority fee collection at any point after the vote is fully executed onchain, for a period of 2 years.

This new contract has been audited by an independent third party (Trail of Bits); a full audit report is available here. Implementing this contract will allow Offchain to enable and disable priority fee collection, without the need for additional votes, should the ArbitrumDAO pass this proposal.

### Fast Feed

The Fast Feed distributes information from the sequencer as soon as the PGA round has completed, but because it is optional, supplemental, and costly to provide, it will be a paid product. Once ordering is resolved deterministically, that ordered stream carries clear economic value for latency-sensitive participants.

Rather than making this value reachable only by those who can co-locate or operate the fastest infrastructure, the Fast Feed packages access as a subscription product whose proceeds flow back to the ArbitrumDAO and the Arbitrum Developer Guild.

- **Open, not exclusive:** Access is paid but permissionless; any participant willing to subscribe can obtain access, subject to availability. Ticket holders from the previous round receive preferential access during a grandfather phase, in which they may renew before tickets are offered to new participants.
- **Ordering-neutral:** the feed does not change transaction ordering, inclusion guarantees, or the priority or transaction fees any user pays. It only changes the timing by which subscribers are able to observe the ordered stream of transactions.
- **Transparent, on-chain revenue:** proceeds are split through the RewardDistributor and enforced on-chain (97% to the ArbitrumDAO Treasury, 3% to the Arbitrum Developer Guild), with every payment and distribution emitted as an on-chain event for public audibility.
- **Consistent governance precedent:** revenue routing follows the framework established by Timeboost and the proposed transition to use PGA, keeping Arbitrum's ordering-related revenue products aligned.
- **The ArbitrumDAO retains control:** the ArbitrumDAO and, if the DAO permits, Offchain can configure the new feed payment parameters. The DAO alone can additionally control the revenue split.

## Key Terms

### Priority Gas Auctions

**Priority Fees:** are user-supplied ordering incentives paid in addition to the network's base transaction fee. Priority fees are denominated in Arbitrum's native gas unit and are paid directly to the ArbitrumDAO Treasury.

**Priority Gas Auction:** an auction in which multiple participants simultaneously submit transactions with their specified priority fees in order to secure preferential ordering by the sequencer.

### Fast Feed

**Fast Feed:** an authenticated, data stream that publishes the individual transactions, their relative ordering, and relevant metadata after they are ordered by the sequencer, available to paid subscribers.

**Sequencer Feed Endpoint:** the Fast Feed endpoint exposed by the sequencer by which authenticated subscribers can connect to for access to the Fast Feed.

**Fast Feed Payment Contract:** the audited smart contract on Arbitrum One that manages access to the Fast Feed. It manages sell access to the feed with pricing determined using the same pricing mechanism in EIP-4844.

**Subscription Credential:** the API key hash recorded by the Fast Feed Payment Contract upon payment, which the sequencer cross-references to admit or deny incoming feed connections.

**propAMM (Proprietary Automated Market Maker):** an automated market maker whose pricing relies on an external trusted price-pusher source to update quotes on-chain rather than relying solely on the constant-product curve and arbitrageurs. propAMMs are an emerging class of actors who offer attractive swap prices/quotes and usually bring their own liquidity on-chain to facilitate this.

## Specifications

### 1. Priority Gas Auctions (PGA)

We are formally introducing our Priority Gas Auction design, which will enable Arbitrum One users to affect their transaction ordering within a block by specifying a `maxPriorityFeePerGas` in each transaction. We added some modifications in the ordering mechanism to help facilitate that valid transactions with low or null priority fees are included in a timely manner by adding an anti-starvation boost to all transactions that remain in the mempool after a PGA round.

#### 1.1 How PGA Ordering Works

1. The sequencer receives a transaction and places it into a private mempool tagged with:
    1. a priority value `p` equal to its `priorityFeePerGas` bid, and
    2. an arrival timestamp (at the sequencer) in milliseconds for tie-breaking.
2. Based on the arrival timestamp (at the sequencer), transactions are slotted into PGA rounds. Transactions arriving during a running PGA round are held and enter the sequencer's mempool only at the start of the next PGA round. Depending on the block time of the chain, which we call B, the PGA round time is B/K, for some K chosen by the chain operator with permission from the DAO. On Arbitrum One, given the 250ms block time and a proposed value K = 2, the nominal PGA round duration is 125ms.
3. At the start of each round, all queued transactions are ranked in descending order of `priorityFeePerGas`, with ties broken by earliest arrival timestamp.
    1. The `priorityFeePerGas` is calculated as follows: `priority_fee_per_gas = min(transaction.max_priority_fee_per_gas, transaction.max_fee_per_gas - block.base_fee_per_gas)`
    2. Note: The sequencer collects the computed priority fee per gas according to EIP-1559.
4. Transactions are appended to a block greedily until: the Block Gas Limit of 32 Mgas is hit, the calldata limit of 95,000 bytes is reached, or the round expires. The effective block limit is 64 Mgas; individual transactions are capped at 32 Mgas. So, the effective block gas limit is (L+T), where L is the block gas limit and T is the transaction limit.
5. After each PGA round, if the mempool is non-empty, all waiting transactions receive a virtual priority boost (see section 1.2 for more details).
6. The sequencer will publish a regular block at 250 ms intervals and publishes ordered transactions within every 125ms round, via a new fast sequencer feed. In the case where a block is full before the 125ms are completed, the sequencer will start building the next block. Note: There is a limit of 8 blocks per 1 second that can be produced.

#### 1.2 Anti-Starvation: Priority Boost Mechanism

This mechanism helps facilitate that transactions with null or low priority fees will get included within a reasonable time. The mechanism works as follows:

- At the end of each round, all remaining transactions receive a virtual priority fee or boost, which gets calculated by adding `p / (2K)` to all waiting transactions in the mempool, where `p` is the priority of the last transaction included in the previous PGA round, and `K` is the number of rounds per block.
- This boost is a virtual ordering artifact only — it does not change the fee charged to senders.
- During the following PGA round, any transactions that were received in the previous PGA round that were not included in that round will be sorted by descending priority, taking into account the boost, before being appended to a block. This way, transactions that didn't get included in a previous PGA round due to a low/null priority fee get a virtual boost to facilitate their inclusion in the following PGA rounds.
- The sequencer will maintain a nonce cache for transactions with future nonces in the same fashion as it is currently done today, preserving their original priority for restoration when they re-enter the mempool. Transactions in the nonce cache will not receive the boost.

#### 1.3 Configuration Parameters

| Parameter | Default (Arbitrum One) | Configurable By | Notes |
| --- | --- | --- | --- |
| K (rounds per block) | 2 → 125ms rounds | Current sequencer operator, with permission from the DAO | Higher K = faster rounds up to a limit. Otherwise it becomes FIFO |
| Anti-starvation boost divisor | 2K | Implicitly set via K | Lower K = faster anti-starvation |

This AIP proposes granting Offchain, the current sequencer operator, the below rights to make the following adjustments from time to time for a period of 2 years. The rights described below are expected to only be exercised in circumstances where doing so would enhance PGA's long-term stability, preserve or improve the user experience for those using Arbitrum One, increase the security posture, resiliency, or stability of the chain, and/or otherwise help increase revenue for the ArbitrumDAO:

- The right to change the `K round` parameter, a value which determines the number of rounds per block. The starting default is 2 but adjustments could be to any value between [1 & 10], inclusive.

### 2. Timeboost Sunset

Upon passage of this AIP, the following steps will be applied to both Arbitrum One and Arbitrum Nova:

- Timeboost users that have funds locked in the Auction contract will be able to remove their deposits anytime.
- The Timeboost autonomous auctioneer will cease accepting new bids.
- The sequencer will cease enforcing the 200ms non-express lane delay for normal transactions (note that this delay only exists when there is a Timeboost Express Lane owner).
- The express lane endpoint will be decommissioned. Any transactions submitted to this endpoint after decommissioning will be rejected.
- Any collected funds from completed auctions can be flushed to the ArbitrumDAO's L2 Treasury Timelock contract at anytime, by anyone. Note that this is possible today as well.

Explicitly, this AIP only proposes sunsetting Timeboost on Arbitrum Nova and reinstating First-Come First-Served (FCFS) ordering; it does not propose adopting PGA as an ordering policy for Nova.

### 3. Fast Feed

We formally introduce the Fast Feed which consists of three components: 1) the Sequencer Feed Endpoint and payload, 2) the Subscription and Credential Management, and 3) the Payment Contract itself.

#### 3.1 Sequencer Feed Endpoint and Payload Schema

A new WebSocket endpoint that publishes individual transactions once they are ordered but before a full block is constructed and emitted from the regular feed. The endpoint is authenticated: only clients presenting a valid subscription credential are admitted. Note that the Fast Feed will only publish information about transactions after these transactions have been sequenced for execution.

The ordering cannot be influenced or changed past this point and, therefore, types of MEV like sandwiching or frontrunning should not be able to be performed.

Each transaction is wrapped in a `FeedMessage` envelope that provides ordering and timing metadata.

````json
{
  "FeedMessage": {
    "description": "Envelope wrapping each transaction with ordering and timing metadata.",
    "fields": {
      "version": {
        "description": "Protocol version for forward compatibility",
        "type": "uint32",
        "json_type": "number"
      },
      "timestamp_ms": {
        "description": "Unix timestamp in milliseconds when the sequencer created this message",
        "type": "uint64",
        "json_type": "number"
      },
      "pga_round": {
        "description": "Number of the PGA round for the current block",
        "type": "uint64",
        "json_type": "number"
      },
      "transaction": {
        "description": "Transaction data and incomplete receipt",
        "type": "IncludedTransaction",
        "json_type": "object",
        "fields": {
          "block_number": {
            "description": "Tentative block number (not guaranteed to be finalized)",
            "type": "uint64",
            "json_type": "number"
          },
          "tx_index": {
            "description": "Transaction position within the block so far",
            "type": "uint32",
            "json_type": "number"
          },
          "raw_tx": {
            "description": "RLP-encoded signed transaction",
            "type": "bytes",
            "json_type": "string (hex-encoded)"
          },
          "tx_hash": {
            "description": "Transaction hash",
            "type": "bytes32",
            "json_type": "string (hex-encoded)"
          },
          "receipt": {
            "description": "Execution result. Incomplete because the block is not yet finalized; does not include block_hash.",
            "type": "IncompleteReceipt",
            "json_type": "object",
            "fields": {
              "status": {
                "description": "1 = success, 0 = failure",
                "type": "uint8",
                "json_type": "number"
              },
              "gas_used": {
                "description": "Gas consumed by this transaction",
                "type": "uint64",
                "json_type": "number"
              },
              "gas_used_for_l1": {
                "description": "Gas attributable to L1 data costs (Arbitrum-specific)",
                "type": "uint64",
                "json_type": "number"
              },
              "cumulative_gas_used": {
                "description": "Cumulative gas used in the block up to this transaction",
                "type": "uint64",
                "json_type": "number"
              },
              "effective_gas_price": {
                "description": "Actual gas price paid (relevant for PGA priority fee analysis)",
                "type": "uint256",
                "json_type": "string (hex-encoded)"
              },
              "base_fee": {
                "description": "Current block base fee",
                "type": "uint256",
                "json_type": "string (hex-encoded)"
              },
              "contract_address": {
                "description": "Set only if the transaction created a contract",
                "type": "address (optional)",
                "json_type": "string (hex-encoded)"
              },
              "logs": {
                "description": "Event logs emitted during execution",
                "type": "[]Log",
                "json_type": "array of objects",
                "array_item_fields": {
                  "address": {
                    "description": "Emitting contract",
                    "type": "address",
                    "json_type": "string (hex-encoded)"
                  },
                  "topics": {
                    "description": "Indexed event fields",
                    "type": "[]bytes32",
                    "json_type": "array of strings (hex-encoded)"
                  },
                  "data": {
                    "description": "Non-indexed event data",
                    "type": "bytes",
                    "json_type": "string (hex-encoded)"
                  }
                }
              }
            }
          }
        }
      }
    }
  }
}
````

#### 3.2 Subscription and Credential Management

The Fast Feed Payment Contract governs subscription validity. Access to the Fast Feed is granted by successfully purchasing a ticket, effective at the end of the round in which the purchase is made. To purchase, a user submits a payment transaction to the Fast Feed Payment Contract that includes the Keccak-256 hash of their API key. The contract then records this hash as the user's Subscription Credential. To connect, the user presents their raw API key to the sequencer, which hashes it with Keccak-256 and cross-references the result against the recorded credentials to admit or deny the connection.

Credential rotation and subscription renewals are handled through direct interaction with the Fast Feed Payment Contract by the subscriber. Note: credentials can only be rotated when purchasing tickets in new rounds.

#### 3.3 Fast Feed Payment Contract

The Fast Feed Payment Contract is an audited smart contract that will be deployed on Arbitrum One. This contract will:

- Sell access to the feed with pricing determined using the same pricing mechanism in EIP-4844; market parameters are listed further below.
- Receive payments denominated in an ERC20, USD-backed stablecoin. We explicitly leave the asset selection to the Arbitrum Treasury Management (ATM) Council and OAT to ensure alignment with the portfolio's goals.
- Emit on-chain events for each subscription payment and distribution, enabling transparency and audibility of all revenue flows.
- Have 3 roles built-in:
    - `DEFAULT_ADMIN` → controlled by the ArbitrumDAO and has admin permissions to assign all other roles to accounts.
    - `BENEFICIARY_SETTER` → controlled by the ArbitrumDAO and has permissions to change the destination of the proceeds. This AIP proposes that this be set to the RewardDistributor contract address.
    - `MARKET_PARAMS_SETTER` → proposed to be controlled by Offchain and the ArbitrumDAO such that either entity can change the parameters in Table 1 below.
        - Note: parameter changes take effect at the next round, based on the initial value of the round duration there is a wait time of up to 24 hours.
- Send proceeds to the RewardDistributor contract, which automatically routes 97% of proceeds to the ArbitrumDAO and the remaining 3% to the Arbitrum Developer Guild.
    - the RewardDistributor contract will be deployed alongside the Fast Feed contract
    - 97% of proceeds will be sent to the L2 Treasury Timelock (`0xbFc1FECa8B09A5c5D3EFfE7429eBE24b9c09EF58`); 3% of proceeds will be sent to the Arbitrum Developer Guild (`0x6A075E9a02eef6978DD66cB63DE430a8c0C419E9`)

Both contracts have been independently audited by Trail of Bits prior to deployment: Fast Feed, RewardDistributor. All contract addresses will be documented in the Arbitrum One developer documentation post deployment.

Should this AIP pass, the DAO grants Offchain permission to change the Fast Feed Payment parameters listed below in Table 1. Note that the ArbitrumDAO may also change any of these parameters at any time via the `MARKET_PARAMS_SETTER` role in the Fast Feed Payment Contract described above.

#### Table 1: Fast Feed Payment Contract Parameters

| Parameter name | Description | Proposed default value |
| --- | --- | --- |
| Round duration (in hours) | Length of each sales round, the recurring period over which a fixed allotment of feed tickets is sold at a single uniform price before the mechanism re-prices and the next round opens. Also sets the cadence at which newly purchased tickets become active and prior-round tickets expire. | 24 |
| Target tickets per-round | The per-round sales volume the pricing curve targets, analogous to EIP-4844's target blob count. | 100 |
| Maximum tickets per round | Hard limit on feed tickets sold in any single round. | 200 |
| Minimum price (in USD) | The price floor for a ticket. | 17 |
| Price update fraction | Sensitivity of the EIP-4844-style pricing curve, analogous to the blob base-fee update fraction. | 144 |
| Excess tickets sold | The running tally of tickets sold above target across all rounds that drives the pricing curve. Exposed as a settable parameter so the curve can be re-anchored to a chosen starting price when the floor or sensitivity is changed. | 0 |
| Grandfather period fraction | The portion at the start of each round reserved for renewals, during which only prior-round subscribers may repurchase, up to the number of tickets they held the previous round, before sales open to everyone. | 128/256 (or ~0.5) |

This yields a maximum next round price of ~2p and a minimum next round price of ~0.5p where p is price, derived by `e^((max-target)/144)` and `e^((0-target)/144)`, respectively.

## Post-Temperature-Check Updates and Clarifications

The following updates reflect implementation decisions made after the respective Snapshot votes. They are separated from the reproduced component text above so delegates and reviewers can identify the changes clearly.

### PGA

1. **Authorization rather than immediate activation.** Should this vote pass, the ArbitrumDAO grants Offchain authority to enable PGA and priority-fee collection sometime after the vote is fully executed on-chain.
2. **Toggle mechanism.** Priority-fee collection will be controlled by the `TipCollectionToggler`, which can activate or deactivate collection through an ArbOwner precompile call to `setCollectTips`.
3. **Coordinated activation.** Offchain will enable priority-fee collection and the sequencer's PGA mode simultaneously after ArbOS 61 is active on Arbitrum One and the appropriate system testing has concluded.

### Fast Feed

1. **Stablecoin selection.** The payment asset will remain an ERC20, USD-backed stablecoin selected by the ATM Council and OAT.
2. **Deferred contract deployment.** Once the payment asset has been selected by the ATM Council, a Fast Feed contract and a dedicated RewardDistributor contract will be deployed; the Fast Feed contract will point proceeds at this dedicated RewardDistributor.
3. **Superseded source address.** The existing RewardDistributor address reproduced in section 3.3 will not be used for Fast Feed. The dedicated deployment described above will replace that address in the final on-chain proposal materials.
4. **Operational activation.** Execution of this proposal does not require Fast Feed to begin broadcasting immediately. Fast Feed will be activated after the required development, contract deployment, testing and operational-readiness work has been completed.

## Combined On-Chain Execution

This proposal will be submitted as one Constitutional on-chain vote with one combined execution payload.

The final payload and proposal description must enumerate the calls that will be executed when the proposal passes, including the relevant targets, contract addresses, role assignments and parameter values. The final materials should also distinguish actions executed by the governance payload from authority granted for later exercise by Offchain, the ATM Council/OAT or another approved operator.

## Steps to Implement

1. **Forum discussions — complete.** The PGA and Fast Feed AIPs were discussed separately on the Arbitrum governance forum.
2. **Temperature checks — complete.** The PGA and Fast Feed proposals completed separate Snapshot temperature checks.
3. **Combined payload preparation.** Prepare and review the single execution payload, including all contracts, addresses, permission changes and parameter settings to be executed upon completion of a successful onchain vote.
4. **On-chain vote.** Submit the consolidated proposal through Alt Arbitrum Gov for a Constitutional on-chain vote.
5. **Proposal execution.** If approved, execute the combined payload after the applicable governance waiting periods. Proposal execution grants or configures the approved authorities but does not itself require PGA or Fast Feed to become operational.
6. **PGA activation.** After ArbOS 61 is active and the relevant system testing has concluded, Offchain may enable priority-fee collection and PGA mode. Timeboost on Arbitrum One will be disabled around the same time. Timeboost will also be sunset on Arbitrum Nova without enabling PGA on Nova.
7. **Fast Feed activation.** After payment-asset selection and completion of the required deployment, testing and operational-readiness work, activate Fast Feed and begin accepting subscription payments.

## Overall Cost

The ArbitrumDAO has full control over how to spend the proceeds from the PGA auction and the Fast Feed, with 3% of auction proceeds to be set aside for the Arbitrum Developer Guild, which helps fund core Arbitrum development.

The PGA proposal comes at no additional development cost to the ArbitrumDAO given it is already covered by an Offchain and AF contract through January 2027. The engineering work will be owned by Offchain in its capacity as an Arbitrum Aligned Entity.

---

To vote or create proposals from an AI assistant, connect the Snapshot MCP at https://mcp.snapshot.box

