Key Features • Short Description • How To Use • Inspirations •
- Easy to create peanut link for crypto transfers
- Waku for non-tracked P2P network data transfers
- Keeping IPs private and avoid tracking
- Sismo for gate-kept access to link, enabling targeted access
- Access is witheld until web2 account or web3 wallet ownership is proven (ZKP)
- Secret Network for enhanced privacy encrypted NFT metadata containing the peanut link
- Servicing more than EVM
- ENS integration for sponsors to quickly find prize winners and vice-versa
- Minimising wrong contract address and misdirecting funds
- Gnosis and Base to hold SBTs for EVM catering
- Custom SubGraph for sponsors to keep track of all deployed SoulBoundTokens
- Essentially for sponsors to monitor all historical bounty awards
The service we provide is that we privately track deliveries of cryptocurrency bounties earned in hackathons. The identity of the recipient and sender are scrutinised and both parties are given constant information about the whereabouts of the package.
Identification of a common pain-point in the process of onboarding developers into our industry seems to be the disconnection between earning a monetary reward from a Hackathon and not knowing when it will be received into our wallets. This coincides with a dangerous and increasingly vulnerable attack vector for our protocols, the advent of deep fakes for example urges the development and strengthening of our KYC procedures.
-
As a sponsor you must log into the platform through Sismo in order to prove your identity also. This is important because phishing attacks are becoming more sophisticated.
-
Once wallet is also connected. Then its time to define the parameters to generate the peanut link. This includes the target address, the amount to transfer and which network.
-
Then you have the choice of either sending them an EVM based soul-based-token containing the link OR you can create a view-key for a secret NFT and send the view key to the user allowing them to claim.
-
User then signs in using sismo identity check by verifying their github for example. Then is able to either access the SBT or the view key (and the private metadata containing the link).
-
The user goes through the peanut claiming procedure and receives their money.
https://goerli.basescan.org/address/0x36a20007846639De19d63C3da976f8b5Ea1BfeDc https://gnosis-chiado.blockscout.com/address/0xb5dD8f6770593bC05Dc5B336F809695Ee481c991
https://api.studio.thegraph.com/query/50144/soulbound/0.1
https://twitter.com/The_Game_2030/status/1710885983283991014
We are solving the issue of misdirected funds by gatekeeping the dashboard utilising Sismo to only unlock peanut link generation if the profile meets the security checks.
- Why is this necessary?
Businesses manage many invoices, it’s not unknown for bad actors to spoof invoices and will become a bigger exploit as we scale. Plus, people don’t actually mind waiting one quarter for their earnings. They mind being in the dark about when they will receive them.
- How is this different from sending a transaction to a wallet address and double checking its correct?
Firstly, there is an adaptable KYC procedure whereby by configuring sismo, sponsors can enforce the targeted recipient to have specific web2 account or other bespoke requirements. There is also the notable difference that it utilises a Peer-to-Peer network to broadcast the peanut link as opposed to a direct transaction.
- What is the plan going forward?
Combine the peanut link delivery mechanisms to achieve a stronger more secure system. Whereby the viewkey and tokenid from the secret network NFT is passed through Waku.
GitHub @Podima2 · Twitter @The_Game_2030
GitHub @mxber2022 · Twitter @mx_maharaja