-
-
DApp main page
-
One time payment request modal. Requestor specifies the token and amount
-
One time payment page. Sender pays the token amount specified by requestor
-
Permanent payment page. Sender can manually input the token and amount
-
Portfolio page
-
Ethereum Mainnet portfolio page
-
Polygon Mainnet portfolio page
-
Transaction page
Inspiration
Currently as a payer, in order to send a recipient money on EVM-compatible blockchains, he or she needs to know the address of the recipient. However, a recipient may feel uncomfortable sharing his or her wallet address with the payer because:
- it allows the payer to make a connection between the recipient’s wallet and the identity of that recipient
- it exposes all of the recipient's financial history to the payer (ex. number of tokens, amount of each token, transaction histories of each token, NFTs, and to whom and where money is being sent or received)
What it does
Wisp is the first decentralized bank protocol which allows anyone to:
- Receive payments without revealing their wallet addresses
- Send payments straight from their Wisp wallet
- Download account statements for official reporting
- Passively re-invest money right from their wallet (under development)
How we built it
- DApp frontend is built using Next.js and TypeScript
- DApp utilizes SNARK zero-knowledge proofs and asymmetric cryptography to keep your assets secure and private
- ZK circuits are built using circom language and solidity verifies are exported via snarkjs
- Smart contract wallet allows automatic funds reinvestment
What's next for Wisp
- Re-invest funds in the smart contract using Aave or own lending protocol for APY gains
- Turn the app into a full-featured wallet
- Allow private NFT transfers
- Wisp SDK for private payment integrations
Built With
- circom
- graphql
- nextjs
- solidity
- thegraph
- typescript


Log in or sign up for Devpost to join the conversation.