# Under the Hood The RIPS platform is built by a full-stack team of backend engineers, frontend developers, and product designers who’ve worked together for years. We believe products like RIPS succeed when built by a dedicated, full-time team focused on long-term community value. Our stack combines Farcaster-native app development with modern web and onchain infrastructure to deliver a fast, reliable, and secure experience. **Architecture & Infrastructure:** RIPS is a Farcaster mini-app built with Next.js and deployed on AWS serverless infrastructure, with a potential move to Vercel. The backend handles authentication, user state, and coordination between on-chain contracts and off-chain services, providing scalable, consistent performance. **Smart Contracts:** The RipsManager contract on Base manages on-chain actions for pack purchases and ERC-20 distributions. Purchases emit PackPurchased events with unique identifiers and metadata. Coin claims transfer ERC-20 tokens from the contract treasury to user wallets, with all gas fees paid by users. **Coin Swap Mechanism:** Users can consolidate up to 10 RIPS ecosystem coins into USDC via the 0x Protocol API for optimal routing and live pricing. The system enforces a $0.01 minimum per coin and warns when gas costs exceed 10% of swap value. Wallets using EIP-5792 batch multiple approvals and swaps into a single signature to reduce friction. **Notifications:** User alerts are delivered through Neynar’s Farcaster service, with CloudWatch-triggered Lambdas resetting claim quotas and sending notifications daily. **Anti-Abuse System:** A behavioural analysis module detects abnormal request patterns to prevent automated abuse and protect the free daily claim system. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.rips.app/under-the-hood.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.