crypto

6. Based rollups ultimately won't take off in 2025.

Good enough interop via protocols like Across will be achieved.

No line of sight to universal synchronous composability.

7. TEEs will become an integral (and ultimately permanent) component of L2 infrastructure.

Mippo 🟪

What does this mean?

https://x.com/MikeIppolito_/status/1870938945971949745

TEEs are the best technology today for speed, privacy, and decentralization.

They are particularly salient for L2s since L2s optimize for different things than L1 and as a result are harder to decentralize in the typical ways. In particular, super fast UX or novel ordering schemes like prio fee ordering.

There's also a lot of novel crypto use cases that are unlocked by TEEs that are interesting to the developer communities of L2s.

See: web3 x web2 interoperability with teleport.best or https://nousresearch.com/setting-your-pet-rock-free/ for a glimpse

Am I correct that developing software to run on a TEE requires some form of licensing/authorization from the manufacturer?

Pragmatism (Security) at OP Labs.
Prev: ConsenSys & Coinbase.

Attribs: Friendly, curious, introverted, mid-witted.
Chans: /eth-security /maurelian /stoicism




No, that used to be the case with Intel SGX "EPID" attestation (which relies on Intel as an intermediary, but completely deprecated now anyway) but not the case with "DCAP". You can produce SGX and TDX apps without any interaction or registration with Intel, same w/ AMD

junior product @ teleport.best 
incubated by flashbots[x]

Basically you can run any program you run in a TEE,.when you get a remote attestation it includes the hash of this program.
Check these:
- https://github.com/Account-Link/teleport-gramine-rs/blob/main/AUDITING.md
- https://collective.flashbots.net/t/flashwares-ii-end-to-end-useful-enclave-in-gramine-python-intro-to-controlled-channel-attacks/3432
- https://sgx101.gitbook.io/sgx101/sgx-bootstrap/attestation

So as a user, do I just tell my tee what keys I trust to sign software?