<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
    <channel>
        <title>The DAO Kit</title>
        <link>https://paragraph.com/@thedaokit</link>
        <description>The DAOKit are Wonderverse.xyz, Guild.xyz, SnapshotLabs, Otterspace.xyz, Utopialabs.com, Coordinape.com, and Clarity.so</description>
        <lastBuildDate>Thu, 09 Apr 2026 14:18:04 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>https://github.com/jpmonette/feed</generator>
        <language>en</language>
        <image>
            <title>The DAO Kit</title>
            <url>https://storage.googleapis.com/papyrus_images/24ce2f34ed7f14d6c01e0826c5afe0f625af911c043c7f2f44869856d2c7ef17.png</url>
            <link>https://paragraph.com/@thedaokit</link>
        </image>
        <copyright>All rights reserved</copyright>
        <item>
            <title><![CDATA[Should my project be a DAO?]]></title>
            <link>https://paragraph.com/@thedaokit/should-my-project-be-a-dao</link>
            <guid>SsoB5dZ2VAwBoQtMqIWR</guid>
            <pubDate>Thu, 03 Nov 2022 14:35:29 GMT</pubDate>
            <description><![CDATA[Do you remember the first time you ever heard the word “DAO”? Maybe your green-pilled web3 friend was trying to sell you the idea, or you saw it in a tweet during the bull market. We’ve surely all gone through the process of diving into a rabbit hole around this nascent vision. Naturally, this discovery leads us to wonder, “should my project be a DAO?” Understanding the layers of what makes a DAO a DAO can help us comprehend the various opportunities and obstacles of organizing as one. Hello,...]]></description>
            <content:encoded><![CDATA[<p>Do you remember the first time you ever heard the word “DAO”? Maybe your green-pilled web3 friend was trying to sell you the idea, or you saw it in a tweet during the bull market. We’ve surely all gone through the process of diving into a rabbit hole around this nascent vision. Naturally, this discovery leads us to wonder, “should my project be a DAO?” Understanding the layers of what makes a DAO a DAO can help us comprehend the various opportunities and obstacles of organizing as one. </p><h3 id="h-hello-from-the-dao-kit" class="text-2xl font-header !mt-6 !mb-4 first:!mt-0 first:!mb-0">Hello, from The DAO Kit!</h3><p>Welcome to our second conversation with the DAO Kit crew, if you missed our first one on “Coopetition in DAOs &apos;, check it out <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://mirror.xyz/thedaokit.eth/Npy1wG4xOlh1qvs_QRih428qBPbmiro8US37H7EwIag">here</a>. Who are we? This post was written by <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://twitter.com/victoriakimse">@victoriakimse</a> based on our recent <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://twitter.com/i/spaces/1YqJDoYVWmEGV?s=20">Twitter Spaces</a> discussion in a series co-organized by a group of DAO tool builders: <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://twitter.com/wonderverse_xyz">@wonderverse_xyz</a>, <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://twitter.com/guildxyz">@guildxyz</a>, <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://twitter.com/SnapshotLabs">@SnapshotLabs</a>, <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://twitter.com/otterspace_xyz">@otterspace_xyz</a>, <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://twitter.com/utopialabs_">@utopialabs_</a>, <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://twitter.com/coordinape">@coordinape</a>, and <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://twitter.com/clarityteams">@clarityteams</a>. At our core, we believe in interoperability and collaboration. We decided to refer to our collaboration as ‘The DAO Kit,’ capturing the idea that DAOs can compose their toolset by combining our products rather than reaching for an all-in-one solution.</p><h3 id="h-what-makes-a-dao-a-dao" class="text-2xl font-header !mt-6 !mb-4 first:!mt-0 first:!mb-0">What makes a DAO a DAO?</h3><p>DAOs are often defined not by what they are at this moment but by what they aspire to be. Aspirational values revolve around distributed power, ownership, and transparency. It is the idea that no central body is dictating and operating an entire group. DAOs, we envision, are on the horizon and we are continuously defining it by working toward that future. </p><p>But where did it all start? Formally, a “DAO” spells out to be a “Decentralized Autonomous Organization.” The initial inception of the concept is most commonly attributed to a group of developers, Stephan Tual, Simon Jentzsch, and Christoph Jentzsch. A DAO, as they described in 2016, is an organization formed on top of the Ethereum blockchain with smart contracts to execute and make decisions autonomously. A smart contract is a “collection of code (its functions) and data (its state) that resides at a specific address on the Ethereum blockchain.” (<a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://ethereum.org/en/developers/docs/smart-contracts/">Ethereum Org</a>) </p><p>The measure of how much an organization operates via these smart contracts, still to this day, is heavily used to delineate Decentralized Autonomous Organizations. A tangible example of this is organizations that utilize a multi-signature wallet, a wallet composed of smart contracts to enable multiple ownership, and those who may decide to use a hot wallet with a singular owner.</p><p>As we examine how far these DAOs are technically on-chain and autonomous, it is essential to additionally question the culture and values of the people applying these technologies. For example, on-chain voting still has a lot of opportunities for improvement. Today, on-chain votes replicate Web2-like voting, where a single token equates to a single vote. In other words, being “on-chain” is not always synonymous with embodying the cultural values of what it means to be a DAO. </p><p>Navigating the idea of a DAO means challenging our technical boundaries and the values that make up our culture. <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://twitter.com/cult_leader_en">En, the Head of Community from Wonderverse</a>, prefers to define a DAO as a “Democratic Asynchronous Organization”, claiming that these words are a much better descriptor of what we’re trying to achieve in the web3 space. Essentially, that is an entity structure where our opinions feel valued, there are no authoritarian CEOs backed by a board of directors who make decisions, and there is space for work to be done wherever and whenever. </p><h3 id="h-should-my-project-be-a-dao" class="text-2xl font-header !mt-6 !mb-4 first:!mt-0 first:!mb-0">Should my project be a DAO?</h3><p>The evaluation of whether your project should be a DAO should begin with questioning your goals and objectives. As you can imagine, forming a DAO has both technical and cultural implications. There are a few tactical questions that may help guide your decisions. </p><p><strong>Do your project goals have emergent outcomes?</strong> </p><p>In this scenario, your project does not require a hard set of expectations and your community will likely act as agents of change. You can continue to iterate and decide on what success means for you. Your project would thrive in an environment where lots of experimentation is encouraged. You could leverage consensus-based decision-making and channel ambiguity as inspiration. This type of project may be suited as a DAO. </p><p><strong>Do your project goals have deliberate outcomes?</strong></p><p>These are the types of projects that require strict rules and expected outcomes. Projects like these require an environment where decisions are made quickly, and processes are streamlined. In this case, forming as a DAO may not necessarily be best suited for your project. </p><p>In short, your project doesn’t <em>need</em> to be a DAO; your project&apos;s goals can help you understand whether it may be best suited for one. </p><h3 id="h-conclusion" class="text-2xl font-header !mt-6 !mb-4 first:!mt-0 first:!mb-0">Conclusion</h3><p>It’s been over a year since we witnessed the Cambrian explosion of DAOs. Since then, we’ve continued to understand better what it means and what it takes to become a DAO. We’ve rigorously been working on improving the technologies that become the backbone of DAO functions while simultaneously evolving our values and cultural practices. Being a DAO means becoming comfortable with sitting in this gray. It means resisting the urge to adopt definitions and rules imposed upon us and letting the community come to its own understanding in an autonomous and decentralized fashion. At this stage DAOs, their structures, best practices, and successes are still changing rapidly. It may take a few years until there is a universally adopted definition of what DAOs are. Those comfortable with this process will be best equipped to see their project to fruition as a DAO.  </p><br><p>** **</p>]]></content:encoded>
            <author>thedaokit@newsletter.paragraph.com (The DAO Kit)</author>
            <enclosure url="https://storage.googleapis.com/papyrus_images/c3e4ed4c62d38e1f15983562cfbab7c877e578ceb69a01a57bf5d5e2d7fc7663.jpg" length="0" type="image/jpg"/>
        </item>
        <item>
            <title><![CDATA[Coopetition in Web3]]></title>
            <link>https://paragraph.com/@thedaokit/coopetition-in-web3</link>
            <guid>C6hHKuaWLfpz2I1HoEKX</guid>
            <pubDate>Wed, 19 Oct 2022 15:27:14 GMT</pubDate>
            <description><![CDATA[Have you ever heard the saying “a little competition never hurts” ? While we’ve all been conditioned to accept and embrace some level of competition, cooperation can take us further. Within Web3, we’ve heard the term ‘coopetition’ thrown around to describe how projects are interacting and evolving in the space. There is no doubt that Web3 brings with it a new culture, technology, and business model that disrupts the Web2 ‘winner-takes-all’ mindset. Who are “we”?Introducing The DAO KitThis pos...]]></description>
            <content:encoded><![CDATA[<p>Have you ever heard the saying “a little competition never hurts” ? While we’ve all been conditioned to accept and embrace some level of competition, cooperation can take us further. Within Web3, we’ve heard the term ‘coopetition’ thrown around to describe how projects are interacting and evolving in the space. There is no doubt that Web3 brings with it a new culture, technology, and business model that disrupts the Web2 ‘winner-takes-all’ mindset.</p><p>Who are “we”?</p><h3 id="h-introducing-the-dao-kit" class="text-2xl font-header !mt-6 !mb-4 first:!mt-0 first:!mb-0">Introducing The DAO Kit</h3><p>This post was written by <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://twitter.com/emthemaker">@emthemaker</a> based on the discussion in the first <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://twitter.com/i/spaces/1vOxwMnvyMbGB?s=20">Twitter Spaces</a> in a series co-organized by a group of DAO tool builders: <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://twitter.com/wonderverse_xyz">@wonderverse_xyz</a>, <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://twitter.com/guildxyz">@guildxyz</a>, <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://twitter.com/SnapshotLabs">@SnapshotLabs</a>, <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://twitter.com/otterspace_xyz">@otterspace_xyz</a>, <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://twitter.com/utopialabs_">@utopialabs_</a>, <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://twitter.com/coordinape">@coordinape</a>, and <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://twitter.com/clarityteams">@clarityteams</a>. We came together several months ago to regularly meet and discuss how we can collaborate to create positive sum outcomes for our respective projects. We decided to refer to our collaboration as ‘The DAO Kit’, capturing the idea that DAOs can compose their own toolset by combining our products, rather than reaching for an all-in-one solution.</p><h3 id="h-why-does-cooperation-matter" class="text-2xl font-header !mt-6 !mb-4 first:!mt-0 first:!mb-0">Why does cooperation matter?</h3><p>As humans, we have both an innate competitive response when we feel threatened, and a natural propensity toward cooperation when we feel safe. On a personal level, it is exhausting to constantly have to one-up everyone around you. Our experiences in Web2 and the traditional corporate world taught us to always be looking over our shoulders and anxiously rushing to outrun our competitors to the holy grail of the “winner takes all” market domination. This state is no more ‘natural’ than the cooperative state, but we have been conditioned to accept it and pursue winning at all costs.</p><p>However, there is another way, and the conditions in Web3 make this path more feasible than was previously possible. There are three elements that drive cooperation in Web3: technology, culture, and business models. These three elements are intertwined and contribute to an increased level of cooperation between projects like ours, relative to what would be expected in Web2.</p><h3 id="h-technology" class="text-2xl font-header !mt-6 !mb-4 first:!mt-0 first:!mb-0">Technology</h3><p>The first driving force behind cooperation in Web3, especially for those of us building on Ethereum, is the technology underpinning it. The Ethereum blockchain has built-in transparency and interoperability, which encourages cooperation between developers.</p><p>In Web2, competition is possible by maintaining ownership and control over the software and user accounts. Smart contract code, on the other hand, is public and can be run by anyone. It resembles a public good more than a proprietary resource. When the code developers write is transparent to the public, this encourages a more cooperative mindset - rather than re-building the same functionality as someone else and ‘competing’, it becomes more attractive to extend existing functionality and produce a greater whole.</p><p>Interoperability is also intrinsic to the Ethereum ecosystem, as the blockchain can be likened to a single global computer that everyone is programming based on a set of accepted standards and rules. Applications are compatible with each other and often integrated ‘out-of-the-box’. This inherent interoperability makes integration and extension of functionality straightforward, which once again encourages cooperation over competition.</p><p>These properties of blockchains make possible the concept of a ‘Hyperstructure’, which Jacob Horne of Zora defines as “<a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://jacob.energy/hyperstructures.html">Crypto protocols that can run for free and forever, without maintenance, interruption or intermediaries.</a>” A Hyperstructure creates a positive-sum environment by disincentivizing the re-building of the infrastructure and allowing participants to profit from their contribution to the system. It should be noted that not all protocols are Hyperstructures by default, but that the conditions within Web3 enable and perhaps even encourage the building of Hyperstructures.</p><p>While blockchains create an environment that can incentivize cooperation, they are certainly not deterministic. There are plenty of Web3 companies that combine smart contract code with privately-owned databases in such a way that the smart contract cannot function without the database. There is another important element to cooperation in Web3 - the culture that has evolved in the space.</p><h3 id="h-culture" class="text-2xl font-header !mt-6 !mb-4 first:!mt-0 first:!mb-0">Culture</h3><p>Cooperation in Web3 is facilitated by an open, global, and distributed infrastructure, but the evolving culture is an equally important driver. There is a noticeable sense of camaraderie, wagmi (we’re all going to make it) mentality, and positive-sum thinking among builders in the Ethereum ecosystem.</p><p>One important driver of this culture is without doubt a reaction to the Web2 era, which was marked by a small group of big tech monopolists selling personal data, exploiting content creators, spreading fake news, and generally capitalizing on their market position instead of considering their infrastructure as a public good. The deep distrust towards big tech has led people to look for alternatives that promise greater self-determination, transparency, and bottom-up cooperation.</p><p>There is a sense of working towards a collective mission of building the next generation of the Internet without making the same mistakes as predecessors. This mission-over-profit mentality creates a sense of belonging and shared fate. If our goal is to fundamentally re-structure the dynamics of the Internet, then we need to work together to enable the whole space to succeed. By constructing a shared antagonist in the legacy Web2 way of doing things, we see each other as part of the same team.</p><p>The culture of being involved in multiple Web3 projects at the same time and frequently moving between them has also facilitated greater cooperation. Relationships are built across a network of DAOs, which builds trust and strengthens the ability to cooperate.</p><h3 id="h-business-models" class="text-2xl font-header !mt-6 !mb-4 first:!mt-0 first:!mb-0">Business Models</h3><p>While the culture in Web3 certainly challenges traditional ways of looking at business models and profit, there is also a more fundamental shift at play. The nature of blockchains enables the flow of value (in the form of tokens) between network participants, turning Web2 business models on their heads.</p><p>The Ethereum blockchain is not just a shared programmable global computer, but it also has a built-in store and exchange of value in the form of tokens. Network participants, including infrastructure providers, are able to exchange small and large sums with each other based on the value they add to the network.</p><p>This means that multiple interoperable pieces of technology can participate as value creators in the same network and receive compensation for the value they created. While the business models of Web2 encouraged zero-sum competition to own all the supply and demand in a network, the business models enabled by the blockchain make possible a positive sum ecosystem that invites and thrives with cooperation.</p><p>** **</p><p>The increased level of cooperation that we’re seeing in Web3 is no accident but is driven by the combined forces of technology, culture, and business models. The conditions within Web3 create an environment that incentivizes greater cooperation between projects, and perhaps attracts people who are naturally drawn to more open and collaborative environments. But it by no means demands it - there is a world in which Web3 goes down a familiar path, with organizations competing tooth and nail for market share.</p><p>Every builder in the space ultimately has a choice in how we want the ecosystem to evolve and what role we want to play in that. The wagmi meme and culture of openness and positive-sum thinking might be the strongest tool we have to perpetuate collaborative behaviors and realize our vision of a Web3 that is different from previous generations of the Internet.</p>]]></content:encoded>
            <author>thedaokit@newsletter.paragraph.com (The DAO Kit)</author>
            <enclosure url="https://storage.googleapis.com/papyrus_images/b7474c4a88bccbe64289b7b8df9ff72a63dd424a03344ecd1458ba88ad2a53c8.png" length="0" type="image/png"/>
        </item>
    </channel>
</rss>