Contract console

Read and write any EVM smart contract straight from your wallet. Check its state, call owner functions, send payable calls. You no longer need Remix or an explorer's "Write Contract" tab with a browser extension: paste the contract's address and ABI into Launch Lab, and every function is a form on your phone, signed by your wallet.

It works for contracts you deployed with Launch Lab (their ABI is built in) and for any other contract: your own, a team contract, or one you deployed elsewhere.

Add a contract

1. Open Launch Lab → Manage and tap Add Contract + ABI.
2. Template: choose the Launch Lab template the contract was deployed from, or Custom Contract for anything else.
3. Choose the Chain, give it a Label, and paste the Contract address.
4. Set Decimals (used to read and enter token amounts).
5. Paste the Contract ABI, the JSON array your compiler or the explorer gives you. It's optional for Launch Lab templates (their ABI is built in) and needed for custom contracts.
6. Tap Save Contract.

Where to find an ABI

On a verified contract's explorer page, open the Contract tab and copy the ABI (or Contract ABI). From Hardhat or Foundry, it's the abi array in the compiled artifact.

The contract and ABI are stored on your phone only.

Read and write functions

Tap Methods on the contract card.

1. Method: pick a function. The list shows each one as name:stateMutability, for example balanceOf:view or mint:nonpayable. Payable functions are marked Write + value.
2. Fill in each Parameter, or see No parameters if there are none.
3. For payable functions, enter the Native value in wei to send with the call (optional).
4. Tap Read Method (view / pure functions) or Send Method (anything that changes state).

• Reads are free and instant: the result appears as Read result (Read Complete).
• Writes are real transactions: your wallet signs, pays the network fee and waits for confirmation (Method Confirmed, with the transaction hash). If the call would fail, you'll see why (Method Failed).

The wallet you use must be able to sign and be on the contract's network (Switch to a wallet on … before using these contract methods).

Entering values

Type	How to enter it
address	A full 0x… address
bool	true / false (also 1 / 0, yes / no)
uint… / int…	Whole numbers in the token's smallest units (for 18 decimals, 1 token = 1000000000000000000)
string	Plain text
bytes	Hex, with or without 0x
bytes32	32 bytes of hex with 0x, or plain text, which is hashed (keccak-256)
Arrays (address[], uint256[], …)	Values separated by commas

Functions that take or return tuples (structs) are hidden, to keep mobile forms safe and readable. For those, use a desktop tool.

Inspect

Inspect reads the common state of a contract in one tap: name, symbol, decimals, total supply, owner, pending owner, paused, trading and limit status, max transaction and max wallet, LP pair and more, whatever the ABI provides.

What Launch Lab recognises

From the ABI, Launch Lab labels what a contract is, so you know which tools apply: ERC-20, Ownable, Ownable2Step, AccessControl, Pausable and Launch ops (trading and pair controls). For Launch Lab templates you also get the one-tap contract actions and the guided Launch Flow.

Writes are final

A write call is a real blockchain transaction. Check the function, inputs and network before you tap Send Method. Owner functions like renouncing ownership can't be undone.