Custom Contract

Custom Contract creates a Mission Control task for a specific EVM contract call when a built-in provider workflow does not apply. Use it only when you trust the target contract and understand the function, arguments, and value.

Create a stopped task

1. In Mission Control, choose + Task, then select Custom Contract.
2. Select the intended network and enter the exact contract address. Sthang blocks ABI loading when the address has no contract code on that network.
3. Choose one construction route:
   • Enter trusted raw hex calldata directly.
   • Open ABI Wizard, load a verified ABI or paste a trusted ABI, select the function, and enter its arguments.
4. Review the encoded data, native value, schedule or launch window, fee model, gas limits, delivery route, and selected wallets.
5. Create the task. It appears in Mission Control stopped and must be reviewed again before Start.

Use ABI Wizard

For supported explorer-backed networks, ABI Wizard can load verified contract functions. Configure the optional Etherscan V2 API Key in Networks when the selected explorer requires it. You can also paste trusted ABI JSON or Solidity function fragments.

1. Confirm the displayed network and contract.
2. Load the ABI and select the exact function overload.
3. Enter every argument, checking address values, integer units, arrays, and tuple fields.
4. If a public contract function exposes a start time, review the returned schedule and choose to apply it only when it matches your trusted source.
5. Apply the result to the task and compare the generated calldata and value with an independent encoder or trusted project source.

Applying ABI Wizard output only fills the task form; it does not approve, sign, start, or submit the call. A verified ABI describes an interface and is not proof that a contract is safe. If the contract, function, arguments, calldata, value, schedule, or network differs anywhere in review, stop and rebuild from trusted inputs.

Never put a private key, recovery phrase, signed transaction, RPC credential, or unknown calldata in documentation or support channels.