# Adoption of the SEAL Safe Harbor Agreement - Boosting Onchain Security

- Space: [QuickSwap](https://snapshot.box/s:quickvote.eth.md)
- Author: 0x7D084883107cb900a637Ce65B5CCFDE7859d0D3e
- State: Closed
- Voting type: Single choice
- Start: 2026-01-14 11:08 UTC
- End: 2026-01-16 10:30 UTC
- Votes: 13
- Discussion: https://www.reddit.com/r/QuickSwap/comments/1qarla8/governance_proposal_adoption_of_the_seal_safe/
- Open in Snapshot: https://snapshot.box/#/s:quickvote.eth/proposal/0xfa0848ba5803219ab8d20082f9b44e49644aede5ce0902c1f4644e28b2a4e6e3

## Results

- Yes - adopt agreement: 740,152.99 voting power, 100.0%
- No - do not adopt agreement: 0 voting power, 0.0%

## Proposal

Web3 hacks and exploits continue to pose a major threat and risk to dApps and protocols across the entire industry.

Just a few weeks ago in November 2025, an attacker drained $128M in user funds through identifying smart contract vulnerabilities. A few months earlier in July 2025, GMX was hit with a reentrancy attack because of a patch that introduced a new bug on the protocol. And the list goes on.

QuickSwap has never suffered from a major hack or exploit, continuing to prove that the dragon DEX is resilient and continues to keep security top of mind. But what if there was a way to drastically increase platform security, adding an additional layer where active/ongoing exploits could be stopped to protect user funds?

This proposal has been put forward for the community to decide if QuickSwap should adopt the SEAL (Security Alliance) Whitehat Safe Harbor Agreement (“Safe Harbor Agreement”), which would improve the security of the protocol’s onchain assets by allowing whitehats to intervene during active exploits to save protocol funds.

Read the entire blog for more: https://x.com/QuickswapDEX/status/2010662160607654030

---

To vote or create proposals from an AI assistant, connect the Snapshot MCP at https://mcp.snapshot.box

