Skip to content
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

Update polkadot 1.15.0 #161

Closed
wants to merge 7 commits into from
Closed

Update polkadot 1.15.0 #161

wants to merge 7 commits into from

Conversation

rdoria1
Copy link
Contributor

@rdoria1 rdoria1 commented Oct 24, 2024

Pallet treasury
remove ApproveOrigin -> Found this comment on this type before it was effectively removed https://github.com/paritytech/polkadot-sdk/pull/4831/files
// The creation of proposals via the treasury pallet is deprecated and should not be utilized.
// Instead, public or fellowship referenda should be used to propose and command the treasury
// spend or spend_local dispatchables. The parameters below have been configured accordingly to
// discourage its use.
Remove OnSlash-> This was added to the bounty pallets instead (PR comment in paritytech/polkadot-sdk#4831)
Remove ProposalBond ProposalBondMinimum and ProposalBondMaximum -> paritytech/polkadot-sdk@3d26a92 I feel this is because they all related to proposal and based on the first point. proposals are not done via the treasury pallet anymore which is why these types are useless now

Pallet bounties
Added OnSlash as specified before, coming from treasury

Pallet staking
Replace OffendingValidatorsThreshold with DisablingStrategy paritytech/polkadot-sdk#2226

node
remove deprecated RuntimeGenesisConfig : paritytech/polkadot-sdk#4410

TODO Re run benchmark for pallet_balances

@rdoria1 rdoria1 marked this pull request as ready for review October 24, 2024 23:56
sc_consensus_grandpa::grandpa_peers_set_config(grandpa_protocol_name.clone());
sc_consensus_grandpa::grandpa_peers_set_config::<_, Network>(
grandpa_protocol_name.clone(),
NotificationMetrics::new(None),
Copy link
Collaborator

Choose a reason for hiding this comment

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

Shouldn't we attach our Prometheus metrics here ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Didn't know we had Prometheus metrics, in that case yes, I think they should go here. I'll dig a bit more.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Copy link
Contributor

Choose a reason for hiding this comment

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

Sorry I just noticed this; indeed, we should attach prometheus metrics here. I can change this in #168.

@@ -152,7 +153,7 @@ pub fn development_config() -> Result<ChainSpec, String> {
pub fn local_config() -> Result<ChainSpec, String> {
Ok(ChainSpec::builder(
WASM_BINARY.ok_or_else(|| "Development wasm not available".to_string())?,
None,
Default::default(),
Copy link
Collaborator

Choose a reason for hiding this comment

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

What's the default here ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

my bad, this was something I forgot to undo due to some change that was not needed in the end.
Bottom line: No need to do this, I'll undo it.

@DanieleDiBenedetto
Copy link
Collaborator

Closing in favor of #168

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants