Speedyploy

Our hackathon project simplifies the deployment of NFTs and ERC20 tokens, making it accessible even to those without advanced smart contract knowledge. Our platform offers a fast and straightforward process where users can deploy their NFTs or ERC20s in just minutes using their email, SMS, or passkeys. This removes the typical barriers associated with smart contract creation, allowing anyone to participate in the blockchain ecosystem effortlessly.

To ensure accessibility, the platform leverages custodial wallets, enabling users to sign up and deploy contracts using just their email, SMS, or passkey credentials. This approach eliminates the need for users to manage their private keys directly, streamlining the onboarding process and enhancing user experience.

Currently, the system is compatible with any Ethereum Virtual Machine (EVM) blockchain, with initial support for the Base Network, Avalanche, and Polygon. We plan to expand to additional EVM chains in the future to offer even broader reach and flexibility. A key feature of our platform is the "gasPayer" model, where contract deployment costs are covered by a centralized ETH address. This innovative approach allows users to deploy contracts without worrying about gas fees, further lowering the entry barrier.

For the user interface and experience, we've integrated the shadcn/ui component library, providing a clean, intuitive, and user-friendly interface that simplifies the deployment process even further. This ensures that users, regardless of technical expertise, can navigate and utilize the platform with ease.

Our project was built using a variety of technologies aimed at streamlining development and ensuring robust functionality. We started with a Next.js project template to quickly establish the foundational framework, which allowed us to focus on building the core features rather than setting up basic infrastructure. The primary programming language used was TypeScript, chosen for its strong typing and integration with modern JavaScript frameworks, which enhances both development speed and code reliability. For our database, we opted for PostgreSQL, a powerful and flexible relational database system that offers the stability and scalability needed for handling user data and contract deployments. On the front end, we incorporated the shadcn/ui component library, which provided us with a set of pre-designed UI components that allowed for a consistent and user-friendly interface, speeding up the design process while ensuring a polished look and feel.

These technologies were carefully pieced together to create a cohesive system. The backend, built with Next.js and TypeScript, communicates with the PostgreSQL database to manage user accounts, store deployment data, and handle other essential operations. The frontend, also powered by Next.js, uses shadcn/ui to render a seamless user experience, enabling users to deploy NFTs and ERC20 tokens with just a few clicks. By using this technology stack, we were able to create a smooth flow from user input to contract deployment, integrating each component to ensure a responsive and reliable system.

While we didn’t rely on specific partner technologies outside of the blockchains we integrated, such as Base Network, Avalanche, and Polygon, these blockchain partnerships were crucial in bringing our project to life. They provided the underlying infrastructure that allowed us to deploy and manage contracts efficiently, giving our users access to well-established and secure blockchain networks from the start. The choice of these EVM-compatible blockchains also ensures that our platform can be easily expanded to other networks in the future, offering scalability and flexibility as we grow.

One of the more "hacky" aspects of our project is the system we've devised for enabling users to deploy smart contracts without needing any prior smart contract knowledge. This was particularly challenging and remains an area we plan to refine post-hackathon. For instance, when users deploy contracts and mint tokens, these actions are executed from our centralized "gasPayer" ETH address. This setup requires us to handle subsequent actions, such as transferring tokens from the custodial wallet to another user’s wallet which may or may not be custodial. To accomplish this, we need to transfer the appropriate network gas tokens (e.g., Base ETH for the Base Network) to the user's address so they can call transfer functions. This behind-the-scenes complexity is hidden from the user, ensuring a seamless experience, but it also represents a significant technical challenge that we continue to work on, with plans to optimize and fully automate these processes.