Solidity REPL
PRIVACY

Know what stays local and what uses the network.

The default Solidity workflow runs in your browser. Network requests occur only for normal site assets, compiler downloads, a fork RPC, or verified-contract metadata as described below.

LOCAL EXECUTION

Compilation and simulation

Solidity source is compiled in a browser worker. Local mode runs the resulting bytecode in an EthereumJS EVM in that worker. It does not request a wallet, sign a transaction, or broadcast one.

BROWSER STORAGE

Sessions and project files

Sessions, transcript entries, drafts, compiler settings, execution context, and in-browser Solidity files are saved in IndexedDB with a localStorage fallback on this device. Non-GitHub repository scans also use a temporary IndexedDB filesystem for shallow Git objects. Exported session files remove RPC URLs.

NETWORK REQUESTS

When data leaves the browser

Site and compiler assets

Opening the site requests its page and assets from the site host. When a compiler is not bundled, the browser downloads that exact release from the official Solidity compiler distribution and caches it.

Fork RPC

Enabling Fork sends JSON-RPC state-reading requests to the endpoint shown in Controls. The provider receives the usual request information plus requested chain addresses, slots, proofs, and block identifiers. Execution remains local and no transaction is broadcast.

Sourcify

Selecting Add verified contract sends the chosen chain ID and contract address to sourcify.dev. The browser uses the returned public ABI and compilation name to create the interface file.

Public Git repositories

For GitHub, Scan repository reads the public repository API and selected raw files directly from your browser. Other Git hosts use read-only discovery and upload-pack requests through the Solidity REPL Worker. The endpoint rejects credentials, private hostnames, writes, unrelated paths, and oversized pack responses.

YOUR CONTROL

Removing saved work

Delete individual sessions from the session menu. Clearing this site’s browser storage removes the local session database, preferences, and cached compiler assets. Deleting an exported JSON file is controlled by your device or storage provider.