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
Initial PoC PR to play around with Dynamic Allocation Proposal here: https://hackmd.io/a0KSL4XHQ1WvcGZlKykGzg
6
6
7
-
So far, I am just currently removing treasury burn and staking slashing, redirecting them to the DAP / issuance buffer.
7
+
Initial version supports the following:
8
+
- Introduced FundingSink and FundingSource traits in frame-support
9
+
- Introduced pallet-dap with minimal implementation of FundingSink trait only. This pallet is meant to be
10
+
deployed on AssetHub as the central DAP pallet.
11
+
- Redirected treasury unspent to pallet-dap instead of burning
12
+
- Redirected staking slashes to pallet-dap instead of burning
13
+
- Introduced pallet-dap-satellite, to collect funds that otherwise would be burned (e.g. tx fees,
14
+
coretime revenues, ...) into a local satellite account. These funds are accumulated locally and
15
+
will be sent to pallet-dap periodically in future iterations. This pallet is meant to be deployed
16
+
on system chains like Coretime, People and BridheHub and on the RelayChain. It should not be deployed
17
+
on AssetHub, which hosts the central DAP pallet.
18
+
19
+
asset-hub-westend-runtime and staking-async test runtime have been modified to include pallet-dap and to send part of slashing and treasury's unspent funds to pallet-dap.
20
+
coretime-westend-runtime has been updated to include pallet-dap-satellite. Coretime revenues are now accumulated in the pallet-dap-satellite account instead of being burned.
0 commit comments