Limitations of the GenLayer Studio

GenLayer Studio limitations are Studio-specific caveats for building and testing Intelligent Contracts outside a full live-network replica. GenLayer Studio supports core contract execution, consensus testing, appeals, web access, and native value transfers, but live-network behavior should be validated where exact gas, chain-layer, EVM, or web-access behavior matters.

Gas Usage

Studio's EVM-compatible wallet layer is gasless: eth_gasPrice returns 0, and eth_estimateGas returns a compatibility estimate. Consensus v0.6 protocol fees are a separate layer and can still be enabled for Intelligent Contract transactions. Read those through the GenLayer fee estimate and finalized receipt; do not use eth_gasPrice or the outer EVM receipt to decide that a Studio deployment has no protocol fees.

Chain-Layer and EVM Parity

Studio tracks contract and account state in its local database. Native value transfers are supported for local testing, but Studio does not fully model the live network's chain-layer and ghost-contract behavior.

EVM contract interaction beyond value transfers to EOAs or addresses is not implemented in Studio. @gl.evm.contract_interface calls that depend on EVM contract execution should be validated on a live network.

Web Access

Studio web access depends on its local browser/WebDriver service and the network access available to your Studio environment. Validate production-critical web reads against the target network before relying on exact rendering, timing, or availability behavior.