Pinned Tweet
Welcome, @tempo
Today, we're thrilled to share that Tempo is building with the @commonwarexyz Library, supporting our growth as a new core contributor, and accelerating our research and engineering with a strategic investment.
commonware.xyz/blogs/welcome…
commonware retweeted
Because we built on QMDB which is fundamentally a merkle log it’s trivial to arbitrary fork virtual verifiable disks while they are running.
I can nearly instantly spin one node off another scaling up to serve as much traffic as your application needs.
No waiting for cloning EBS volumes, no downtime, rapid auto scaling of stateful workload.
This is ideal for agentic systems where swarms need to rapidly startup from the same sandbox.
commonware retweeted
In TK verifiable state we solve this with external anchoring. Every flush produces a merkle root and a majority of the TEEs in a quorum must acknowledge the root before the kernel tells the filesystem a write has succeed.
This also allows for super fast cooperative handoff of virtual disks and failover in the event of a node dropping out.
Think of it like raft but inside a TEE over the merkle roots of every disk.
It’s also possible to externally anchor virtual disks in a blockchain or other noncustodial ledger.
commonware retweeted
When building verifiable state one thing you have to think about a lot is rollback attacks.
Each TEE has its own virtual disk, but if a TEE reboots how can it provably start up again while guaranteeing the host cannot rollback the state?
commonware retweeted
We achieve this by running a virtual userspace block device on top of a custom highly optimized interactive merkle proving protocol built on a fork of @commonwarexyz’s excellent QMDB library.
Every single read and write is verified inside of the TEE before the kernel sees it.
commonware retweeted
Turnkey variable state is a complete solution for non-custodial storage.
It’s built to allow any web2 database, agent sandboxes and anything you can think of to run within nitro enclave fully cryptographically attested.
Your normal linux software just sees the file system.
commonware retweeted
Why build your own merkle tree when you can just use sqlite or pg with the same cryptographic guarantees.
Looking for development partners for our alpha release now!
Historically, the TEE security boundary covered the processor and memory, leaving every application to build its own solution for persistent, encrypted, rollback-protected storage
Today that all changes with @turnkeyhq's Verifiable State
Verifiable State is OS managed and extends the TEE trust boundary to include a private, persistent file system; all protected from operator rollback
Like everything else in QuorumOS, long-lived encryption secrets and code upgrades are quorum managed - enabling trust-minimized applications
Read more in our blog post here turnkey.com/blog/tvc-verifia…
commonware retweeted
For high performance blockchains, indexing and querying data quickly becomes the bottleneck. It doesn’t matter if your chain runs at 1M TPS if your data can only be ingested at 100K TPS
Excited for this launch from @commonwarexyz! @exowarexyz is an important solution to this
At Frontiers this morning, we launched our first two @exowarexyz products: log + store
Stream and index a stupid amount of data in realtime (~20-40ms cross-AZ durability at 5M keys/sec) for cheap 💸
At Frontiers this morning, we launched our first two @exowarexyz products: log + store
Stream and index a stupid amount of data in realtime (~20-40ms cross-AZ durability at 5M keys/sec) for cheap 💸
commonware retweeted
Learn more about @exowarexyz and our (free) private alpha:
nitter.cf/_patrickogrady/status/…
At Frontiers this morning, we launched our first two @exowarexyz products: log + store
Stream and index a stupid amount of data in realtime (~20-40ms cross-AZ durability at 5M keys/sec) for cheap 💸
commonware retweeted
don't trust me bro (the @commonwarexyz story)
📍 @paradigm Frontiers
commonware retweeted
At Frontiers this morning, we launched our first two @exowarexyz products: log + store
Stream and index a stupid amount of data in realtime (~20-40ms cross-AZ durability at 5M keys/sec) for cheap 💸
commonware retweeted
i dont worry about PQ safety in Tempo - we are prepared on the consensus side w Pat and team’s work and on execution side configurable accounts enable us to do in place key rotations / disable the non PQ keys
Post-Quantum Simplex (ML-KEM + Falcon-512) now supported in the @commonwarexyz Library 🔐
* 50 c8g.large (2 vCPU/4GB RAM) in 13 regions
* 220ms blocks + 340ms finality
* Browser (still) verifies all certificates
Post-Quantum Simplex (ML-KEM + Falcon-512) now supported in the @commonwarexyz Library 🔐
* 50 c8g.large (2 vCPU/4GB RAM) in 13 regions
* 220ms blocks + 340ms finality
* Browser (still) verifies all certificates
Use the new @commonwarexyz curve25519 to verify ~16k signatures in 2.74ms (0.167µs/sig on 32 cores):
github.com/commonwarexyz/mon…
![[parallel, cryptography, cryptography/curve25519] Speed up curve25519 signing, verification, and...](https://pbs.twimg.com/card_img/2115167820879163393/E4avjfX-?format=jpg&name=800x419)
The @commonwarexyz Library would be much worse without the opinionated and nuanced feedback we've received from @LayerZero_Core and @tempo over the past few years.
Thanks for taking the time to pave the road for anyone building a fast and scalable blockchain with the CL 🛣️
We had it all in 1992.
By leveraging the gap between corruption and quorum sizes in consensus protocols (t=2f+1 vs n=3f+1), we construct a pairing-free BTE scheme with >5x faster decryption than the previous SOTA (Simple BTE):
commonware.xyz/blogs/1992
commonware retweeted
IBC & CosmWasm, meet @commonwarexyz
(CosmosSecp256k1 / 118 CT support, working through Cosmos IBC migration path now)
How Things Work #7: Jolt and The Return of Sumcheck
Today, we trace the once infeasible idea of verifiable compute from 1980s theory to Jolt, @a16zcrypto's sumcheck-based zkVM, with @SuccinctJT and @moodlezoup.
TL;DW can going post-quantum actually make a zkVM faster?
