* to v2 macro
* line width
* fix mock
* actually compile moxk
* compile tests
* add hooks
* origin back in mocks
* assimilate_storage
* add generic
* maybe mock compiles now
* origin between parachain and system causing problem
* change origin
* type alias as origin
* keep origin
* add aliases to tests
* remove unnecessary imports
* Parachain -> Paras
* paras test
* nvm
* use genesis build in mock
* Update impl-codec to use new upstream MaxEncodedLen trait
* Adapt crates to use the updated codec crate for `MaxEncodedLen`
* Remove max-encoded-len crate altogether
* Fix test compilation in `pallet-proxy`
* reorganize import (#9186)
* Fix remaining `MaxEncodedLen` imports
* Fix remaining old usages of max-encoded-len crate
* Fix UI test
* Manually depend on new impl-codec to fix Polkadot companion build
* Use newly released primitive-types v0.9.1 that has new codec impls
* Make sure codec deps are up-to-date in crates that use them
Co-authored-by: Guillaume Thiolliere <gui.thiolliere@gmail.com>
* bump a bunch of deps in parity-common
* primitive-types 0.10.0
* update Cargo.lock
* downgrade a few more
* this is unlikely to help
* try something
* Checkmate, Atheists!
* always implement storage info on Pallet
* fix UI test
* Fold span computation into trait and method computation
Co-authored-by: Keith Yeung <kungfukeith11@gmail.com>
* Add `Chilled` event to staking chill extrinsics
* Update do_remove_{nom, val} doc comments
* Not working: trying to match on event
* Account for chilled event in offences benchmarking
* trigger ci
* correct
A prometheus "server" typically refers to the prometheus process running
on a central server which connects to various prometheus "exporters" and
collects metrics. What is implemented here in substrate is a prometheus
exporter.
This patch fixes the associated log message to avoid confusion for new
users.
* Propose bumping StringLimit to 64 bytes
The StringLimit of 50 bytes is too short for useful hashes of different protocols:
- When using IPFS, the hash is 46 bytes. With a protocol prefix and type prefix (IPFS vs IPNS) it becomes: `ipfs://ipfs/QmPK1s3pNYLi9ERiq3BDxKa4XosgWwFRQUydHUtz4YgpqB` or 59 bytes.
- On arweave, the hash is 43 bytes. Prefixed with just `arweave://` bumps it up to 53: `arweave://BNttzDav3jHVnNiV7nYbQv-GY0HQ-4XXsdkE5K9ylHQ`.
- On Sia, with 46 char hashes, adding `sia://` as the protocol to use will bump it past 50: `sia://GACjmEWXmYF1N3Rc-PyjN304-8M0zOXHYzAXY9222xkGhA` (52)
As such, we feel that 64 bytes is a reasonable minimum for the `StringLimit`.
* Update lib.rs
* Add different const for `UniquesStringLimit`
Co-authored-by: Shawn Tabrizi <shawntabrizi@gmail.com>
* implement InspectEnumerable in pallet_uniques
* use `iter_keys` and `iter_key_prefix`
* return an iterator instead of constructing a vec
* update comments
* additional warning about storage reads
Co-authored-by: Shawn Tabrizi <shawntabrizi@gmail.com>
* Implement `iter_keys` function for all types of storage maps
* Remove draining iterator API
* Rename associated key iterator types
* Simplify iteration code
* add test for `iter_keys().drain()`
Co-authored-by: Shawn Tabrizi <shawntabrizi@gmail.com>
* Do not call `initialize_block` before any runtime api
Before this change we always called `initialize_block` before calling
into the runtime. There was already support with `skip_initialize` to skip
the initialization. Almost no runtime_api requires that
`initialize_block` is called before. Actually this only leads to higher
execution times most of the time, because all runtime modules are
initialized and this is especially expensive when the block contained a
runtime upgrade.
TLDR: Do not call `initialize_block` before calling a runtime api.
* Change `validate_transaction` interface
* Fix rpc test
* Fixes and comments
* Some docs
* Move alloc primitive (not used in /pallets)
* Move to alternative location as not shared
* moved crates to different dir
* ren sp_chain_spec to sc_chain_spec_primatives
* merged sc-chain-spec and moved allocation up one.
* no no_std
* nudge
* Bump CI
* only allow `chill_other` near threshold.
* improve test
* skip limit check for existing validators / nominators
* add `ChillThreshold`
* rename to `set` for consistent api
* more tests
* fix some line width
* Companion for Decouple Staking and Election - Part 3: Signed Phase
https://github.com/paritytech/substrate/pull/7910
* remove some config types
* allow up to 5 signed submissions on polkadot and kusama
* signed phase is equal induration to unsigned phase
* use chain defaults for base and per-byte deposits; >= 16 SignedMaxSubmissions
* use a small but non-trivial solution reward
* reduce signed deposit per byte fee
* reduce signed reward, adjust polkadot expected soln size
* copy submit benchmark from substrate
* demo calculating an appropriate fee for the signed reward
Unfortunately, this doesn't work: it needs to be a constant function,
and AFAIK there's no way to make a trait method constant.
* SignedRewardBase is 1.5x the fee to submit a signed solution
* all chains use deposit byte of base per 50k
* update Substrate
* cargo update -p pallet-election-provider-multi-phase
Co-authored-by: parity-processbot <>
chore: refactor for consistant naming of the crates and paths of the runtimes
* tests: ignore folder created by the tests
* chore: refactoring
* Update polkadot-parachains/Cargo.toml
Co-authored-by: Bastian Köcher <bkchr@users.noreply.github.com>
* Only send one collation per relay parent at a time to validators
This changes the way we are sending collations to validators. Before we
answered every collation request immediatley. Now we only answer one
pov request at a time per relay parent. This should bring down the
bandwidth requirements and should help parachains to include bigger
blocks more easily.
* Guide updates
* Review feedback.
ferrell-code