Provision light-client state in mu-ra; fix w2 startup #1398
Conversation
…ion import type.
…-production import type." This reverts commit c3c46fd.
…ms such that it can be shared across threads in an arc. [light-client] add constructor to `LightClientStateSealSync` fix light-client adjustments remove pending wip of sealing adjustements
| pub unjustified_headers: Vec<Block::Hash>, // Finalized headers without grandpa proof | ||
| pub verify_tx_inclusion: Vec<OpaqueExtrinsic>, // Transactions sent by the relay | ||
| pub scheduled_change: Option<ScheduledChangeAtBlock<Block::Header>>, // Scheduled Authorities change as indicated in the header's digest. | ||
| } | ||
|
|
||
| impl<Block: BlockT> RelayState<Block> { |
There was a problem hiding this comment.
Todo to me: introduce separate datatype instead of implementing this on the RelayState itself, and do some testing
| /// Light client db seal. | ||
| pub static GLOBAL_LIGHT_CLIENT_SEAL: ComponentContainer<EnclaveLightClientSeal> = | ||
| ComponentContainer::new("EnclaveLightClientSealSync"); |
There was a problem hiding this comment.
Had to introduce a separate component to access this in the tls-ra domain
| where | ||
| ShieldingKeyRepository: AccessKey<KeyType = Rsa3072KeyPair> + MutateKey<Rsa3072KeyPair>, | ||
| StateKeyRepository: AccessKey<KeyType = Aes> + MutateKey<Aes>, | ||
| // Constraint StateT = StfState currently necessary because SgxExternalities Encode/Decode does not work. | ||
| // See https://github.com/integritee-network/sgx-runtime/issues/46. | ||
| StateHandler: HandleState<StateT = StfState>, | ||
| { |
There was a problem hiding this comment.
unnecessary type constraints on the type definition
|
I can't explain currently, why I see the following erros in the failing integration tests: |
This sometimes happens, because we are really pushing those machines when running the tests in parallel, and we (@mosonyi and I) suspect that the |
|
Alright, thanks a lot! 👍 |
|
Rebased on master and merge into master here #1399 |
This implementation should actually be independent of the polkadot-v0.9.42 update, I will also rebase this branch on master and file a standalone pr.