<p>With the newly deployed runtime v540, we also needed to update our teeracle enclave. This proposal updates the whitelist with the new MRENCLAVE which you can verify against our&nbsp;<a href="https://github.com/integritee-network/worker/releases/tag/v0.14.0">release 0.14.0 /&nbsp;</a><a href="https://hub.docker.com/layers/integritee/teeracle/v0.14.0/images/sha256-75432419775be447e35ebacfd893d9bb1f0b88afaa2d7be51368ac4c1f84d5c1?context=explore">docker image</a></p>
<p>The purpose of this teeracle is to regularly fetch the TEER exchange rate fro mcouingecko and coinmarketcap and write it to our chain. Learn more in our&nbsp;<a href="https://medium.com/integritee/introducing-integritees-teeracle-a-framework-to-build-tee-based-oracles-f54c5957e83d">blog article</a></p>

Send a batch of dispatch calls.

May be called from any origin except `None`.

- `calls`: The calls to be dispatched from the same origin. The number of call must not
  exceed the constant: `batched_calls_limit` (available in constant metadata).

If origin is root then the calls are dispatched without checking origin filter. (This
includes bypassing `frame_system::Config::BaseCallFilter`).

## Complexity
- O(C) where C is the number of calls to be batched.

This will return `Ok` in all circumstances. To determine the success of the batch, an
event is deposited. If a call failed and the batch was interrupted, then the
`BatchInterrupted` event is deposited, along with the number of successful calls made
and the error of the failed call. If all were successful, then the `BatchCompleted`
event is deposited.

- Problem Statement: Updating the whitelist with the new MRENCLAVE for the teeracle enclave.
- Significance: Ensuring accurate exchange rate data is fetched and written to the chain.
- Proposed Solution: Update the whitelist with the new MRENCLAVE.
- Expected Outcomes: Improved accuracy in fetching and writing exchange rate data to the chain.

#36 Whitelist Teeracle 0.14.0

No Active Proposals