8000 Update fees splits, 50% burned, 50% to treasury by ghzlatarev · Pull Request #770 · Manta-Network/Manta · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Update fees splits, 50% burned, 50% to treasury #770

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

Merged
merged 3 commits into from
Aug 24, 2022

Conversation

ghzlatarev
Copy link
Contributor
@ghzlatarev ghzlatarev commented Aug 23, 2022

Signed-off-by: Georgi Zlatarev georgi.zlatarev@manta.network

Description

relates to: #691

  • Update transaction fees split - 50% burned, 50% to treasury, because of the switch to proof of stake.
  • Update related integration tests

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

  • Linked to Github issue with discussion and accepted design OR have an explanation in the PR that describes this work.
  • Added one label out of the L- group to this PR
  • Added one or more labels out of A- and C- groups to this PR
  • Re-reviewed Files changed in the Github PR explorer.

Situational Notes:

  • If adding functionality, write unit tests!
  • If importing a new pallet, choose a proper module index for it, and allow it in BaseFilter. Ensure every extrinsic works from front-end. If there's corresponding tool, ensure both work for each other.
  • If needed, update our Javascript/Typescript APIs. These APIs are officially used by exchanges or community developers.
  • If modifying existing runtime storage items, make sure to implement storage migrations for the runtime and test them with try-runtime. This includes migrations inherited from upstream changes, and you can search the diffs for modifications of #[pallet::storage] items to check for any.
  • If runtime changes, need to update the version numbers properly:
    • authoring_version: The version of the authorship interface. An authoring node will not attempt to author blocks unless this is equal to its native runtime.
    • spec_version: The version of the runtime specification. A full node will not attempt to use its native runtime in substitute for the on-chain Wasm runtime unless all of spec_name, spec_version, and authoring_version are the same between Wasm and native.
    • impl_version: The version of the implementation of the specification. Nodes are free to ignore this; it serves only as an indication that the code is different; as long as the other two versions are the same then while the actual code may be different, it is nonetheless required to do the same thing. Non-consensus-breaking optimizations are about the only changes that could be made which would result in only the impl_version changing.
    • transaction_version: The version of the extrinsics interface. This number must be updated in the following circumstances: extrinsic parameters (number, order, or types) have been changed; extrinsics or pallets have been removed; or the pallet order in the construct_runtime! macro or extrinsic order in a pallet has been changed. You can run the metadata_diff.yml workflow for help. If this number is updated, then the spec_version must also be updated
  • Verify benchmarks & weights have been updated for any modified runtime logics

Signed-off-by: Georgi Zlatarev <georgi.zlatarev@manta.network>
@ghzlatarev ghzlatarev self-assigned this Aug 23, 2022
Signed-off-by: Georgi Zlatarev <georgi.zlatarev@manta.network>
@ghzlatarev ghzlatarev added L-changed Log: Issues and PRs related to changes A-collator-program Area: Issues and PRs related to the Collator Program A-consensus Area: Issues and PRs related to Consensus and removed A-collator-program Area: Issues and PRs related to the Collator Program A-consensus Area: Issues and PRs related to Consensus labels Aug 23, 2022
Signed-off-by: Georgi Zlatarev <georgi.zlatarev@manta.network>
@ghzlatarev ghzlatarev added A-collator-program Area: Issues and PRs related to the Collator Program A-consensus Area: Issues and PRs related to Consensus labels Aug 23, 2022
Copy link
Contributor
@Garandor Garandor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ghzlatarev could you pls link the code section where fees are actually being collected from the TX author?

@ghzlatarev
Copy link
Contributor Author

LGTM

@ghzlatarev could you pls link the code section where fees are actually being collected from the TX author?

https://github.com/paritytech/substrate/blob/master/frame/transaction-payment/src/lib.rs#L758

Copy link
Contributor
@Dengjianping Dengjianping left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm!

@ghzlatarev ghzlatarev merged commit e2e66f8 into manta Aug 24, 2022
@ghzlatarev ghzlatarev deleted the ghzlatarev/fee-change branch August 24, 2022 14:40
@ghzlatarev ghzlatarev linked an issue Aug 24, 2022 that may be closed by this pull request
@Garandor Garandor added A-calamari Area: Issues and PRs related to the Calamari Runtime A-dolphin Area: Issues and PRs related to the Dolphin Runtime labels Sep 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-calamari Area: Issues and PRs related to the Calamari Runtime A-collator-program Area: Issues and PRs related to the Collator Program A-consensus Area: Issues and PRs related to Consensus A-dolphin Area: Issues and PRs related to the Dolphin Runtime L-changed Log: Issues and PRs related to changes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Nimbus Consensus Migration Stage 2
4 participants
0