-
Notifications
You must be signed in to change notification settings - Fork 7
Conversation
Any plan to make this into Substrate / Cumulus so each parachain team don't need to create their own copy of something similar? |
pub mod pallet { | ||
use frame_support::{dispatch::DispatchResultWithPostInfo, pallet_prelude::*, inherent::Vec, traits::{Currency, ReservableCurrency}}; | ||
use frame_system::{pallet_prelude::*, ensure_root}; | ||
use frame_system::Config as SystemConfig; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not substrate-idomatic IMO, but not a big deal.
Co-authored-by: Kian Paimani <5588131+kianenigma@users.noreply.github.com>
Co-authored-by: Kian Paimani <5588131+kianenigma@users.noreply.github.com>
Co-authored-by: Kian Paimani <5588131+kianenigma@users.noreply.github.com>
Co-authored-by: Kian Paimani <5588131+kianenigma@users.noreply.github.com>
Co-authored-by: Kian Paimani <5588131+kianenigma@users.noreply.github.com>
Co-authored-by: Kian Paimani <5588131+kianenigma@users.noreply.github.com>
@@ -793,8 +819,14 @@ impl_runtime_apis! { | |||
let params = (&config, &whitelist); | |||
|
|||
add_benchmark!(params, batches, frame_system, SystemBench::<Runtime>); | |||
add_benchmark!(params, batches, pallet_balances, Balances); | |||
add_benchmark!(params, batches, pallet_timestamp, Timestamp); | |||
//TODO we should re run all benchmarks for used pallets together |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should be fixed IMO
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ya, but I was thinking it falls out of scope of this PR and to make an issue and do it after this is merged
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
created issue #37
Co-authored-by: Kian Paimani <5588131+kianenigma@users.noreply.github.com>
Co-authored-by: Kian Paimani <5588131+kianenigma@users.noreply.github.com>
Co-authored-by: Kian Paimani <5588131+kianenigma@users.noreply.github.com>
Co-authored-by: Kian Paimani <5588131+kianenigma@users.noreply.github.com>
Co-authored-by: Kian Paimani <5588131+kianenigma@users.noreply.github.com>
Co-authored-by: Kian Paimani <5588131+kianenigma@users.noreply.github.com>
Co-authored-by: Kian Paimani <5588131+kianenigma@users.noreply.github.com>
Co-authored-by: Kian Paimani <5588131+kianenigma@users.noreply.github.com>
Co-authored-by: Kian Paimani <5588131+kianenigma@users.noreply.github.com>
Co-authored-by: Kian Paimani <5588131+kianenigma@users.noreply.github.com>
Co-authored-by: Kian Paimani <5588131+kianenigma@users.noreply.github.com>
Co-authored-by: Kian Paimani <5588131+kianenigma@users.noreply.github.com>
Even simpler than that, we will just make a
It will eventually kick collators who don't produce a block for some time, but no slashing.
Correct, short term, governance will either increase the number of slots or increase the bond requirement. Medium term, we will just rotate through candidates so that they will all get a chance in the set.
It's meant to function for collator selection for a common good chain. Collation is not a secure operation, so it doesn't require that many features. It's called "simple staking" for a reason; there aren't many features. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need followups, but okay for now.
yup using #9 to track, will add you to it |
TODO