Capability honesty and the EVM-free boundary
Leani exposes what the running node can answer. Capability depends on all three layers:
- the source can supply the required headers, bodies, receipts, logs, or consensus proof;
- the processor or raw-history policy retained the required product; and
- the query can locate the requested block or transaction exactly.
That is why applications should inspect /v1/capabilities, processor status,
and collection metadata instead of assuming every compiled route is usable for
every configured node.
What the EVM-free core can do
With capable sources, Leani can serve blocks, transactions, receipts, logs, chain metadata, subscriptions, processor snapshots, generic collections, and processor-owned queries. Hash-only historical lookup also requires a retained locator or recent material.
What it refuses
Without execution state and an EVM, arbitrary eth_call, eth_getBalance,
eth_getCode, eth_getStorageAt, eth_estimateGas, and debug/trace methods are
not honest implementations. They fail explicitly. Derived balances or prices
are processor products with documented scope; they are not substitutes for
arbitrary historical Ethereum state.
Keep an execution provider for unsupported methods and as an independent fallback.
Over JSON-RPC
implemented exactly, when available
- eth_getBlockByNumber / ByHash
- eth_getBlockTransactionCountByNumber / ByHash
- eth_getTransactionByBlockNumberAndIndex / ByHashAndIndex
- eth_getTransactionByHash / Receipt
- eth_getBlockReceipts
- eth_getLogs (recent, on-demand, or materialized)
- eth_blockNumber · eth_chainId · eth_config · eth_syncing
- web3_clientVersion · net_version
- leani_getCapabilities
- eth_subscribe: newHeads, logs (reorg-correct)
refused, explicitly
- eth_call · eth_estimateGas
- eth_getBalance · eth_getTransactionCount
- eth_getCode · eth_getStorageAt
- debug/trace methods
The exact matrix lives in Ethereum JSON-RPC compatibility.
Built by Smart-Byte · Legal notice (Impressum) · Privacy