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
the XP score management needs to be gasless from the users' pov
ideally they shouldn't have to claim their XP, it should be airdropped to them
we could say that we airdrop XP at the end of every epoch, but it wouldn't feel as real as doing an onchain transaction -> see XP score go up by 1
XP score should be integrated and displayed in (at least) Status app mobile + desktop + status.network website. could maybe even be merged with the Logos OP project (depending if the tokenomics make sense. if they don't, we can always say that users with XP on OP receive an XP airdrop on status network)
XP need to be soulbound (non transferrable) but lendable (like https://eips.ethereum.org/EIPS/eip-4907 if we consider that they are an NFT)
at some point in the future, XP could be burned for SNT
initially XP can earned by:
--> staking SNT
--> making an onchain tx on status network
--> having pledged TVL prior to the network launch
then we can give users other ways to earn XP:
--> getting an XP grant for building a project or deploying a protocol on status network
--> using specific apps or protocols that get an XP boost for some defined time (like campaigns where users can earn more XP when they interact with those protocols)
--> voting (for example Snapshot would be a boosted app in that perspective)
later when we have a deeper integration in status apps:
--> creating/joining/interacting with Communities
--> doing transactions on Status wallet but on other chains than Status Network
--> using Keycard (?)
There's a bunch of things we need to figure out and clarify here with the TKE an Status chain team.
EIPs of interest:
The goal of this issue is to settle on what a first version of this NFT will look like and how it will be distributed via the staking protocol.
The text was updated successfully, but these errors were encountered: