DSS 2026 — Can security judgement be financialized without corrupting it? Don Josey Source video: https://www.youtube.com/watch?v=CcgXlJiCoLM Automatic captions — not human-reviewed. Complete spoken-audio coverage is unverified. Source language tag: en (English). Source export SHA256: 84098c983d11cdd501f32afc2fa76aa4561ad3fac76260e032c6e0852df8fb15 [0:00] Hey, I'm Dawn with Glosify and today I'm [0:03] here to talk about [0:04] what we built and specifically whether [0:07] security judgment could be financialized [0:09] without corrupting it. Um so [0:13] basically [0:14] uh at Glosify we built uh a protocol [0:17] which is a swarm that allows um it's a [0:21] it's a protocol that allows you to [0:22] coordinate economically a swarm of [0:24] agents that attack security challenges [0:27] basically. So what do I mean by that? [0:29] We're talking about attacking not [0:31] operational security um but code bases [0:35] and dependency graphs within kind of our [0:37] software ecosystem. Um and uh yeah I [0:41] mean uh modern software code bases are [0:43] built of these maps of you know [0:47] uh all these [0:49] dependencies where you know somewhere up [0:51] at the top of the stack if you have one [0:53] thing one failure it would propagate [0:55] downstream you know into a lot of [0:58] different services and our argument is [1:00] that structurally kind of we underfund [1:03] um paying for uh research in a lot of [1:06] these you know frameworks like for [1:07] example PHP 6 or whatever that just [1:09] failed you know um and looking out for [1:12] vulnerabilities that might uh surface [1:14] kind of in the long tail. So what can we [1:17] do to address that? That's the question. [1:19] And um so we're uh [1:23] basically trying to align incentives [1:24] this is especially relevant for DeFi um [1:27] which a lot of these apps you know rely [1:29] on uh these dependency graphs. So we [1:34] built this protocol and the idea is [1:36] coordinate continuous swarms that are [1:39] looking at code bases and building a [1:41] graph of security intelligence. So this [1:44] is continuous as opposed to kind of like [1:46] the one time uh you know bug bounty or [1:50] audit you know paradigms which are super [1:52] important but this is intended to kind [1:54] of complement those tasks basically and [1:57] bring humans and agents to the of [1:59] attacking, you know, security. [2:02] Um, and how do we do that specifically? [2:04] It's a ranking process. I describe it as [2:06] like a cousin of a prediction market [2:08] basically, where we take in data that is [2:10] like an oracle on failures of open [2:13] source code that surface up. And then [2:16] you in the ecosystem as a researcher [2:19] would have an account and do staking and [2:22] get, you know, rewards if you do a good [2:24] job of predicting these failures [2:26] basically. So [2:28] um and uh yeah. And your kind of key [2:32] account unit in the system is a vault [2:34] and EIP 4626 style vaults, which um as [2:40] uh for those not familiar, these allow [2:42] you to uh basically [2:45] have users who would back your work. Um, [2:48] so you can attract liquidity into this [2:50] vault uh as a researcher and kind of [2:52] attract attention if you do a good job [2:54] of doing the research. And then uh your [2:57] funds are staked in the vault in such a [2:59] way where your rewards payout based on [3:02] your performance, you know, multiplied [3:04] by your staking. So if you do a good job [3:06] finding vulnerabilities, [3:08] uh that amplifies your reward payout [3:10] basically. And this creates like a [3:11] flywheel of intelligence is the idea [3:13] where researchers who do a good job [3:15] attract more capital and they get paid [3:17] more because, you know, [3:19] they are successfully finding [3:20] vulnerabilities. So um and um yeah. We [3:24] kind of smooth the rewards out uh so [3:26] they're not coming in kind of uh [3:29] in chunks. They basically like buffer [3:30] in, which kind of is supposed to fight [3:33] like basically people gaming the system [3:35] and kind of just like jumping in ahead [3:37] of a reward. Also the system's based on [3:39] uh staking but not slashing with the [3:41] idea being that that creates a mechanism [3:44] where uh basically [3:46] people feel more comfortable backing [3:48] these pools because it's not going to be [3:49] like some adversarial scam where the [3:51] pool runner is going to attack them or [3:53] something. Um, we also built a basically [3:55] a cryptographic bounty for vulnerability [3:58] disclosure, which you can attach to your [4:00] vault basically a signature of a [4:02] vulnerability, which goes against the [4:04] timestamp, and later, when the [4:05] vulnerability's found, be awarded [4:07] retroactively for the payout. Um, [4:11] so the whole idea here is to kind of [4:13] harness collaborative and cooperative [4:15] energies in one place for vulnerability [4:17] disclosure in a way that's dynamic, [4:19] continuous, where people can get paid [4:21] for work and build agents and, you know, [4:23] basically find security work through [4:26] attention and reputation they get in the [4:27] system. There's a token, you know, [4:29] that's locked in the contract, so [4:30] everyone is collaborating and locking [4:32] that up to secure the network while also [4:35] competing by finding kind of different [4:37] layers to build this data stream. Um, [4:41] and yeah, once the data is produced, uh, [4:44] you know, we can build future mechanisms [4:47] for insurance and basically route this [4:50] data back in like a feedback loop to [4:52] users within a software supply chain so [4:54] they can secure their own systems. So [4:57] this is what we're doing. We've built [4:58] this. This is live on Sepolia now. Check [5:00] the app out. Um, break it, please, uh, [5:04] and um, sign up for our mailing list and [5:07] hear more. We're trying to launch in the [5:09] next few months and yeah, get our audit [5:11] launch, everything done. And yeah, so [5:13] that's it. Glossify. Thanks.