ROSE (ROSE)

. @OasisProtocol just started a new investment arm focused on scaling real-world asset (RWA) infrastructure. $ROSE #Oasis #RWA https://t.co/OXUYhqP2zQ

The key change: they’re moving beyond one-off grants into a more long-term “back builders + help them grow” approach, especially for products that need privacy + heavy compute.

Their first investment is in SemiLiquid, a team building credit infrastructure for tokenized assets (RWAs). This is the unsexy part of RWAs, but it’s the part that actually makes them useful.

Why credit matters: tokenizing an asset is step one. The bigger question is how institutions lend, borrow, enforce rules, and stay compliant without exposing everything publicly on-chain.

Oasis’s angle is clear: the future of on-chain finance needs confidentiality. SemiLiquid uses Oasis’s confidential compute (via Sapphire) to keep sensitive financial data private while still being verifiable. https://t.co/VY2kansKkj

SemiLiquid also mentions using “Liquefaction” (built on Sapphire, developed at Cornell Tech) to handle policy enforcement and breach monitoring without exposing sensitive details.

They’re also pointing to a pilot with Franklin Templeton, Zodia Custody, and Ava Labs, basically: “we’re building something institutions can actually use.” Interesting signal for where RWAs are headed. For more info: https://t.co/4cWH4706uV

Remote attestation gets treated like a trust stamp for TEEs: “Here’s the quote, it’s verified, we’re done.” In practice, that quote is just evidence that something ran on some hardware once. $ROSE #Oasis @OasisProtocol https://t.co/LOOJBEK58O

Anyone who’s touched SGX/TDX attestation knows the vibe: huge blobs, collateral, cert chains, TCB statuses, flags that are easy to misread. One wrong interpretation and you’re confidently trusting the wrong thing.

Even when verification is perfect, attestation only proves a snapshot: -The measurement matched then -The platform looked acceptable then -The operator presented it, but it doesn’t automatically bind to the rest of the system.

That’s where the real gaps show up: Freshness (stale quotes still look valid), liveness (are you checking continuously?), and rollback (an enclave can be restarted with an older encrypted state and still “attest” fine).

Plus, the stuff dashboards never show: Who’s actually operating the enclave? What do they lose if they cheat? What code ran before this version? Was it reproducibly built? Was there a bad upgrade that could’ve leaked secrets? https://t.co/Xp2dv0dkQy

So “attestation verified” isn’t the finish line, it’s the starting input. What you need is policy + enforcement: acceptable hardware, required re-attestation cadence, upgrade transparency, operator binding, rollback protection… and a way to make all of that automatic.

This is why the “consensus as verifier” approach matters. Instead of every user parsing Intel quotes, a fault-tolerant validator set checks the evidence, enforces on-chain policies, and outputs a clean on-chain signal you can actually build on.

That’s essentially what @OasisProtocol pioneered with TEEs: the quote is the raw material, the network makes it usable. For more information on this, check out this article: https://t.co/vzVuWGw4NN