Commits on Source (32)
-
clangenb authored
Closes #7845 --------- Co-authored-by:
cmd[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by:
Guillaume Thiolliere <guillaume.thiolliere@parity.io>
Unverified007565a7 -
Bastian Köcher authored
Close: https://github.com/paritytech/polkadot-sdk/issues/7816 --------- Co-authored-by:Unverified4ada34bd -
jpserrat authored
Closes #6851 This PR adds an `EventEmitter` trait to the XCM Executor configuration, enabling event emission for XCM handling. The implementation introduces three dedicated functions to emit relevant events: - `emit_sent_event`: Emits a `Sent` event when an XCM is successfully sent. - `emit_send_failure_event`: Emits a `SendFailed` event when an XCM fails to send. - `emit_process_failure_event`: Emits a `ProcessXcmError` event when an XCM fails during processing. Kusama address: FkB6QEo8VnV3oifugNj5NeVG3Mvq1zFbrUu4P5YwRoe5mQN --------- Co-authored-by:
Raymond Cheung <178801527+raymondkfcheung@users.noreply.github.com> Co-authored-by:
Adrian Catangiu <adrian@parity.io> Co-authored-by:
Unverifiedea8783b1 -
Bastian Köcher authored
As proposed by Gui :)
Unverified0bea374d -
Sebastian Kunert authored
Follow up of : #7217, #7529 When the zombienet tests were integrated into github, it seems like the gitlab ones remained active. But they look a lot more unstable. This causes confusion when the same tests fail and pass at the same time (aside from extra costs). This PR attempts to get rid of the gitlab ones.
Unverifiedfb19de2b -
Sebastian Kunert authored
**Summary:** This PR enables authoring of multiple blocks in one AURA slot in the slot-based collator and stabilizes the slot-based collator. ## CLI Changes The flag `--experimental-use-slot-based` is now marked as deprecated. I opted to introduce `--authoring slot-based` instead of just removing the `experimental` prefix. By introducing the `authoring` variant, we get some future-proofing in case we want to introduce further options. ## Change Description With elastic-scaling, we are able to author multiple blocks with a single relay-chain parent. In the initial iteration, the interval between two blocks was determined by the `slot_duration` of the parachain. This PR introduces a more flexible model, where we try to author multiple blocks in a single slot if the runtime allows it. The block authoring loop is largely the same. The [`SlotTimer`](https://github.com/paritytech/polkadot-sdk/blob/f1935bd9/cumulus/client/consensus/aura/src/collators/slot_based/slot_timer.rs#L48-L48) now lives in a separate module and is updated with the last seen [core count](https://github.com/paritytech/polkadot-sdk/blob/f1935bd9 /cumulus/client/consensus/aura/src/collators/slot_based/block_builder_task.rs#L231-L231). It will then trigger rounds in the block-building loop based on the core count. This allows some flexibility where elastic-scaling chains can run on a single core in quiet times. Previously, running on 1 core with a 3-core elastic-scaling chain would result in authors getting skipped because the `slot_duration` was too low. ## Parameter Considerations The core logic does not change, so there are a few things to consider: - The `ConsensusHook` implementation still determines how many blocks are allowed per relay-chain block. So if you add arbitrary cores to an async-backing, 6-second parachain, `can_build_upon` in the runtime will deny block-building of additional blocks. - The `MINIMUM_PERIOD` in the runtime needs to be configured to allow enough blocks in the slot. A "classic" configuration of `SLOT_DURATION/2` will lead to slot mismatches when running with 3 cores. - We fetch available cores at least once every relay chain block. So if a parachain runs with a 12-second slot duration and 1 fixed core, we would still author 2 blocks if the parachain runtime allows it. --------- Co-authored-by:
Michal Kucharczyk <1728078+michalkucharczyk@users.noreply.github.com> Co-authored-by:
Javier Viola <javier@parity.io> Co-authored-by:
Bastian Köcher <git@kchr.de>
Unverified8ddb0714 -
Serban Iorga authored
This PR includes: - deduplicating some XCM decoding logic - making use of `decode_with_depth_limit` consistently for `VersionedXcm` - some cleanup
Unverified2a239206 -
PG Herveou authored
[pallet-revive] Add support for eip1898 block notation https://eips.ethereum.org/EIPS/eip-1898 --------- Co-authored-by:Unverifiedfb98291e -
Egor_P authoredUnverifiede9a15dce
-
Egor_P authored
This PR contains few fixes for the Promote RC to final flow: - Now the `polkadot-preapre-worker` and `polkadot-execute-worker` artefacts will be uploaded alongside with the `polakdot` artefact (it was missing before) - Added missing upload of the deb package - Few typos fixed Closes: https://github.com/paritytech/release-engineering/issues/241
Unverified544fefac -
Alexandru Vasile authored
This PR makes the litep2p backend the default network backend in Kusama. We performed a gradual rollout in Kusama by asking validators to manually switch to litep2p. The rollout went smoothly, with 250 validators running litep2p without issues. This PR represents the next step in testing the backend at scale. Thanks to everyone who contributed to making this happen! A special shoutout to the validators for their prompt support and cooperation
🙏 While at it, the litep2p release is bumped to the latest 0.9.2, which downgrades a spamming log to debug. ### CLI Testing Done ``` ### Kusama without network backend specified RUST_LOG=info ./target/release/polkadot --chain kusama --pruning=1000 --in-peers 50 --out-peers 50 --sync=warp --detailed-log-output 2025-03-10 14:24:18.503 INFO main sub-libp2p: Running litep2p network backend ### Kusama with libp2p RUST_LOG=info ./target/release/polkadot --chain kusama --pruning=1000 --in-peers 50 --out-peers 50 --sync=warp --detailed-log-output --network-backend libp2p INFO main sub-libp2p: Running libp2p network backend ### Kusama with litep2p RUST_LOG=info ./target/release/polkadot --chain kusama --pruning=1000 --in-peers 50 --out-peers 50 --sync=warp --detailed-log-output --network-backend litep2p INFO main sub-libp2p: Running litep2p network backend ### Polkadot without network backend specified RUST_LOG=info ./target/release/polkadot --chain polkadot --pruning=1000 --in-peers 50 --out-peers 50 --sync=warp --detailed-log-output 2025-03-10 14:27:03.762 INFO main sub-libp2p: Running libp2p network backend ``` cc @paritytech/networking --------- Signed-off-by:Alexandru Vasile <alexandru.vasile@parity.io> Co-authored-by:
Unverifiedbcc272a1 -
Kian Paimani authored
Co-authored-by:Ankan <ankan.anurag@gmail.com>
Unverified57f72199 -
Ankan authored
## Summary The existing fungible migration code has an issue when handling partially unbonding accounts, leaving them in an inconsistent state. These changes fix it by properly withdrawing overstake from unlock chunks. This PR also removes the `withdraw_overstake` extrinsic from pallet-staking, as this scenario could only occur before the fungible migration. With fungibles, over-staking is no longer possible. ## TODO - [ ] Backport to stable2503. --------- Co-authored-by:Unverifiedf540d2b3 -
Francisco Aguirre authored
The xcm-executor will not support `ExecuteWithOrigin` from the start. It might be implemented again in the future when more time can be spent on it. --------- Co-authored-by:Unverifiedf323814d -
ordian authored
This PR adds a convenience extrinsic `manual_slash` for the governance to slash a validator manually. ## Changes * The `on_offence` implementation for the Staking pallet accepts a slice of `OffenceDetails` including the full validator exposure, however, it simply [ignores](https://github.com/paritytech/polkadot-sdk/blob/c8d33396 /substrate/frame/staking/src/pallet/impls.rs#L1864) that part. I've extracted the functionality into an inherent `on_offence` method that takes `OffenceDetails` without the full exposure and this is called directly in `manual_slash` * `manual_slash` creates an offence for a validator with a given slash percentange ## Questions - [x] should `manual_slash` accept session instead of an era when the validator was in the active set? staking thinks in terms of eras and we can check out of bounds this way, which is why it was chosen for this implementation, but if there are arguments against, happy to change to session index - [X] should the accepted origin be something more than just root? Changed to `T::AdminOrigin` to align with `cancel_deferred_slash` - [X] should I adapt this PR also against https://github.com/paritytech/polkadot-sdk/pull/6996? looking at the changes, it should apply mostly without conflicts --------- Co-authored-by:
Tsvetomir Dimitrov <tsvetomir@parity.io> Co-authored-by:
Ankan <10196091+Ank4n@users.noreply.github.com>
Unverifiedf8c90b2a -
thiolliere authored
giving the wrong origin in `extrinsic_call` would result in: ``` | 43 | #[benchmarks] | ^^^^^^^^^^^^^ | | | expected associated type, found `Result<RawOrigin<...>, ...>` | arguments to this function are incorrect | = note: expected associated type `<T as frame_system::Config>::RuntimeOrigin` found enum `Result<RawOrigin<<T as frame_system::Config>::AccountId>, <T as frame_system::Config>::RuntimeOrigin>` note: method defined here --> $WORKSPACE/substrate/frame/support/src/traits/dispatch.rs | | fn dispatch_bypass_filter(self, origin: Self::RuntimeOrigin) -> DispatchResultWithPostInfo; | ^^^^^^^^^^^^^^^^^^^^^^ = note: this error originates in the attribute macro `benchmarks` (in Nightly builds, run with -Z macro-backtrace for more info) ``` Now it results in an error message with good span. --------- Co-authored-by:Unverifieda71a701c -
PG Herveou authored
Support "latest" blocktag in ethGetLogs from_block and to_block parameters This is not in specs (https://github.com/ethereum/execution-apis/blob/main/src/schemas/filter.yaml#L17) but defined and used by 3rd parties and in some other reference docs See https://docs.metamask.io/services/reference/ethereum/json-rpc-methods/eth_getlogs/ --------- Co-authored-by:Unverifiedab7c6080 -
Matteo Muraca authored
# Description Part of #3326 As per title, the `pallet:getter` usage has been removed from: - `pallet-bridge-beefy` - `pallet-bridge-grandpa` - `pallet-bridge-messages` - `pallet-bridge-relayers` - `pallet-xcm-bridge-hub-router` polkadot address: 12poSUQPtcF1HUPQGY3zZu2P8emuW9YnsPduA4XG3oCEfJVp --------- Co-authored-by:
Branislav Kontur <bkontur@gmail.com> Co-authored-by:
Unverified66e3196a -
Egor_P authoredUnverified64dc0eff
-
Alexandru Vasile authored
This PR punishes behaviors that deviate from the notification spec. When a peer misbehaves by writing data on an unidirectional read stream, the peer is banned and disconnected immediately. In this PR: - The `NotificationOutError` is enriched with termination reason and made publically available for higher levels - The protocol misbehavior is propagated through the `CloseDesired` events - The network behavior of the protocol is responsible for banning the peer. - The peer is banned immediately and, as a result, the reputation system disconnects the malicious / misbehaving peer - Logs are enriched with protocol names Closes: https://github.com/paritytech/polkadot-sdk/issues/7722 cc @paritytech/networking --------- Signed-off-by:
Unverifiedaa67d2ae -
PG Herveou authored
Update pallet-revive-fixtures so that it can build without looking up dependencies from the workspace --------- Co-authored-by:Unverified8265c65f -
Iulian Barbu authored
# Description It is difficult to spot changes to umbrella features when reviewing, when defined on a long line, so made sure tomls formatting will be applied to long array lines by splitting them on multiple lines. This will be applied to any tomls in the monorepo that is not excluded from taplo. ## Integration N/A ## Review Notes Set global taplo config `array_auto_expand` to true. --------- Signed-off-by:Iulian Barbu <iulian.barbu@parity.io>
Unverifiedd4155b6c -
Javier Viola authored
Set timeout to 60mins. Prevent failures like this one https://github.com/paritytech/polkadot-sdk/actions/runs/13651327605/job/38160444244?pr=7790 Thanks! --------- Co-authored-by:Unverified425d6188 -
Francisco Aguirre authored
Asset Hub was using the native token for benchmarking xcm instructions. This is not the best since it's cheaper than using something in `pallet-assets` for example. Had to remove some restrictive checks from `pallet-xcm-benchmarks`. I'll bring back the checks with a better framework in the future that allows for handling multiple assets (`fungibles::*` traits). --------- Co-authored-by:Unverifiedc4b8ec12 -
PG Herveou authored
Add missing pre-compiles 02 -> 09 [weights changes](https://weights.tasty.limo/compare?repo=polkadot-sdk&threshold=10&path_pattern=substrate%2Fframe%2F**%2Fsrc%2Fweights.rs%2Cpolkadot%2Fruntime%2F*%2Fsrc%2Fweights%2F**%2F*.rs%2Cpolkadot%2Fbridges%2Fmodules%2F*%2Fsrc%2Fweights.rs%2Ccumulus%2F**%2Fweights%2F*.rs%2Ccumulus%2F**%2Fweights%2Fxcm%2F*.rs%2Ccumulus%2F**%2Fsrc%2Fweights.rs&method=asymptotic&ignore_errors=true&unit=time&old=master&new=pg%2Fprecompiles02_09&pallet=revive) --------- Co-authored-by:Unverified4c74a109 -
tmpolaczyk authored
Shouldn't matter much, but this is run on every produced block so free performance
Unverified363bd6bd -
Bastian Köcher authored
This brings support for declaring variables in parameters as `mut` inside of `impl_runtime_apis!`. --------- Co-authored-by:Unverifiedd5327157 -
Andrei Sandu authored
Changes the POV format used by pov exporter and validator. The `pov-validator` will now work with PoVs recovered from relay chain DA and created by the collator pov exporter. --------- Signed-off-by:
Andrei Sandu <andrei-mihail@parity.io> Co-authored-by:
ordian <write@reusable.software>
Unverifiedc7d7a3ef -
PG Herveou authored
Fix pallet-revive-uapi resolution when building pallet-revive-fixtures contracts follow up from https://github.com/paritytech/polkadot-sdk/pull/7844 --------- Co-authored-by:
xermicus <cyrill@parity.io>
Unverified3a6c4894 -
kvalerio authored
The page [2-token-economics](https://research.web3.foundation/en/latest/polkadot/overview/2-token-economics.html) is a dead link, replacing it with [token-economics](https://research.web3.foundation/Polkadot/overview/token-economics). Co-authored-by:Unverified762f9023 -
Eugen Snitko authoredremove compromised tj-actions/changed-files set all related vars to 'true' for now https://news.ycombinator.com/item?id=43368870
Unverifiedd3f68513 -
seemantaggarwal authoredUnverified98a0fb26
Showing
- .config/taplo.toml 1 addition, 1 deletion.config/taplo.toml
- .github/scripts/common/lib.sh 3 additions, 3 deletions.github/scripts/common/lib.sh
- .github/scripts/release/release_lib.sh 1 addition, 1 deletion.github/scripts/release/release_lib.sh
- .github/workflows/build-publish-images.yml 63 additions, 0 deletions.github/workflows/build-publish-images.yml
- .github/workflows/checks-quick.yml 0 additions, 1 deletion.github/workflows/checks-quick.yml
- .github/workflows/release-11_rc-automation.yml 1 addition, 1 deletion.github/workflows/release-11_rc-automation.yml
- .github/workflows/release-30_publish_release_draft.yml 3 additions, 13 deletions.github/workflows/release-30_publish_release_draft.yml
- .github/workflows/release-40_publish-deb-package.yml 8 additions, 8 deletions.github/workflows/release-40_publish-deb-package.yml
- .github/workflows/release-50_publish-docker.yml 1 addition, 1 deletion.github/workflows/release-50_publish-docker.yml
- .github/workflows/release-reusable-promote-to-final.yml 13 additions, 7 deletions.github/workflows/release-reusable-promote-to-final.yml
- .github/workflows/release-reusable-rc-buid.yml 1 addition, 1 deletion.github/workflows/release-reusable-rc-buid.yml
- .github/workflows/reusable-preflight.yml 16 additions, 16 deletions.github/workflows/reusable-preflight.yml
- .github/workflows/zombienet-reusable-preflight.yml 26 additions, 26 deletions.github/workflows/zombienet-reusable-preflight.yml
- .github/workflows/zombienet_cumulus.yml 54 additions, 0 deletions.github/workflows/zombienet_cumulus.yml
- .github/zombienet-env 1 addition, 1 deletion.github/zombienet-env
- .gitlab/pipeline/zombienet.yml 0 additions, 4 deletions.gitlab/pipeline/zombienet.yml
- .gitlab/pipeline/zombienet/cumulus.yml 0 additions, 177 deletions.gitlab/pipeline/zombienet/cumulus.yml
- .gitlab/pipeline/zombienet/substrate.yml 0 additions, 93 deletions.gitlab/pipeline/zombienet/substrate.yml
- Cargo.lock 61 additions, 5 deletionsCargo.lock
- Cargo.toml 8 additions, 2 deletionsCargo.toml