You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A handy tool/feature to send tokens via link (URL), without having to know the recipient address.
Interaction Flow
(Extension) Sender selects the Send via Link option when sending tokens
(Extension) Sender enters information (select token, enter quantity)
(Extension) Sender generates a copyable link and QR code
(External) Sender sends the link or QR code to the recipient using any messenger
(Webpage) Recipient enters the dedicated webpage via the link or QR code to claim tokens
(Webpage) Recipient creates a new wallet (Google Login provided) or connects an existing wallet and claims the tokens
Possibilities
Can be something that helps to lower the "Web3" barrier for newcomers.
Can generate multiple links at once and send each link to multiple people (airdrop, events, etc).
Can make good synergies with MPC login tools (Google Login etc) for not crypto-friendly users.
Consideration
Should make a limit on the token amount that can be sent using the SVL (to prevent the loss of funds due to human mistakes).
URLs should be random/secure enough so that URLs cannot be first accessed by others.
Should add a claimable period (i.e., only claimable within 24 hours since the link generation), and if not claimed, the funds go back to the original sender.
Should be 100% open source, plain written in Gnolang.
Any feedback is welcome!
The text was updated successfully, but these errors were encountered:
@adr-sk Can you create an issue for each of the pending features/improvements we're planning on adding to Adena? This way, we can make them visible, gather feedback for improvement, and set priorities internally.
Overview
A handy tool/feature to send tokens via link (URL), without having to know the recipient address.
Interaction Flow
Possibilities
Consideration
Any feedback is welcome!
The text was updated successfully, but these errors were encountered: