Replymessage unavailable
That distinction helps. The framework and storage can protect the normal path, yet a non-TEE node still makes runtime exposure part of the threat model, especially if an app uses an unencrypted volume. Does Ratio1 expose a node's TEE status to an application before it sends confidential input?