Conditional Payment Releaser

WHAT IT DOES

Conditional Payment Releaser connects to any EVM-based conditional payment or escrow contract and enables you to execute the release function when all conditions are satisfied. The tool reads comprehensive contract state including payment amount, token address, payer address, payee address, individual release conditions and their fulfillment status, current block timestamp, deadline parameters, external oracle/price feed data, multisig approval status, dispute status, and payment history. It then allows you to review each condition individually before submitting a release transaction that transfers the locked funds to the payee. The tool handles multiple release function signatures (release, execute, fulfill) and automatically detects the correct function to call. After submission, the tool displays the transaction hash and refreshes the contract data to show the updated payment status.

HOW TO USE

Connect your Web3 wallet (MetaMask, WalletConnect, or any EIP-1193 provider). Select the correct network for your conditional payment contract — the tool supports Ethereum, Polygon, Arbitrum, Optimism, Base, Avalanche C-Chain, and BNB Chain. Paste your contract address into the input field. The tool reads the contract using a default ABI that covers standard conditional payment functions, but you can paste a custom ABI if your contract uses non-standard naming. Review the displayed data carefully: payment amount, token type, payer and payee addresses, deadline, multisig approval count, dispute status, oracle data, and most importantly — the detailed condition list showing each condition's fulfillment status. Only when all conditions show as met and no dispute is active will the release button become enabled. When ready, click "Release payment" — the tool will show a confirmation dialog with all details, submit the transaction, and wait for confirmation. After successful execution, the contract data refreshes automatically to show the payment as released.

THE REAL MECHANISM

This tool does not assume a single condition evaluation method — it reads the contract's actual storage through eth_call at the current block. It first detects the correct release function by testing common names (release, execute, fulfill) through static calls, falling back to the user-provided name if none are found. For conditions, the tool reads the total condition count via conditionCount() then iterates through each condition using the conditions(uint256) view function, building a complete list of individual condition statuses. This gives you granular visibility into exactly which conditions are met and which are not, rather than a single boolean. The tool also checks disputeStatus() to ensure no active dispute is blocking the release, and reads deadline() to verify the contract hasn't expired. For contracts using oracle data, the tool reads and displays the oracle bytes so you can see what external data is being used for condition evaluation. All transaction parameters are estimated using eth_estimateGas and sent with the wallet's preferred gas strategy. The tool monitors the transaction receipt and extracts the effectiveGasPrice to display actual gas cost, not the cap. For multisig contracts, the tool reads the current approval count so you know how many signatures are still needed.

WHAT IT CANNOT SEE

Conditional Payment Releaser cannot verify that the release conditions are fair, complete, or correctly implemented in the contract bytecode. It cannot detect off-chain agreements, side letters, or manual condition overrides that bypass the contract logic. It cannot guarantee that the payer will not front-run the release with a competing transaction. It cannot validate that the deployed bytecode matches the source code you expect or that the contract is not maliciously constructed. It cannot prevent gas price manipulation or transaction ordering attacks (MEV). It cannot verify the accuracy, reliability, or timeliness of external oracle data used in condition checks. It cannot detect if condition evaluation can be manipulated through reentrancy, flash loans, or other attack vectors. It cannot ensure that the multisig approvers are trustworthy or that the required approval threshold hasn't been changed. It cannot recover funds if the release transaction fails or if the contract lacks a release function. It cannot detect phishing attempts or social engineering attacks.

PLEASE NOTE — EVM CHAINS ONLY

This tool works exclusively with EVM-compatible blockchains. Non-EVM chains are not supported. The tool does not deploy contracts, manage private keys, or sign anything outside the connected wallet's secure environment. It is a read-and-execute interface that relies entirely on the conditional payment contract's implementation and the condition evaluation logic defined therein.