Build Your Own DAO vs Using DAO Platforms: Pros and Cons

Who this is for

• If you're a decision-maker at a startup or a bigger company and you're getting into on-chain governance or looking to take charge of your treasury, this is for you!
• We're seeing a cool trend in the Web3 world where product teams are moving away from relying on multisig committees and are now letting token holders take the reins with governance.
• Our legal and operations teams are busy putting together governance processes that not only meet compliance standards but are also super easy to audit.

---

The decision in 30 seconds

If you're looking for top-notch security, unique voting features, the ability to execute across different chains, or if you just want to steer clear of vendor lock-in, then it's definitely worth considering the build route. It's a smart move, especially if you're familiar with tools like OpenZeppelin Governor, Timelock, Safe modules, and Defender/Forta automation. Feel free to take a look at it here. It’s got some really useful information!

If you want something that’s quick, easy to use, and works really well right from the start, you might want to check out some platforms like Tally MultiGov, Aragon OSx plugins, DAOhaus v3 “Baal,” and Snapshot + SafeSnap. They really deliver on speed and functionality! Make sure to keep an eye on vendor roadmaps and stay aware of the risk that some platforms might disappear. If you're looking for more details, you can check it out here.

---

What “build” and “buy” actually mean in 2025

• Build your own
• Smart-contract layer: Let's use OpenZeppelin Governor v4 or v5 and spice it up with some awesome extensions! Think Timelock, Prevent Late Quorum, and make sure it's compatible with Compound Bravo. Oh, and don’t forget to throw in those EIP-6372 clocks for good measure! Also, if you feel like it, you can add in some custom modules! Things like guardian veto, fractional counting, or even cross-chain execution are all options you can explore. Take a peek at the details right here. You’ll find all the info you need!
• Treasury layer: Go with Safe (it used to be called Gnosis Safe) and spice things up with Zodiac modules like Delay, Roles, Bridge, and Reality/SafeSnap. With this setup, you get way more control over things. You can fine-tune permissions, set time delays, execute off-chain votes, and even manage multiple chains all at once. It's pretty flexible! Dive into it here.
• Ops/Sec layer: When it comes to keeping an eye on things and automating tasks, you can’t go wrong with OpenZeppelin Defender. It’s got all the essentials like Monitors, Actions, and Relayers, and works great with Forta bots to give you that extra layer of security. If you want to dive deeper into it, you can check it out here.
• Use DAO platforms
• Tally: This is a really user-friendly, ready-to-go on-chain governance interface that makes it a breeze to delegate and cast your vote--plus, you won't have to worry about gas fees! On top of that, it comes packed with awesome features like partial delegation, elections for the security council, and MultiGov support across various chains. Pretty neat, right? If you’re looking for some extra resilience, definitely give their IPFS-hosted “Tally Zero” a look! ” (docs.tally.xyz).
• Aragon OSx: So, this one's pretty cool! It features a super flexible plugin framework that lets you do all sorts of things like token voting, multisig setups, address list voting, and you can even dive into gauges and dual governance. It's all about making governance easier and more versatile! It features a thoroughly reviewed core and a design that really puts permissions front and center. (aragon.org).
• DAOhaus (Moloch v3 / “Baal”): This cool platform lets you use shares and loot as ERC-20 tokens, which is pretty neat! You can easily manage your treasury using Safe, and when it comes to executing proposals, you’ve got plenty of options at your fingertips. Plus, with the handy “Shaman” extensions, automating membership and governance is a breeze. This really simplifies everything! Check it out at docs.daohaus.club.
• Snapshot + SafeSnap: This duo lets you vote off-chain, and then it gets executed on-chain through Reality.eth. Pretty neat, right? With optional shielded voting, you can steer clear of that herd mentality and all those last-minute shenanigans that come from big players swooping in and making waves. Plus, it totally supports strategies that work across different chains! You can check out all the details here.

---

Pros of building your own DAO stack

1. Maximum Design Control and Security Posture

• Build Just What You Need: Stick with the Governor and TimelockController, and don’t forget about PreventLateQuorum. Choose your storage and clock settings that work best for EIP‑6372--whether that's based on a block or a timestamp. Keep it simple and tailored to your needs! This lets you really refine your voting windows, quorum, and how you handle execution, all based on the risk model that works best for you. Check it out here.
• Add Veto and Circuit-Breaker Features: Consider including options like a "veto/circuit-breaker" or even some creative vote counting methods, such as splitting votes into fractions. You could also allow for adjustable quorum levels, which gives governance the flexibility to make decisions that suit the community's needs. We've been noticing this approach pop up in some of the newest L2 governance systems lately. Get the details here.

2. Governance across different platforms without being limited by them. You can handle contracts across various chains by tapping into OpenZeppelin’s cross-chain patterns or using Safe’s Zodiac Bridge Module. You can run votes on an affordable Layer 2 solution and then carry out those decisions using the mainnet treasuries. Take a look at this link: (docs.openzeppelin.com). You'll find some really helpful info there!

3. Vendor Independence and Longevity

Platform roadmaps can be pretty hard to anticipate. In 2023-2024, Aragon made the bold move to sever connections with their old models. They gradually phased out the previous front-ends--like Court, Govern, and Voice--so they could really focus on developing OSx. It was definitely a significant shift for them! This tech is really cool, but it definitely reminds us to keep reversibility in mind when we're designing stuff. Sticking with open standards can make it way easier to handle changes when they come up. (blockworks.co).

4. First-class ops automation

With Defender, you can easily streamline your proposal queue, tackle each step like a pro, keep your timelock roles in check, and manage incident response workflows effortlessly. Also, make sure to stay updated on the markets, multisigs, and governance status by using Forta/Defender Monitors. They’re super helpful for keeping track of everything! Companies like Compound are pretty open about sharing their strategies. Take a look at their insights right here: OpenZeppelin. It’s pretty interesting stuff!

5. Identity and Privacy Flex Options

Hey, have you thought about trying out shielded voting options like Shutter? It’s a great way to make privacy-conscious choices without any rush, letting you take your time and feel comfortable with your decisions. You might want to consider checking out “permanent shielded voting,” especially now that Snapshot is starting to use homomorphic encryption. It’s an exciting development! If you're curious to learn more about it, just hop over to this link: blog.shutter.network. It's got all the details you need!

Where This Shines

There are a few key areas where this really shines:

• Protocols with Treasuries over $50M: If you've got some serious cash to play with, this could really change the game for you.
• Multi-Chain Product Surfaces: This is great for projects that work across various chains.
• In Regulated Settings: If you're in a situation where everything needs to be super transparent and easy to verify--think things like timelocks and defined roles--this is really important.
• Long Governance Horizons: Perfect for those projects that are looking to stick around for the long run and really need solid governance in place.

---

Cons of building your own

• Bigger Initial Investment and Longer Launch Time: There's definitely a lot to think about in this situation. When you're diving into this project, keep in mind that you'll want to focus on a few key areas. Think about developing contracts, running audits, and paying attention to user interfaces and infrastructure. Don't forget about indexers, data pipelines, and those handy runbooks too! It’s all about pulling it together for a smooth experience. Getting everything up and running might take a bit more time because of this.
• DevSecOps Workload: You've got quite a bit on your plate! This includes stuff like patching, adjusting monitors, managing role rotations, overseeing key ceremonies, and getting those cross-chain adapters up and running. Wow, it’s definitely a lot to keep in balance!
• UX Debt: If your front-end design isn’t looking great, you could end up with fewer people participating in voting. To handle this, a lot of teams usually go for a governance client, like Tally or even whip up their own version based on Agora, regardless of whether they've created their own custom contracts. If you’re looking for more info, don’t forget to take a peek at the Tally docs. They’ve got everything you need!

---

Pros of using DAO platforms

1. Fast Production with a Sleek User Experience. Tally really simplifies the whole proposal drafting process. You can easily work with flexible executables, find delegates, and take advantage of gasless delegation and voting. Plus, there’s partial delegation and MultiGov for those cross-chain options. And the best part? You won’t have to deal with any custom work--it's all pretty straightforward! On top of that, with "Tally Zero," you can really enhance your resilience in case your primary front-end takes a hit and goes offline. Take a look at the details right here: (docs.tally.xyz).

2. Modular Governance Made Easy. With Aragon OSx plugins, you can easily manage multi-chain execution, set up budget styles like gauges, and tap into a cool dual governance system that combines councils and token voting. Plus, it’s all built on a secure core that goes through regular audits to keep everything in check! Check it out here!.

3. Familiar, Low-Friction Voting at Scale

So, Snapshot’s off-chain voting combined with SafeSnap’s on-chain execution is a clever way to keep those gas costs down. Plus, it still builds that all-important trust using Reality.eth. On top of that, it creates a space for shielded voting, which really helps to keep things fair by stopping that herd mentality and those sneaky last-minute changes from the big players. So, the platform just rolled out some new updates that really help with native multichain strategies. Take a look at this link: (docs.snapshot.box). You'll find all the info you need there!

4. Composable Membership and Exit Patterns

Hey there! So, I just wanted to share some exciting updates about DAOhaus v3, also known as Baal. They’ve rolled out some cool new features! Now, you can enjoy shares and loot as ERC-20 tokens, which is a nice upgrade. Plus, they’ve introduced Safe treasuries to help you manage your assets better. And if that wasn’t enough, there are also “Shaman” permissions for more control and flexibility. Lastly, the ability for arbitrary execution opens up some interesting possibilities. It's definitely worth checking out! With this setup, you can easily get started and then slowly build up your features over time. It's all about taking it step by step! Take a look at this link: docs.daohaus.club. You might find it really helpful!

Where This Shines

You'll definitely notice some great advantages in areas like treasuries under $50 million, consumer communities, grant programs, product councils, and teams that focus on user experience (UX), analytics, and making everything run smoothly with turn-key operations.

---

Cons of platforms (what to watch)

• Roadmap and Governance Risk: Vendors can decide to retire features or make significant changes whenever they feel like it, just like Aragon did with their 2023-2024 updates. It’s definitely a good idea to have those exit strategies and migration plans all set up and ready to roll. (blockworks.co).
• Off-chain Trust Assumptions: So, Snapshot really relies on oracles--big thanks to Reality.eth for that! They have this neat cooldown and bond process in place too. Make sure to get your arbitrators in place and sort out the bonds. It’s also a good idea to stay vigilant to ward off any pesky snipe-attacks or spam that could throw your trust levels off track. Keep an eye on everything! (docs.snapshot.box).
• Strategy/Rule Updates: Snapshot is saying goodbye to the old "multichain" wrapper and embracing a more straightforward native multichain approach. It’s a fresh start! Just a heads up, these platform-driven migrations are going to require some hands-on attention. You'll want to stay involved and keep an eye on things! (help.snapshot.box).

---

Practical architectures you can copy

A. Protocol governance with on‑chain execution (L1+L2)

• Contracts
• Make sure to utilize OpenZeppelin's Governor, Settings, Votes, and TimelockControl. And hey, don’t skip over PreventLateQuorum--it’s pretty important too! Just a heads-up: make sure you're using EIP-6372 clocks consistently when casting your votes with your tokens. (docs.openzeppelin.com). If you’re in the mood to mix things up a bit, why not think about throwing in some cool optional features? Stuff like fractional counting, guardian veto, and adjustable quorum can really spice things up. Plus, there are loads of audited examples out there from recent L2 governance that you can check out for inspiration! (blog.openzeppelin.com).
• Treasury Alright, so here’s the plan: first, you'll want to set up a Safe with a Zodiac Delay Modifier. This handy feature helps you manage cooldowns on transactions that are initiated by modules. Next up, add a Roles Modifier. This lets you get super specific about who’s allowed to do what, which is really useful for keeping things organized. And don’t forget to throw in a Bridge Module as well; it’s essential for managing your mainnet funds coming from L2. (github.com).
• Front-end and Ops If you’re looking for a way to manage proposals and delegation, definitely check out Tally. And if you’ve got to juggle things across different chains, MultiGov could be a solid option for you. Also, setting up gasless delegation can really help get more people involved! (docs.tally.xyz). Hey there! Make sure to use those Defender Monitors to track any changes in timelock roles, monitor proposal state transitions, and keep tabs on emergency actions. Plus, don’t forget about Defender Actions--they can automatically queue or execute proposals for you and even send updates to your Discord or Slack channels. It’s a great way to stay on top of everything! (docs.openzeppelin.com).
• Privacy and Integrity If you have votes that need to stay under wraps, go ahead and enable Snapshot shielded voting for your quick checks. Once you’ve got everything wrapped up, just finalize it on-chain through the Governor. And when the option pops up, definitely consider switching to permanent shielded voting! (blog.shutter.network).

Why This Works

It’s really about having those clear, on-chain guarantees that you can actually check yourself. Plus, with solid permissions and a few smart automation tricks, everything just flows effortlessly. Voters get to use an interface they're already familiar with, which is awesome! Plus, the best part is they can delegate without worrying about those pesky gas fees.

B. Community treasury and grants (fastest path)

• Voting and Execution If you're looking to get into some off-chain voting, definitely take a look at Snapshot. And for on-chain execution, SafeSnap by Reality.eth is a solid choice; it focuses on keeping trust to a minimum. So, there's a cooldown period of 24 hours, along with a bonding system. Hey, just a quick reminder to make sure you set up that arbitrator! (docs.snapshot.box).
• Risk Controls Hey there! Just a quick tip: if you want to manage cooldowns for your module executions, make sure to use the Safe + Delay Modifier. It’s super handy for keeping things on track! Plus, the Roles Modifier lets you set spending limits, which is great if you want to give operators a little freedom while keeping things in check. (github.com).
• Privacy and Fairness
• Hey, have you thought about turning on shielded voting? It could really help out! It really helps to reduce herding and those crazy last-minute swings. Not only is this method super popular, but it's also totally free to get started! (shutter.network).
• Optional: Hey! If you need a handy tool to help you split your budget into percentages across various options, take a look at the Aragon OSx gauges plugin. It might just be what you’re looking for! This might be exactly what you're looking for! Check it out over at aragon.org.

Why This Works: Minimal Engineering, Predictable Ops, and Defensible Controls for Non-Protocol Treasuries

So, when we chat about non-protocol treasuries, there are some really important parts that make this method work well. Let’s break it down:.

Minimal Engineering

If we keep engineering work to a minimum, we can really zero in on what’s most important. Basically, this means things get simpler, which usually means we run into fewer bugs and it’s way easier to scale up when we need to. At the end of the day, it’s really about making everything run smoother. We want to get stuff done efficiently without all the extra fluff.

Predictable Ops

When it comes to managing non-protocol treasuries, having a handle on predictability in operations is super important. When we have solid protocols in place, we can pretty much predict outcomes more reliably. This, in turn, makes planning for the future a whole lot easier! Knowing that things are pretty predictable gives stakeholders a sense of assurance about how stable and well the treasury is doing.

Defensible Controls

Having solid and well-thought-out controls in place really helps keep the treasury safe from any potential risks. These controls are built to be clear and dependable, giving everyone involved a solid framework they can really count on. So, it's not just about keeping track of assets; we’re actually making sure they’re protected too.

So, to wrap it up, when you put together a simple engineering approach, operations that are pretty easy to anticipate, and some solid controls, you end up with a dependable system for handling non-protocol treasuries. It really works well! The goal here is to build a sustainable and reliable environment that benefits everyone.

---

Emerging best practices in 2024-2025

• How about we stick with EIP‑6372 clocks? It’ll help us avoid those vote-manipulation headaches that come from reorg sensitivity. Plus, this way we can ensure the UI works smoothly since Tally checks for CLOCK_MODE. (docs.tally.xyz).
• Let’s make delegation a bit more exciting!
• Set up delegate programs that include clear performance goals and share the reasons behind your decisions with everyone. Big names in the game, like Uniswap, are stepping up their efforts by funding delegate rewards and treasury delegation programs. They’re really trying to ramp up participation! (gov.uniswap.org). Hey, just a quick reminder to keep partial delegation and the super useful “delegate override” features from OpenZeppelin v5 in mind! They can really come in handy. Sure, no problem! Just give me a bit more context about what you need, and I’ll be happy to help you out. (openzeppelin.com). How about we make shielded voting the go-to option for off-chain votes? We should also keep our fingers crossed and stay tuned for permanent shielded voting as Snapshot/Shutter preps for that homomorphic encryption. (blog.shutter.network).
• Get everything instrumented! Using Defender or Forta to keep tabs on governance, access control, any sketchy activity, and timelock queues is definitely a savvy choice. Plus, a ton of leading DAOs are willing to share their setups, so you can learn from the best! (docs.openzeppelin.com).
• How about we break those permissions into smaller, more manageable pieces? Safe’s Zodiac Roles/Delay has really become the go-to method for figuring out function selectors and making sure there’s a little pause between when a proposal gets the green light and when it actually gets executed. (docs.roles.gnosisguild.org).
• Embrace multi-chain, but make sure you’ve got a solid reason behind it! You can manage everything on a budget-friendly Layer 2 and smoothly transition to the mainnet with the Zodiac Bridge. If you prefer a simpler approach, take a look at MultiGov flows for an easier setup. (zodiac.wiki).

---

Legal wrappers: practical options in the U.S. and offshore

So, starting January 1, 2024, the Utah DAO Act is coming into play! This new law is pretty cool because it actually gives DAOs their own identity as a legal entity type - kind of like an LLC, but with a twist. You can think of it as an LLD/DAO! Great news! Registration is officially open! This is really convenient, especially if your organization is aiming for entity status but doesn't want to get stuck in that outdated model. Take a look at this link: (commerce.utah.gov). It's got some interesting info!

Hey there! So, in Wyoming, they’ve really broadened their horizons. They’re not just sticking with DAO LLCs anymore; they’ve also introduced DUNAs, which stands for decentralized unincorporated nonprofit associations. Pretty cool, right? So, this new setup is rolling out on July 1, 2024, and it’s a great fit for public-goods DAOs that aren’t really focused on making a profit. If you're curious to dive deeper into the topic, check it out right here: (jdsupra.com).

Back in 2022, the Marshall Islands took a big step to improve their DAO LLC setup, and now they’re taking it a notch higher! They’ve introduced faster registration, along with Series DAO LLCs (which are basically sub-DAOs), and they’ve made things clearer when it comes to classifying tokens. This means you’ll know which governance tokens don’t carry any economic rights. Super exciting stuff! If you want to dive deeper, just check out this link: (coindesk.com). Happy reading!

*Just a quick note: I’m not a legal expert, so definitely check in with a local attorney for the best advice. *.

---

Cost, time, and maintenance (what we see in practice)

• Using platforms:
• Launch: You can plan on taking around 1 to 3 weeks to get everything up and running. This will involve setting things up, getting your governance docs sorted, onboarding delegates, and connecting SafeSnap.
• Ongoing: You’ll be responsible for managing operations and keeping an eye on moderation. Plus, there will be times when you’ll need to update strategies and plugins, especially when it comes to those Snapshot multichain strategy migrations. If you want to dive deeper into this topic, feel free to check out more info here. You'll find all the details you need!
• Building your own:
• Launch: It usually takes about 6 to 12 weeks, but sometimes it can stretch beyond that, depending on a few factors. You'll have your hands full with a bunch of tasks like setting up and customizing contracts, running audits, getting the front-end ready, putting together incident runbooks, and building those automation pipelines. It’s going to be a mix of things, but it should keep you engaged!
• Ongoing: Just a quick reminder to keep an eye on monitoring and tuning. Also, don’t forget about managing those timelock roles, handling cross-chain relayers, and making sure the UI stays in tip-top shape!

Budget signals:

Once your treasury starts getting up there--like in the eight-figure range--it's super important to dive into on-chain execution. Don't forget about timelocks, setting up roles and delays, and getting some automation in place right from the start. It'll save you a lot of headaches later on! If you’re all about participatory grants or looking to boost community engagement, you can’t go wrong with Snapshot and SafeSnap. The shielded voting feature is super handy--it really gets the job done while allowing you to make quick updates as needed. Hey, if you're looking for the details, just hop over to this link: (docs.snapshot.box). You'll find everything you need there!

---

Decision checklist

Just answer with “yes” or “no.” If you answered "yes" to three or more questions, then you should definitely go with Build. But if you got fewer than that, it’s best to stick with Platform.

Hey, do we need to set up any custom rules for quorum, counting, or vetoes that go beyond what the usual Governor extensions provide? You can check out more about it here. So, do we really need deterministic timelocks and specific roles with on-chain enforcement to make sure everything stays compliant and helps with audits? Check it out here: github.com.

• So, are we planning to manage assets across multiple chains and still make sure everything gets executed on-chain as promised? Check out zodiac.wiki for more info! So, are we all set to take charge of stuff like monitoring, incident response, and automation--kind of like what Defender and Forta offer? You can check out some more details here.
• Do we really need to be independent from vendors over the long haul? I mean, it could be a smart move considering the risk of platforms shutting down, right? (blog.aragon.org).

---

Implementation nuances most teams miss

If you're looking to manage voting power effectively, definitely go with getPastVotes and getPastTotalSupply. And don't forget about the EIP‑6372 clocks--they’ll guide you through the entire process from beginning to end!
It's best to steer clear of calculating voting power with live balances. This approach helps avoid any last-minute tricks and keeps everything running smoothly for the clients. (docs.tally.xyz).

For SafeSnap, it's super important to establish some solid Reality bonds, pick a trustworthy arbitrator, and stay on top of the questions that come up. If the bonds are too simple, you could end up attracting a ton of spam. (docs.snapshot.box).

• Placing a Delay Modifier between your governance modules and the Safe is definitely a clever choice! This lets operators cancel or flag actions even when they're in cooldown. Also, it’s a smart move to test out your proposals on testnets first. That way, you can smooth out any rough edges before going live. (github.com).

When you're working on stuff that spans different chains, it's a good idea to keep your bridges, chain IDs, and function selectors to a minimum. This will help things run smoother. It's really important to steer clear of letting random calldata flow through AMBs without proper boundaries. (zodiac.wiki).

Hey, remember to give your delegates some real power! Think about kicking off a delegate program that sets clear goals, like participation levels and the quality of their input. And don't forget to include some transparent rewards to keep everyone motivated and engaged! (gov.uniswap.org).

---

Concrete playbooks (brief)

• Kick off governance using Tally. First things first, let's get the ball rolling! Start by deploying Governor and Timelock, and then connect them with Tally. After that, don’t forget to set up gasless delegation. Once that’s all squared away, you can create those delegate profiles and launch a campaign. And when you feel ready to take things further and dive into new chains, just add MultiGov to the mix! If you’re curious about the details, just click here!
• Community treasury using Snapshot. Alright, let’s get the shielded voting rolling! First up, we need to set up SafeSnap, making sure there’s a 24-hour cooldown in place. We should also include an arbitrator and make sure there’s a decent bond established. And hey, don’t forget to throw in some Zodiac Delay/Roles on the Safe while we’re at it! If you're interested in digging deeper, you can check out more details here. It's packed with useful info!
• A long-term protocol that lets you choose your own vendors. Alright, here’s the game plan: Start off by using Governor and Timelock together with the OZ extensions. Then, set up Safe along with Roles and Delay to keep everything secure and organized. You can either whip up a custom governance UI if you're feeling ambitious, or just go with Tally as a client - it’s super user-friendly.

To make your life easier, think about automating things with Defender and Forta. And don’t forget to put together a solid migration plan in your documentation. Make sure you include the steps for rotating timelock roles or swapping executors so everyone knows what to do when the time comes. It’ll save you a lot of headaches down the road! If you want to dive deeper, check out this page for all the details!

---

Final word

You know, everyone has their own priorities when it comes to governance. That's why platforms are super helpful! They really help us get things off the ground quickly and provide a pretty solid experience for users. On the other hand, if you opt for a custom stack, you'll enjoy way more control, have improved audit choices, and it usually holds up a lot better over time.

If you're feeling a bit overwhelmed, why not kick things off by checking out a platform that’s got modular components? Something like Safe, Snapshot, shielded voting, and Delay/Roles could be just what you need to get started! As you start to see your treasury and protocol risks rise, that's a good time to think about moving to on-chain Governor execution bit by bit. It's all about making smart decisions, right?

Whatever route you decide to take, 7Block Labs has your back! We're ready to team up with you to map out your plan, get it rolling, and make sure everything's running smoothly along the way. Let's start by putting together a governance threat model and outlining a migration plan right from the beginning.

---

References Cited:

• So, we've got the OpenZeppelin Governor, along with its extensions, and don’t forget about that EIP-6372 clocking feature. Plus, there's also the latest version of OpenZeppelin Contracts, which is v5. 2 updates. Read more here.

So, we've got a couple of cool things to talk about: the Safe/Zodiac modules, which include Delay, Roles, Bridge, and Reality. Plus, there's the integration of SafeSnap and Reality, too! Hey, take a look at this on GitHub! It’s definitely worth checking out.

Sure thing! So, we’ve got some cool features to talk about here. First off, there's Tally governance and MultiGov - these are all about managing decisions smoothly. Then there's Tally Zero, which focuses on resilience, making sure everything runs smoothly even when things get tough. Plus, we’ve got some awesome tools for delegation that really help in getting things done efficiently. Check out all the details over at Tally. You’ll find some great info there!

So, let’s talk about the cool features of DAOhaus v3, also known as Baal. This version brings some exciting upgrades that really enhance the whole experience.
Check out the latest updates over at DAOhaus!

• We've been working on getting shielded voting up and running, and we've got a solid plan in place for making it a permanent feature on Snapshot. Check out the plans over at Shutter Network. You might find something that really catches your eye!

Alright, let’s chat about Aragon OSx and what’s happening with its focus and the end of its legacy products. So, the big picture here is about how Aragon OSx is evolving and what that means for its older offerings. They're shifting gears, moving away from some of the legacy stuff that’s been around for a while. It’s like when you realize it’s time to let go of the old gadgets that just don't cut it anymore.

As they hone in on new features and improvements, it’s all about ensuring that the platform stays fresh and relevant. It’s a pretty exciting time, but I know it also means saying goodbye to some familiar tools. Change can be tough, but it’s all part of growth. Check out Aragon's website to dive deeper into what they offer!

• So, let's talk about some of the legal frameworks that are popping up, like the Utah DAO Act, Wyoming's DUNA, and some recent updates from the Marshall Islands. Check out the newest updates over at Utah Commerce. They’ve got some cool info about how the Utah Department of Commerce is starting to take registrations for decentralized autonomous organizations (DAOs). Don't miss it!
• Using Defender and Forta in DAO operations. Hey, you should definitely take a look at this case study over at OpenZeppelin. It's really interesting how Compound is using Defender to improve their DAO operations. You might find some cool insights in there!