This market will resolve to “Yes” if a smart contract/program, set of related smart contracts/programs, crypto project, crypto business, or crypto service suffers from a hack/exploit totalling $1,000,000 or more, at anytime between the initiation date of this market and exactly 7 days later. Otherwise this market will resolve to “No.” For the purposes of this market, the loss of funds must be verifiable onchain. Compromised private keys (leading to loss of funds) will count under a “hack” for the purposes of this market, as long as the loss is provably verifiable onchain. Oracle manipulation/misconfigurations leading to loss of funds count under a “hack.” The value exploited must total $1,000,000 or more in a single incident to qualify for a “Yes” outcome. The value of an exploit is measured by the realized loss incurred by users or the protocol(s) affected as a result of the incident. Unrealized losses by protocols or users do not count towards the measurable value of the exploit.

Market activity includes traded volume and minted collateral.

Quotes are in TYD; Yes and No pools are priced independently. 100% = 1 TYD.

Resolution source: • Onchain data • DefiLlama hacks dashboard

Earliest possible resolution: Oct 27, 2026, 5:04 AM UTC. This is not the event deadline or a trading cutoff.

Resolution history

1. CreatedOct 20, 2026, 5:22 AM UTC

Recent activity

1. No trade · 238.1 TYD at 17.4%Oct 21, 2026, 1:15 PM UTC
2. Yes trade · 11.29 TYD at 82.7%Oct 21, 2026, 1:15 PM UTC
3. No trade · 95.62 TYD at 17.2%Oct 21, 2026, 9:07 AM UTC
4. No trade · 62.62 TYD at 17.1%Oct 21, 2026, 7:54 AM UTC
5. No trade · 8.57 TYD at 17.1%Oct 21, 2026, 7:54 AM UTC