The problem Gasless Chain Agnostic Minter solves

At present, Ethereum users experience very high gas fees and operational complexity, which causes people to lose money and discourages them from using the network. Layer two solutions exist, but the user experience is difficult due to customizing wallet RPC nodes, switching networks, and understanding how layer two solutions relate to Ethereum mainnet.

Our Gasless Chain Agnostic Minter makes the user experience fast and simple when creating an NFT. The user simply inputs NFT data, clicks a button, and approves the transaction in Portis wallet. We take care of the gas payment with Biconomy and the layer two connection with a chain agnostic relay, giving the user a simple UX while taking advantage of speed and cost savings.

We see much potential for building beyond this proof of concept. We could offer gasless, agnostic functions to NFT marketplaces so they would improve their speed and expand their user base. We could also allow marketplaces to import existing NFTs with easy composability between Ethereum and layer two solutions. In addition, we see the possibility to make the user experience even easier by integrating social account logins (ex. Google, Facebook, etc.). There is also the possibility of adding NFT income streams to the gasless, agnostic experience with superfluid, enabling artists and other creators to give and receive payment streams.

We are enthusiastic about this proof of concept and see much potential for building upon the foundation we have laid with Gasless Chain Agnostic Minter.

Challenges we ran into

We were challenged to integrate Biconomy Mexa SDK into our app since this was our first time using it. Following the Biconomy docs, we tried implementing the steps and found errors at Step 4 (https://docs.biconomy.io/guides/network-agnostic-transactions/eip-2771). There was also errors integrating Portis instead of MetaMask. We then reached out to the Biconomy team and helped Biconomy confirm that the docs were outdated. Biconomy then sent us a corrected example which we then tried to integrate into our dApp. The process moved forward but we found that the the Forwarder is not relaying to the dApp’s smart contract residing on the testnet. As part of this bounty, we believe that we have assisted Biconomy with a sample use case that highlighted that the documentation requires updating (and that the SDK is possibly having minor issues in handling the signed transactions to call the smart contracts. It seems that the trusted forwarder is also required for network agnostic meta transactions, whereas the docs states that it is only required if we are trying to enable paying gas in ERC20). We are still working with a Biconomy engineer up to the submission deadline and would be happy to see this collaborative effort recognized.