* CI: build a test artifact
* CI: try building before testing
* CI: try proper bin name
* CI: preempty cache to benchmark properly
* CI: run build after test
* CI: change target source
* CI: try build before test once again
* CI: chore
* CI: prepopulate target cache
* CI: conditional build; aws sync
* CI: mock building to test publishing
* CI: lacks permissions in the other job
* CI: undebug
- add builds for "statemint", "rococo", "shell"
- switch to chevdor/srtool-actions@v0.3.0 which default the new srtool image from paritytech/srtool
- bumps up the version of subwasm
- cleanup
- ability to start builds on-demand
* 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>
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>
* Adds support for checking the timestamp inherent while validating a block
This adds support for checking the timestamp inherent while validating a
block. This will use the relay chain slot number * relay chain slot
duration to calculate a timestamp. This timestamp is used to check the
timestamp in the timestamp inherent.
* Update polkadot-parachains/rococo-runtime/src/lib.rs
Co-authored-by: Shawn Tabrizi <shawntabrizi@gmail.com>
* Update polkadot-parachains/statemine-runtime/src/lib.rs
Co-authored-by: Shawn Tabrizi <shawntabrizi@gmail.com>
* Update primitives/timestamp/src/lib.rs
Co-authored-by: André Silva <123550+andresilva@users.noreply.github.com>
* Fix warnings
Co-authored-by: Shawn Tabrizi <shawntabrizi@gmail.com>
Co-authored-by: André Silva <123550+andresilva@users.noreply.github.com>
* feat(ci): update runtime build workflow
- switch to a tag for the chevdor/srtool-actions
- trigger to only tags & ignore folders not involved in the runtime
- add weekly build schedule
- add timestamp to the artifacts
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>
It doesn't make sense to log them as a warning, especially when it could
happen that a parachain id could be reused over the lifetime of a relay
chain.
* 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>
Denis Pisarev