Beyond the PDF: Building the Data Layer for On-Chain Trust

Transcript

Okay. Uh, so we're going to get started as people walk in. Hey, I'm Torv, chief product officer at the Stella Development Foundation. You've made it to uh the last finest lightning talk session of uh DeFi Security Summit. So give yourself a round of applause. [applause] Good job. Uh we're going to start with Belle from Trust Block who's going to tell us about uh how to overcome issues in PDFs. [applause] Thank you, Tor. Hi everyone.

Um, so let's jump right into it. Uh, let's talk quickly about the balancer hack. Uh, tragedy of course for the team and the users. Uh, but I want to bring your attention to an image that's been shared widely on crypto Twitter. uh right after the attack, a screenshot of Balancer's documentation, probably listing over 10 audits by some of the best firms we know. Um and the immediate reaction of the public was uh brutal to say the least. Uh we hear uh audits are useless. Even 10 audits cannot save you.

And as security professionals, we know that's the wrong conclusion. Uh but we have to admit something painful. The public is right to be confused. Uh but what we have here is not an audit crisis. It's a data transparency crisis. Uh that static list of audits basically PDFs in a GitHub repo failed to answer the most basic questions users need to know. Was the specific component that got hacked, the composable stable pool, actually covered by all 10 audits? No, it was covered by only two. Um, when were those audits

done? Uh, was the code deployed on chain the exact same code that was audited? And maybe the most critical of all, uh, standardization. Uh, was the specific issue actually caught? How was it classified? etc. So a long list of PDFs uh gave users a false sense of security because the context and the standards were completely missing. And we cannot let our industry's critical work die in a PDF. We need to build a live verifiable and continuous data layer. And that's trust block. We work with the most reputable audit

firms. over 70 of them are uh already using trust block to liberate this critical uh data from the PTF and put it where users need it most. We do this by enforcing two fundamental standards. Uh every audit is immutable linked to a specific commit hash and or verified uh onchain address. And second, auditors can post can track post audit um events like uh upgrades instantly updating a client's security status ecosystemwide.

Uh and this new model unlocks two powerful things for everyone in this room. Uh as an auditor, you protect your reputation. When a project is exploited on a different commit, you can prove that wasn't your fault. uh users can access your unbiased history of work uh metrics and uh profile and second it gives your work massive distribution. Uh we put verified data where uh users make decisions. Trust block is already live on some major platforms like etherscan and block scout making uh audit data accessible to u millions of users.

um DeFi protocols, researchers, AI agents, wallets, you name it, can all leverage trust block to programmatically check asset risk. Uh if a connected protocol is flagged unsafe, uh integrations pause instantly, preventing contagion. So trust block turns uh auditor's work from a static stamp into composable onchain assets. Uh this is the foundation uh for a true reputation system. This is just the beginning. We are collaborating with leading security firms to establish a council governed uh standard for

security data. moving from reputation based on marketing budgets and towards reputation uh based on verifiable quality, transparency and consistency. So stop letting your critical work end with a PDF and let's make the space safer for everyone. Thank you. >> Thank you. Thank you so much. Um, our next uh session description is probably one of the best ones. Uh, I'll read this. Saying top auditors just read the code is like saying Michael Phelps just swims.