19 BUIDLs selected

  • Screen Protocol
    Mohit Jain  ·  Updated 329 days ago
    A Smarter Approach to Self-Custody: Integrating 3rd Party Co-signers for Improved Wallet Recovery, Fraud Detection, and Insurance in Multi-sigs and Smart Contract Wallets. This is inspired by the hybrid custody solution, mentioned by SAFE team in this blogpost 1. SAFE Core SDK - It was used to add gaurdians, sign + fetch transactions, and show the current state of SAFE 2. Gelato Network - Used to enable paymaster and initiate transactions Full self-custody is perceived as unsafe and inefficient by users. 1. Cumbersome key management - Users lack a convenient method for storing private keys in the form of 12/24-word phrases. 2. ’Heart attack’ - Users feel unsafe transacting on different dApps. 3. Subpar experience - UX deteriorates when using multi-sig. We enable users to appoint trusted 3rd party Guardians as co-signers in their multi-sig wallets. Take a peek at our demo to see what we've built: STEPS First step is to setup up your current SAFE account with us: SETUP SAFE Demo transaction: Demo Transaction.mp4 Through this approach, we offer users a range of key benefits including: Wallet recovery: Users can retrieve their assets anytime with the backup key and chosen Guardian. Fraud protection : Our platform utilizes advanced fraud detection and fallback mechanisms to protect users against fraudulent activity. Every approved transaction is co-signed by the guardian to attest to its authenticity. Enhanced user experience : By performing multi-sig safe transactions co-signed by guardians with just a single click, users can experience the convenience of signing with a single wallet while ensuring their safe is still 2/n protected. Moreover, they have the option to pay gas fees via their safe contracts in ETH and other ERC20 tokens. Upon adoption of our core features, we will explore the following: Asset insurance: We plan to offer insurance on all assets in SAFEs with us as Guardians, delivering additional peace of mind for users. Compliance assurance: As signers will be registered and regulated entities, we envision better compliance for all users. Although still in the early stages, we see tremendous potential here. Preserving the essential advantages of self-custody - such as censorship resistance, no lock-ins, and composability - our platform presents a solution to the challenges faced by exisiting self-custodial wallet users. ###Target Customers Immediate target customers: We are targeting individuals who are already using SAFE. This group currently represents around 45% of the existing 120k SAFEs. Future expansion of target users: Our future target customers include retail users who are looking for a secure alternative to Ledger for their "savings account." We aim to attract people who are transitioning from centralized exchanges (CEXes) to decentralized exchanges (DEXes) for better security and self-custody.
  • SafePay
    kamalbuilds  ·  Updated 328 days ago
    Cross Chain Pay-roll Management using AA -> Get paid and Pay with any Crypto Currency seamlessly using SafePay Features Using this system, companies can easily pay their employees with any cryptocurrency or fiat currency, which could potentially lead to faster, more secure, and cheaper transactions than traditional payroll methods. Additionally, using smart contracts for payroll management reduces the risk of fraud, errors, and disputes by automating payroll calculations and payments. Account abstraction could make this system much more efficient and cost-effective. By abstracting the user's account, it separates the user's private key from their on-chain address. This means the private key could be stored safely and remotely, and only the user can transfer funds from the account. This would increase the security of the system and reduce the risk of a breach.
  • compassSafe
    coamsp  ·  Updated 332 days ago
    compassSafe is a RBAC (role based access control) protocol built on Safe. As the most popular smart contract wallet, Safe supports the standard multi-signature, and compassSafe builds on Safe Module to provide users with enhanced security and flexibility. compassSafe provides fine-grained permission configurations with contracts, methods, and parameter levels, applicable to all types of contracts. For institutions and DAOs (multi-player organizations), compassSafe enables the organization to set permissions to different members, allowing them to perform specific actions based on their roles. e.g. Traders can only swap specified token pairs with specified Dex protocol. For individual users , compassSafe can be used as a multi-level safe vault, where they can set different levels of permissions for different wallets to isolate the risks with different operations. e.g. a user may set hardware wallets as the owners of the Safe with the core permissions, but grant some daily-use-low-risk permissions with a software wallet. More info: https://docs.compassdao.com/how-to-use/compasssafe
  • Signless
    kevincharm  ·  Updated 339 days ago
    Make web3 feel like Web 2.0 Submission for Safe "March for Account Abstraction" tracks: Safe, Gnosis Chain, Gelato, Base Check out signless.xyz ! Signless is a concept that allows dApp enjoyoooooors to sign-in just once with their existing wallet. After signing in, transactions being made from the wallet do not require any additional signature prompts. A demonstration of Signless is implemented as a Gnosis Safe module in this repository. To enable Signless for a Safe: First, the user must use the Signless Safe forked webapp. (GitHub: gnosis-safe-web-core ) A user enables the Signless module for their Safe in the Settings/Signless tab. The user then creates an ephemeral private key that lives in their browser's local storage. This ephemeral key is registered as a delegate on the Signless module for this particular Safe. After the above steps have been executed, the user will be able to browse Safe Apps without ever having to sign a transaction again (at least, until the ephemeral key expires). This is possible as the Signless Safe webapp intercepts any incoming transaction signing request, signs it with the stored ephemeral key, then submits it to the Gelato Relay network. Gas fees are paid using native tokens in the Safe. Ethereum Mainnet: 0xb9Cd1dd44799f508769040156962E01ADf97e330 Gnosis Chain: 0xb9Cd1dd44799f508769040156962E01ADf97e330 Base Goerli: 0xb9Cd1dd44799f508769040156962E01ADf97e330
  • Superfluid - NFT Lending
    Rahul  ·  Updated 329 days ago
    This project demonstrates the use of Superfluid as a sublayer that powers financial applications. The protocol allows a user to deposit an NFT as collateral and borrow DAI against it. The borrow function generates a stream from the borrower to the contract, which pays interest on the loan. The flow rate is determined based on the APR specified in the contract and the loan amount. For instance, if a user takes out a 100 DAI loan at an APR of 10%, a stream of 10 DAI/year is created from the borrower to the NFT Lending contract. In addition, if the user repays half of the loan, the repay function updates the stream downwards. Finally, if the user repays the entire loan, the payment stream is canceled. If the user attempts to cancel the stream by themselves, liquidations are also carried out. This involves seizing the NFT and transferring it to an NFTChest owned by the NFT Lending contract, which acts as a safe place. Frontend- It uses Safe AA SDK - Auth Kit for authentication and onramp kit for stripe payments (under development beacuse api keys are not working)
  • FlowSafe Wallet (Base Goerli deployment)
    tomosaigon  ·  Updated 329 days ago
    A smart contract wallet protected with 2FA (Google Authenticator) and optional social login. The wallet has protections in place to keep the user on allowed defi protocols and can only return funds to the owner in case an attacker gets access to the signing keys. The wallet makes it easy to create Superfluid money streams so that a company's accountant could use it to pay salaries without being able to steal or lose the company's funds. Using Web3Auth for social logins, Google Authenticator for 2FA, Superfluid for money streaming, ERC-4337 account abstraction, Stackup bundler, deployed on Polygon and Base. We want to configure a smart contract wallet that requires knowledge of time-based one time pass (OTP) codes generated from an app like Google Authenticator but we don't want to keep the secret on the device. In order to verify that a code is correct without knowledge of the secret used to generate it, we will generate a list of future OTP codes and put them in a Merkle tree. We can then commit the root of the tree to the smart contract wallet, which can then verify witnesses that a future generated code is the correct code at a given time. The Merkle tree is structured like the image below. https://github.com/hotpot4337/contracts/raw/develop/FlowSafeTOTPmerkleTree.png
  • Papa Wallet
    shaddamciv  ·  Updated 319 days ago
    A family wallet/portfolio manager using gnosis safe and enzyme finance. Utilize Stripe to top up, superfluid to manage subscriptions and gelato to setup gasless payments. A good way to pass on your legacy to the future generation, the papa wallet features a recovery module.
  • onNFT
    Ananya_Gupta  ·  Updated 328 days ago
    The project builds a flow allowing users to sign-in using web2 Social Accounts or Web3 EOAs, get access to their own smart contract wallets, and be able to buy NFTs or other web3 assets using credit cards . Stripe Gelato Web3Auth Safe AA onNFT helps you access all the capabilities of Web3, directly through your Social Logins using Web3Auth Removes the requirement to create a Metamask Wallet, or remembering 12-word Seed Phrases A Safe wallet is created under the hood, that allows users to initiate and execute transactions The need to understand Cryptocurrencies before buying an NFT is gone now You can simply buy an NFT directly through your Credit Cards, implemented using the Onramp Kit The fiat-to-crypto transactions are handled by the Onramp Kit. Your credit card transactions are secured by Stripe, making the entire flow seemless While buying NFT's, you will not have to manually sign every transaction With a single click, your NFT will be minted directly to your account No need to understand the concepts of Gas Fees or Approvals on Web3 We bear The transaction fees (or the gas fees) of your NFT minting using Gelato's Gasless Transactions The website requires no need of an additional application for any functionality Makes it easy to access it from all devices. After this POC, the aim is to abstract it into a wrapper, thus providing a AA solution with onramp support, so that dApps can direcly plug it to support SCWs, gasless payments, token-independent gas payments, and credit card payments for web3 asset purchases. Further, using a SCW opens up the possibility of developing transaction safeguards, adding access control and building better account recovery to further improve the UX.
  • Geo Web
    graven  ·  Updated 328 days ago
    Hackathon Scope Description For this hackathon, we overhauled the onboarding process and transaction flow for the Geo Web Cadastre (interface for the Geo Web's NFT land market) to take advantage of all that account abstraction has to offer. Our hackathon scope included: Social login (signer account) via Auth Kit & Web3Auth Geo Web-sponsored Safe (smart account) initialization via Gelato 1Balance Batched transactions via MultiSend (wrap ETH to ETHx, authorize token transfer, authorize Superfluid token stream, & land parcel transaction/claim) Paying ongoing gas fees from the user's Safe via Relay Kit & Gelato SyncFee These changes make the Geo Web dramatically more accessible to new users and open up possibilities for power users (e.g. privacy). It reduced the number of distinct transaction submissions required to make a parcel claim/bid from 4 (wrap ETH to ETHx, approve ERC20 allowance, approve Superfluid stream allowance, & mint/bid) to just 1! Looking forward, we plan to add the Stripe fiat-to-crypto onramp when it becomes available on Optimism. Support for ETHx gas payments with SyncFee will allow us to completely abstract away the difference between ETH & ETHx too. Demo Note: We have not yet implemented Safe/smart account control of Geo Web parcel Ceramic streams, so content changes (e.g parcel name & content link) don't yet persist. Tracks Applied For Safe Gelato Web3Auth Superfluid Ongoing Project Description The Geo Web is a set of protocols that build public consensus for geospatial augmented reality. Think of Pokemon Go but rather than just a siloed application, relevant & composable content, applications, & information are discoverable at physical-world locations through a universal spatial browser (like a web browser that uses GPS instead of URLs). We use a novel property rights system ( partial common ownership /Harberger taxes) to administer a fair & productive market for who can anchor content where in the world on the network. Instead of installing apps on a device, publishers anchor “apps” to locations on Earth for all visitors to experience in augmented, shared reality. 100% of the funds collected through the land market are allocated to public goods and the creation of positive externalities through market incentives. With this model, we can bootstrap a coherent open spatial web browsing experience that challenges the app stores & attention economy algorithms for supremacy in the metaverse era.
  • Gelato Art
    hurley87  ·  Updated 328 days ago
    Gelato Art uses Gelato's account abstraction to make it easy for anyone to sign up and mint NFTs without needing a crypto wallet. It's built on Base (Coinbase's L2) so transactions are quick and cheap. Gas is sponsored for all transactions so it feels like a web2 app.
  • Chora
    rawmahn  ·  Updated 175 days ago
    Chora is a self-custody telegram chat bot designed to simplify and enhance your DeFi journey. It redefines how you interact with the DeFi world. ✨ With Chora's account abstraction based on Safe, managing your transactions has never been smoother. Experience a new level of convenience as Chora transforms your intents into transactions in the blink of an eye, powered by the intelligence of ChatGPT. 🔒 But what about security? Fear not! Chora empowers you to keep your keys safe while effortlessly connecting your Metamask mobile wallet, ensuring your assets are in your control at all times. 🌟 Trade with unparalleled ease on decentralized exchanges and beyond! This hackathon submission is our first telegram chatbot MVP. Our previous concept was based on a web app. Only Polygon PoS is supported atm. And we have much more on our roadmap: Delegating partial control, enforced by the smart contract. Think limit orders, trading strategies, and more, without giving the custody away Ultimate security + recoverability for your account, powered by Chora recovery module Extensive protocol support (staking, bridging, borrowing, etc)
  • AIrtist
    markcarey  ·  Updated 329 days ago
    AIrtist is like Instagram for AI art: instead of uploading photos, users enter text prompts used by AI to generate the images. Features include both "web 2.0" style social features like commenting, liking, and reposting, as well as (optional) web3 features like minting images as NFTs on the blockchain. AIrtist uses "account abstraction" to make it seamless for users, without needing wallets nor gas tokens to get started. Even when minting NFTs, users never have to "send transactions", "sign messages", nor write down 12- or 24-word phrases on pieces of paper. AIrtist uses sponsor tech related to the following tracks for the Safe “March for Account Abstraction” Hackathon : Safe Gelato Superfluid Stripe web3auth Try it now: https://airtist.xyz (minting on Goerli testnet) Slide Presentation Demo Video: https://youtu.be/HlvKtf1z-AM Using web3Auth, AIrtist login options include social, email, or wallet. Social/email logins will generate an app-specific private key … behind the scenes, no seed phrase needed – only the user has access to the complete private key (self-custody), enabled by Multi-Party Computation (MPC). Social login users: do not need a wallet do not see an EVM address are not asked to “sign” any messages do not need ETH or any other token for “gas” Note that when choosing the wallet login option, AIrtist checks for an ENS name for the connecting address, and if found, will use that as the "name" of the user on AIrtist. For example, if I choose to login via web3auth using my primary Metamask address, AIrtist will show me as markcarey.eth . Several "web 2.0" styles features include: Creating and sharing AI images. User enter text prompts to share AI-generated art. (powered by DALL-E from OpenAI) Liking. Users can "like" images shared by others Commenting. User can post comments in reply to shared images Reposting. This is a bit like retweeting , but with a twist. A repost does not re-share the same identical image, but rather uses the same identical text prompt to generate an entirely new image. Following. Users can follow other users, if they like their artwork. Some users may optionally decide to mint images as NFTs on the blockchain. When users post new artwork, they can: Choose to immediately mint the image on the blockchain. Enable others to mint the image for a price. Neither (image will not be minted) Creators can always decide later -- after posting -- to mint their own images. Minting during art creation is done by toggling a checkbox. For images already posted, minting involves a single click/tap. In both cases, the user does not have to send transactions nor sign messages. When minting your own artwork, it costs 1 pAInt token. When minting images posted by others, you pay the price set by the creator, denominated in either pAInt or WETH . pAInt is a native Super Token that supports real-time streaming, powered by Superfluid. It acts as a utility token on the AIrtist platform for minting NFTs. Users start with 5 pAInt and after their first mint, active users receive 3 pAInt per month, streamed in real-time. See the streams on Superfluid Console . It's like watching paint stream.😐 When the user decides to mint their first NFT -- and not before -- on-chain transactions are triggered, behind the scenes: A Safe smart wallet is deployed. This is a “1 of 3” multi-signature Safe. The user’s web3auth-generated address has full access as 1 of the 3 owners. The second owner is a AIrtist Hot wallet enabling behind-the-scenes Safe transactions on the behalf of the user. The third owner is a AIrtist cold wallet for emergency/recovery purposes. ERC20 Approval transactions are sent from the Safe to facilitate the first and future mints. Sent via Gelato Relay, a transaction is sent to start streaming 3 pAInt per month to the Safe. Also via Gelato Relay, the minting transaction is sent to mint the NFT to the shared AIrtist NFT contract. Remember, the above 4 transactions happen behind the scenes . From the user's perspective all they did was check a box or tap a link . AIrtist uses Gelato Relay to send tokens and NFTs to users' Safes (and one more action discussed below). These requests are signed and submitted on-chain by Gelato relayers, with gas paid from AIrtist's Gelato 1 Balance account. Each of the three contracts deployed by AIrtist support ERC2771 Context which enables secure transactions to be signed by AIrtist but relayed onchain by Gelato Relayers. This works seamlessly with OpenZeppelin's AccessControl permissions to restrict functions to authorized signers. Subsequent NFT minting triggers a single transaction -- via Gelato Relay -- to mint the NFT to their Safe, while withdrawing 1 pAInt from the Safe for each NFT minted of their own art (or the required amount of pAInt or WETH if minting others’ art). If a user has less than 1 pAInt they cannot mint and must wait until they accumulate enough via the incoming stream (or by other means 🦄) Scenario: a creator has joined AIrtist and posted several images, but has not minted any yet. But the creator has enabled minting of the posts, and set prices and currencies ( pAInt or WETH ) in each case. What happens when another user decides to mint these images? How does the creator get paid, when no Safe has (yet) be deployed for the creator? As mentioned above, the Safe is only deployed when the user does their first mint, and not before. Even though the Safe has not been deployed, the creator still gets paid! When the creator joined AIrtist, the Safe SDK is used to accurately predict the user's Safe address, even though it has not yet been deployed . This predicted Safe address is assigned to creator's user account, and when pAInt or WETH gets sent to that address, it just works, and the funds are owned by the predicted Safe address . When/if the creator triggers their first mint, the Safe will then be deployed to the predicted address and the creator will have full access to the tokens sent previously. Since we are sponsoring -- paying the gas for -- users' transactions, using pAInt as a utility token helps limit the gas costs associated with users on the FREE plan. These users receive 3 pAInt monthly, streamed in real-time. For serious AIrtists, minting 3 NFTs per month may not be enough. AIrtist uses a freemium business model, where cloud-computing and gas costs are subsidized (sponsored) for FREE users, while revenue from PRO users more than offsets those costs. AIrtist PRO is a monthly subscription powered by Stripe Billing. Consistent with the goal of account abstraction, PRO users pay via credit card recurring billing (with future plans to add support for crypto-native billing options). a dedicated NFT contract for each PRO user (deployed from the AIrtist Factory contract via Gelato Relay) increased stream, now 30 pAInt streamed monthly in real-time preview before posting: view multiple images based on your text prompt, then choose the best to post (coming soon) option to keep prompts private from other users (coming soon) more to come When a user buys a PRO subscription, an event is sent from Stripe to a webhook endpoint on the AIrtist API. This triggers the 2 transactions (via Gelato Relay) to deploy an NFT contract for the user and to increase the stream to 30 pAInt per month. Additionally, as an "upgrade bonus", 10 pAInt are airdropped to the PRO user's Safe at the time of the upgrade. From this point forward, the user's images are minted to their own contract/collection, which contains only their own artwork. When a PRO subscription is cancelled, another event webhook automatically triggers a transaction to reduce the stream back to 3 pAInt per month and flip the user back to minting on the shared NFT contract. There are three main categories of code for AIrtist: Frontend Client App Server APIs and Datastore Ethereum Smart Contracts The live demo of the front end AIrtist app is located at https://airtist.xyz . The app includes javascript code that primarily interfaces with AIrtist server API endpoints. The javascript web3auth SDK is used in the frontend to power all forms of authentication. Using web3 auth, the user can choose to login with social apps (ie. Twitter/Facebook), email, or wallet (ie. Metamask/WalletConnect). The web3auth SDK interfaces with the nodes in the Auth Network to produce an app-specific private key for the user. The private key exists only in the browser and it never sent to AIrtist servers nor saved by any third party. The web3auth SDK also produced a JWT auth token, that is used by AIrtist as an API key when calling authenticated AIrtist API endpoints (see more below). The frontend uses the Firebase Firestore SDK to fetch and render AIrtist data stored in a Firestore data store: data about users, posts, followers, social reactions, etc. The HTML and CSS of the AIrtist frontend was built using the Instello Ultimate Photo Sharing HTML Template set, used under license. The frontend is hosted using Firebase Hosting. The frontend code can be found in the repo at server/hosting/ . AIrtist uses three core services from Google Firebase for server-side functions. Firestore . Data about users and posts are store in a noSQL Firestore datastore. Storage . Once images have been generated via OpenAI SDK, they are stored using Firebase Storage (Google Cloud Storage) Firebase Functions There are three types of serverless functions. The first is an HTTPS function that handles requests to the AIrtist API endpoints, used to access and modify Firestore data and interact with Ethereum smart contracts. Next there are several functions that are triggered by adding or updating data in the Firestore database, which in turn may trigger interactions with the Safe and Gelato SDKs to execute functions onchain. Finally, there are two "cron" functions that run periodically. These poll the Gelato Relay API for the status of transactions that have been relayed to Gelato. Once Gelato reports that a transaction has been executed, the transaction is fetched using EthersJS and relevant data is extracted from the event logs, such as the tokenId of a newly minted NFT, or the nftContract address of a newly deployed AIrtNFT contract for a PRO user. Three smart contracts were written in Solidity for AIrtist: AIrtNFT.sol - This is an ERC721 NFT smart contract, leveraging OpenZeppelin contracts. A notable inclusion is the support for ERC2771Context which enables secure permission-based function calls via Gelato Relay. Also added are two minting functions which power minting of new images, collecting and transferring pAInt or WETH tokens when necessary. AIrtNFTFactory.sol - This a factory contract used to deploy minimal Clones of the AIrtNFT.sol contract. This contract was used to deployed the main NFT contract that is shared by FREE users, and also used to deploy NFT contracts for each PRO user when they upgrade. Fun fact: Using the minimal clone approach, it actually costs less gas to deploy an NFT contract for a PRO user, compared to minting an AIrtist NFT! . Streamer.sol - This contract uses the Superfluid protocol to enable streaming of the pAInt utility token, which was also deployed by this contract at deployment time. The core function of the streamer contract enables the starting, updating or stopping of a pAInt stream to a recipient, while optionally dropping some pAInt immediately (not streamed). (Shared) AIrtNFT contract: 0x85ea20193d88A4e4BCb45224CE462029608158c3 # AIrtNFTFactory contract: 0x9d1248BA4EF720da649aE5bFa9cA46311C028af4 # Streamer contract: 0x83D4A49b80Af1CE060361A457a02d057560A9aD9 # pAInt Super Token: 0xB66cf6eAf3A2f7c348e91bf1504d37a834aBEB8A # Example PRO AirNFT contract deployed using the factory contract via Gelato Relay: 0xbeccc3e7bfcc3a2071ff4c11ef5eab7d134906f2 # Note: the "Transactions" tab on Etherscan shows empty (or almost) for the above contracts. This is because almost all transactions are executed via Gelato Relay. As such, you can view the "Internal Transactions" tab to view the activity on these contracts. Here are some quick links to code in this repo, including some examples of where hackathon sponsor tech was used: Contracts Frontend AIrtist API Server cron functions Server DB Triggers web3auth SDK: client , server-side JWT verification Safe SDK: deploy/predict Safe address , send Safe transaction Gelato Relay SDK: update Superfluid stream , mint NFT , deploy contract via Factory , poll API for task status Superfluid: streaming contract , update Superfluid stream via Gelato Relay Stripe: frontend redirect user to Stripe payment link , server-side Stripe webhook handler OpenAI SDK: generate AI image Further development of PRO premium features: Art generation tools Open Edition NFTs NFT auctions Mobile apps for iOS and Android Better support for web3-native users (use own wallet instead of Safe, on-chain Subscriptions, etc.) Production launch to Layer2(s) and ETH mainnet (with higher prices) Try it now: https://airtist.xyz (minting on Goerli testnet) Slide Presentation Demo Video: https://youtu.be/HlvKtf1z-AM Twitter: @mthacks Farcaster: @markcarey Discord: @markcarey#5670 Github: @markcarey
  • artDrop
    Yajassardana  ·  Updated 328 days ago
    ArtDrop lets you turn your artistic ideas into reality using generative AI and then gaslessly mint your creations as NFTs on the base network. The product as one aim: to bring a new wave of users into web3 by creating an experience, which is simple and easy to use while being interesting and fun at the same time. Gelato Base Web3Auth Safe AA Most people never stepped in the world of Web3 with all the intricacies and jargons surrounding it. These exist in terms of:- Creating and understanding EOA Wallets, and managing Seed Phrases Understanding how NFTs work, and how to create and access them Jargon aroung Payments (in terms of pricing, chains, and gas fees) Lack of entry points that make Web3 interesting and fun No more remembering Seed Phrases powered by Web3Auth Login directly through your Socials (Gmail, facebook, discord etc.) Seamless Login Powered by Web3Auth No need to create or connect Metamask wallet, we handle accounts for you. Zero Transaction fees, Go Gasless with **Gelato Gasless Wallet SDK ** The NFTs you Mint are free, owned by you No transaction fees, we provide gas to fuel your creativity! Gas fees on us, by using Gelato's Gasless Onboarding No more manual transaction approvals, by Safe No need to sign and approve every transaction Account Abstraction achieved through Smart Contract Wallets provided by Safe Image Creation With Prompts using Stable Diffusion AI Simply add a prompt to inspire the image you want to create Get an NFT of the image you create rendered on the website Secure, Fast and Reliable NFT Minting with Base Mint the image you create with a single Click Get the NFT in your account in just a few seconds Access Across All Your Devices Create and Mint your NFTs from anywhere, everywhere directly through mobile phones, tables or desktop devices No app downloads (not even Metamask) to enter the world of Web3 Catalogue of all your creations No need to go to other platforms to see what you possess Find all the NFTs you create and mint, directly on the website under "View NFTs" Web3 Auth for enabling Social Login Gelato Gassless Wallet for sponsoring Gas Fees, making the app completely free to use Base-Testnet for deploying NFT Smart Contract for NFT minting Stable Diffusion AI @ Replicate for Image Generation Chakra-UI for styling NextJs for App Creation
  • Weather Forecaster Game
    aeither  ·  Updated 330 days ago
    Watch Try it Fun and Simple Prediction Game based on real-life events with Seamless Web3 Integration for Web2 experience. Starting point for building a fullstack dapp, a fun and simple prediction game with seamless Web3 integration for a Web2 experience. It's also a great fit for learning the basics of smart contract development and integrating Gelato into your project. The project is a monorepo setup to be easily extended to any device you would like to use: IOS, Android, Macos, Window, Web. The Current working version is in the nextjs folder. The Weather Game allows players to login with their email and predict the weather for the next hour. By accurately predicting the weather, players will automatically receive reward tokens in their wallet. Deploy ERC20 Token Contract Deploy Weather Contract passing ERC20 Token to the constructor Deploy Web3 Functions and update the addresses in use-weather-game.ts Set up the env variables cp .env.example .env Install and run yarn && yarn web next, trpc, tamagui, gelato Building a decentralized betting game that relies on real-world events can be a challenging task. However, with the power of Web3 functions, this process becomes much easier. By leveraging the ability to call any type of API and trigger on-chain functions, developers can create seamless and engaging user experiences that integrate with the real world. This project can serve as a solid foundation for your own Web3 project. With gasless onboarding and Web3 functions already integrated, the possibilities are endless. Here are a few ideas to get you started: Create an option market Develop a lottery system Build a sports betting platform Let your imagination run wild and use this project as a starting point to bring your Web3 ideas to life!
  • BetMe
    darcksday  ·  Updated 325 days ago
    BetMe is a decentralised, peer-to-peer prediction market, built via Account Abstraction technologies for improve UI experience. For build AA and gasless transaction we use combination of Gelato 1Balance && Relay, Web3Auth and Safe Contract Address. To display current prices on the UI, we using the RedStone API. On the contract side, we implemented the RedStone Price Feed to obtain current prices and close bets. The Gelato Web3 functions are responsible for generating and updating the redstonePayload (byte code required for the getPrice function) and controlled the expiration of bets for distribute funds. Three smart contracts were written in Solidity for BetMe: CustomChallenge.sol - This contract responsible for Custom bets. Deployed on Mumbai Testnet 0xDb0C8933A0EEe4a07d8A524f27E9041fA58C0AFc PriceChallenge.sol - This contract responsible for Price bets. Extend RedStonePrice contract. Deployed on Mumbai Testnet 0xbB2c5955eFf974Dd4F870f4902183732318C9415 Link Here are some quick links to code in this repo, including some examples of where hackathon sponsor tech was used: Contracts Frontend Gelato Gasless Wallet Web3Auth Gelato Gasless Transaction These instructions will get you a copy of the project up and running on your Mumbai testnet for development and testing purposes. nodeJS >= 16.0 npm Install dependencies and create environment file: npm install cp .env-example .env Fill environment variables. npx hardhat run smart_contract/scripts/deploy.js --network mumbai npm run start npm run build Go to https://relay.gelato.network/apps Deposits some tokens to 1Balance Create App and copy Api Key Fill GELATO_API_KEY on .env git clone https://github.com/darcksday/betme-gelato-functions npm install cp .env-example .env Fill environment variables. npx w3f deploy src/web3-functions/my-web3-function/index.ts Copy CID Go to https://app.gelato.network/ Create task with you contract and CID Run on mainnet and add ability deposits via credit card Launching pool bets, with dynamic coefficient and unlimited participants Dynamic automated events (sources of information for Oracle setup manually) Add ability to bet for more assets,real-world events,sport, politics etc. Try it now: https://challenge-seven-psi.vercel.app/ (on Mumbai testnet) Demo Video: https://youtu.be/u4QmkGzS8wQ Twitter: @MacksPopov Discord: Macks darcksday#0596 Github: @darcksday
  • Memento - Creator Platform with Account Abstraction
    diay  ·  Updated 329 days ago
    Try out memento @ https://experimental.memento.supply Our mission is to empower traditional creators & brands to unlock the full potential of NFTs. Traditional creators mostly care about three main things: (1) growing their audience, (2) engaging & reward loyal fans, (3) monetizing from new revenue streams. NFTs unlock opportunities for each of these needs; however, traditional creators have been held back by crypto complexities, high gas fees and limited UX. Memento enables creators to release digital collectibles for a consumer audience which can be claimed in 1 single click. Creators can use this product to create an NFT. Once created & deployed on-chain, they can share a claim page to their fans via a link or embeddable widget. Fans can then collect the item with just an email address in 1 click. Fans who collect the NFT will have an account abstraction wallet created for them using email as the log-in method, and they’ll receive the collectible in that wallet without having to worry about gas fees. Creators can log into the product to see their collectors and grow their email contact list. We’re already seeing creators use this as a reward mechanism to build out their email list & engage with their audience. Optionally, creators can enable payments for the collectible which will require a credit card payment to purchase the NFT. Collect a free memento: https://experimental.memento.supply/castle/memento-x-safe-on-base-1 Collect a “paid” memento w/ Stripe test info: https://experimental.memento.supply/castle/memento-x-safe-on-base-2 Test Stripe Payment Info: Card Number: 4242 4242 4242 4242 Expiry: 12/34 CVC: any three digits (e.g. 123) Zip: any (e.g. 10006) Photo or video is uploaded on Cloudinary Link is returned from Cloudinary and added to a JSON file with the rest of the Memento metadata JSON file is uploaded to IPFS using web3.storage . The ERC 721 collection is created by Memento We have funded a 1balance account on Gelato Network We’ve created a Relay app on Gelato Network to allow-list NFT factories After the user adds all the relevant data for the Memento they want to create, we create a task with Gelato Network Creators and collectors access Memento with just an email address. Memento app creates an externally owned account (EOA) and a smart contract account (SCA) for the creators and collectors. The EOA is created with web3Auth via the safe account abstraction SDK. The SCA is created with Safe ’s AA core SDK. For the SCA, we use counterfactual addresses so that we don’t need to deploy unnecessarily The EOAs are owners of the SCA. The SCA store the Mementos (ERC-721 tokens) collected by the FAN. If an SCA requires deployment, we can leverage the 1Balance and Relay app created for Mementos to do a meta-transaction for the SCA deployment. Collectors can claim / collect Mementos with just their email. New users provide their email to the app and the app generates a counterfactual SCA address for them Gelato’s 1Balance and Relay app is setup with a MultiSend smart contract a. MultiSend is allow listed and our app stores the addresses for NFTs created Stripe payments are required for NFTs that are purchased instead of claimed for free. App is setup to work on Goerli Base network Custom smart contracts: NFT Factories Multisend Safe Factory Gelato Network Relay app has the custom smart contracts added @safe-global/auth-kit is used to create EOA accounts for users when they sign in or collect a memento with their email We’ve written a custom wrapper to use Safe contracts to deploy a safe but we added a few functions to easily generate the CREATE2 address Our contracts are deployed to the Safe ecosystem NFT Factory contracts Multisend contract This is used to do mints (since NFT contracts will each have different addresses); we’ll prepare the transaction data and then send it over to this contract This contract has an allowlist (only Relay app and us are able to use it at this time; will probably add more restrictions as time passes so that our 1Balance account is not drained) Safe Factory contracts We’ve set up a 1Balance account on Goerli so that we can leverage Gelato Relay Apps on Base Goerli. We use the Relay App to interact with NFT Factory, Multisend, and Safe Factory contracts Users can accept payments for card payments for their NFT using Stripe. We use the stripe npm package and stripe webhooks to facilitate this When a creator is creating a memento, they have the option to add a price If a price is added, the creator is prompted to setup a merchant account via stripe onboarding flow Once a merchant account is approved we allow creator to create a memento with a price, and we create a product record for the memento in stripe When collectors mint a paid memento, they’re redirected to the stripe checkout to complete their purchase Once the purchase is complete, the memento it collected
  • Safe Team
    Maadhav  ·  Updated 328 days ago
    Safe Team is the ultimate team-based wallet solution for hackathons, grants, and accelerators. Say goodbye to the hassle and insecurity of using individual wallets for team funds, and hello to a secure and easy-to-use platform that empowers teams to collaborate effectively and compete with confidence. Pitch Deck Video Demo Inital Whitepaper : Flowcharts included Traditional wallet solutions for team funds can be problematic, with security and trust being major concerns. It can be difficult to ensure that team members are contributing equally and that the funds are being distributed fairly. In addition, there is always a risk of theft or fraud, and disputes over the division of funds can arise. Safe Team addresses these issues head-on with a secure and intuitive platform that allows team leaders to create teams, approve member requests, and submit teams for hackathons with ease. Using web3auth, users can sign in with their socials leading to a seamless expereince. Safe Team uses account abstraction and the Safe Core SDK to create a new multisig safe wallet, with the restriction that every team member must sign every transaction. This ensures that the team's funds are secure and that there is no risk of any one member taking off with the winnings. Also, e very transaction that happens in the wallet is relayed using Gelatos Relayer which allows the team to do gas less transaction on the funds they won. In addition, Safe Team allows hackathon organizers to require a refundable stake, which can be paid using the Stripe SDK for fiat-to-crypto transactions. This ensures that teams are committed to the project and that there is a level playing field for all participants. With Safe Team, the possibilities are endless for how teams can distribute funds among team members. They can split the funds instantly, set up a payment stream using Superfluid to fund future work on the project, or come up with their own creative solutions. The only limit is their imagination. NEXT.js Base Testnet Safe Core SDK for AA (all kits have been used) Polybase Safe Components for UI Gelato Gas Relayers Safe Team is the ultimate solution for teams who want to collaborate with confidence and win securely. With its user-friendly interface, powerful security features, and endless possibilities for fund distribution, Safe Team is the perfect platform for hackathon success. Safe: Ref Gelato Network: Ref Coinbase: Ref Web3Auth: Ref Stripe: Ref Superfluid
  • Nest Wallet
    yuan  ·  Updated 181 days ago
    NestWallet is a browser extension that aims to make using Gnosis Safes much simpler. It will significantly improve the UI/UX for multisig wallets and make them more accessible to a broader audience in the long run. Key features: Browser Extension Wallet: simply import your Safe in NestWallet extension and you are ready to go. Organization Management: create an organization in NestWallet and invite users and grant them admin/manager access. Seamless Team Coordination: multisig managers and signers will receive push notification and emails every key step of the transaction. Get your transactions signed faster! Transaction Simulation: visualize each interaction so you know exactly what you're about to sign and how much value is at risk. Paying Gas in Stripe: With Stripe integrated, we won’t have to worry about running out of gas anymore and it’s easier than ever to fund a fresh wallet. Tracks we are participating: Safe, Base, Gnosis Chain, Stripe In our demo video , we showcase our browser extension wallet, alongside tools like transaction simulation, counter factual deployment and Stripe payments for gas fees.
  • ZenGuard
    Koshik Raj  ·  Updated 288 days ago
    Detailed docs: https://docs.zenguard.xyz ZenGuard provides the easiest way to onboard users to Web3 and yet ensures that they never have to worry about losing access to their wallets. The secure recovery solutions that are seamless to set up ensure that the user always retains control of the wallet. Wallet recovery is an important aspect of the wallet UX, but this has been the missing piece in many existing wallets until now. The currently available recovery method in smart contract wallets is social recovery. Vitalik too has been the advocate of social recovery wallets for quite some time. But there are plenty of things to consider in social recovery to make it secure and easy to use as pointed out here:  https://twitter.com/VitalikButerin/status/1636608740513263617?s=20 At Zenguard we are trying to provide the best recovery solution leveraging the concept of social recovery but considering a whole lot of other things to make this as secure and convenient as possible for normal wallet users. With the help of ZenGuard, a user can quickly get started with social logins, email, or even existing wallets. Users can set various recovery mechanisms such as biometrics, email, or even arbitration. ZenGuard has been built with the help: Safe SDKs (auth and account abstraction) Web3Auth for authentication and email JWT generation and server verification Base Goerli chain for all the Safe and recovery contract deployments Wallet recovery is an important aspect of the wallet UX, so we focus on making this secure and convenient for the user. Vitalik has been the advocate of social recovery wallets for quite some time. But there are plenty of things to consider in social recovery to make it secure and easy to use as pointed out here: https://twitter.com/VitalikButerin/status/1636608740513263617?s=20 At Zenguard we are trying to provide the best recovery solution leveraging the concept of social recovery but considering other factors as well. In this hackathon, we are leveraging the account abstraction SDKs of Safe to create a Safe wallet for a user with basic social login authentication. Once the user has a wallet, they can then set the recovery mechanism with a few simple clicks and also set a secondary account or beneficiary for the wallet with additional guards like time delay. We leverage Safe modules to add these functionalities. Thanks to the following design and ideas for references: Candide Wallet social recovery module: https://github.com/candidelabs/CandideWalletContracts oAuth 2.0 verification guide by Stackup: https://www.notion.so/oAuth-2-0-verification-cac17e20dec94845973603bd34e9ce9b Here are the features that are served by ZenGuard Frictionless onboarding No more seed phrases: Thanks to smart contract wallets leveraging account abstraction that provides easy authentication mechanisms Gas sponsorships: Completely sponsor the transaction fee for the user or pay them in any tokens. Granular transaction permissions Transaction guards such as 2FA can be added to provide additional security at the transaction level. Secure and convenient recovery Thanks to smart contract wallets that enable secure and convenient recovery of wallets ZenGuard leverages Safe modules to provide the secure recovery features Additional recovery guards (conditions) can be added to enable the inheritance mechanisms. ZenGuard makes two things easy and secure. Wallet Onboarding Wallet Recovery Create a wallet by using simple auth mechanisms like social logins, email, touch ID, and face ID or even with the existing wallets like MetaMask . Perform transactions without the native currency to pay for transaction fee. Transaction fee can be completely sponsored or paid in any token. Additional security can be added for the wallet while performing transactions such as MultiSig (Provided by Safe thresholds) and 2-factor authentication MultiSig Guards : Add more than one signer (user) to approve the transaction 2FA Guards: Enable 2FA such as mobile, email OTP, Touch ID, and Face ID authentications to approve transactions Transaction limits: Set transaction limits for each crypto asset ZenGuard allows a recovery mechanism to be added to the wallet anytime. Users can add recovery mechanisms for each wallet. A recovery module will be enabled for the wallet with the help of ZenGuard's recovery infrastructure. Wallet users can select between various recovery options: Recovery types: Social recovery: Recover the wallet with the help of other devices, family and friends, or custodial signers 2FA-based recovery with the help of email, mobile number biometrics (touch ID, face ID with the help of WebAuthn ) Add your secondary email, a mobile number which will be verified before the wallet is recovered Add your biometric recovery methods with the help of a mobile device touch ID or face ID We make use of Web3Auth OAuth verification and LitProtocol Auth verification for this Addition recovery conditions (guards): To enhance and further the security of the wallet recovery process, additional conditions can be added. We call them recovery guards. Additional conditions are simple conditions that are verified only onchain These conditions provide users to set inheritance mechanisms for their wallets where the beneficiary gets access to the wallet only after an event is verified. These guards could be: Cooling period: Allows users/ beneficiaries to access the wallet after a specified inactivity period. Date/session-based: Allows the beneficiary to access the wallet at a specified date and time for a specified time duration. Arbitration-based : Allows the beneficiary to access the wallet after a specified onchain or off-chain event has been proven such as the demise of the wallet owner. We use decentralized court Kleros for this