Ab/shield from shard vault

[brenzi]

closes #1495

testing

run node on host:

./target/release/integritee-node --dev --tmp --unsafe-ws-external --rpc-cors all 

run sidechain

SGX_MODE=SW WORKER_MODE=sidechain WORKER_FEATURES=dcap make
cd bin
export RUST_LOG=info,substrate_api_client=warn,ws=warn,mio=warn,its_consensus_common=info,sidechain=info,integritee_service=trace,enclave_runtime=trace,ac_node_api=warn,sp_io=warn,itc_parentchain_indirect_calls_executor=trace,itp_stf_executor=trace,itc_parentchain_light_client=trace,itc_parentchain_block_importer=trace,itp_stf_state_handler=trace,ita_stf=trace,itp-attestation-handler=debug,itc_parentchain_indirect_calls_executor=trace,itp_top_pool=debug,itc_offchain_worker_executor=debug,ita_parentchain_interface=trace
./integritee-service -c -u ws://172.17.0.1 run --skip-ra --dev &> worker.log 

once you see the ProxyAdded event in js/apps, remember the delegator account which is the vault.

Now, use js/apps to send funds from Bob to Vault

• worker log should show shielding for ....
• and ita_stf::trusted_cal[....] balance_shield([...]

check shielded balance for Bob (find mrenclave in worker log)

./integritee-cli -u ws://172.17.0.1 trusted --mrenclave 2MyXuroF4yiR8A6S8t334C4ZvY6qyKxVBKsd8SPnVW3y balance //Bob

should return the amount you sent
q.e.d.

[clangenb]

Looks good to me in general, but I am failing to see where the vault account is set.

[clangenb]

So we decide not to handle any events at all if the vault key is not present?

[brenzi]

at the moment. we'd need to become more generic yet if we want to support other cases