Geode Labs

Session Recap | 🇲🇾 Kuala Lumpur, Malaysia | 19th Sept | Topic: Private Distributed Inference on Consumer Hardware WPRC took over the @ETHKL1 Hacker House for an afternoon on this question: can a stranger’s Mac run your prompts without reading them? 📖 Read a full summary here - drive.google.com/file/d/1rHJ… 📝 Topic Overview & TL;DR Over 100 million @Apple Silicon Macs sit idle most of the day. Darkbloom wants to rent that capacity out as an inference network where the Mac owner cannot see the prompt, even with root access. The catch is that Apple Silicon has no SGX-style TEE for third-party code. A TEE is a sealed hardware zone the machine’s owner cannot look inside, so Darkbloom builds the guarantee from four layers instead: Secure Enclave identity, Apple-signed attestation, MDM cross-checks and a hardened process. ✍🏻 1st argument - Where does plaintext actually exist. Darkbloom is hop-by-hop encrypted, not end-to-end, which means each leg of the trip is encrypted but the prompt gets unwrapped at the stops. The coordinator is confidential, but the provider’s hardened process has to decrypt your prompt to run the model in memory. So the whole privacy claim comes down to one thing: is that process truly sealed off from the person who owns the machine. ✍🏻 2nd argument - is four layers a substitute for a real TEE. Darkbloom says the only attack left is physically probing the memory soldered into the chip, the same residual threat Apple accepts for Private Cloud Compute. But PCC runs on Apple’s own servers in its datacenters. Darkbloom runs on someone’s desk. ✍🏻 3rd argument: every layer roots back to Apple. Secure Enclave, the attestation certificate and MDM are all Apple-controlled, so the compute is decentralized but the root of trust is not. The room split on whether that is a flaw or just an honest trade-off. None of it would have been possible without your support! Our session lead: @StPinkie Our moderators: @yudhishthra @shuenrui Our venue partner: @ETHKL1 🫶🏻 Missed this session? No worries! Stay tuned for our upcoming events👇🏻 luma.com/whitepaper

Upcoming Session at @EDCON_Official | Kuala Lumpur 🇲🇾 | 18th Oct | Topic: Hegota Upgrade 🎟️ RSVP - luma.com/wprc-tpe-261018-heg… *This session takes place inside the main @EDCON_Official 2026 venue. Please register for EDCON first to join - luma.com/x54fvix6 📝 Topic & TL;DR Today one builder decides what goes into each @Ethereum block. Hegotá is @Ethereum’s attempt to take that power away, and maybe to cut the time you wait for a confirmation. ✍🏻 What we'll cover: 1/ FOCIL (EIP-7805) : A committee of validators publishes lists of transactions the next block must include, so censoring a transaction is no longer one builder’s decision; Author - @soispoke 2/ Quick Slots (EIP-8198) : Ethereum’s fixed 12-second slot becomes a configurable setting, with 10 seconds as the first step down; Author - @carlbeek 3/ Optional Execution Proofs (EIP-8025) : time permitting: Nodes can check a block with a zk proof instead of re-running every transaction, and nothing consensus-critical depends on those proofs yet; Authors - @kevaundray @drakefjustin @codytouchgrass Ignacio Hagopian Han Cody Gunton 4/ Governance: How an EIP goes from a forum thread to a scheduled fork, and who decides which proposals make the cut; Shout out to our Session Guides: Bing and NC from Lodestar Team @ChainSafeth 🤝🏻 @geodelabs & @ETHKL1 for hosting us 🫶🏻 And our supporting power from Taiwan @joy_890913 from @fluidkey More thoughts about Hegota Upgrade? Let's bring your questions and join us! ​📑 EIP Sources: forkcast.org/upgrade/hegota