PayPol

PayPol

Streamline transactions, simplify payments - Web3 made easy with app-specific handles and ENS support, plus seamless token requests between users.

PayPol

PayPol

Streamline transactions, simplify payments - Web3 made easy with app-specific handles and ENS support, plus seamless token requests between users.

The problem PayPol solves

Managing transactions in the current digital landscape can be complex and time-consuming, with the need to remember and share wallet addresses and other sensitive information. However, a new Web3 based application aims to simplify this process by solving the problem of complicated transactions.

This application introduces the use of app-specific handles and ENS support to create a more secure and user-friendly environment for transactions. Users can easily send and receive payments through their customized handle or personalized domain name, which eliminates the need to remember and share wallet addresses. This not only saves time but also reduces the chances of errors and fraudulent activities.

Furthermore, the application also addresses the issue of requesting tokens from other users. Users can request tokens through the app's interface by providing the recipient's handle or ENS domain name associated with their account. This eliminates the need to navigate complex token transfer processes, making it easier and more convenient for users to request tokens from others.

We also have Gullak which is a service by which users can save their tokens away from their wallets. Gullak is a Payable smart contract which enables you to hide the tokens that you hold. This also helps in saving of tokens as you don't readily hold them to spend them.

In conclusion, PayPol solves the problem of complicated transactions by introducing app-specific handles and ENS support, making transactions simpler, more secure, and user-friendly. By addressing these issues, this application creates a more efficient and effective digital payment system for all users.

Challenges we ran into

Faced alot of challenges while integrating arcana where the we were not able to get provider and signer from arcana, next we faced issues with it as it was giving errors like Invalid Hook Calls, due to useAuth(). We were able to fix these issues with help of Arcana's Documentation and some help from their Discord Server.

Tracks Applied (3)

Polygon: Open Track

Our Project is around making a UPI like user experience for a web3 user which has features like send and recieve using h...Read More

Polygon Technology

Arcana

We have used Arcana's auth and Wallet for seamless user onboarding in our app using its login with Email and Social. Als...Read More

Arcana Network

Quicknode: Built on QuickNode RPC

We use Quicknode's RPC provider for fetching and signing transactions.

QuickNode

Discussion