-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Encointer contributions #174
Merged
brenzi
merged 30 commits into
integritee-network:master
from
encointer:enhancements-upstreaming
Sep 9, 2020
Merged
Encointer contributions #174
brenzi
merged 30 commits into
integritee-network:master
from
encointer:enhancements-upstreaming
Sep 9, 2020
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
brenzi
force-pushed
the
enhancements-upstreaming
branch
from
September 8, 2020 20:53
2e77df9
to
9ce0c47
Compare
* [stf] make Alice root, and check root in TrustedCall::set_balance call * [tests/commons] annotate that alice is root * [enclave/attestation] remove weird todo * [stf] fix test compilation * [worker/enclave_api] enclave_shielding_key now returns Rsa3072PubKey instead of Vec<u8> * [worker/tests/ecalls] remove todos for testing the get_shielding_key/get_signing_key as successful fetch is verified in all integration tests and we have no means of verifying here that a "correct" key was fetched. Only if the call was successful.
* bump substrate-api-client: 0.4.6-sub2.0.0-alpha.7. Update compose extrinsic macro call accordingly add tag for sgx-runtime * bump substratee-node-runtime: 0.6.5-sub2.0.0-alpha.7. Change report timestamp unit from seconds to millis [stf] rename my-node-runtime -> substratee-node-runtime to be consistent * bump version: 0.6.4-sub2.0.0-alpha.7
* include hash of trusted_call_signed in shield_funds extrinsic * change call_hash to H256
* [worker] initialize chain after keys have been provisioned * [worker] fix cli for key_provisioning tests * [worker/mu-ra] pass shard that should be exchanged is passed to request_key_provisioning * [enclave/cert] fix mr_enclave fetch and comparison * [enclave/tls_ra] remove state exchange from ra as every new worker fetches calculates the state from 0. * [worker] change get_most_recent_worker -> get_first_worker that is not equal to self * [worker] ensure_shard_initialized now in any case as we do not fetch a state while provisioning secrets. And put it at the very beginning of `fn worker` * [enclave/tls_ra] remove unsafe from request_key_provisioning * bump version: 0.6.5-sub2.0.0-alpha.7
* [enclave] extracted verify worker response. * [STF/enclave] whip update storages upon block import * [enclave] perform state updates on all shards upon block import * [enclave] Create shard if it does not exist. Currently, the workers follow an auto-join policy for new shards. * clippy * [enclave] do not return an error if could not execute relevant extrinsic in stf. Only log the error.
* [enclave] return preemptively if there are no worker_requests to be performed in state_update upon block import * [worker] use lazy_static to create a global static reference to the node_url. No longer passing the node_url to the enclave needed. * [enclave/stf] support on-chain storage access in get_state * perform_ra: rename url -> w_url to prevent confusion with node_url * clippy * [enclave] ! fix: init-shard if it does not exist
clean up chain relay sync logging
* changed ws_server completely. Requests from client are now handled in the worker main event loop to prevent race conditions with on state/chain_relay access. * [ws_server] remove unwrap and send instead "invalid_client_request" to client
* updating block number in stf state * fix #9. apply demurrage in client * bump version to 0.6.8
… headers themselves
* fixes #7 * add total-issuance to client CLI * bump version to 0.6.7 * document new function in script
brenzi
force-pushed
the
enhancements-upstreaming
branch
from
September 8, 2020 20:56
9ce0c47
to
3977104
Compare
…ke encointer reference release
brenzi
added a commit
to encointer/encointer-worker
that referenced
this pull request
Nov 3, 2020
* automatic-shard-joining-and-per-shard-updates-on-block (integritee-network#160) * [enclave] update_map contains options. This is needed if a storage value needs to be deleted in the STF [enclave, stf] perform state updates per shard, auto join new shards * [worker] only feed 100 blocks at a time into the chain relay. Improved logging while syncing to keep track of sync status * [WorkerApi] Remove default protocol ws. * update ipfs version (integritee-network#165) Co-authored-by: bwty <whalelephant@users.noreply.github.com> * Implement Ipfs read and write with verification in enclave this implements gitcoin bounty integritee-network#70 Co-authored-by: bwty <whalelephant@users.noreply.github.com> * Encointer contributions upstreaming (integritee-network#174) * [enclave] ! fix: init-shard if it does not exist * back up chain relay db before update in case of file corruption * clean up chain relay sync logging * Ws server refactor (#13) * changed ws_server completely. Requests from client are now handled in the worker main event loop to prevent race conditions with on state/chain_relay access. * [ws_server] remove unwrap and send instead "invalid_client_request" to client * updating block number in stf state * [enclave/chain_relay] store only hashes of the headers instead of the headers themselves * enclave: patch log and env_logger to mesalock * worker should panic if it can't write to shard * add public getters for unpermissioned statistics (#16) * don't request key provisioning form other worker. assume its there or generate new (dangerous!) * bump version to 0.6.11 like encointer reference release Co-authored-by: clangenb <37865735+clangenb@users.noreply.github.com> Co-authored-by: Marcel Frei <marcel.frei@electronix.ch> Co-authored-by: Christian Langenbacher <christian.langenbacher91@gmail.com> * fix integritee-network#176 and update some dependiencies * upgrade to upstream 2.0.0-rc5 fix .dispatch filtering introduced in paritytech/substrate#6318 depend on tag version for sgx-runtime * Upgrade upstream 2.0.0 (integritee-network#182) * enclave builds * worker and client builds * fix metadata module index * successfully tested shielding-unshielding example * fix merge. builds and demo works Co-authored-by: clangenb <37865735+clangenb@users.noreply.github.com> Co-authored-by: bwty <18553484+whalelephant@users.noreply.github.com> Co-authored-by: bwty <whalelephant@users.noreply.github.com> Co-authored-by: bwty <email-me@belsy.space> Co-authored-by: Marcel Frei <marcel.frei@electronix.ch> Co-authored-by: Christian Langenbacher <christian.langenbacher91@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fixes #162