Network FAQ

What are the hardware requirements?

What's the max expected TPS?

~700

Is it fully EVM-compatible? Is there any customization already being made on the IP blockchain? Or are there any coming customization to be applied?

Yes, it’s EVM-compatible. Story’s execution client is a fork of Geth with our custom precompiles, which enhance the IP graph's performance while maintaining strict EVM compatibility. Other Ethereum execution clients, such as RETH and Erigon, can be supported later.

Which is your consensus mechanism?

Our consensus mechanism is CometBFT

Batches support? Limit on batch request?

Batch RPCs are supported - for Geth there is a 1K limit and on the consensus side there is 10 request limit

WS connections? (if yes, how do they work)

Yes, WS is enabled on the execution client, and is recommended for subscription use-cases. It is open on port 8546

How many different paths does node serves (several path with diff methods RPC)?

Please see Geth’s latest JSON-RPC documentation for a full comprehensive list here. In the future, we may add more.

Caching rules for RPC method?

We recommend employing standard in-memory caching with a 1-10 min TTL based on the RPC method

What is the best method to get latest block and check node is healthy and in sync?

Use eth_syncing RPC call on the execution client to check if the node is sync and eth_blockNumber for getting the latest block

What are the heaviest RPC methods? How much time does it take to respond to request with such method?

eth_call / eth_getLogs / eth_getBlockByNumber
We are still running latency tests to get a sense of response times.

Is archive node provisioning a requirement? If yes how big?

No, not at the moment.

Are there snapshots available for full / archive?

Not yet, but we are working on it.