What does it really take to make Web3 trustworthy?

Last week’s episode of the @HeliosStaking podcast featured @RosuGrigore on verifiability, formal methods, and building provable systems for the future of decentralized infrastructure.

↓ Here’s what stood out:

From @NASA to blockchain infrastructure: @RosuGrigore began by applying formal methods to mission-critical systems at NASA. Today, those same tools are being applied to blockchains that demand provable correctness.

How Runtime Verification took shape: @RosuGrigore founded @rv_inc to bring formal methods to real-world systems. Initially rejected by both testing and formal methods conferences, the term “runtime verification” reframed the approach—blending runtime observation with correctness guarantees. It now defines an entire category of system assurance.

Why semantics matter: Without formal semantics, programming languages become moving targets. Pi Squared uses the K Framework and Matching Logic to define and reason about program behavior with mathematical precision.

Support from @IOHK_Charles and @VitalikButerin: IOHK funded early work on formalizing languages in K. Vitalik provided grants to verify Ethereum’s Casper protocol, Vyper, Uniswap, and the ETH2 deposit contract—some of the first formal verification efforts in the space.

Verifiability without ordering: Pi Squared introduces a decentralized settlement layer where claims—whether from rollups, AI agents, or exchanges—can be verified independently and in parallel. No global ordering required. Just proof.

“Without verifiability, it is not Web3.”

Correctness becomes portable.
Truth becomes programmable.