Get started · 3 of 3
Safety, simulation, and signing
How ENS.Tools keeps state-changing actions in your wallet.
stableWeb appVerified 2026-07-29Owner: ENS.Tools Product
ENS.Tools is non-custodial. The web app and MCP server can calculate calldata, values, dependencies, and typed data, but the connected wallet remains the final signing and broadcast boundary.
Private keys and recovery phrases are never accepted.
Onchain MCP actions return unsigned plans and do not broadcast. Signed publish, authorize, observe, and revoke tools can persist platform state after their declared checks.
Prepared transactions expose the target contract, calldata, ETH value, prerequisites, and dependencies.
Simulation uses eth_call and gas estimation; it reduces avoidable failures but is not a guarantee of future execution.
Dependent operations wait for required confirmations, especially registration commit/reveal and two-phase agent registration.
Production contract
Before you run this workflow
Networks
- Ethereum mainnet unless the page explicitly labels a test network
Prerequisites
- A current browser; a wallet is only required for address-specific data or signing
Wallet permissions
- Public reads require none
- State changes require a separate wallet review and signature
Expected result
- A current read result, prepared action, or explicit unknown/error state
Errors and recovery
- Confirm the active wallet and network
- Refresh stale evidence
- Never force-send a failed simulation
Workflow
How to use it
- 1
Prepare
Review the human-readable action, target, value, and any approval or ownership prerequisite.
- 2
Simulate
Run the available simulation and read any revert reason or gas estimate.
- 3
Sign
Confirm the same target and value in your wallet. Reject anything that differs from the prepared summary.
- 4
Verify
Wait for confirmation and check the transaction status before starting dependent work.