Fluidium

Currently, dapps are adopted by mainly developers and traders with sufficient blockchain knowledge. If we want to achieve mass adoption, we require that the onboarding step (creating a wallet) is linked with our daily life (phone number).

Current payment apps (Venmo, Bizum) require digital bank app onboarding, a cumbersome and oftentimes several-day registering process that cannot send real-time payment streams.

Whether streaming money to a software service, paying for energy use, renting out digital real estate, or simply streaming to a friend, we must make the process as seamless and understandable as possible for the average user.

Fluidium seeks to supercharge the superfluid protocol, introducing non-tech/non-trade newcomers to the benefits of blockchain and payment streams. This is possible by creating wallets on the user's behalf quickly (if they choose to and until they're ready to perform tasks on their own) that are linked to their phone number for wallet verifications and notifications, while also educating them throughout the process.

As well, we do not have access to their wallet (seed phrase through zk, etc.), only their credentials and public address.

1. Phone Identification, association with blockchain address

   • Creation of random password (vrf Chainlink)
   • Custom chainlink adapter posting to sms provider the random password
   • Encrypted password validate period 5 minutes
   • Store address=> phone number on chain

2. Leverage Superfluid for money transfer

   • Stable coin as supertoken
   • Establishing maximal and minimal accepted deviation of exchange variation

3. Dapp in Angular frontend with components:

   • Phone Identificition
   • Stream into to checkout

Front-end in Angular.

Cloud function for SMS verification using a third-party SMS API.

Superfluid SDK integration in front-end to control the token flows.

Superapp smart contract deployed to Mumbai.

The Superapp associates users phone numbers to their address allowing us to abstract out the blockchain address for the user on the front-end which allows for a more user-friendly experience.

WE HAD TECHNICAL DIFFICULTIES ON BACKEND WHEN RECORDING SO WE USED FIGMA FOR DEMO. It is fixed now.