Marlin

TEE coprocessors for decentralized AI

[Marlin @MarlinProtocol]

Wondering how to secure your AI agent within a TEE? We’ve got you covered!

Check out our latest post by @roshanrags @0xkrane @PrateekReddyy @0xlinguine:

Securing TEE Apps: A Developer's Guide

[bedlam research @bedlamresearch]

Securing TEE Apps: A Developer's Guide

In this post, @roshanrags, @PrateekReddyy, @0xlinguine and @0xkrane explore the features that have made TEEs popular for crypto x AI, discuss security concerns and lay out some practical solutions to build TEE applications

[Marlin @MarlinProtocol]

With confidential compute, privacy stops being a promise and becomes something you verify.

This tutorial makes that concrete on Oyster with privacy-preserving addition inside an enclave: deploy the VM, run the compute with hidden inputs, then check the attestation yourself.

[Marlin @MarlinProtocol]

"Trust me bro" is not a security model. Attestation is.

[Marlin @MarlinProtocol]

TEE-based inference doesn't have to be built in-house by each provider.

Marlin provides it as open, verifiable compute infrastructure. Same hardware guarantees. No proprietary stack required.

Learn more: https://t.co/74v9a7R9gp

[Marlin @MarlinProtocol]

Meta's Private Processing puts AI inference inside a TEE. The host sees encrypted memory. Nothing else.

Secure enclaves. Encrypted processing. Anonymous routing. Verifiable code. This is the new standard for private AI.

How the full stack fits together: https://t.co/YpogC06DIs

[Marlin @MarlinProtocol]

TEEs solve a core AI problem:

Models need plaintext to run, you can't compute on ciphertext. Usually, that means trusting the server.

With a TEE, decryption happens inside a sealed enclave. The operator provides compute but can't see the data, removing the trust assumption.

[Marlin @MarlinProtocol]

When TACo relaunches under WEDF stewardship and/or Seal (https://t.co/kxPSk14gQP) launches on mainnet, a new KMS root seed ceremony can be performed against the relaunched network. That ceremony would re-establish a root seed backup for the new operational setup.

[Marlin @MarlinProtocol]

TACo has announced a transition in stewardship to the World Ethical Data Foundation (WEDF), with a planned network relaunch later in 2026.

What this means for the Oyster Key Management Service (KMS) 🧵

[TACo | World Ethical Data Foundation @buildwithtaco]

We've been quiet on X for 6-ish months, but a lot has happened behind the scenes. TACo fully exited the @ThresholdAC network, expanded the access condition framework, increased support across various EVM chains, and completed numerous secure handovers of cryptographic material between nodes – demonstrating the network's unique resilience in a distributed paradigm.

Through it all, the technology has reached maturity. In the last couple years, TACo has underpinned real-world, high-stakes data sharing patterns; including delivering inheritance information to beneficiaries without trusted middlemen, managing decryption rights for valuable digital media libraries, and securing back-up root keys for TEEs.

[Marlin @MarlinProtocol]

Practically, the KMS can operate even while TACo nodes remain unavailable.

However, there is a caveat: if all current KMS nodes were to go down, the ability for enclaves to derive secrets from the KMS will be lost forever.

[Marlin @MarlinProtocol]

Happy Bitcoin Pizza Day! 🍕🐟

[Marlin @MarlinProtocol]

He’s enjoying those readable inputs a bit too much

Make everything confidential

[Marlin @MarlinProtocol]

What keeps this secure: the key material is never exposed to outside servers during backup. Recovering it means clearing multiple independent checks. Access policy sign-off, hardware-level verification, and threshold server availability all have to pass.

[Marlin @MarlinProtocol]

Marlin’s Key Management Service (KMS) is set to feature another recovery path.

This is powered by Seal on @SuiNetwork and enforced via Sui smart contracts, operating independently from the existing Threshold Network backup.

https://t.co/kxPSk14gQP

[Marlin @MarlinProtocol]

Think of it as two separate vaults for the same critical key, each built on a different system with its own access rules. If one path fails, the other continues working. Neither can be unlocked without clearing multiple layers of independent authorization.

[Marlin @MarlinProtocol]

If you’re not happy single, you won’t be happy in a relationship.

True happiness comes from verifiable state transitions and knowing your data never left the enclave.

[Marlin @MarlinProtocol]

See: https://t.co/EWFuBV97vC

[Marlin @MarlinProtocol]

AWS now supports TPM-based EC2 instance attestation.

Like Nitro Enclave attestation, it gives software a way to prove its identity and boot state cryptographically, instead of relying on “trust me.”

[Marlin @MarlinProtocol]

For Marlin Oyster SDK users, the goal is to make this verification easy.

Developers should be able to check an EC2 instance’s attestation before trusting it, without becoming experts in TPMs, certificates, or AWS internals.