-
Notifications
You must be signed in to change notification settings - Fork 700
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Store nomination pool total value locked on-chain #155
Closed
liamaharon opened this issue
Jul 12, 2023
· 1 comment
· Fixed by #1322 · May be fixed by paritytech/substrate#14775
Closed
Store nomination pool total value locked on-chain #155
liamaharon opened this issue
Jul 12, 2023
· 1 comment
· Fixed by #1322 · May be fixed by paritytech/substrate#14775
Labels
C1-mentor
A task where a mentor is available. Please indicate in the issue who the mentor could be.
I5-enhancement
An additional feature request.
T1-FRAME
This PR/Issue is related to core FRAME, the framework.
Comments
4 tasks
Hey, @liamaharon I would like to work on this. |
the-right-joyce
added
I5-enhancement
An additional feature request.
C1-mentor
A task where a mentor is available. Please indicate in the issue who the mentor could be.
T1-FRAME
This PR/Issue is related to core FRAME, the framework.
and removed
J0-enhancement
labels
Aug 25, 2023
Merged
Ank4n
added a commit
that referenced
this issue
Oct 1, 2023
What does this PR do? - Introduced the TotalValueLocked storage for nomination-pools. - introduced a slashing api in mock.rs - additional test for tracking a slashing event towards a pool without sub-pools - migration for the nomination-pools (V6 to V7) with `VersionedMigration` Why are these changes needed? this is the continuation of the work by @kianenigma in this [PR](paritytech/substrate#13319) How were these changes implemented and what do they affect? - It's an extra StorageValue that's modified whenever funds flow in or out of staking for any of the `bonded_account` of `BondedPools` - The `PoolSlashed`event is now emitted even when no `SubPools` are found Closes #155 KSM: HHEEgVzcqL3kCXgsxSfJMbsTy8dxoTctuXtpY94n4s8F4pS --------- Co-authored-by: Liam Aharon <[email protected]> Co-authored-by: Kian Paimani <[email protected]> Co-authored-by: Ankan <[email protected]> Co-authored-by: Ankan <[email protected]> Co-authored-by: command-bot <>
bgallois
pushed a commit
to duniter/duniter-polkadot-sdk
that referenced
this issue
Mar 25, 2024
What does this PR do? - Introduced the TotalValueLocked storage for nomination-pools. - introduced a slashing api in mock.rs - additional test for tracking a slashing event towards a pool without sub-pools - migration for the nomination-pools (V6 to V7) with `VersionedMigration` Why are these changes needed? this is the continuation of the work by @kianenigma in this [PR](paritytech/substrate#13319) How were these changes implemented and what do they affect? - It's an extra StorageValue that's modified whenever funds flow in or out of staking for any of the `bonded_account` of `BondedPools` - The `PoolSlashed`event is now emitted even when no `SubPools` are found Closes paritytech#155 KSM: HHEEgVzcqL3kCXgsxSfJMbsTy8dxoTctuXtpY94n4s8F4pS --------- Co-authored-by: Liam Aharon <[email protected]> Co-authored-by: Kian Paimani <[email protected]> Co-authored-by: Ankan <[email protected]> Co-authored-by: Ankan <[email protected]> Co-authored-by: command-bot <>
serban300
pushed a commit
to serban300/polkadot-sdk
that referenced
this issue
Apr 8, 2024
* sign PoA transactions from wasm env * cargo fmt --all
serban300
pushed a commit
to serban300/polkadot-sdk
that referenced
this issue
Apr 8, 2024
* sign PoA transactions from wasm env * cargo fmt --all
serban300
pushed a commit
to serban300/polkadot-sdk
that referenced
this issue
Apr 9, 2024
* sign PoA transactions from wasm env * cargo fmt --all
serban300
pushed a commit
to serban300/polkadot-sdk
that referenced
this issue
Apr 9, 2024
* sign PoA transactions from wasm env * cargo fmt --all
serban300
pushed a commit
to serban300/polkadot-sdk
that referenced
this issue
Apr 9, 2024
* sign PoA transactions from wasm env * cargo fmt --all
serban300
pushed a commit
to serban300/polkadot-sdk
that referenced
this issue
Apr 9, 2024
* sign PoA transactions from wasm env * cargo fmt --all
serban300
pushed a commit
to serban300/polkadot-sdk
that referenced
this issue
Apr 9, 2024
* sign PoA transactions from wasm env * cargo fmt --all
serban300
pushed a commit
to serban300/polkadot-sdk
that referenced
this issue
Apr 9, 2024
* sign PoA transactions from wasm env * cargo fmt --all
serban300
pushed a commit
to serban300/polkadot-sdk
that referenced
this issue
Apr 10, 2024
* sign PoA transactions from wasm env * cargo fmt --all
serban300
pushed a commit
to serban300/polkadot-sdk
that referenced
this issue
Apr 10, 2024
* sign PoA transactions from wasm env * cargo fmt --all
jonathanudd
pushed a commit
to jonathanudd/polkadot-sdk
that referenced
this issue
Apr 10, 2024
* sign PoA transactions from wasm env * cargo fmt --all
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
C1-mentor
A task where a mentor is available. Please indicate in the issue who the mentor could be.
I5-enhancement
An additional feature request.
T1-FRAME
This PR/Issue is related to core FRAME, the framework.
Tracking issue for finishing off paritytech/substrate#13319
I'm planning to work on this next month when I get spare time, but it could also make a good mentor issue if someone wanted to pick it up before then (hello pba? ;)).
The text was updated successfully, but these errors were encountered: