Proofcast (@ProofcastLabs) header
Proofcast (@ProofcastLabs) profile picture

Building the future of cross-chain proof generation with the first TEE-VM. Docs @ https://nitter.cf/t.co/knJcUaz8su

Joined May 2024
Photo by Proofcast (@ProofcastLabs)Photo by Proofcast (@ProofcastLabs)Photo by Proofcast (@ProofcastLabs)Photo by Proofcast (@ProofcastLabs)Photo by Proofcast (@ProofcastLabs)Photo by Proofcast (@ProofcastLabs)Photo by Proofcast (@ProofcastLabs)Photo by Proofcast (@ProofcastLabs)Photo by Proofcast (@ProofcastLabs)Photo by Proofcast (@ProofcastLabs)
1/ The first universal teeVM is here! 🧵 Proofcast’s teeVM is the first RISC-V compatible VM that allows you to compile your own code and generate TEE proofs with unparalleled performance.
1
6
3
21
3,804
Proofcast retweeted
Today at the #ZKSummit in Lisbon, exploring the latest in ZK proofs with @ProofcastLabs
1
4
316
Something like our teeVM (RISC V architecture) is the perfect glue 💧 #teeVM
4
364
Exactly, there was a missing piece of the puzzle! An abstraction enabling devs to write truly vendor-agnostic code 🧑‍💻 That’s the promise of @SafeJunctionHQ’s #tRust - you write/audit code once and at compile time you pick your proving target: @SuccinctLabs SP1, @RiscZero, other zkVMs or even teeVMs such as @Acurast and @ProofcastLabs are all supported targets 👉 safejunction.io/key-componen…
ZKVMs promise you can "write normal code" and prove its execution using a zero-knowledge proof. Then I read the docs, and its *rust* with specific annotations, an ugly build system, .... and i'm not sure exactly what for the standard library. Who's got the best tooling here?
3
11
919
We built on RISC-V architecture to optimize for code portability with other zkVMs = everything that runs on SP1, runs on our teeVM. We support multiple TEEs (Nitro/Strongbox atm) to accommodate tailored use cases while abstracting the hardware hurdles. Devs UX is prior n.1
1
1
8
265
In the newly emerging "economy of proofs": - we bet on trusted hardware ("TEEs are dead, long live TEEs") - we bet on abstraction & portability (i.e. devex) #teeVM #zkVM
4
119
GM everyone! Our Medium article “Why does proving matter?” is out 🔥 It is the first of a 3 episodes series where we’ll dig into the “why” behind Proofcast and “what” we want to build. Here are the 3 main concepts to retain 👇🏽 medium.com/@hello_84166/why-…
1
1
1
9
336
4/4 𝐒𝐜𝐚𝐥𝐢𝐧𝐠 𝐭𝐫𝐮𝐬𝐭𝐞𝐝 𝐡𝐚𝐫𝐝𝐰𝐚𝐫𝐞 💾 Given our core expertise in trusted hardware (TEEs), we believe that: 1) abstracting TEEs complexity for proof generation must go beyond abiding by a proving network lock-in; & 👇🏽
1
2
97
2) aggregation layers, instead of vertical integration, will be the real go-to-place of the new economy of proofs; 3) in this proving landscape, devs will value codebase portability way more than before! Have a good read! ✨ #teeVM #zkproofs #Proofcast
2
96
🤯🤯🤯 S/O to the team at @SuccinctLabs for the most performant zkVM in prod ✨ a massive achievement for the proving ecosystem. Can't wait to test it against Proofcast' teeVM too 😏 Let's make "proofs" MAINSTREAM. #teeVM #SP1 #zkVM #TEE #ZKP
SP1 is live and ready for production use. Our blazing fast zkVM enables any developer to create real-world ZKP applications by simply writing Rust. Let's make ZKPs MAINSTREAM.
4
205
Excited to see @iotex_io & @PhalaNetwork joining forces to scale TEEs for proofs of real-world activity 🔥 We must scale the secure computation layer with hardware & abstract it with software. A general-purpose TEE-VM is the next natural step ⚡️ #teeVM #TEE #DePIN
Replying to @iotex_io
Why are TEEs important for DePIN projects? TEEs are a secure enclave in DePIN devices, safeguarding sensitive data ensuring integrity when generating proofs of real world activity. W3bstream, IoTeX's off-chain computing protocol, lets you leverage TEEs alongside ZK provers.
5
240
Everyone loves TEEs these days - but how smooth is it to deploy programs within one? If you want to try, our TEE-VM solves your problems. On a mission to make TEEs easy to interact with and proving commoditized 🫡 #teeVM #TEE #zk #proofs #Proofcast
1
5
214
"The combination of our collective efforts in secure cryptographic prjmitives and trusted hardware will be teuly unstoppable" 🌡️🔥
How you win friends and TEE-fluence people - Chapter 2 Trusted Execution Environments provide fast, practical private compute in trusted hardware via “enclaves”. And they’ve been wrongfully maligned for years so let’s set the record straight 🧵
4
247
#ethCC garnered consensus around the marriage between zk and TEE tech. We've been building along this paradigm since day 1 🫡 Proofs need to be commoditized: easy to generate, cheap to produce, cheap to verify. Once we have this in place, nothing will stop web3. #teeVM
1
8
183
1) one single codebase in Rust 2) multiple proving backends according to the use-case 3) efficient proof aggregation. The proving workflow has never been easier and our #teeVM is a key component of it ✨
Replying to @SafeJunctionHQ
5/6 SJ addresses these issues, allowing devs to: ✅ Write code in Rust once and execute it on any proving environment ✅ Switch easily between proving backends (zkVMs, teeVMs) ✅ Efficiently verify proofs via the integrated proof aggregators How? 👉 safejunction.io/key-componen…
2
1
4
293
Making "proving" easier and more accessible to any developer 🚀 S/O to the team of @SafeJunctionHQ for the launch of their trustless database of proofs, a core component in accelerating the ubiquity of proofs 🍾 Proud partners and ready to execute on this vision 😎 #teeVM
📌 Introducing SafeJunction: A trustless database aiming to make proofs simpler to use, yet safer and more accessible. 🥁 Early access: safejunction.io/early-access
6
160
Couldn't agree more here & it's the exact reason why we're building a TEE-VM. Devs should just choose where / how many proofs to generate for the same Rust program. No complex setup headaches, one abstraction layer, & cheap verification. Period. #teeVM #zkVM
- the TEE vs ZK discussion is pointless - they are complementary technologies - in the end is up to each developer and protocol to choose what's the best tech for their needs we need to offer better infra that can let them build with both of them and be able to move freely from one to the other (when possible)
4
291
Giving tools to devs for us means abstracting the complexities of managing a TEE, encalves, keys etc... by allowing the same Rust program running on SP1/Risc0, to run on a TEE in our teeVM. Generating proofs is commoditizing -> zkVMs and teeVMs are in the same stack. #teeVM
This is why @alignedlayer verifies ZK proofs and will attest TEEs. Our job is to provide the developers with different tools for them to chose what’s best in their own particular case. The usecases are different. They are not real competitors. Whenever you can always use ZK. TEEs enable other options. Proving software will and is getting commoditized. Verification and attestation are the only things that have network effects. Most proving companies will try to move to verification.
2
127
❤️ Last day at #ethCC and we can say that: - side events are the real event - zk has 1000x the ambition & you can feel it - building for/with other protocols is now more important than ever - blessed to be living these times & contributing with our pieces to the puzzle #teeVM
1
6
234