CryptoM.app

Inspiration

Real life - as a crypto owners we cannot utilise it in day-to-day life. We have spoken with coffee shop and bar owners and they would love to accept crypto payments - but they don't understand it at all.

What it does

Easy onboarding crypto wallet owners and leading through Become a Merchant process. As a Merchant - my business information are stored on-chain and visible for CryptoM.app users. Also I'm able to create a Transaction. From every transaction 0.3% goes as a fee to the contract.

As a Client I can find a Merchant that accepts crypto payments, go there and pay with selected by Merchant ERC20 token, f.e. USDC. After the Transaction I can leave a Rating and Review that are stored on-chain. Thanks to that community build trust together.

How we built it

We focused more on design and iterations over ideas together with UX design. Kofi was responsible for creating White Paper draft and tokenomics. Arek build a FE application and I designed UX, architecture and written current smart contract.

Challenges we ran into

The vision was constantly updated - we wanted to integrate ENS creation for Become a Merchant flow - and we still want to do this, but it took some time to understand that we were doing it completely wrong. At very first try we have even started to build a microservice in Scala that searches for a Merchants. Current implementation contains Leaflet as a map provider - we need few days more to update it to Mapbox.

Accomplishments that we're proud of

Evolution of the whole product / protocol / vision from day 1 until today. Focus on our team connecting from across the world in different continents working in different time zones organising amongst schedules to build despite minor language barriers. Typescript - for both developers. Hardhat-ethers version handling. Chainlink, WalletConnect and Leaflet integrations. Quasar as a new framework + Vue3.

What we learned

Now I finally understand basics of Cryptocurrencies ~Arek

Life has a habit of hitting you on a random Tuesday afternoon.

What's next for CryptoM.app

MVP - we are going to finish V1 of CryptoM.app (that contains - ENS Batcher service, Mapbox as an engine, deployment on Arbitrum, total refactor of the contract - we want to implement ERC4337 solutions to allow for account creation with email + give possibility for clients to pay only the amount visible on the screen during the transaction. We want to take a fee from each transaction (0.3%) that goes directly to the paymaster contract + a lump for a fee. More details in our Whitepaper - expect it soon!).

Then we want to get external funding to continue working on V2: V2 - will be a whole WaaS solution and will introduce MAP token. This version with functionalities like paying in whatever crypto you like - swaps during transaction, implement Learning Zone, Challenges allow clients to Become a Merchant with just a MAP tokens. We will focus on solving and updating V1 to get optimal user experience. We also want to give possibility to store the tax into special sub-account and feed Chainlink with product prices taken from updated Receipt system.

V3 - we will decentralized our application, splitting the revenue between MAP token holders and Treasury Fund - we want to airdrop most of the tokens for CryptoM.app users (working on incentives mechanisms).