Customize Endpoint Advanced Features
BlockPI provides users with ample flexibility to customize advanced features of their Endpoints, including Archive mode, MEV protection, ERC-4337 Bundler service, and more.
To determine whether a specific network supports any features, refer to the "Feature" column in the API Key List. In the provided example, the symbol marked with a red box represents the Archive mode, while the one highlighted with a yellow box denotes the ERC-4337 Bundler service. For more detailed supported advanced features, please go to this page,
In the case of Archive mode, the symbol displayed in gray signifies that it is currently off, whereas a green highlighted symbol indicates that it is turned on.
Archive Mode
If you require access to data from earlier blocks, you can utilize the Archive Model. This feature enables users to retrieve and access the complete historical data of the blockchain.
Enabling Archive mode will route all requests sent to this API key to the archive nodes of the blockchain network. It's important to note that there is a 30% increase in RU consumption, since running an archive node requires significant storage capacity.
In order to optimize efficiency, we recommend activating Archive mode only when necessary, or generate an individual API key to send the archive requests. Check Best Practices to more efficiently use the feature. Additionally, processing times may be longer due to the substantial amount of data involved. Check here for the full list of chains that the Archive mode is supported.
By default, the Archive mode is set to off. To enable it, simply click on the Archive mode symbol corresponding to the endpoint in the API Key list,
Or, you can navigate to the subpage of the API key and enable the Archive mode by accessing the Advanced Feature settings,
ERC-4337 Bundler Service
BlockPI now provides Bundler Service for Account Abstraction users on Base Mainnet, Polygon Mainnet and Mumbai. The BlockPI team integrated different open-source Bundler clients in the BlockPI network, providing users with the flexibility to choose their preferred client. The currently supported clients are from Etherspot, Candide, Stackup and Pimlico.
To customize it, go to the BlockPI dashboard, click the endpoint which has the 'ERC-4337' mark. You will be directed to the subpage of the endpoint. (If you do not have any endpoint, please refer to the Generate API Key page to generate a private endpoint).
On the subpage of the endpoint, there is the 'AA Service' section, which presents you with five different options to choose.
'Auto' is the best practice maintained by the BlockPI team. By selecting 'Auto,' BlockPI will automatically assign the most optimal bundler based on each connectivity condition.
The remaining four are Bundler clients by Stackup, Candide, Pimlico, and Etherspot. When you choose one of these clients, your requests will be processed exclusively by the selected Bundler client.
Please check this page for Polygon Bundler RPC references.
MEV Protection
To provide users with a better experience in using BlockPI RPC, we have implemented MEV protection function on BSC mainnet, Ethereum mainnet, and Polygon mainnet. Enabling MEV protection safeguards your transactions against front-running and sandwich attacks. And this feature does not increase RU consumption. We highly recommend enabling it.
You will notice that these keys on your dashboard have a small icon, which is enabled by default.
You are able to switch it off or on in the key subpage.
We employ the MEV-Boost protocol, which is currently the industry's most mature and stable MEV protection protocol. Additionally, we have implemented our own load balancing mechanism. If there is any congestion on the MEV network, we will immediately route user transaction requests to the public mempool.
Last updated
