edit: we have encountered a <a href="https://github.com/integritee-network/worker/issues/1707">minor issue</a> with this release, therefore we'd like to replace this referendum with a later fix. There is no harm if this goes through, but we won't engage voters on this one.
Sidechain blocks can only be finalized by a whitelisted enclave fingerprint (Intel SGX calls it MRENCLAVE), which guarantees integrity of execution.
During beta phase, the Integritee team can deploy upgrades before whitelisting the enclave, but finality will only occur after whitelisting has been ratified by Integritee governance
This proposal aims to whitelist the sidechain-enclave build for Integritee SDK release 0.16.1
<a href="https://github.com/integritee-network/worker/releases/tag/v0.16.1">https://github.com/integritee-network/worker/releases/tag/v0.16.1</a>
MRENCLAVE: 0x1798cf19399c1764ff794da31bee190ab33d52ed08feef66e3786d24910dde6a
Shard: 5wePd1LYa5M49ghuhnp41SP1RwtPVcsuvcf7JzjHcbXg (IncogniteeTEER000000000000000001)

**edit: we have encountered a [minor issue](https://github.com/integritee-network/worker/issues/1707) with this release, therefore we'd like to replace this referendum with a later fix. There is no harm if this goes through, but we won't engage voters on this one.**

Sidechain blocks can only be finalized by a whitelisted enclave fingerprint (Intel SGX calls it MRENCLAVE), which guarantees integrity of execution.

During beta phase, the Integritee team can deploy upgrades before whitelisting the enclave, but finality will only occur after whitelisting has been ratified by Integritee governance

This proposal aims to whitelist the sidechain-enclave build for Integritee SDK release 0.16.1

[https://github.com/integritee-network/worker/releases/tag/v0.16.1](https://github.com/integritee-network/worker/releases/tag/v0.16.1)

MRENCLAVE: 0x1798cf19399c1764ff794da31bee190ab33d52ed08feef66e3786d24910dde6a

Shard: 5wePd1LYa5M49ghuhnp41SP1RwtPVcsuvcf7JzjHcbXg (IncogniteeTEER000000000000000001)

Update shard config
To be respected by L2 instances after `enactment_delay` parentchain blocks
If no previous config exists, the `enactment_delay` parameter will be ignored
and the `shard_config` will be active immediately

- **Problem Statement:** 
  - Minor issue with the release, seeking to replace the referendum with a later fix.

- **Significance:** 
  - Ensuring the integrity of execution by finalizing sidechain blocks only with a whitelisted enclave fingerprint.

- **Proposed Solution:** 
  - Whitelisting the sidechain-enclave build for Integritee SDK release 0.16.1.

- **Expected Outcomes:** 
  - Guaranteeing finality after whitelisting by Integritee governance for enhanced security.

#50 Update Incognitee Sidechain Enclave to 0.16.1 [vote Nay!]

No Active Proposals