Base (L2)
Base is an OP Stack rollup with 2-second blocks. Tessellate plans Base RPC for launch in Q1 2027, served from op-reth node pools behind the same gateway, cache and limits as every other chain.
Talk to Us About Base RPC
Block time
Availability target
Execution client
WebSocket subscriptions
Snapshot cadence
Head lag target
Reorg window
Debug and trace methods
*Targets are measured at our edge, per region, each month, and published on the status page. Contact our team to discuss committed capacity.
Why connect to Base with Tessellate?
-
Status: Launch, Q1 2027
-
An OP Stack chain served from op-reth node pools
-
2-second blocks, with head lag targeted within two blocks
-
A cache keyed by block hash; latest and pending are never cached beyond one block time
-
An archive tier on local NVMe for history and trace_ methods
-
The same plans and limits as every other Tessellate chain
Explore insights from our engineers
Base RPC FAQ
Send JSON-RPC requests to https://base.rpc.thetessellatelabs.com with your API key. Base is planned for launch in Q1 2027, and endpoints need an API key created in the Tessellate dashboard. Three parts matter in practice:
Client: op-reth runs every Base node pool, which keeps the client set consistent with other OP Stack chains.
Archive: A Reth archive tier on local NVMe serves history and the debug_ and trace_ namespaces. Archive depth for Base will be published at launch.
Cache:Immutable data is cached by block hash. latest and pending are never cached beyond one block time.
Blocks arrive about every 2 seconds.
Block time is set by the chain. If it changes, we update our targets and say so on the status page.
eth_getLogs accepts a block range of 2,000 on Developer and Build, 10,000 on Scale, and a configurable range (default 50,000) on Dedicated and Enterprise. See thelimits table in the docs for result caps and response sizes.
Result caps by plan:
- 10,000 logs on Developer and Build
- 20,000 logs on Scale
- 100,000 logs on Dedicated and Enterprise
Limits apply per API key: 25 requests per second on Developer, 150 on Build and 800 on Scale. Archive reads are weighted 5x on Build and 3x on Scale, and the weight ofdebug_ and trace_ calls is 20x on Scale. Debug and trace methods are not on Developer or Build. Dedicated plans are not metered.
Yes, from the Build plan, at 10, 50 or 500 subscriptions per API key depending on plan.
The cache holds immutable data only, keyed by block hash. latest and pending are never cached beyond one block time. Head lag is targeted within two blocks of canonical for 99.9% of minutes.
Finality guidance for Base will be published at launch.
No. Wallets are out of scope. Tessellate provides RPC access and never holds customer keys or assets.
Responses are capped at 10 MB on Developer and Build, 25 MB on Scale and 150 MB on Dedicated and Enterprise. JSON-RPC batches are 25, 100 or 500 requests by plan.
The target is 99.9% availability on shared tiers, measured at our edge per region per month and published on status.thetessellatelabs.com, including the months we miss.
Availability and head lag are published against targets onstatus.thetessellatelabs.com. If a month misses its target, we show it. The dashboard also shows errors and latency per method and region for your own keys.
Explore additional chains
Tessellate supports twelve EVM chains by month twelve. Learn how to connect.
Meet With Us
Bring reliable infrastructure to your organisation.
Tessellate respects your privacy. By submitting this form, you are acknowledging that you have read and agree to our Privacy Policy, which details how we collect and use your information.