Matevž Jekovec

I can't seem to find any Oasis consensus or Sapphire chains listed on https://traceye.io

Workaround for now https://github.com/oasisprotocol/sapphire-paratime/pull/332/files#diff-27993bdc7c99c800edccb88d59a02e792f012d5764aae55a8efaa2d6b0b46e2bR26-R29

Do you have anything particular in mind? The revert messages should work the same for both the transactions and the queries as they do on Ethereum.

Will this enable running queries on a local Sapphire client node that doesn't have access to c10l state and it will automatically relay it to a remote RPC?

> I tested the example and found an issue when you have a different chain selected in Metamask than the one you're deploying the contract to. In my case I...

TODO: 1. https://github.com/oasisprotocol/oasis-core/blob/master/go/runtime/host/tdx/qemu.go: run QEmu with non-tdx flags 2. rofl-containers: prepare a non-tdx Localnet version, special release made in parallel to ordinary release 3. https://github.com/oasisprotocol/oasis-core/tree/master/runtime/src/common/tdx: add `debug-mock-tee` flag 4. https://github.com/oasisprotocol/oasis-sdk/blob/main/runtime-sdk/Cargo.toml#L62:...

Today I realized the Localnet testing should not require any access to the internet (e.g. when you're on a plane or you have a slow internet connection). This means that...

> Is this still needed? If not, then this chapter needs to be updated to reflect it https://docs.oasis.io/node/run-your-node/advanced/sync-node-using-state-sync