* Erasure encoding availability initial commit
* Modifications to availability store to keep chunks as well as
reconstructed blocks and extrinsics.
* Gossip messages containig signed erasure chunks.
* Requesting eraure chunks with polkadot-specific messages.
* Validation of erasure chunk messages.
* Apply suggestions from code review
Co-Authored-By: Luke Schoen <ltfschoen@users.noreply.github.com>
* Fix build after a merge
* Gossip erasure chunk messages under their own topic
* erasure_chunks should use the appropriate topic
* Updates Cargo.lock
* Fixes after merge
* Removes a couple of leftover pieces of code
* Fixes simple stuff from review
* Updates erasure and storage for more flexible logic
* Changes validation and candidate receipt production.
* Adds add_erasure_chunks method
* Fixes most of the nits
* Better validate_collation and validate_receipt functions
* Fixes the tests
* Apply suggestions from code review
Co-Authored-By: Robert Habermeier <rphmeier@gmail.com>
* Removes unwrap() calls
* Removes ErasureChunks primitive
* Removes redundant fields from ErasureChunk struct
* AvailabilityStore should store CandidateReceipt
* Changes the way chunk messages are imported and validated.
* Availability store now stores a validator_index and n_validators for
each relay_parent.
* Availability store now also stores candidate receipts.
* Removes importing chunks in the table and moves it into network
gossip validation.
* Validation of erasure messages id done against receipts that are
stored in the availability store.
* Correctly compute topics for erasure messages
* Removes an unused parameter
* Refactors availability db querying into a helper
* Adds the apis described in the writeup
* Adds a runtime api to extract erasure roots form raw extrinsics.
* Adds a barebone BlockImport impl for avalability store
* Adds the implementation of the availability worker
* Fix build after the merge with master.
* Make availability store API async
* Bring back the default wasmtime feature
* Lines width
* Bump runtime version
* Formatting and dead code elimination
* some style nits (#1)
* More nits and api cleanup
* Disable wasm CI for availability-store
* Another nit
* Formatting
* rename crates as appropriate
* Rename to use master - easy to revert, but shows it's working
* Bump runtime version
* Bump version
* Bump Substrate again
* Update to latest Substrate master (#615)
* Update to latest Substrate master
* Remove unneeded patch + warning
* Update `Cargo.lock`
* Fix tests
* Update again
* Bump Substrate (#616)
* Update lock
* Fix
* Few fixes
* Bump to latest Substrate
* Fixes
* fix pre-tx-pool compilation
* more compilation fixes
* Updates for the injection period
- Liberal slash-refunding
- Instant unbonding
* *: Enable refactored authority discovery (#624)
* *: Enable authority discovery module
* *: List authority discovery id after parachain validator id
Make sure existing key types don't change their order by appending the
authority discovery id instead of injecting it between im online id and
parachain validator id.
* *: Gate authority discovery module behind feature flag
* cli/src/lib.rs: Fix warnings
* cli/src/lib.rs: Shorten line length
* Bump Substrate
* Bump Substrate
* Line widths
* Line widths again
* Revert bump.
* Dockerfile fixed.
* docker: use init.sh to setup rust env
* CMD replaced with ENTRYPOINT in Dockefile
* WIP Sentry/Validator basic setup
* Dockerfile modifier to correspond to master version
* `environment` block added to both sentry and validator
* some environment variables are now used to pass params to containers
Made two small changes to the README.adoc that will help first-time users. First, I added notifications that the user may need to edit their PATH env variable after installing Rust. Second, I added a 'Hello world!' name tag to the Kusama Canary Network connect command so that new users will be better able to find their node on telemetry.
* Update Substrate after repository reorganisation
* Switch back to polkadot-master
* Bump `bitvec` and `parity-scale-codec` (#591)
Also bump other dependencies, but respect semver on them.
* Fix locking, from an updated Substrate (#506)
* Fix locking, from an updated Substrate
* Bump runtime version
* Lock file.
* Bump version and extra fix.
Fedor Sakharov