Faucet Rate Limit Exception — Automated E2E Testing for toodigital

I’m building **toodigital**, a native music distribution app (Flutter + Rust) fully on Sui — zkLogin onboarding, Move contract catalog (sale/listing/catalog), decentralized vendor shops, and NFT purchases with fiat settlement. Currently on testnet, planning mainnet migration.

We run a fully automated E2E testing pipeline: cron-based contract redeployment after testnet resets (30-min monitoring → auto-republish 3 Move modules), Platform Wallet SUI drops to NFT buyers (5-min batch), and gas sponsorship for new zkLogin users (balance starts at 0). Faucet rate limits (`429 Too Many Requests`) cause our deploy to fail post-reset (10 retries × 60s still not enough) and drain our Platform Wallet, blocking all automated tests — sometimes for hours.

**Request:** Rate limit exception for 2 server-side wallets (~5-10 req/hour) to achieve near-100% faucet success during automated test runs. One wallet handles SUI drops and gas sponsorship, the other handles contract publishing after resets.

Happy to demo or share automation scripts. Thanks!

I’m smart contract and DeAI engineer with 7+ years. I’m very interested in your project. I want to implement this project together while sharing the development experience each other. Let’s contact for the future.