Sponsorship Contract Manager

WHAT IT DOES

Sponsorship Contract Manager gives developers and sponsors direct control over sponsorship contracts on EVM-compatible chains. It reads live ERC-20 balances, token allowances, sponsor contract state, native balances, and gas price oracles in real time. You can set and revoke sponsorship policies (allowances) that let a target contract spend tokens on behalf of your wallet, deposit native or ERC-20 funds into a sponsor contract, and withdraw native funds back. The tool shows you exactly what is approved, what the sponsor holds, and what you hold—before you sign any transaction. Designed for teams running gas sponsorship programs, account abstraction paymasters, or any scenario where one contract funds transactions for others, it eliminates blind approvals and costly mistakes.

HOW TO USE

Connect your EVM wallet using the built-in bridge. Enter the sponsor contract address you want to manage. Optionally provide a token address for ERC-20 operations—leave it empty to work with native ETH. Set the target contract (spender) that will receive approval to spend your tokens. Use "Check allowance" to see the current approved amount for that target. Click "Set sponsorship policy" to approve a specific amount, or "Revoke policy" to set it to zero. Use "Deposit to sponsor" to send native or ERC-20 funds into the sponsor contract, and "Withdraw from sponsor" to pull native funds back to your wallet. Each action generates a transaction that you review and sign in your wallet. After confirmation, balances and allowances refresh automatically.

TECHNICAL APPROACH

This tool queries live contract state using ethers v5.7.2, not historical event logs. It calls allowance() directly on the token contract and balanceOf() on both the sponsor and your wallet to confirm current values before and after every transaction. It wraps all RPC calls in a robust error handler that digs three levels deep into Ethers error objects to extract the actual failure reason—so you never see "[object Object]" when a transaction reverts. For transaction costing, it uses receipt.effectiveGasPrice post-EIP-1559 rather than tx.gasPrice, which is only the cap and overstates actual spend. When fetching mempool data or gas oracle prices, it references multiple sources and falls back gracefully. The tool also checks totals per sender, not per row, avoiding the trap where a per-row check passes on every row but the batch still fails with some transfers already sent.

WHAT IT CANNOT SEE

This tool cannot verify off-chain sponsorship agreements, intent, or business logic that your sponsor contract enforces outside the blockchain. It cannot guarantee that sponsored transactions will be accepted by the target contract or included in a block—those depend on network conditions, gas markets, and the target contract's own validation rules. It does not simulate execution or test whether your sponsor contract implements the specific policy functions you expect. It cannot see pending operations that are not yet broadcast to the public mempool, nor can it detect rate limits or whitelists that the sponsor contract may enforce. The tool manages allowances and deposits, but it does not guarantee that the sponsor contract will honor those policies.

PLEASE NOTE

This tool supports EVM‑compatible chains only (Ethereum, Goerli, Sepolia, Arbitrum, Optimism, Polygon). Solana, Tron, Starknet, SUI, TON, Aptos, Bitcoin, Cosmos, and XRP are not supported. This is a read‑write tool that requires signing transactions—always verify the sponsor address, target contract, amount, and recipient before approving. No contract addresses are hardcoded; you paste the contract you are using, so you are responsible for verifying its safety. The tool is free and open under the BotGentz PLAYBOOK‑C specification.