Hello all, here to share a final update on the grant Tally received to create a dedicated user experience for Compound-specific proposals on Tally. The goal of the grant was to make Compound governance more accessible and transparent by improving how Compound’s protocol contracts and proposal types are displayed within Tally.
We’ve successfully completed 3 of the 4 milestones. These updates are already live on Tally and enhance both the UX and readability of Compound governance actions. Please note: After evaluating technical feasibility and prioritizing based on community needs, we’ve decided not to pursue Milestone 4. Below is a breakdown of what we delivered:
Milestone 1: Support for Compound Protocol Contracts on Ethereum
We integrated Compound-specific contracts—including Governor Bravo, Compound v2, and Comet—into Tally’s Proposal UI. This allows users to easily create and read proposals using these contracts, with improved clarity around the functions being called and assets being moved.
Milestone 2: Support for Cross-chain Compound Proposals
Compound is multichain, and governance reflects that. Tally now supports the creation and visualization of cross-chain Compound proposals within the UI. This makes it easier for users to follow governance actions across networks and understand cross-chain messaging flows.
Milestone 3: Decode Calldata of Ethereum Mainnet Proposals Made off Tally
We implemented calldata decoding for Ethereum Mainnet proposals created outside of Tally. Even if a proposal wasn’t drafted via Tally, users can now view a decoded summary of what the proposal does—improving transparency and safety for voters. It is live in use on this proposal: [Gauntlet] - Interest Rate Curve Recommendations (03/25).
Milestone 4: Decode Calldata of Cross-chain Proposals Made off Tally
After careful consideration of technical constraints and community priorities, we’ve opted not to move forward with Milestone 4. While calldata decoding for cross-chain proposals made off Tally would be valuable, implementation proved to be highly complex and difficult to generalize across bridge architectures. The biggest unknown—and ultimately the blocker—was understanding how to reliably retrieve the signatures for bridged action calldata, which varies across implementations and is often not standardized.
Rather than ship an unreliable or incomplete experience, we’ve opted to focus efforts on maintaining the improvements made in Milestones 1–3 and will revisit this functionality if community demand increases in the future. Of course, we will not be claiming the funds for this milestone.
Thank you to the Compound DAO for the opportunity to work on this grant! Tally remains committed to improving governance tooling for Compound DAO and beyond.