FAQ

Today, you fund from any source that supports Tempo L1 (chain 4217). That includes a handful of centralized exchanges with Tempo withdrawals, bridging via Relay Protocol, or a direct on-chain transfer from another EazPay user or external wallet. A PIX / card on-ramp (PIX → USDC in the bot) is on the roadmap for Q3 2026 — see the roadmap page.

Yes, by default. The bot generates a wallet key for you and stores it encrypted (AES-256-GCM) so payments work from a chat. But your USDC lives in a smart contract that you own via that key. Run /export and you walk away with the key — EazPay becomes just one of many wallets you could use. We're transparent about the trade-off; the security page documents the full trust model.

The operator key is on-chain restricted to sendPayment, sendExternal, batchSend, and registerUser. It cannot call withdraw, transferOwnership, or change daily limits — those are onlyOwner. Each UserWallet has a daily limit of 1,000 USDC/day enforced by Solidity. Worst case (key compromised), an attacker can redirect ≤ 1,000 USDC/day per wallet — we'd pause the contract on detection. Roadmap: migrate to a Gnosis Safe multisig + AWS KMS for the operator key.

0.1% flat on every outgoing transfer — P2P, split batches, external withdrawals. Hardcoded 2% ceiling in the TreasuryRouter contract, so we can never push it above that. Gas on Tempo L1 is sub-$0.001 per transaction and we (the operator) pay it. You pay zero gas.

Tempo L1 is a stablecoin-first EVM chain with ~0.6s finality, sub-cent gas, and USDC as the gas token (built with backing from Stripe / Paradigm). For a payments bot, that's the right shape — cheap, instant, EVM-compatible, and no speculative gas token friction. A Relay Protocol bridge to Ethereum / Base / Arbitrum / Optimism / Polygon / Avalanche / BSC / Solana is on the roadmap.

Yes — since EazPay V4 deployed on 2026-04-16. Use /send 0xAddress 10 with any EVM address on Tempo L1. Same 0.1% fee, daily limit still applies. If you're on a legacy V3 account, run /migrate first (takes 10–15 seconds).

Your USDC stays exactly where it is — in your UserWallet on Tempo L1. If you ran /export before the shutdown, you already have the key. If not, the contract has a transferOwnership function you can call via the Tempo Explorer using the operator key backup that the security page documents. Smart contracts don't disappear when websites do.

15 rounds of internal security audits between 2026-04-03 and 2026-04-20 — ~50 findings closed, 0 exploits, Slither clean on the V4 contracts, on-chain bytecode parity verified. The audit cadence is weekly. The latest round (#15) was threat-driven — modeling actual attacker paths rather than only reviewing code. External firm audit (OpenZeppelin / Trail of Bits / Cure53 class) is planned before mass-market launch. Reports will be published on GitHub when the repo goes public.

1,000 USDC / day per wallet for bot-initiated transfers — enforced in Solidity. If you need more, you can /export and call withdraw() directly on the contract — that path has no limit. The limit isn't a price policy, it's a safety net if the bot key ever leaks.

Solo founder (@imxoes on Telegram). Small codebase, open security posture, public audit trail. Contact security@eazpay.xyz for responsible disclosure, contact@eazpay.xyz for anything else.