Solva

UX is well known to be one of the subject that need a lot of improvements in Web3 - there's just too much terms and concepts to understand for your mother to start using a web3 app.

Solva (from the latin solvere, to settle / pay / solve) aims to be a user friendly replacement to a quick payment app like Venmo or PayPal, using crypto under the hood without you even knowing it. Create an account with your email or social login with Google/Apple etc, choose a username and you are ready to go! Top up your account with a credit card and send money to your friends & family in a few clicks without ever seeing a transaction signature modal or seeing the words "gas fees". If you are already a degen, you can of course login with your favorite wallet, top up your account with crypto on EVM chains, and take full control of your underlying wallet at any time (which Solva never has access to).

Solva is a Real World payment app, for Real World users.

To provide a seamless experience, Solva leverages several technologies. The first one is the social login & account abstraction with gas sponsorship by Thirdweb to allow user to connect with familiar methods and interact like they would in a Web2 app. To abstract addresses, ENS subnames of solva-app.eth are used on Polygon mainnet. Interactions with the ENS smart contracts are done by our backend that uses a Cloud Wallet from Curvegrid for simplified blockchain interactions. End users just have to choose a username that isn't already used, and the corresponding ENS subname will be assigned to their address. They can also upload a profile picture, that will be uploaded & pinned on IPFS with Pinata, and saved in the avatar text record of the ENS.

To transfer funds, a proxy smart contract (also on Polygon mainnet) is used to make some checks and emit an event for easy tracking. This event is send to the backend by a Curvegrid webhook to allow it to index transactions in a PostgreSQL database, used to easily and rapidly retrieve informations when a user navigates in the app (all the data in the database can be reconstituted from the on chain interactions).

A potential business model would be to charge transaction fees on payments made to business, and although this wasn't implemented during the hackathon, advanced users can still create webhooks to be alerted on new incoming transactions, which could be one of the feature given to enterprise users.