[dApp Staking][Meta] dApp Staking v3

[Dinonard]

This is the meta item for all dApp staking v3 related implementation activities.

The first goal is to implement MVP of dApp staking v3 pallet, integrate it into local node and provide it to the UI team so they can test their design & frontend implementation.

TODO

Pallet

• implement dApp staking v3 functionality MVP
• benchmarks for dApp staking pallet(s)
• new precompile interface
• storage migration logic

Architecture & Functionality

• use BTreeMap instead of sorted vector for rewards?
• Oracle task definition
• pallet (or functionality) to handle cycles,eras,periods in order to align inflation & dApp staking v3

Documentation

• extensive documentation

Other

• naming adjustment & alignment
• remove forced config set from the inflation pallet before mainnet launch

Functionality

• dApp Staking v3 & Tokenomics 2.0 #990

Docs

• dApp Staking v3 astar-docs#554
• Tokenomics 2.0 docs astar-docs#553

[Dinonard]

I don't know where to comment, sorry. Please back my staked $SBY token. Now I can't use it in Shibuya-testnet. Token.Frozen? with the message.

You should have opened a github issue if you suspect a bug.
Better yet is to ask in Discord first.

For this case, you simply have tokens locked/frozen in dApp staking so you cannot move them.
This is nothing related to dApp staking v3 in particular.

[Dinonard]

@flashack4 since your comments have nothing to do with this metaissue, I will remove your comments.

Please open a proper issue in Github if you think you have found an issue or a bug.

This has nothing to do with dApp staking v3 - your tokens were locked in dApp staking v2, and they continue to be locked in v3. If you want to unlock them, you can use unlock via polkadot-js app and then once unlocking period has passed you can claim the unbonded chunks.

This is literally the same as v2 used to work so it's nothing really new here.

[Dinonard]

Transferred unresolved TODOs into separate issue items.