Oyster coprocessors are built on Nitro Enclaves, a TEE implementation that ensures the security of your code and data by protecting against tampering and leaks, perfect for securely outsourcing computations.

But, enabling network access in enclaves is an engineering challenge.

Nitro Enclaves are isolated with no direct network access, relying on vsocks instead of IP sockets.

This requires apps to be rewritten to communicate with RPCs, APIs or expose endpoints from within this secure environment.

Oyster's goal is make existing apps run inside Oyster without modifications.

Check this piece to learn more about the journey of bringing seamless Internet connectivity to Nitro Enclaves as we delve deep into Oyster's networking stack!

Dive in: https://twitter.com/MarlinProtocol/status/1788910737253085370

Marlin Protocol Announcements

Oyster coprocessors are built on Nitro Enclaves, a TEE implementation that ensures the security of your code and data by protecting against tampering and leaks, perfect for securely outsourcing computations.

But, enabling network access in enclaves is an engineering challenge.

Nitro Enclaves are isolated with no direct network access, relying on vsocks instead of IP sockets.

This requires apps to be rewritten to communicate with RPCs, APIs or expose endpoints from within this secure environment.

Oyster's goal is make existing apps run inside Oyster without modifications.

Check this piece to learn more about the journey of bringing seamless Internet connectivity to Nitro Enclaves as we delve deep into Oyster's networking stack!

Dive in: https://twitter.com/MarlinProtocol/status/1788910737253085370

X (formerly Twitter)

Marlin (@MarlinProtocol) on X

Oyster coprocessors are built on Nitro Enclaves, a TEE implementation that ensures the security of your code and data by protecting against tampering and leaks, perfect for securely outsourcing computations.

But, enabling network access in enclaves is an…

hottg.com/MarlinProtocolAnn/253

626 viewsMay 10 at 12:44