thryec.hl

smart contracts | tees | exploring zk for privacy

building @hyperlink_xyz | @bluethroat_labs |

[thryec.hl @thryec]

@cryptodavidw hey David, how can we get access to zkao?

[thryec.hl @thryec]

@zkaotool hey there! requested access a couple days ago, wanted to use this for our protocol that we're launching soon, was wondering if we could get access? DMs are open as well, would love to test it out and contribute!

[thryec.hl @thryec]

@0xOwenThurm but models find items that multiple SRs and rounds of audits seem to miss, speaking from personal experience. not an argument just curious on your thoughts

[vitalik.eth @VitalikButerin]

Getting increasingly bullish on just vibe-coding the important things in Lean.

eg. see:

https://t.co/YOdVyJMNAv

https://t.co/XbDCD0BCEu

[thryec.hl @thryec]

@lidothegreat avail if not too late

[thryec.hl @thryec]

@OpenZeppelin are there plans to add HyperEVM support anytime soon?

[Bluethroat Labs @bluethroat_labs]

Assumptions Kill Systems.

Bluethroat Labs is now live.

https://t.co/n5nlEAUnLO

[thryec.hl @thryec]

@lidothegreat 😂😂 the cli is usually much better in my exp

[kaden.eth @0xKaden]

✨Introducing evmresearch✨✨

A knowledge graph of nearly everything I've learned about the EVM in the past six years

The graph structure emulates the brain, exponentiating research speeds for both humans and agents

https://t.co/974InOGRmw

[thryec.hl @thryec]

built a HyperEVM testnet explorer in light of purrsec's deprecation - https://t.co/ViAmHWEF95

any feedback/suggestions welcome! 🫡

[parsec @parsec_finance]

After 5 years, parsec is shutting down. Not how we wanted our story to end, but we are proud of what we built and the value we provided along the way.

We are eternally grateful to those that traversed the ups and downs onchain with us. It was quite the ride 🔭

[DAN KOE @thedankoe]

https://t.co/kNfAIZcqin

[Bluethroat Labs @bluethroat_labs]

1/ Side-channel attacks: when isolation isn't enough

We've covered TrustZone, SGX, and SEV—all provide strong hardware isolation to protect secrets.

But there's a catch: even when an attacker can't directly read your data, they can sometimes infer it by watching how the hardware behaves.

Welcome to the world of side-channel attacks—the art of learning secrets without breaking the locks.

[Bluethroat Labs @bluethroat_labs]

1/ Before jumping into vendor specifics, remember: a TEE isn't a strict blueprint—it's more like a set of guidelines.

The Confidential Computing Consortium (CCC) lays out key security must-haves, without dictating the exact tech to get there.

Any TEE solution needs to deliver these basics to earn the label.

[Rahul Saxena @saxenism]

Please. If you're building TEE protocols, DO NOT discount microarchitectural side-channel exploits.

If your protocol grows to a point where it becomes viable to exploit, you HAVE to assume sophisticated attackers going after you.

Do not ignore the bare-minimums.
+ No early returns
+ No trad string comparisons
+ No data-dependent cache access patterns
+ No conditional branching (on sensitive data)
+ No time-dependent code
+ No access patterns reveal (cache hit vs miss timings)
+ No non-constant time crypto

Please, nail the fucking basics of writing enclave code before going live and risking the hard-earned money of your users.

PS: Not directed towards any specific protocol. Just a general observation.

[thryec.hl @thryec]

@JeffKirdeikis @marclou @bryan_johnson would love to collab on this in any way, am a dev based in vancouver and love squamish. DMs are open 🫡

[thryec.hl @thryec]

@saxenism one day late but yes ser!

[thryec.hl @thryec]

@dabit3 @openfront_io @eigencloud would this generalize/apply to any TEE system?

[thryec.hl @thryec]

@chrisdior777 @1inch @LidoFinance @eulerfinance @aave assuming none have gone through a major hack then? 👀