ETHGlobal Buenos Aires- Must be built using Privy’s APIs or SDK. - Must use Privy to create and manage the user’s embedded wallet. - Must integrate x402 authorization in at least one core user flow (e.g., scheduled/recurring actions, automated payments, agent-driven transactions).
- Must be built using Privy’s APIs or SDK. - Must use Privy for embedded wallet auth and management. - Must enable Privy’s native gas sponsorship and demonstrate a sponsored transaction as part of the core user experience. - Sponsored flows must use Privy’s sponsorship configuration (no custom gas abstraction logic).
- Must be built using Privy’s APIs or SDK. - Must use Privy for embedded wallet authentication and management. - Must generate and authorize a Privy session signer key for the user. - Must demonstrate at least one meaningful delegated action using the session signer (e.g., transaction execution without user re-approval, background/automated actions, offline-triggered flows, or high-frequency interactions like trading or payments).