Summary: DeFi teams are really racing ahead, sometimes leaving their governance processes in the dust! All of this can create some real headaches, like missing quorums, dealing with cross-chain fragmentation, and facing proposal attacks--each of which can seriously impact your investment returns. Let’s dive into how we can replace those delicate voting systems with robust, high-quality on-chain governance. This switch could really help us save on gas fees, reduce potential vulnerabilities, and make the process of handling proposals way more efficient.

7Block Labs on On-Chain Governance Advances

ICP: DeFi Protocols and DAO Treasury Teams

If you’re diving into DeFi protocols and handling DAO treasury teams, there are definitely a few important things to keep in mind. Alright, let’s dive into the essentials! Here’s a quick rundown for you:

• Gas Optimization: This one’s all about cutting down those annoying transaction fees. Trust me, every little bit helps! Getting the most out of your gas can really help you save some cash in the long run.
• Delegation: It's super important to hand over decisions to the right people who can really take charge. Handing off tasks can really make things run more smoothly.
• MEV-aware Execution: So, being aware of Miner Extractable Value (MEV) is pretty important because it helps make sure that transactions are handled in a fair and efficient way. Being aware of this aspect really makes a difference!
• Cross-Chain Governance: It's getting really important to figure out how to manage governance across different blockchains. It's really about making choices that take into account the bigger picture.
• Private Voting (ZK): Leveraging zero-knowledge proofs for private voting is a savvy approach! This method lets votes remain private but still makes sure everything is transparent in how it all works.
• Time-to-execute: Time is everything, right? The quicker we can get transactions done, the better! Cutting down execution time not only makes things run smoother but also opens up a whole world of opportunities.
• Quorum Attainment: It’s super important to gather enough votes for any decisions to go through. Getting a solid grasp on quorum and working towards it can really determine the success or failure of your initiatives.

Just a friendly reminder: staying on top of these factors can really boost how well DeFi protocols and DAO treasury operations work!

---

The governance stack that “worked last year” is holding back your roadmap

So, you're still using Snapshot for those off-chain signals tied to a multisig that needs some human touch, huh? Fingers crossed that those crucial upgrades come through right on schedule! But if one signer decides to take a vacation or misreads something in Discord, it can really mess things up. That can lead to missed parameter changes and cause delays that stretch on for a week.

So, you're moving a lot of stuff to L2s, but the governance part is still kind of stuck on L1. When it comes to specific proposals about things like fees, oracles, or emissions, they really seem to hit a wall. Plus, trying to execute things across chains can feel like a real hassle and often ends up being pretty messy and full of mistakes.

Delegation seems pretty stagnant right now. The same popular delegates keep racking up votes, while the experts on certain issues can’t really jump in to correct any misuse of their votes without causing some serious social drama. It's a bit of a mess! So, OpenZeppelin just rolled out their latest Governor, and it comes with this cool delegate override perk thanks to VotesExtended. But honestly, a lot of protocols still haven’t found the time to add it in yet. (openzeppelin.com).

Hey there! Just a heads up--your voting deadlines seem to be a bit out of whack. It looks like your token made a switch to timestamp-based voting (ERC-6372/5805), but those dashboards are still showing block numbers. This has caught a few teams by surprise right in the middle of voting! (docs.openzeppelin.com).

Hey, I noticed that some of the security-sensitive actions are pretty exposed and could easily be swayed by bribes. You've mentioned the idea of “private voting,” but it seems like you haven't really tried implementing ZK-based solutions like MACI v2 yet. Also, have you had a chance to dive into that private delegation research (like Kite)? It could be worth exploring! (maci.pse.dev).

You know, elections for your guardians and security councils can get really tricky sometimes. Just look at what Arbitrum is doing with their elections! They’ve got this interesting system where your voting power actually decays over a 21-day period. It’s a pretty unique approach, for sure. If your delegates miss the deadline to vote, their influence kind of just vanishes. (forum.arbitrum.foundation).

Cross-chain control is definitely something that's constantly evolving. Take Ronin, for example; they rolled out CCIP after placing a Request for Proposal (RFP). Then there’s Aragon OSx, which has adopted a LayerZero/zkSync approach. With these developments, it’s crucial to keep in mind that your vendor options now involve some significant protocol-level risks and costs.
(chainlinktoday.com).

---

Every month you postpone modernization, you compound risk and cost

• Missed deadlines = missed revenue: If emissions, listing fees, oracles, and circuit breakers drag on for more than two governance cycles, it can seriously impact liquidity and the Total Value Locked (TVL) compounding.
• Tokenholder fatigue: When tools lag behind updates like ERC-6372 and the processes take forever, you can bet that participation will start to fade. Sometimes quorums just don’t come together, and that can really dent reputations. Check it out here.
• Governance capture optics: When there aren't any options for delegate overrides or private delegation, it’s usually the same big players and public groups that call the shots. This could really just turn your “community process” into an airdrop farm, where people are only there for the free stuff and not much else. Check out all the details right here. You’re going to find some really interesting stuff!
• Emergency response delay: If your security council or guardian isn’t consistently tested with on-chain rules, they might not hold up well when a real emergency strikes. Also, the way election mechanics work--like that decay thing--can really hit hard if you delay getting your act together. If you're looking for more details, you can check it out here.
• Cross-chain ops tax: Feeling adventurous with those custom bridges for transactions? Just a heads up - they can come with some risks! You know, there are some independent risk networks out there, like CCIP’s own risk management system, and they even have those audited OSx modules. But if you end up dealing with delays in procurement, it really puts you in a tough spot because you might have to cover all the costs for full integration and monitoring yourself. Learn more here.
• Privacy debt: Using public ballots might make it easier for people to buy votes or take revenge on others for how they voted. You’ve got solutions like MACI v2 and those Semaphore-inspired systems that have actually been put to the test in some pretty big grants and hackathons. They’ve shown their stuff on a larger scale, which is pretty cool! Your competitors are already diving into these new features, and it looks like your voters are beginning to expect them too. Take a look at what you can do here!

---

7Block’s “Governance-in-Production” methodology

We think of governance more like a product that’s constantly being refined, rather than just a boring ritual we go through in meetings. Get ready for some real action! You can expect actual shipped code, solid service level agreements (SLAs), and clear-go-to-market (GTM) metrics--way more than just a bunch of whitepapers.

1) Governance Baseline and Threat Model (2-3 weeks)

In this phase, we’re going to review our contracts, assets, and voting processes on various chains. It’s all about making sure we have a clear picture of where we stand! We'll also dive into the boundaries of authority, covering things like timelocks, guardians, and multisignatures. On top of that, we’re going to really dive into those incentive surfaces. We'll be looking closely at stuff like quorum thresholds, proposal spam, and the chance of vote-buying.

• Make the switch to OpenZeppelin Governor 5. So, x has gotten an awesome upgrade! It now automatically detects timestamp clocks, all thanks to ERC-6372. Plus, it’s got support for tokens that are aware of ERC-5805. Pretty cool, right? This is going to make things way less confusing when it comes to using the tools! If you want to dive into the details, just hop over to this link: (docs.openzeppelin.com). Hey everyone! We’ve got something new to share: we're rolling out GovernorCountingOverridable and VotesExtended. These updates will let delegatees jump in and fix any votes that might be off track without stirring up any drama. On top of that, we're keeping things transparent by using event monitoring and public dashboards. This way, everyone can see what's going on! Check out the latest news at openzeppelin.com for all the details! You won't want to miss it! Hey there! You can actually tweak the quorum by setting it as a fraction of the total supply using GovernorVotesQuorumFraction. It might be a good idea to run some backtests to see how it would’ve played out with your historical tokenholder distribution. Check out all the info right here: (docs.openzeppelin.com). You’ll find everything you need!

2) Gas and UX Optimization for Voters (1-2 weeks, parallel)

Voting should definitely be worth more than what you put into it. It shouldn’t end up costing you more than the good stuff it brings.

Hey there! We’re excited to announce that we’re launching ERC‑4337, complete with paymaster-backed sponsored voting for key proposals. And if you’re a long-tail voter, no need to stress! We’ve got your back with meta-tx (ERC‑2771) as a backup option. Take a look at the info right here: openzeppelin.com. You won’t want to miss it! We're excited to share that we're rolling out batch vote signing and relay bundling! This means you won’t have to worry about those pesky high gas fees for every single voter. We're all about making your voting experience smoother and more affordable! We’re also cleverly using timestamp-based windows to steer clear of those annoying block boundary problems. You know, the ones that can really throw a wrench in things, like with ERC‑6372. If you want to dive deeper, just check out the details over at docs.openzeppelin.com. It’s got all the info you need! We're definitely noticing some good gas savings with the Governor stack! We’ve made some cool updates! We’ve improved how we handle storage for proposal states, introduced custom error messages, and moved structs out so they’re easier to manage. We're excited to share some reports with you that dive into the "gas per voter" and "gas per execution" metrics. This way, you can actually see the improvements we've made in action!

3) Private and Sybil-Resistant Voting Tracks (2-4 weeks)

Sometimes, it's just better to keep certain decisions to ourselves.

Let’s get MACI v2 set up so we can enjoy private, receipt-free voting. This version has on-chain verification to keep things secure, while the tallying happens off-chain for a smoother process. Just a heads up, make sure this lines up with your disclosure policy! It might be a good idea to think about sharing those final tallies along with the ZK proofs, while keeping the ballots confidential. Check it out here. Give private delegation a shot with those Kite-style setups whenever you get the chance! Let’s take a “caucus followed by public approval” approach when rolling this out. This way, we can keep an eye on the risks that pop up with new cryptography in a real-world setting. If you’re interested in digging a bit deeper, you can check out the details right here. Happy reading!

• Use Semaphore-based signaling to quickly gather opinions with straw polls whenever you need a speedy and secure way to get feedback. It’s a great way to make sure everyone’s voice is heard without the hassle!

4) Off-chain Signaling, On-chain Execution (1-2 weeks)

Hey there! If you're diving into Snapshot, just remember to handle it with care--safety comes first!

Alright, let’s get the Zodiac Reality Module, which you might know as SafeSnap, up and going! This way, we can run Snapshot results through the Reality.eth oracle, complete with a challenge period. Let's make it happen! This makes sure that there are no hold-ups with signers, all while keeping those fraud-proof windows secure and in place. Check it out here. Feel free to tweak the challenge and timeout settings based on your treasury risk and how you plan to time your moves in the market. We're diving into the “time-to-cash” for stuff like grants, buybacks, and emissions.

5) Cross‑chain Governance Hub-and-Spokes (3-5 weeks)

Let's focus on using L1 as our primary reference, while L2s smoothly complement it.

Check out the different cross-chain executors such as CCIP, LayerZero, and Wormhole. It’s a good idea to see how each one measures up to your particular threat model. This way, you can figure out which one fits your needs best! For example, the validators at Ronin took a good hard look at things and chose to go with CCIP after they went through a thorough request for proposal (RFP) process that really honed in on risk isolation. That's the kind of procurement standard we believe you should really shoot for! (chainlinktoday.com). Hey, if you're looking for something else, you might want to take a look at the multichain module from Aragon OSx. It's pretty cool because it uses LayerZero messaging along with zkSync, so you can manage DAO permissions across different EVMs. Definitely worth checking out! We'll also check in on the audit status and see if there are any remaining risks hanging around. (prnewswire.com). Hey, make sure you normalize your network and account identifiers with those CAIP utilities that came along with OpenZeppelin 5. You don't want to skip that step! 2. This is a fantastic way to help reduce those pesky chain-id logic problems! (openzeppelin.com).

6) Guardian / Security Council Operations (2-3 weeks)

Honestly, it’s a smart move to get some practice in with those emergency levers before the moment actually hits when you need to use them.

Alright, let's make sure we’ve got the election mechanics all squared away. We should set up a decaying vote weight and don’t forget to include those KYC and eligibility checks whenever your constitution calls for it. It’d be a good idea to take a look at what’s going on with Arbitrum’s cycles and Optimism’s bicameral design for some inspiration.
(forum.arbitrum.foundation). Alright, so let’s dive into those drill runbooks! We need to focus on the “freeze-vote-thaw” processes, figure out some ways to get around those timelocks that are locked by council thresholds, and make sure we have straightforward conflict-of-interest attestations in place. Let’s make it easy to understand and follow!

7) Monitoring, Forensics, and MEV-awareness (continuous)

When you dive into proposal execution, keep in mind it’s really just another transaction. That means there’s always a chance of facing some ordering risk.

• When it makes sense, go ahead and route through private order flow. Just be sure to watch out for any failed or censored execution transactions. If you spot any, don’t hesitate to resubmit them using fee escalators to get things moving again. We analyze data outside of the blockchain to keep an eye on how voter behavior shifts after some not-so-great events. Recent studies indicate that there's been a noticeable shift toward private routing after certain exploits. This insight is super valuable for our post-mortem discussions, and it really helps us enhance the user experience. (arxiv.org).

When needed, we also bring in an independent review using our security audit services. This way, we can ensure everything aligns perfectly with your procurement process.

• Build: Take a look at our smart contract development for governance and don't miss our awesome custom blockchain development services too! We've got you covered on all fronts.
• Integrate: Don't worry, we've got your back! Check out our blockchain integration services and our super cool cross-chain solutions. We've made sure to make things seamless for you!
• Transform DeFi Flows into Products: Check out our awesome DeFi development services and take a look at what we’ve got for dApp development. We’re here to help you bring your ideas to life!

---

Implementation details you can ship this quarter

1. A governor that includes a delegate override feature and a timestamp clock. We're all about connecting the OZ 5! We’ve designed the x modules so that delegates can effortlessly correct any miscasts. Plus, everything stays transparent and won’t break the bank on gas fees.

pragma solidity ^0.8.24;
import {Governor} from "@openzeppelin/contracts/governance/Governor.sol";
import {GovernorCountingOverridable} from "@openzeppelin/contracts/governance/extensions/GovernorCountingOverridable.sol";
import {GovernorVotes} from "@openzeppelin/contracts/governance/extensions/GovernorVotes.sol";
import {GovernorVotesQuorumFraction} from "@openzeppelin/contracts/governance/extensions/GovernorVotesQuorumFraction.sol";

contract ProtocolGovernor is
    Governor,
    GovernorCountingOverridable,
    GovernorVotes,
    GovernorVotesQuorumFraction
{
    constructor(IVotes token)
        Governor("ProtocolGovernor")
        GovernorVotes(token)
        GovernorVotesQuorumFraction(8) // start at 8%, backtest and adjust
    {}

    // set timestamp-aware windows per ERC-6372
    function votingDelay() public pure override returns (uint256) { return 2 hours; }
    function votingPeriod() public pure override returns (uint256) { return 5 days; }

    // standard overrides
    function quorum(uint256 timepoint) public view override(Governor, GovernorVotesQuorumFraction) returns (uint256) {
        return super.quorum(timepoint);
    }
}

This setup helps your governor automatically figure out if the token is using block numbers or timestamps. Pretty neat, right? On top of that, it lets you override delegates. We also include monitoring hooks that send out alerts anytime a delegate override changes the tally. This way, your team can jump on it immediately! (docs.openzeppelin.com).

Snapshot → Safe Execution Without Signers Blocking

Go ahead and roll out the Zodiac Reality Module, and don't forget to set up a challenge window that’s perfectly timed. It’s also a great idea to have a runbook handy for handling any disputes that come up.

• Once the oracle finishes everything up, anyone can jump in and get things rolling. That means you won't have to stress about whether the multisig signers are available or not. If you're aiming for those bigger payouts, we've got a cool "dual-track" system in place. It’s called Snapshot+Reality for grants, and then there’s the Governor for fine-tuning the parameters. And the best part? You can do it all with the same Safe! Take a look at this! You can check it out here: (zodiac.wiki).

3) Private Voting Lane for Sensitive Proposals

If you're dealing with proposals that might come with some backlash or even a hint of bribery--like those for elections, pay, or listings--it's worth checking out MACI v2. Give it a look! It's a really great choice if you want to keep things private and safe.

Alright, so here’s the scoop: we've got these super secure encrypted ballots, and our tally is verified with zero-knowledge proofs right on the blockchain. Pretty cool, right? And when it comes to the final results, everything's crystal clear. Plus, our coordinators can’t just do their own thing; they're held accountable through attestations. It’s all about keeping the process fair and transparent! We customize circuits to fit your specific scale, whether it’s a handful of voters or a whole lot of options. Our goal is to speed up proof generation and perfectly time those reveal windows so that crucial decisions wrap up exactly when you want them to. For more info, just head over to maci.pse.dev. You'll find all the details you need there!

4) Cross-chain execution you can audit and insure

Pick the best transportation option for your needs, and don't forget to spot any potential risks that could come up along the way. Make sure to keep an eye on those and handle them properly!

You’ve got a couple of great options for managing risks. One is CCIP, which is all about handling risk through token or control messages. Imagine it like having a robust risk network with solid operations backing you up.

Alternatively, there’s LayerZero. It’s a pretty straightforward choice that offers lightweight messaging and the flexibility to pick your own trust levels. Whatever path you go down, you’re covered! Aragon OSx has this awesome setup that combines LayerZero messaging with a Layer 2 voting platform, kind of like what zkSync does. It's pretty neat how they blend these technologies! We definitely take the time to sort out SLAs and on-call escalation when you're setting up with your vendor. It’s super important to get that right! (chainlinktoday.com).

5) Gas Optimization Checklist (DeFi-Grade)

We provide reliable metrics in a pre/post report.

We've managed to put together a pretty packed proposal state and some checkpoints, too. Plus, we threw in some custom error messages and made the revert strings shorter. We're taking an easy approach to how we write vote receipts--basically, we're going with lazy storage. So when it's switched on, for any “support=abstain” situations, we'll stick to just logging events. We're making the most of calldata whenever possible, avoiding those pointless zero-initializations, and using unchecked math for loop counters that remain steady. Hey, just a heads-up! You can look forward to some sponsored voting coming your way via the 4337 paymaster for those really important proposals. And don’t worry about the smaller ones either; there will be fallback meta-tx relayers to have their backs. (openzeppelin.com).

---

Best emerging practices we recommend adopting in 2026 planning

• It’s time to revamp your dashboards and start using timestamp-based voting across the board! If you make it compatible with ERC-6372/5805, you'll clear up any deadline confusion and stay updated with the latest tools. Hey, just a quick reminder to throw in a migration flag in your analytics and communications! You can check out the details here. Don't miss it!
• Make sure to use CAIP utilities to standardize those cross-chain identifiers! This is pretty new in OZ 5, so it’s a good time to dive in. This way, you won't have to worry about “chainId drift,” and you can keep your allowlists nice and secure as you explore new L2s and L3s. (openzeppelin.com).

Make sure to include those decaying vote windows in your election user experience, not just in the contracts. It’s all about creating a better experience for everyone involved! Hey there! So, I’ve noticed that in Arbitrum's latest cycles, those who vote late really end up losing their influence. Just a heads up--it's super important to ensure your UI, alerts, and calendars are set up to reflect this reality. It can make a big difference! (forum.arbitrum.foundation).

• Think of privacy as a must-have, not just an afterthought. It’s super important! Thanks to Ethereum's PSE initiatives and the new privacy cluster from the Ethereum Foundation, private voting is starting to feel like a must-have rather than just a nice little extra. Alright, let’s get started on planning that MACI pilot for this quarter! (blog.ethereum.org).
• Make sure to keep your off-chain signaling and on-chain authority organized and distinct. If you’re using Snapshot, go ahead and make it binding with Reality.eth, or just make those decisions on-chain. Don’t let it be one of those situations where something passed Snapshot but then gets stuck in the multisig limbo! ” (zodiac.wiki).

---

GTM metrics we instrument for your pilot and beyond

We're not here to just say, "trust the process" and leave it at that. "Instead, we like to share our dashboards and acceptance thresholds in the same way that growth teams share their funnel metrics."

• Proposal Throughput: So, this basically measures how many proposals were executed compared to how many actually got the green light. We’ll break it down by venue, looking at both Governor and Snapshot+Reality. We’re aiming to reach at least 95% within a month after the upgrade. Let’s make it happen!
• Quorum Attainment Rate: Here, we’re checking out the percentage of proposals that successfully reach quorum on their first attempt. Now that we’ve launched the sponsor/relayer, we're shooting for a nice 20-30% increase over last quarter. Fingers crossed we hit that mark!
• Time-to-Execute: This looks at the average time it takes for a proposal to go from being created to actually being executed, broken down by category. We're really looking forward to seeing a drop of 20-50% during this transition as we move grants to Snapshot+Reality. Plus, we’re planning to change the parameters so they're based on timestamps in the Governor.
  If you want to know more about this, feel free to check it out here.
• Delegate Correction Activity: In this section, we're keeping an eye on how many times the Governor has overridden events. This helps us spot alignment issues and catch any big miscasts before they get out of hand. Want to dive deeper? Check it out here for all the details!
• Cross-Chain Execution Reliability: We'll be looking at how well things are working by checking out the success rate and average confirmation time for different bridges and messengers. We’ll be using the evaluation criteria from Ronin’s CCIP RFP as the basis for our procurement scoring. If you want to dive deeper into this topic, you can check out more details here.
• Privacy Adoption: We're keeping an eye on how participation varies between MACI proposals and public votes. For our initial targets, we'll dive into insights from a bunch of recent large-scale MACI events, such as hackathons and grant rounds. Our goal is to figure out how we can adapt this for your voter scale. Check out more here.
• Keeping an Eye on MEV-Resilience: So, we're going to take a closer look at those execution retries that didn’t go through and see how many private routes pop up after the upgrade. We’ll compare this with what we've seen lately--like how users seem to be moving towards private channels after an attack. If you want to explore this topic a bit more, you can check it out here. It's definitely worth a look!

We’ve crafted all our metrics to really fit what procurement is looking for. Just picture SLOs in your statement of work and documents that can breeze through those vendor security checks! We can either connect straight to your existing data setup or provide you with a lightweight warehouse and some cool dashboards to go along with it. Whatever works best for you!

---

Procurement and delivery model

We're starting off with a pilot project that will run for about 4 to 8 weeks. We've got some clear acceptance criteria set up ahead of time, just like we talked about earlier.

• When it comes to security sign-off, we’ve got all our bases covered. We've handled change control for roles, timelocks, and the emergency council. Plus, we're getting an independent review through our security audit services, just to make sure everything's on point.
• When it comes to building and integrating, we’ve got your back! We’ll handle all the heavy lifting using Solidity and ZK. We're here to help you out with all things web3 development, blockchain development, and cross-chain solutions. No matter what you need, we’ve got the expertise to back you up! Next up, we'll link everything to your treasury and dApps using some sweet blockchain integration. You can check it out here!
• Finally, once we wrap up the pilot, we’ll start rolling out those cool extra features for your DeFi projects. You know, stuff like gauges, emissions control, and fee switches. We’ll be using our DeFi development services and our top-notch dApp development to make it all happen.

---

A pragmatic example rollout (6 weeks)

Week 1-2:

• Kick off the ProtocolGovernor, which involves setting up a timestamp clock, determining the quorum fraction, and adding any necessary overrides.
• If it’s needed, go ahead and switch the token over to ERC‑5805 and make sure to update the analytics too. (docs.openzeppelin.com). Let’s get the 4337 paymaster up and running so it can take care of sponsored votes for our most important proposals. (openzeppelin.com).

Week 2-3:

• We're excited to announce that we're launching Snapshot+Reality to connect our treasury and grants! Oh, and we’re launching a 72-hour challenge, which is super exciting! Plus, we’re also putting in place an emergency “pause” option that you can use through the council if needed. Take a look at it over at zodiac.wiki. You might find it interesting! Hey, just a quick reminder that we’ll be putting out the operator runbook and the security page soon too!

Week 3-4:

• Cross-chain executor proof of concept: We're diving into CCIP and LayerZero profiles, and we’ll even run a simulation of a fee switch on Layer 2. We're going to have a vendor-neutral bake-off that will be tailored to your specific threat model! Take a look over here: (chainlinktoday.com). You won't want to miss this!

Week 4-6:

Hey everyone! We're excited to get started with the MACI v2 pilot for a pretty important vote--think along the lines of elections or compensation. To make sure everything goes smoothly, we're going to do a dry run first to help everyone get comfortable. Let’s ease into it together! We’re planning to share a public tally and some proofs soon, and we’ll also throw in a few UX notes as we go. Stay tuned! Take a look at this: (maci.pse.dev). You'll find some cool stuff there! Alright, let's dive into those dashboards! We're also planning to launch the “first 30 days” governance scorecard so everyone can check it out.

By the end, you’ll have a strong governance baseline that’s all set for production, and you won’t have to stress about any leftover “research spikes.”

---

Hey there! If you want to make governance a real game-changer and get those numbers onto the blockchain, let’s kick things off with a pilot project!

References:

Hey, don't forget to take a look at the OpenZeppelin Governor info! You’ll want to check out the details about the ERC‑6372 and 5805 clock, as well as the quorum fraction and v5. It's all pretty interesting stuff! Check out the docs and release notes for the info on 2 override! (docs.openzeppelin.com).

• Curious about the Zodiac Reality Module (SafeSnap)? Check out the tutorials and docs we’ve got ready for you! (zodiac.wiki). If you're looking to dive into all things MACI v2, check out the docs and release notes--they’ve got everything you need! (maci.pse.dev). Hey, have you seen the latest updates on Optimism’s Season 8 bicameral governance? They’ve got some cool stuff happening! (optimism.io).
• Let’s dive into how the Arbitrum Security Council elections work! We'll cover everything from decay windows to the different phases involved. (forum.arbitrum.foundation). Hey there! If you’re interested in cross-chain governance procurement signals, you might want to check out Ronin’s CCIP selection and the Aragon OSx multichain module. They’ve got some cool stuff happening that’s worth a look! (chainlinktoday.com).
• Finally, don’t miss the Ethereum Foundation’s efforts to enhance privacy through their Privacy Solutions Effort (PSE) and their research on how users are adapting to MEV. It's all super interesting stuff for future planning! (blog.ethereum.org).