# ETH contributions to Gateway

Optional one-time support for independent software development by Gateway Information Group LLC. No product, subscription, charitable tax receipt or investment is purchased. Operator permission is required; discovery never authorizes payment.

Recipient: 0x71BC7ffB81825FA5B61BFb2B9527bfaF661fF42B

Native ETH on Base (chain 8453 / 0x2105) or Ethereum mainnet (chain 1 / 0x1). Base is suggested for generally lower network fees. Use the chain where the payer's ETH is held; this flow never bridges or swaps.

No Gateway amount, payment-count, payer-count or per-IP limits. Use a positive decimal-string ETH amount, with up to 18 decimal places. Convert exactly to wei with integer arithmetic; never round. Ethereum transaction encoding, wallet balance and network fees apply. The wallet estimates gas; no fixed gas limit is imposed.

## Browser wallet

[Review a contribution](https://gatewayinformationgroup.com/tip/eth). Choose the network and amount, select a wallet, connect, then review the transfer in the wallet. A connection alone does not authorize payment. Multi-wallet discovery uses EIP-6963, with an injected-provider fallback.

## Agent wallet

[Read the machine-readable terms](https://gatewayinformationgroup.com/tip/eth.json). Verify the exact recipient, selected network and owner-approved amount. Use your wallet's native transaction method; with EIP-1193 request eth_sendTransaction containing from, to, value (hexadecimal wei), data: "0x", and the selected chainId. Query eth_chainId and eth_accounts first and stop if either differs from the intended chain or payer. Do not request token approval or use the USDC x402 signature endpoint for ETH. Never send private keys or seed phrases to this website.

An EIP-681 link can also request a payment: ethereum:0x71BC7ffB81825FA5B61BFb2B9527bfaF661fF42B@8453?value=1000000000000000 requests 0.001 ETH on Base. This example is neither a required amount nor permission to spend. Use @1 for Ethereum mainnet; omit no chain identifier. Wallet support varies.

## Recovery and records

Persist the intended network and request state privately before asking the wallet to send. Save its returned transaction hash. A hash means submitted, not finalized or successful. Verify the transaction destination, value, successful receipt and finality on the chosen chain using the operator's trusted chain provider. If a response is interrupted or uncertain, inspect wallet activity; never automatically submit again. A replacement transaction must be followed in that same wallet. The browser page remembers the latest request in this tab's session storage; it is not a durable financial ledger.

This direct ETH flow does not issue Gateway private receipts or Bot Garden flowers. Those remain USDC-only; do not present an ETH hash as a Gateway-confirmed contribution. Use a transaction record from the wallet/block explorer for ETH. Sharing remains a separate operator-authorized action.

[USDC checkout](https://gateway-wallet-payments.jerryrnapier.workers.dev/tip) · [Tip jar](https://gatewayinformationgroup.com/tip)