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.

* compact, need to be made optional and look into/compress child trie
roots/state.

* proto with child trie support

* Missing set_offchain_storage overload.

* right name

* Ignore offchain indexing in validation function.

* patch trie-db

* decompress from iter

* use compressed proof

* remove wasm blob from proof (no inject plugged yet)

* change lock

* update trie

* change in toml

* Revert "change in toml"

This reverts commit aa5c568.

* use patch to branches

* i

* i:wq

* switch branch

* ii

* ok, needed to patch the runtime by putting substrate patch in polkadot
project.

* test passing with this conf

* actual lazy code fetch

* patch issue

* Code reorg

* restore commented tests.

* update deps.

* remove polka patch

* fixes

* remove patch

* revert cargo.lock

* cargo update -p sp-trie polkadot-service

* fix collator test (using parent state root).

* Update pallets/parachain-system/src/validate_block/implementation.rs

Co-authored-by: Bastian Köcher <[email protected]>

* Remove encode_witness test function.

* Update pallets/parachain-system/src/validate_block/implementation.rs

* Fix compilation

Co-authored-by: Bastian Köcher <[email protected]>
Co-authored-by: Bastian Köcher <[email protected]>

(cherry picked from commit 57d2993)

… integritee

…x_logger.sh

…executor.

…hell.spec_version + 1

…a that allows valid extrinsics.

…revious error upon upgrade: `panicked at Timestamp no inherent data provided.` Is a client error - not a runtime.

This reverts commit 460102a

…d. The previous error upon upgrade: `panicked at Timestamp no inherent data provided.` Is a client error - not a runtime."

This reverts commit 23242cb

… the aura stuff to the shell-runtime. Also align declaration order with integritee-runtime for simpler comparison.

… docker image.

* remove pallets/ use cumulus stuff

* remove primitives/ use cumulus stuff

* remove client/ use cumulus stuff

* [polkadot-parachains] remove chain_spec jsons of polkadot chains

…eys used to be less error prone.

…tegritee.state, integritee-spec.json.

…d in the build-spec command

…tegriTEE Network` or `IntegriTEE Shell`. Add network name extensions: dev, local, custom

[commands] add kusama options for the networks

…d to authority ids.

… endowance for alice, bob does not work

…stantiation

…er polkadot-launch configs.

This reverts commit 92b25f4

…e seamless client upgrade.

…shes.

…d code, which was unveiled afterwards.

… Update the tested artifacts

…r`, update --chain arg for integritee-collators

…th two parachain-collators

…artifact names.

Closes #13 

Tested with `launch-rococo-local-with-shell` config:

Tested:

- [x] Cannot send xt's: `Balances::transfer`, `Vesting::vested_transfer`.
- [x] Can send: `Vesting::force_vested_transfer` as root.

Closes #14 
Checked:
- [x] Block production with `launch-rococo-local-with-shell.json`
- [x] Block production with `launch-rococo-local-with-integritee.json`
Note: I have not rebased cumulus on upstream - only updated the branches and manually applied changes with directory diff. IMO we deviated too from upstream for a rebase.

Outsource the pallets directly from Cumulus Repo:
* ParachainInfo: Was outsourced already, only deleted the directory
* Removed cumulus pallet ping. This pallet we could also remove from the runtime.

Fix Ci by bumping pallet-teerex, which referenced an unexisting commit.