TEE coprocessors for decentralized AI
- Tweets 2,136
- Following 346
- Followers 52,414
- Likes 2,191
Pinned Tweet
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
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
52
76
254
102,346
Machines cannot vouch for themselves with words. On Oyster, they do not have to.
An enclave connecting over Scallop can present an EC2 instance attestation, evidence signed by the hardware about exactly what is running on that machine.
2
2
10
2,364
That timing is the point. By the time two enclaves are exchanging anything real, the question of what each one is has already been asked and answered.
A channel exists because the evidence held, not because anyone extended benefit of the doubt.
1
6
259
The rules for all of this are not tucked away in a service somewhere. They are written into the Marlin SDK, in the open, where anyone can read how a proof is made and how it is judged.
github.com/marlinprotocol/ma…
5
212
Genuine TEE or not? The Marlin Hub UI tells you in seconds.
Paste a hex-encoded Oyster attestation, click Verify, and it checks the document structure and traces the certificate chain back to a trusted hardware root.
Don't trust, verify: hub.marlin.org/oyster/attest…
3
2
12
2,246
"So the TEE keeps everything sealed while it runs, the host just sees a black box, they can't open it, can't copy it, can't even-"
"Peter I'm getting married."
2
4
15
3,260
The Marlin Oyster SDK now ships the verification side of EC2 instance attestation.
Users of the SDK can check a workload runs the expected code in a locked down environment before handing it anything private, with the checking logic maintained upstream.
3
4
20
4,211
Builders declare their expectations, from PCRs and image id to a timestamp and user data, and the SDK enforces only what they set. A passing check returns the decoded attestation, ready to act on.
2
1
3
623
No TPM or certificate expertise required, just declared expectations and a single call. The whole check is open to inspect.
Here's the implementation:
github.com/marlinprotocol/ma…
1
6
492
There are two kinds of confidential AI: the kind that says private, and the kind that can prove it.
Only one runs in a TEE.
2
2
18
3,459
Every connection on Marlin Oyster starts with a question: How does one side know the other is genuine?
Scallop is the protocol built to answer it.
2
4
24
4,705
First-time connections go through full verification. Repeat connections move faster, without giving up any security.
The connection that results is encrypted, authenticated, and does not depend on any certificate authority to hold up.
1
1
9
1,405
Scallop is what sits underneath this. Open-source, part of the Oyster SDK.
github.com/marlinprotocol/ma…
1
1
9
1,298
