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
We are building a new page called Snapshots. The purpose of snapshots is created a new rewards stream for vaults users that also stake somm and otherwise participate in cosmos side somm activities.
User story:
A vault user wants to gain extra somm rewards, received airdrops etc.
They record an Ethereum account in the system by signing date with their keplr wallet. This links the two accounts. They are allowed to claim 1 Ethereum address per linked accounts.
A nice to have would be to show the amount of somm staked for the users wallet.
They can then receive airdrops and other rewards. The user flows for rewards claiming is not specified here.
When users visit the page after signing a message and connect their keplr wallet, they should see their snapshot ethereum address.
Implementation details
Create a new page modeled after the bridge page.
Users will connect their wallet and it will with the arbitrary signature api until the addresses module is live and then we will switch.
Signatures needs to be stored in database/server side component. We need to be able to look signatures by cosmos address and write new signatures to the database. We should validate the signature server side.
The text was updated successfully, but these errors were encountered:
We are building a new page called Snapshots. The purpose of snapshots is created a new rewards stream for vaults users that also stake somm and otherwise participate in cosmos side somm activities.
User story:
A vault user wants to gain extra somm rewards, received airdrops etc.
They record an Ethereum account in the system by signing date with their keplr wallet. This links the two accounts. They are allowed to claim 1 Ethereum address per linked accounts.
A nice to have would be to show the amount of somm staked for the users wallet.
They can then receive airdrops and other rewards. The user flows for rewards claiming is not specified here.
When users visit the page after signing a message and connect their keplr wallet, they should see their snapshot ethereum address.
Implementation details
Create a new page modeled after the bridge page.
Users will connect their wallet and it will with the arbitrary signature api until the addresses module is live and then we will switch.
Signatures needs to be stored in database/server side component. We need to be able to look signatures by cosmos address and write new signatures to the database. We should validate the signature server side.
The text was updated successfully, but these errors were encountered: