* Extract `NetworkKVProvider` trait in `sc-authority-discovery` and remove unnecessary dependency
* Extract `NetworkSyncForkRequest` trait in `sc-finality-grandpa`
* Relax requirements on `SyncOracle` trait, remove extra native methods from `NetworkService` that are already provided by trait impls
* Move `NetworkSigner` trait from `sc-authority-discovery` into `sc-network-common` and de-duplicate methods on `NetworkService`
* Move `NetworkKVProvider` trait from `sc-authority-discovery` into `sc-network-common` and de-duplicate methods on `NetworkService`
* Minimize `sc-authority-discovery` dependency on `sc-network`
* Move `NetworkSyncForkRequest` trait from `sc-finality-grandpa` to `sc-network-common` and de-duplicate methods in `NetworkService`
* Extract `NetworkStatusProvider` trait and de-duplicate methods on `NetworkService`
* Extract `NetworkPeers` trait and de-duplicate methods on `NetworkService`
* Extract `NetworkEventStream` trait and de-duplicate methods on `NetworkService`
* Move more methods from `NetworkService` into `NetworkPeers` trait
* Move `NetworkStateInfo` trait into `sc-network-common`
* Extract `NetworkNotification` trait and de-duplicate methods on `NetworkService`
* Extract `NetworkRequest` trait and de-duplicate methods on `NetworkService`
* Remove `NetworkService::local_peer_id()`, it is already provided by `NetworkStateInfo` impl
* Extract `NetworkTransaction` trait and de-duplicate methods on `NetworkService`
* Extract `NetworkBlock` trait and de-duplicate methods on `NetworkService`
* Remove dependencies on `NetworkService` from most of the methods of `sc-service`
* Address simple review comments
* Restore `wasmtime`'s default stack size limit to 1MB
* Add extra comments
* Enforce different maximum call depth in release mode
* Split the call depth limit in two
Before `highestBlock` was an optional that was omitted when it was `None`. We recently changed the
way the `highestBlock` is determined, this resulted in having this value in 99.99% of the time being
`None` when the node is syncing blocks at the tip. Now we always return a block for `highestBlock`.
If sync doesn't return us any best seen block, we return our own local best block as `highestBlock`.
This should mainly reflect the same behavior to before we changed the way the best seen block is determined.
* Rename transactions protocol to include genesis hash
* Add protocol name generation to sc_network::utils
* Use utils functions for transactions protocol name generation
* Extract protocol name generation into public module
* Use sc_network::protocol_name::standard_protocol_name() for BEEFY and GRANDPA
* minor: add missing newline at EOF
* Change block-announces protocol name to include genesis_hash & fork_id
* Change protocol names to include genesis hash and fork id
Protocols changed:
- sync
- state
- light
- sync/warp
* Revert "Use sc_network::protocol_name::standard_protocol_name() for BEEFY and GRANDPA"
This reverts commit cd60a95a3face397e1b67f4bc95dd0f2b581bfae.
* Get rid of `protocol_name` module
* Prevent duplicated leaves in the backend
* Comments...
* Use highest known heaf as a shortcut for not existing header detection
* Apply code review suggestion
Co-authored-by: Bastian Köcher <bkchr@users.noreply.github.com>
Co-authored-by: Bastian Köcher <bkchr@users.noreply.github.com>
* don't require default features for an API crate
Let the consumer define by overriding the features for the inner deps as needed.
Cargo feature resolution allows this.
Ref https://github.com/paritytech/polkadot/pull/5792
* Update client/relay-chain-inprocess-interface/Cargo.toml
Co-authored-by: Bastian Köcher <bkchr@users.noreply.github.com>
* Timestamp: `set_timestamp` sets `DidUpdate`
There exists the `set_timestamp` in the Timestamp pallet for setting the current timestamp. The
problem is that it doesn't set `DidUpdate`. This results in `on_finalize` panicking. There is no
real reason why the function doesn't also set `DidUpdate`.
* Update frame/timestamp/src/lib.rs
Co-authored-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io>
* Fix Babe tests
Co-authored-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io>
* beefy: use VersionedFinalityProof instead of SignedCommitment.
* Change the exposed RPC API to support versioned proofs.
Co-authored-by: Adrian Catangiu <adrian@parity.io>
The benchmarks have been run internally with at least two values
even when called with --steps=1. substrate/#11890 changed this
to explicitly require at least --steps=2.
Signed-off-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io>
* point to my branch
* girazoki-add-TakeFirstAssetTrader-to-utility
* Commit lock
* point at custom branch
* add new trader to statemine runtimes
* compiles
* Back to master
* Update last tomls
* Imports up
* remove non-needing imports
* FMT
* log messages properly
* Use TakeRevenue instead of HandleCredit
* Introduce xcm fee handler
* check total supply in tests
* FMT
* fix test
* Start decoupling balance calculation into different traits
* Make traits a bit more generic
* PR suggestions
* add import
* import well
* Place xcmfeesassethandler into parachains common
* fix tests
* config parameters
* Min amount to fee receiver
* Make minimum amount for block author to be at least the ED
* Doc in AssetFeeAsExistentialDepositMultiplier
* saturating sub
* make sure we dont enter twice
* FMT
* fmt again
* adapt tests
* Add doc and struct for weight refund
* Doc
* More doc
* PR suggestions
* store all info related to asset payment as multiasset
* return AssetNotFound instead of TooExpensive
* Use asset transactor to deposit fee
* uninstall from statemint
* R for RUntime and CON for BalanceConverter
* Rework logic to avoid unnecesary match and error
* Rework ED check, also in case of refund
* rework typo
* In case refund makes drop below ED, just refund the difference
* fix test westmint
* clone id
* move test imports to preamble
* move test imports to preamble
* test-utils with builderS
* lock file updated
* remove unused imports
Co-authored-by: Stephen Shelton <steve@brewcraft.org>
Co-authored-by: joe petrowski <25483142+joepetrowski@users.noreply.github.com>
Co-authored-by: joepetrowski <joe@parity.io>
* Revert non-best block
This makes `revert` also revert non-best blocks.
* Update client/db/src/lib.rs
* Do not count leaves against the maximum number to revert
* Add some explanation
* Fix bug
* Apply suggestions from code review
Co-authored-by: Davide Galassi <davxy@datawok.net>
Co-authored-by: Davide Galassi <davxy@datawok.net>
Nazar Mokrynskyi