Summary: Seatbelt is best understood as CI for live DAO proposals. Rather than changing how token voting works, it changes what delegates can know before they vote by simulating proposal execution, enumerating touched addresses, checking contract verification status, and producing proposal reports on a recurring cadence. The reusable governance insight is that practical authority can migrate toward the teams and tooling layers that define which proposal checks are run, how much state-change detail is surfaced, and which risks are considered legible enough for delegates to act on.
What it does:
Monitors live governance proposals for supported DAOs and simulates proposal execution on a recurring schedule
Produces markdown reports that summarize proposal effects before tokenholders or delegates cast votes
Lists referenced addresses touched by proposal execution, checks whether referenced contracts are verified, and records state changes and emitted events
Supports Compound Governor Bravo and OpenZeppelin-style governors, making it a reusable verification layer rather than a Uniswap-only internal script
Integrates optional static-analysis and simulation tooling flows, including Slither-oriented checks and Tenderly-backed execution paths for local use
Key claims:
Uniswap Labs described Seatbelt as a test suite for governance proposals built with ScopeLift to generate reports on proposals prior to votes so communities have critical information for decision-making
The launch post says Seatbelt checks Ethereum for new proposals on a recurring schedule, runs checks on all active proposals, and publishes reports for public review
The repository README says the tools are meant to make on-chain governance safer by applying automated checks to live proposals for better informed voting
The README says reports can capture transaction reverts, state changes, and events from proposal execution, while intentionally omitting some execution-process noise to keep reports readable
The README also says current support covers Compound Governor Bravo and OpenZeppelin-style governors, which matters because Seatbelt is a portable governance-control primitive rather than a one-off Uniswap monitor
The deeper mechanism comparison is that Seatbelt operates before execution, unlike rollback systems that intervene after execution; it is a proposal-verification layer, not an emergency veto layer
Whitepaper: No canonical whitepaper or litepaper surfaced in this pass. The strongest primary materials were the Uniswap launch post and the public repository README; see ../whitepapers/seatbelt-primary-sources-2026-05-07.md.