This is basically a hack that prevents the inclusion of `:code` in the
storage proof. A proper fix requires some changes to the trie crate to
not include nodes that aren't read.
* add raw chainspecs
* rename chain specs
* add statemine to accepted --chain values
* fix up westmint chainspec
* fix up westmint chainspec
* add token symbol and decimals to statemine chain spec
Co-authored-by: Alexander Popiak <alexander.popiak@parity.io>
* set default para id to 1000
* add genesis value generation script
* add statemine chain spec and genesis values
* add westmint chain spec and genesis values
* rename chain specs to _genesis to indicate that they are not usable for syncing the chain
* adjust chain names to reduce confusion
* add westmint chain spec
* set chain id to shell
* comment out statemine chain spec
* fix build
Co-authored-by: joepetrowski <joe@parity.io>
* Start with a failing integration test & some refactorings
* More work
* Make it "work"
* Add `NullConsensus` for the test
* More refactorings
* Move stuff over to its own crate
* Refactorings
* Integrate it into `service` and make the test working
* Docs and some exit condition
* Use the real import queue
* Fix tests
* Update client/pov-recovery/src/active_candidate_recovery.rs
Co-authored-by: Bernhard Schuster <bernhard@ahoi.io>
* Fetch slot duration from the relay chain
* Docs
* Fixes
Co-authored-by: Bernhard Schuster <bernhard@ahoi.io>
* Introduce `CollectCollationInfo` runtime api
Instead of using well known keys to communicate information about a
collation between the runtime and the collator, we now use a runtime api
for this.
* Fixes bug
* Apply suggestions from code review
Co-authored-by: Sergei Shulepov <sergei@parity.io>
* Doc update
Co-authored-by: Sergei Shulepov <sergei@parity.io>
Before when loading a chain spec from a file it was always using the
rococo parachains runtime genesis config. This leaded to problems when
trying to convert a shell chain spec json file to a raw chain spec.
Bastian Köcher