Good morning pNewtorkerzzz! 🔥
It’s our 5th monthly update AND the hottest of the year so far 🥵🥵
Temperatures have reached record highs in Milan, along with my budget for almond granita and watermelon ice cream 🍦
Wait a minute: are people even working in August?
We know some people might be enjoying their “margarita with salt on the rim”, but the only salt we can taste is that from our forehead’s sweat 🫡💦
Yessir, no baking hot Italian summer will ever stop pNetwork’s team from building the future of cross-chain interoperability!
And why should we?
White Knights have already committed almost $20k into the DAO Treasury!
A good boost of liquidity & a good boost to our devs 🥷 mood, prompting them into faster execution and more productive afternoons.
To all of you, aspiring White Knights, here is the sweet news: White Knight’s APR is around 65%!
Not a bad deal overall, considering that on top of buying PNT at a fixed price, you can receive protocol rewards in several currencies (TLOS, BTC, PNT, etc.). An example? Last epoch, White Knights who invested $2k, received $110 worth of TLOS.
For what better reason than, if not to help our team in the execution of the roadmap, from the spin-off of Proofcast to the implementation of pNetwork v4?
Speaking of which… 🪄✨
The roll-up of pNetwork v4 is well underway, and it is time for internal audits & testnet contracts to lead the pace (check our last Periodic Update).
To kick off with a bang 💥, we’re working with a partner to see the first official bridge of pNetowrk v4 be part of… opps, it’s still top secret 🤐
I will give you some hints:
-
cooler than Civilization, smarter than WOW
-
its market cap is higher than Bernie’s net worth
-
it’s the only activity where @Carbonaut beat the whole team 🤕
You guessed it? In case not, don’t worry because we will soon make the official announcement.
The pNetwork v4 will also have a completely new look 💃🏻💃🏻💃🏻💃🏻
Proofcast? e don cast!
Lots of news on Proofcast territory too.
We have just published the first of a series of articles, where we communicate the “why” and the “how” behind Proofcast. Don’t miss it!
Last month we announced the first universal TEE-VM 🚀. Today, I’m going to drill down a bit into its workings for the sake of clarity.
With the teeVM, our goal is to play a role in the “new economy of proofs” by pushing forward 3 key features:
-
abstraction → Developers don’t need to bother with TEE setup and knowledge of trusted hardware to generate attestation; we abstract these complexities for you.
-
portability → you don’t have to customize your code. You can run the same program you run on zkVMs and multiple trusted hardware.
-
security → by supporting multiple trusted hardware providers (Nitro, SGX, Strongbox), we make sure proof-generation is more diversified in its sources, and thus more reliable and fault-proof.
What does the TEE-VM look like today?
-
A machine on AWS with TEE configured and a public API that can be called.
-
A toolchain (like SP1) that allows you to compile the code and get a binary file as output that can be placed on a RISC-V 64-bit machine.
The user can upload the application on a normal AWS machine and communicate with a command (JSON RPC interface) to launch the teeVM. As it runs the user’s program, it returns data related to the teeVM, the attestation of the application, and other information about the teeVM, such as the number of CPUs, memory, etc…
This is cool, but we have work to do left. In particular:
-
refine I/O primitives;
-
create a unique certification attached to the teeVM - uncorrelated with the program running within it;
-
allow for arbitrary calls to exit the execution of the program
As we aim to simplify developers’ lives, we keep working on strategic partnerships to steer the development of our teeVM the closest possible to the needs of the end user ✨
The summer is slowly moving to its end, and we are more than ready for “la rentrée” 🚌
Happy to be part of this amazing journey and to bring you all along the way 🫡
Is there something you would like to read in our Monthly that hasn’t been included? Write me at @y4nnickdez4 on Telegram and I will make sure to include it in next month’s review!