DSS 2026 — Your Governance Proposal is Clean. Your Laptop Isn't. Elliot Friedman Source video: https://www.youtube.com/watch?v=S2r9ygZ33pA Automatic captions — not human-reviewed. Complete spoken-audio coverage is unverified. Source language tag: en (English). Source export SHA256: 41bbe5b9ecb2894e0de3ad2d6ec13cfc44ecfafa3eabaf0fe9d409081161092e [0:02] Hello everyone. I am Elliot Friedman, [0:05] the founder of Solidity Labs. And today, [0:09] I'll be talking about [0:13] operating in a new world where [0:15] your computer is probably going to get [0:17] compromised at some point and how you [0:19] keep your governance proposals [0:22] safe in that world. [0:25] Okay, there we go. [0:27] Okay, so the first thing is to assume [0:29] that your computer has been compromised. [0:32] We saw this with the recent Binance hack [0:35] where [0:36] an individual developer's laptop got [0:38] compromised and that was enough to [0:41] actually go and [0:43] steal funds. And so [0:46] yes, you will have malware on a machine [0:48] you trust and threat models today [0:51] absolutely have to include [0:53] this in their threat model. [0:57] So things are going a lot more local and [0:59] social with spear phishing [1:02] attacks. And so if you're running a DAO [1:05] or you have some sort of on-chain system [1:08] that you're trusting with significant [1:09] amounts of funds, you need to have a [1:11] system that [1:13] if a single honest node gets compromised [1:16] or if you only have one honest node [1:18] remaining, your funds can still be safe. [1:23] And so really what this boils down to is [1:26] becoming a harder target. So if you have [1:29] one laptop, one developer laptop that [1:31] can propose to a DAO and propose [1:34] actions, [1:35] it's going to be really easy for a [1:37] threat actor to [1:39] compromise that system. But if you have [1:41] you know [1:43] multiple laptops and multiple developers [1:45] or multiple tool chains to create your [1:49] proposals and craft them, it's going to [1:51] be a lot lot harder [1:53] for attackers. [1:55] And so here we have a call data [1:57] evaluation maturity framework which [2:01] how you can build a system that um even [2:05] if one part is compromised as you're [2:07] generating your call data, uh it's [2:09] unlikely for an attacker to be able to [2:11] get through. [2:12] And so, you know, if you only have the [2:15] bottom of this maturity, you only have [2:18] one laptop with one framework, you work [2:20] your way up, you build out a second uh [2:23] toolchain, and so that way you have [2:27] um [2:28] you know, if there's some sort of supply [2:29] chain attack in in the code that builds [2:32] your call data, you're able to catch [2:34] that issue. [2:36] Um and then rung two, you know, now you [2:39] have multiple reviewers and multiple [2:41] toolchains, so you're not just [2:43] generating the call data on your local [2:44] machine, you're also generating it on [2:47] another developer's machine with [2:48] different um toolchains for that. And [2:52] then, you know, if you want to continue [2:54] stacking and making this more and more [2:56] complicated for an attacker to [2:58] compromise this uh vector, uh you can [3:01] add, you know, additional reviewers, add [3:03] CI, etc. [3:06] And so this is what a typical, you know, [3:08] governance proposal uh will look like [3:10] from start to finish. You have it on [3:12] your local machine, you broadcast it, it [3:14] waits on chain, and then it executes. [3:17] Um and really not a lot happens while [3:19] it's on chain before execution. And [3:22] we've built out uh the Forge proposal [3:24] simulator, which is a open source [3:26] toolchain [3:27] which allows you to um combine your [3:30] deployment scripts, your governance uh [3:33] proposals into a single uh unit and then [3:36] test it um as well as monitor it [3:39] throughout the whole proposal lifecycle [3:41] when it goes on chain. And so then even [3:44] if you have a developer's machine that [3:47] is compromised, you'll be able to go and [3:49] check um what's on chain versus what you [3:52] actually are supposed to have for that [3:54] proposal. [3:56] And so this is what uh an ideal [3:59] governance proposal will look like. It [4:01] will have um it will go from end to end [4:04] on your local machine to on chain, but [4:07] the the difference here is that you'll [4:09] have, you know, a CI job that will [4:11] verify or you'll have local developers [4:13] that will [4:14] um [4:15] craft that same call data and check it [4:17] versus what is on chain and expected, [4:20] which makes it um [4:22] much much harder for an attacker to add [4:25] a back door. [4:27] And this is this was an experience I had [4:30] um on a previous project where [4:33] we had to transition from uh old [4:36] TypeScript tooling to um a Foundry [4:39] Solidity tooling. We actually kept two [4:41] different tool chains running at the [4:43] same time while we tested out um [4:47] you know, to make sure that [4:48] we had call data that did the same thing [4:51] on on both uh machines. [4:54] So looks like my time is up here. Um [4:57] thank you all and if you're interested [4:59] in uh diving more in, you can find more [5:03] um [5:04] on our website and we have a whole page [5:06] up for for this um [5:09] tool. Thank you.