<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Dennison Bertram on Medium]]></title>
        <description><![CDATA[Stories by Dennison Bertram on Medium]]></description>
        <link>https://medium.com/@dennisonbertram?source=rss-ce7746cc56ef------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Nck_fsajfhgK7SJ_w_4-1g.jpeg</url>
            <title>Stories by Dennison Bertram on Medium</title>
            <link>https://medium.com/@dennisonbertram?source=rss-ce7746cc56ef------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 13:22:33 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dennisonbertram/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Towards Better Airdrops!]]></title>
            <link>https://medium.com/tally-blog/towards-better-airdrops-aaad54d4889e?source=rss-ce7746cc56ef------2</link>
            <guid isPermaLink="false">https://medium.com/p/aaad54d4889e</guid>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[decentralization]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[airdrop]]></category>
            <category><![CDATA[dao]]></category>
            <dc:creator><![CDATA[Dennison Bertram]]></dc:creator>
            <pubDate>Wed, 22 Feb 2023 15:45:09 GMT</pubDate>
            <atom:updated>2026-01-06T15:49:58.002Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*byjYw_disNNMlr1NfK21gg.png" /></figure><p>Airdrops have become a popular method for distributing governance tokens in Web3, but their effectiveness in building sustainable communities can vary greatly depending on how they are designed and implemented. While the idea of rewarding users with governance tokens for their engagement with a protocol or service is compelling, it can also be problematic if it results in token distribution that is too broad or does not target the right individuals.</p><p>One issue with airdrops is that the overlap between capable administrators and users of a service is not always clear. Operating web3 protocols effectively requires specialized knowledge in areas like cryptographic systems, Solidity, law, and brand building. Additionally, airdrops can attract opportunists looking to manipulate the system for personal gain, such as airdrop farmers who accumulate tokens just to dump them for a quick profit.</p><p>Choice of token holders has significant implications for the health of a DAO. Poorly chosen token holders can lead to governance gridlock, malicious attacks, or even the collapse of the DAO. To craft a better airdrop, consider the following strategies:</p><ul><li>Slow down the process and avoid giving users instant liquidity. A slower distribution process can help weed out opportunists and give genuine users time to engage with the protocol and provide value.</li><li>Be more selective about who receives tokens. Participation in a protocol alone may not be enough to justify receiving an airdrop. Instead, a more active involvement or evidence of providing value to the community should be considered. When Optimism launched, their Airdrop took into consideration individuals who actively participated in on-chain governance as a metric.</li><li>Linking the airdrop to specific actions or behaviors that are aligned with the values and goals of the protocol or service can also be effective. This could include completing tasks, contributing to the development of the protocol, or providing feedback and suggestions for improvement.</li></ul><p>It’s also important to consider the sustainability of the airdrop. A successful airdrop should not only benefit early holders, but also contribute to the long-term growth of the protocol or service. This requires careful planning and consideration of the incentives and governance mechanisms that are put in place.</p><p>Airdrops can be a powerful tool for building communities and distributing governance tokens, but they must be designed and implemented thoughtfully to be effective. By being selective about who receives tokens, linking the airdrop to specific actions, considering the sustainability of the distribution, and requiring users to delegate their tokens when they collect their airdrop, it’s possible to create a healthy and sustainable community of token holders that supports the growth and success of the protocol or service.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aaad54d4889e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tally-blog/towards-better-airdrops-aaad54d4889e">Towards Better Airdrops!</a> was originally published in <a href="https://medium.com/tally-blog">Tally</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to create a soulbound governance token in 5 minutes (or less!)]]></title>
            <link>https://medium.com/tally-blog/how-to-create-a-soulbound-governance-token-in-5-minutes-or-less-4151d2164b9d?source=rss-ce7746cc56ef------2</link>
            <guid isPermaLink="false">https://medium.com/p/4151d2164b9d</guid>
            <category><![CDATA[governance]]></category>
            <category><![CDATA[tally]]></category>
            <category><![CDATA[dao]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[ethereum]]></category>
            <dc:creator><![CDATA[Dennison Bertram]]></dc:creator>
            <pubDate>Thu, 02 Jun 2022 14:46:48 GMT</pubDate>
            <atom:updated>2026-01-16T20:39:06.151Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W-jdJ9VtspuDOW6b7LnEhw.png" /></figure><p>Soulbound Tokens, or SBTs, are hot right now. Like, really hot.</p><p>Described in Puja Ohlhaver, Vitalik Buterin, and Glen Weyl’s recent paper “<a href="https://papers.ssrn.com/sol3/papers.cfm?abstract_id=4105763">Decentralized Society: Finding Web3’s Soul</a>”, SBTs are essentially non-transferable NFTs. Because they are non-transferable, SBTs can be associated with one specific person or “soul” and used to represent an individual’s unique on-chain identity. You can imagine soulbound tokens being used to represent all sorts of important permanent information such as voting history or on-chain work credentials. With a collection of soulbound tokens, an on-chain “soul” or identity can represent a definitive, decentralized on-chain repository of information about a specific person.</p><p>One promising use case for SBTs is DAO governance. For example, soulbound tokens can be used to implement one-person, one-vote rules, or to enforce on-chain voting requirements for specific proposals.</p><h3>Let’s build one!</h3><p>Despite the lofty sounding name, SBTs are down to-earth tech. We already have and know all the code necessary to build them. In this example we will build a non-transferable NFT which can be used with <a href="https://blog.openzeppelin.com/governor-smart-contract/">OpenZeppelin Governor</a> to power a DAO.</p><h3>Step 1</h3><p>To start, we’ll open the <a href="https://docs.openzeppelin.com/contracts/4.x/wizard">OpenZeppelin Wizard</a> to build the base of our contract.</p><p>Since we’re building an NFT, we’ll select “ERC721” as our contract type, “Mintable” so we can create new ones and “Votes” so it’s compatible with DAOs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/984/0*W64x6yYvAQgU30rv" /></figure><h3>Step 2</h3><p>Now that we have the base, we need to customize our code. To do that, let’s open our code in Remix by clicking, “Open in Remix”. You can also click <a href="https://remix.ethereum.org/?#code=Ly8gU1BEWC1MaWNlbnNlLUlkZW50aWZpZXI6IE1JVApwcmFnbWEgc29saWRpdHkgXjAuOC40OwoKaW1wb3J0ICJAb3BlbnplcHBlbGluL2NvbnRyYWN0c0A0LjYuMC90b2tlbi9FUkM3MjEvRVJDNzIxLnNvbCI7CmltcG9ydCAiQG9wZW56ZXBwZWxpbi9jb250cmFjdHNANC42LjAvYWNjZXNzL093bmFibGUuc29sIjsKaW1wb3J0ICJAb3BlbnplcHBlbGluL2NvbnRyYWN0c0A0LjYuMC91dGlscy9jcnlwdG9ncmFwaHkvZHJhZnQtRUlQNzEyLnNvbCI7CmltcG9ydCAiQG9wZW56ZXBwZWxpbi9jb250cmFjdHNANC42LjAvdG9rZW4vRVJDNzIxL2V4dGVuc2lvbnMvZHJhZnQtRVJDNzIxVm90ZXMuc29sIjsKaW1wb3J0ICJAb3BlbnplcHBlbGluL2NvbnRyYWN0c0A0LjYuMC91dGlscy9Db3VudGVycy5zb2wiOwoKY29udHJhY3QgTXlUb2tlbiBpcyBFUkM3MjEsIE93bmFibGUsIEVJUDcxMiwgRVJDNzIxVm90ZXMgewogICAgdXNpbmcgQ291bnRlcnMgZm9yIENvdW50ZXJzLkNvdW50ZXI7CgogICAgQ291bnRlcnMuQ291bnRlciBwcml2YXRlIF90b2tlbklkQ291bnRlcjsKCiAgICBjb25zdHJ1Y3RvcigpIEVSQzcyMSgiTXlUb2tlbiIsICJNVEsiKSBFSVA3MTIoIk15VG9rZW4iLCAiMSIpIHt9CgogICAgZnVuY3Rpb24gX2Jhc2VVUkkoKSBpbnRlcm5hbCBwdXJlIG92ZXJyaWRlIHJldHVybnMgKHN0cmluZyBtZW1vcnkpIHsKICAgICAgICByZXR1cm4gImh0dHBzOi8vd3d3Lm15YXBwLmNvbS8iOwogICAgfQoKICAgIGZ1bmN0aW9uIHNhZmVNaW50KGFkZHJlc3MgdG8pIHB1YmxpYyBvbmx5T3duZXIgewogICAgICAgIHVpbnQyNTYgdG9rZW5JZCA9IF90b2tlbklkQ291bnRlci5jdXJyZW50KCk7CiAgICAgICAgX3Rva2VuSWRDb3VudGVyLmluY3JlbWVudCgpOwogICAgICAgIF9zYWZlTWludCh0bywgdG9rZW5JZCk7CiAgICB9CgogICAgLy8gVGhlIGZvbGxvd2luZyBmdW5jdGlvbnMgYXJlIG92ZXJyaWRlcyByZXF1aXJlZCBieSBTb2xpZGl0eS4KCiAgICBmdW5jdGlvbiBfYWZ0ZXJUb2tlblRyYW5zZmVyKGFkZHJlc3MgZnJvbSwgYWRkcmVzcyB0bywgdWludDI1NiB0b2tlbklkKQogICAgICAgIGludGVybmFsCiAgICAgICAgb3ZlcnJpZGUoRVJDNzIxLCBFUkM3MjFWb3RlcykKICAgIHsKICAgICAgICBzdXBlci5fYWZ0ZXJUb2tlblRyYW5zZmVyKGZyb20sIHRvLCB0b2tlbklkKTsKICAgIH0KfQo&amp;optimize=false&amp;runs=200&amp;evmVersion=null&amp;version=soljson-v0.8.7+commit.e28d00a7.js">here</a> to open in Remix.</p><p>The code should look like this:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/c97cf3bdbaa7183fb70aa45b0dce49ac/href">https://medium.com/media/c97cf3bdbaa7183fb70aa45b0dce49ac/href</a></iframe><p>We already have all the code necessary to launch a DAO Compatible NFT token! (The <a href="https://docs.openzeppelin.com/contracts/4.x/wizard">OpenZeppelin Contracts Wizard </a>is pretty awesome). Now, we just need to make a few changes to make it “soulbound” (i.e. non-transferable).</p><p>In the OpenZeppelin <a href="https://docs.openzeppelin.com/contracts/4.x/api/token/erc721#ERC721">ERC721 Contracts API</a> docs, you will find some hooks that we will use to control the transferability of our tokens.</p><p>We are already using function _afterTokenTransfer(address from, address to, uint256 tokenId) but we need to add a new function to check <em>before</em> a token is transferred to stop it from happening.</p><p>To block token transfers, add the following to your code:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/23ef87bc6ae8691d0acb997ec6b03fa6/href">https://medium.com/media/23ef87bc6ae8691d0acb997ec6b03fa6/href</a></iframe><p>Now, before anyone sends a token, the require statement will check if: true == false</p><p>and when it obviously doesn’t it, will block the transfer with the error message Err. token is SOUL BOUND.</p><h3>Step 3:</h3><p>Great, except we have a problem. This hook will run on <em>all transfers</em> meaning it will even block minting which is technically a transfer from the zero address to a real address. This isn’t a soulbound token, it’s just broken!</p><p>To fix it, we should do a check to see that the <em>sender</em> is the zero address, that way we know this is a mint transaction and not a transfer. Let’s update our code to check for this:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/57e98fb6cad0dfa167d2144992b0d8ef/href">https://medium.com/media/57e98fb6cad0dfa167d2144992b0d8ef/href</a></iframe><p>Perfect! Now we have a soulbound NFT that can be minted, but not transferred. This is perfect for non-transferable voting systems, or badges that you don’t want participants to sell on the open market. Because we’re using ERC721 with the Votes extension, our new SBT is also ready for use in a DAO with OpenZeppelin Governor.</p><p>The final Code:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/d1d95f79f44282671aa01f10b5dc30a4/href">https://medium.com/media/d1d95f79f44282671aa01f10b5dc30a4/href</a></iframe><p>Enjoy!</p><p>For more useful DAO content follow Tally on <a href="https://twitter.com/tallyxyz">Twitter</a>, <a href="https://blog.tally.xyz/">Medium</a>, and <a href="https://www.youtube.com/channel/UC0J5KuukgFn8KCMuuhkBZQw">YouTube</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4151d2164b9d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tally-blog/how-to-create-a-soulbound-governance-token-in-5-minutes-or-less-4151d2164b9d">How to create a soulbound governance token in 5 minutes (or less!)</a> was originally published in <a href="https://medium.com/tally-blog">Tally</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Invisible Work of Community]]></title>
            <link>https://medium.com/tally-blog/the-invisible-work-of-community-e37c5ed14699?source=rss-ce7746cc56ef------2</link>
            <guid isPermaLink="false">https://medium.com/p/e37c5ed14699</guid>
            <category><![CDATA[community]]></category>
            <category><![CDATA[community-management]]></category>
            <category><![CDATA[dao]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[discord]]></category>
            <dc:creator><![CDATA[Dennison Bertram]]></dc:creator>
            <pubDate>Thu, 07 Apr 2022 17:08:34 GMT</pubDate>
            <atom:updated>2026-01-16T20:57:46.328Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>What is it about Discord</strong> that creates a utopian environment for some and a grueling, soul-crushing experience for others?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W-jdJ9VtspuDOW6b7LnEhw.png" /></figure><p>High speed, 24/7 discussions wear down community moderators. “Soft fudders” undermine the confidence of builders. Endless streams of repetitive questions, scammers, and real time feedback make participation a battlefield.</p><p>Discord is an accidental tool for DAO’s. The memetic quality of the “idea” of DAO’s spread faster than native tools could be built to support them. So much of the crypto hype cycle is reliant upon FOMO and tools like Discord, Twitter, and Telegram facilitate FOMO like few other platforms can. The irony is that the same tools which can drive initial community growth can become unmanageable environments in which to nurture and support the very same community.</p><p>Discord, Twitter, and Telegram don’t function without the hard work of what is generally a volunteer base of Mods and Admins who patrol the channels and threads weeding out scams, abuse, price talk and naked shills.</p><p><strong>Is the hard work of the community rewarded?</strong></p><p>The volunteers that arrive to define a community’s spirit, mission, and goals, are rarely compensated for their work. They don’t arrive from job postings on AngelList, they arrive because something about the project itself compels them, and they see an opportunity to shape a thing that they themselves have a hand in building.</p><p>Initially, this work is emotionally rewarding for many members. There is the enthusiasm of a launch or drop, the excitement from working together with “fellow degens” to deploy smart contracts or setup channels. Camaraderie from agreeing to ban or kick members they collectively find to be disruptive.</p><p>Over time however, as communities grow, the moderation work load expands, and the emotional rewards feel less tangible. Early communities are defined by a strong sense of shared purpose, a clarity about the task at hand and a huge dose of optimism. As communities move out of the “early” phase though, members start to confront day-to-day challenges of building something in a collective.</p><p>The challenges faced by volunteer participants are genuinely stressful and emotionally draining. While DAO participants are generally anonymous, even anonymous handles fronted by cartoon penguins are managed by real humans behind them. Volunteers can feel responsible for ETH lost in failed transactions. Their attempts to remedy a single participant’s bad experience can open them up to a sense of unlimited responsibility, lest they be accused of playing favorites- or worse.</p><p>When things go well, there are still challenges. Crypto moves at about 10x normal human life speed, and Discord another 10x on top of that. Software or products that in the “real” world can take entire teams of professionals months or years to build are demanded overnight. “Soft fudders” demand updates in the darkest hours of night, declaring the community to have been abandoned if their messages don’t receive instantaneous response. Mods do their best to coordinate answers, but when the midnight cohort is satisfied, the morning comes and the process is repeated.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ok1NjZU44HSrRYLx" /></figure><p>Volunteers quickly find themselves emotionally trapped. Taking a reduced role rarely works. Volunteers feel responsible for the success of the community. Caught between stress of staying, and the guilt of announcing a departure (and thus being labeled a “fudder” themselves) the only option is to silently depart. Most quietly leave. The only evidence of their hard work long since scrolled far, far, far, up somewhere in the difficult-nigh-impossible to search message history.</p><p>Builders find themselves in similarly grueling roles. Focused on building the software of an idea, builders can be interpreted by community members as “core devs” and “accountable to the community”. Builders who check-in to chat often find themselves sucked into debates on why they are building what they are building, why its taking so long, why it doesn’t work as well as a product built by someone else, why they aren’t taking community feedback seriously, why aren’t they doing it for free, and why they haven’t made bag holders rich yet.</p><p>Builders who are financially rewarded by their efforts are interpreted as somehow being beholden to the community, which at times of high stress, can feel like a mob. Builders are human, and thus possess limited resources. The more builders engage in discussion, trying to “set the record straight”, the less time they have to build. The less time they have to build the less satisfied the more critical elements are of their work, the greater the demands for progress become.</p><p>In speaking with builders who have taken a step back from, or left their communities, there is a common theme. They joined the community as a creative, looking to build and have a purpose to build. Success in the community brought a pressure to address community feedback, input or demands. Communities that rewarded builders financially frequently began to perceive them as staff engineers, rather than incentivized contributors.</p><p>For contributors who were hired for tasks, being adequately compensated can be difficult and stressful. Contributors need to charge a fee for their services that allows them to afford the cost of living where they are based. Internet communities are frequently geographically dispersed and what might make a reasonable rate for a San Francisco based contributor can seem grossly overpaid to community members in practically any other geographic location. Contributors are then forced to defend their rate in what can be a demoralizing and degrading public conflagration in which they are treated as greedy, exploitative and disposable.</p><p><strong>Where do we go from here?</strong></p><p>While tooling and best practices can go a long way to addressing the issues outlined above, perhaps the most useful first step for contributors is to better understand their role in a decentralized organization.</p><p>Being a volunteer, contributor, or builder in an open decentralized community is an <strong>inherently political position</strong>. It requires balancing the needs and opinions of vocal community factions, while brokering compromise on decisions over what to do with limited resources. While communities have a responsibility of creating healthy, thriving environments for their contributors, contributors must recognize that it falls upon their shoulders to build and shape exactly those environments themselves.</p><p>Purposefully setting boundaries can help contributors prevent burnout and inadvertent exploitation. Clear methodologies around rewards, compensation and expectations can help to prevent community ‘buyers remorse’. Moderators can reinforce that volunteer builders are volunteers, not staff, and that if members want to ‘get something done’ everyone in the community should be empowered to make ideas a reality.</p><p>Best practices can also help communities prepare for success. Handbooks for communities and templates for how things are done can reduce mistakes that come from ‘building on the fly’ and can provide a roadmap for sustainability.</p><p>Normalizing the financial support of volunteers will help ensure the long term success of a DAO. Community management starts as a passion, but when done day in and day out, it becomes a job. Compensation, clearly defined, can go a long way to support the health of a DAO and manage the expectations of the community.</p><p>Recognizing that Discord personalities are also people and enforcing standards of conduct and behavior enables sustainable productive debate. Members need to feel they will be respected and treated fairly ,even when voicing unpopular opinions. Respect for participants personhood and participation signals an inclusive environment to everyone in the community.</p><p>Despite the “Autonomous” part of the acronym, DAOs are a new frontier in <em>human</em> organization. For DAOs to reach their full potential, we have to design for people. Let’s work together to make DAOs a wonderful place for all of us humans that make them happen.</p><p>🙋🏽‍♀️ Have ideas how we can improve the community contributor experience? please reach out, I would love to hear from you:</p><p>🐦 <a href="https://twitter.com/DennisonBertram">@dennisonbertram</a></p><p>🗳 <a href="http://www.tally.xyz/">Tally.xyz</a></p><p><em>Thank you to all the DAO community members who helped inform this article.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e37c5ed14699" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tally-blog/the-invisible-work-of-community-e37c5ed14699">The Invisible Work of Community</a> was originally published in <a href="https://medium.com/tally-blog">Tally</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Denver, here we come!]]></title>
            <link>https://medium.com/tally-blog/denver-here-we-come-6d94f19f448c?source=rss-ce7746cc56ef------2</link>
            <guid isPermaLink="false">https://medium.com/p/6d94f19f448c</guid>
            <category><![CDATA[dao]]></category>
            <category><![CDATA[tally]]></category>
            <category><![CDATA[governance]]></category>
            <category><![CDATA[defi]]></category>
            <category><![CDATA[ethdenver]]></category>
            <dc:creator><![CDATA[Dennison Bertram]]></dc:creator>
            <pubDate>Thu, 27 Jan 2022 19:43:49 GMT</pubDate>
            <atom:updated>2026-01-16T20:46:51.855Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W-jdJ9VtspuDOW6b7LnEhw.png" /></figure><p>Last year Tally onboarded some of the biggest DAO’s in the Ethereum ecosystem and tens of thousands to decentralized governance. In 2022 we have even bigger plans- onboard everyone to DAO’s!</p><p>We have some exciting new updates to the Tally platform:</p><ol><li>Multichain support — Add your DAO on Polygon, Optimism, Fantom, and more. If there is an EVM network you would like to see supported on Tally, come to our booth and let us know. We are rolling out support incrementally so your input would be very helpful!</li><li><a href="http://www.koken.club/">Koken.Club</a> — Visualize the contributions of your DAO community members through dynamic NFT’s that grow like Trees!</li><li><a href="http://www.dao.new/">DAO.NEW</a> — Need a DAO? Need it Now? Need it <em>cheap</em>? <a href="http://www.dao.new/">Dao.new</a> is a no-frills multi-chain DAO deployer that uses <a href="https://docs.openzeppelin.com/contracts/4.x/api/proxy#Clones">OpenZeppelin Clones</a> to save you thousands of dollars in deploying a complete Membership DAO. Comes with treasury management, NFT Royalties, and a starter kit based on Austin Griffith <a href="https://github.com/scaffold-eth/scaffold-eth">Scaffold-eth</a> for creating a minting drop website. <a href="https://github.com/withtally/dao.new">Check out the Repo</a>!</li><li><a href="https://github.com/withtally/chrome-extension">Chrome Extension</a> — With one click, a new Open Source chrome extension lets you discover the NFTS, POAPs, Tokens, and Governance participation of any ENS and Ethereum address on the web!</li></ol><h3>Workshops:</h3><p>We’re doing two workshops in ETH Denver that we think folks will find very interesting.</p><p><strong>🔥 Cross Chain governance with Tally and Optimism 🔥</strong></p><p>Learn how to build a DAO on Optimism that controls a treasury on Ethereum. Have cheap on-chain proposals and access the liquidity of Ethereum at the same time!</p><p>📍 February 17th, Location: Mirus Loft Time: 3–5 pm (EventBrite coming soon)<br><a href="https://ethdenver.sched.com/event/7a77fc5dbec3529c10730bc94b09065d">Buidl Week Link</a></p><p>🌈 <strong>Easy DAO Proposals </strong>🌈</p><p>Want to create proposals in your favorite DAO? Then, we’ve got just the thing for you! Learn about the latest update to Tally: our easy Proposal wizard for <a href="https://blog.openzeppelin.com/governor-smart-contract/">Governor DAOs</a>.</p><p>📍February 18th, Location: Sports Castle Time: TBD (Open Entry)</p><p>We will have a table set up at ETH Denver with T-shirts and plenty of good DAO vibes. So come by to talk with us about your DAO idea.</p><h3>Resources</h3><p><a href="https://blog.openzeppelin.com/governor-smart-contract/">Learn about OpenZeppelin Governor DAOs</a></p><p><a href="https://docs.openzeppelin.com/contracts/4.x/governance">How to setup a Governor DAO</a></p><p><a href="https://docs.openzeppelin.com/contracts/4.x/api/governance">OpenZeppelin Contracts: Governor</a></p><p>Connect Governor to Gnosis Safe (Coming soon!)</p><p><a href="https://github.com/withtally/rollcall">RollCall Cross Chain Governance Solutions</a></p><p>Listing your DAO on Tally (Medium Post coming soon!)</p><p>You can also reach us online during ETH Denver:</p><p>📩 Email: hello@withTally.com</p><p>👋🏽 Discord: <a href="https://discord.gg/GFa4GDxZzQ">https://discord.gg/GFa4GDxZzQ</a></p><p>👩🏻‍💻 Web: <a href="https://www.withtally.com/">https://www.withTally.com</a></p><p>🐦 Twitter: <a href="https://twitter.com/voteWithTally">https://twitter.com/voteWithTally</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6d94f19f448c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tally-blog/denver-here-we-come-6d94f19f448c">Denver, here we come!</a> was originally published in <a href="https://medium.com/tally-blog">Tally</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ERC721Votes —DAO Governance comes to NFTS]]></title>
            <link>https://medium.com/tally-blog/erc721votes-dao-governance-comes-to-nfts-38b6b76f98c8?source=rss-ce7746cc56ef------2</link>
            <guid isPermaLink="false">https://medium.com/p/38b6b76f98c8</guid>
            <category><![CDATA[dao]]></category>
            <category><![CDATA[tally]]></category>
            <category><![CDATA[governance]]></category>
            <category><![CDATA[nft]]></category>
            <category><![CDATA[ethereum]]></category>
            <dc:creator><![CDATA[Dennison Bertram]]></dc:creator>
            <pubDate>Mon, 24 Jan 2022 13:25:53 GMT</pubDate>
            <atom:updated>2026-01-16T21:04:04.088Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W-jdJ9VtspuDOW6b7LnEhw.png" /></figure><p>OpenZeppelin has added the draft of ERC721votes preset to their standardized <a href="https://openzeppelin.com/contracts/">contract library</a>. This draft update brings the power of the <a href="https://blog.openzeppelin.com/governor-smart-contract/">Governor DAO framework</a> used by projects such as <a href="https://compound.finance/">Compound</a>, <a href="https://uniswap.org/">Uniswap</a>, <a href="https://gitcoin.co/">Gitcoin</a>, and <a href="https://ens.domains/">ENS</a>, to NFTs projects in a standardized format.</p><p>Originally pioneered by the <a href="https://nouns.wtf/">NounsDAO</a> and used by community-run video game development studio <a href="https://dopewars.gg/">DopeWars</a>, ERC721Votes is an extension on the standard NFT contract used by top NFT projects to add voting capabilities directly to the individual tokens.</p><p>Unlike most DAO’s where voting power is based on fungible token ownership, ERC721Votes supports each NFT == one vote. This means it’s possible to create NFT communities where instead of having a separate token for governance, the individual NFT’s can be used to vote themselves.</p><h4>Upgrading</h4><p>To add ERC721Votes to your project, replace the import with the new draft specification and inherit the ERC721Votes contract instead of ERC721. Initialize your ERC721 as you normally would. An added advantage for projects sensitive to gas cost is ERC721Votes is not <em>enumerable</em> and is cheaper than the ERC721Enumerable contract that most NFT projects use.</p><p>Additionally, OpenZeppelin has a fantastic support community, so if you have any technical questions, you can get expert input from others using ERC721Votes on their <a href="https://forum.openzeppelin.com/">forum</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R0HWv-p7eO71ShMZYllchw.png" /></figure><h3>Tally Support</h3><p>Tally fully supports ERC721Votes today, meaning your NFT DAO can leverage the community and tooling that Tally offers: rich voter profiles with voting delegation, detailed charts and data on participation, and powerful proposal creation tools.</p><p>To add your DAO to Tally, simply click on the “Add a DAO” link at the top of the homepage and fill out a simple form. You will be added to the leaderboard in no time!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kataUh6SrXcNeQd3V7MXQw.png" /></figure><h3>Stay Connected</h3><p>Questions, comments, ideas? Just want to say hello?</p><p>Swing by our discord with any technical questions or ping us on Twitter!</p><p>🐦 <a href="https://twitter.com/voteWithTally">Twitter</a></p><p>⚡️ <a href="https://discord.gg/GFa4GDxZzQ">Discord</a></p><p>🤙🏽 <a href="http://www.withtally.com/">Web</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=38b6b76f98c8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tally-blog/erc721votes-dao-governance-comes-to-nfts-38b6b76f98c8">ERC721Votes —DAO Governance comes to NFTS</a> was originally published in <a href="https://medium.com/tally-blog">Tally</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Future is DAO]]></title>
            <link>https://medium.com/tally-blog/at-tally-we-believe-that-internet-native-organizations-daos-will-become-the-dominant-7a30c0c2516a?source=rss-ce7746cc56ef------2</link>
            <guid isPermaLink="false">https://medium.com/p/7a30c0c2516a</guid>
            <category><![CDATA[defi]]></category>
            <category><![CDATA[governance]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[dao]]></category>
            <category><![CDATA[crypto]]></category>
            <dc:creator><![CDATA[Dennison Bertram]]></dc:creator>
            <pubDate>Fri, 13 Aug 2021 18:09:31 GMT</pubDate>
            <atom:updated>2026-01-16T21:12:56.983Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W-jdJ9VtspuDOW6b7LnEhw.png" /></figure><p>At Tally, we believe that Internet-native organizations — DAOs — will become the dominant organizational form for human capital, energy, and creativity!</p><p>If this sounds far-fetched, it’s not: it’s happening now, today. Defi Protocols such as Compound, AAVE, Uniswap are owned and governed by their creators and users alike. PleasrDAO and FlamingoDao are moving the art world forward with NFTs, Index Coop creates collective investment indexes. Radical decentralizes code collaboration. Opolis and RaidGuild are building the future of work. TheLAO and MetaCartel Ventures are leaders in the DAO-powered VC space. TheGraph has created a global network of indexers who power the data pipeline and backbone of Web3. Most of the DefiPulse list is now composed of DAOs, with treasuries in the billions.</p><p>It’s an ecosystem of DAOs, powering DAOs, hired by DAOs to create new DAOs supporting billions of dollars in capital and countless hours of human productivity.</p><p>This is the future.</p><p>At our core, we know that talent is evenly distributed, but that opportunity is not. We believe that DAO’s will allow us to evenly distribute opportunity, but it’s early and we need the tools.</p><p>Tally is building the infrastructure and tools for user-owned economies and internet native communities, where talent and opportunity can merge to build the future together.</p><p>To do this, we have raised $6 million led by Blockchain Capital and Placeholder VC , with participation by 1KX, Notation Capital, Castle Island Ventures, Collab+Currency, Lemniscap, Robot Ventures (Robert Leschner, founder of Compound), Stani Kulechov (Founder of AAVE), Ryan Sean Adams (Founder of Bankless), DeFi alliance, Larry Sukernik, Dave Balter, Regan Bozeman, BlackRock Capital, Tarrence van As, Yalor Tackson, and Ramon Recuero (Founder Babylon Finance).</p><p>What is really exciting? Joining this round we had substantial participation from DAOs such as TheLAO, MetaCartel Ventures, BAires DAO and Fire Eyes.</p><p>That’s DAO’s funding the tools for more DAOs.</p><p>The future is now.</p><p>We are excited about what’s coming next. If you believe in the future the way we do, reach out on <a href="https://discord.com/invite/sCGnpWH3m4">Discord</a> or <a href="https://twitter.com/voteWithTally">Twitter</a>!</p><p>Join us: <a href="http://careers.withtally.com/">careers.withTally.com</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7a30c0c2516a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tally-blog/at-tally-we-believe-that-internet-native-organizations-daos-will-become-the-dominant-7a30c0c2516a">The Future is DAO</a> was originally published in <a href="https://medium.com/tally-blog">Tally</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UniSwapicus Maximus]]></title>
            <link>https://dennisonbertram.medium.com/uniswapicus-maximus-d24351e0ca00?source=rss-ce7746cc56ef------2</link>
            <guid isPermaLink="false">https://medium.com/p/d24351e0ca00</guid>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[uniswap]]></category>
            <category><![CDATA[defi]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[ethereum]]></category>
            <dc:creator><![CDATA[Dennison Bertram]]></dc:creator>
            <pubDate>Tue, 13 Apr 2021 20:30:51 GMT</pubDate>
            <atom:updated>2021-04-13T20:30:51.936Z</atom:updated>
            <content:encoded><![CDATA[<h3>UniSwapicus-Maximus</h3><p>Crypto Protocols should model themselves after the Roman Empire because the future is Chaos and the time for Empire building is now.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O1uymQNWLiGk9enVDRa1PA.jpeg" /><figcaption>The Roman Empire as a playbook for the Crypto Ecosystem</figcaption></figure><p>Let me start by saying: the future in Crypto is chaos and I might be totally wrong.</p><p>I was speaking recently with Brendan Asselstine of PoolTogether on the future of governance in a multi-chain world. The complexity of governance once a project expands beyond L1 Ethereum was instantly apparent.</p><p>Each Layer, L1, Optimism, BSC, and otherwise, is essentially its own closed world. Bridges in and out of networks are going to be slow and costly at the best of times, and for the consumer, so much choice will abound via arbitrageurs, new solutions, and marketing that it won’t be obvious there exists any value in leaving the environment they currently exist in.</p><p>Anyone who believes in evolution knows what will happen next: different environments have different ecosystems, different parameters, different social networks, different tools. What works on L1 Ethereum, will have to work slightly differently on L2. Who uses what, how much liquidity is available, what primitives exist, will most likely never be universal or at feature parity across networks.</p><p>This means evolutionary pressure will exist upon all protocols in each “layer” or “island” independently. In fact, I quite like the island analogy for the different layers, because the Islands are where we see the most evolutionarily extraordinary adaptations. From flightless birds to prehistoric dragons.</p><p>What does this mean for Crypto? It means that a protocol that exists on L1, and deploys on L2 will quickly diverge in liquidity, userbase, environment, and their needs and design will also quickly diverge.</p><p>For governance this might be a nightmare- how will L1 SushiSwap voters, in the long term, remain aligned with the users of L2 SushiSwap? Is the same governance token going to be used on both layers? In both places? What happens if Uni were to pool inside Optimism, to the point where L1 governance is impossible? What happens, much like the colonies, Sushiswap L2 users get tired of the inaction of L1 users? What if there isn’t overlap between the two? No taxation without representation right?</p><p>For governance though, this is also a huge opportunity. Rome’s strength was at its greatest when it was well governed by a diverse and wide-reaching participant base.</p><p>I mean to keep this short, and I will.</p><p>The conquest of Italy by the Roman Empire looks very much like the conquest and challenges playing out on L1 Ethereum today. The future, of course, is the colonies. North Africa, England, Sicily, Byzantium.</p><p>The Roman empire has many similarities: power is isolated in different places, separated by slow communication channels. Long-term success depends upon the domination of many places that are difficult to link up. Colonies are sources of revenue, of strength. Alliances build markets and bring a greater population of users onboard. Successfully holding control over the colonies requires decentralized governance, where locals not only feed the mother empire but also benefit from it. See a parallel in blockchain where L1 provides liquidity, insurance, etc… to activities on Layer 2.</p><p>Failure to strike a balance of control will lead to the colonies revolting, offering different incentives to the local population to rebel. You can think of BSC’s Pancake swap as a kind of Carthage. Modeling itself on Uniswap, with similar ambitions and goals, and always a potentially existential threat to the empire.</p><p>The analogy is simple, and I won’t tire the reader at this point.</p><p>Uniswap should model itself on the Roman Empire. It brings prosperity to everyone through effective governance, and projection of power and order through the known “layers”. It is an expensive process, it requires many layers of governance, but it is ultimately the goal that every AMM will have on every network in one way or another.</p><p>Let&#39;s discuss. @dennisonbertram</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d24351e0ca00" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Prints of an Artist.]]></title>
            <link>https://dennisonbertram.medium.com/prints-of-an-artist-e304c5348f29?source=rss-ce7746cc56ef------2</link>
            <guid isPermaLink="false">https://medium.com/p/e304c5348f29</guid>
            <category><![CDATA[painting]]></category>
            <category><![CDATA[nftart]]></category>
            <category><![CDATA[nft-collectibles]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[nft]]></category>
            <dc:creator><![CDATA[Dennison Bertram]]></dc:creator>
            <pubDate>Sun, 11 Apr 2021 23:26:02 GMT</pubDate>
            <atom:updated>2021-04-11T23:26:02.893Z</atom:updated>
            <content:encoded><![CDATA[<p>How Solos is creating a new future for traditional Artists in the digital realm</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LNGOXbI9l6D5MirsWj3Lxg.png" /><figcaption>Works from the Solos inaugural edition: Saturnalia</figcaption></figure><p><a href="http://www.solos.so/">Solos</a> are generated digital paintings drawn from the archive of the artist, <a href="http://jeremiahpalecek.com/">Jeremiah Palecek</a>. Each Solos painting is a kind of ‘automatic collage’, each element drawn from some work in Jeremiah’s vast collection of paintings done over the years, selected in a pseudo-random fashion, taking the origin of the purchasers&#39; transaction into account.</p><p>Each is unique. None of them have ever existed before, and over 2,000 of them sold in a matter of hours of being announced.</p><p>The thing which makes Solos so radical, and magical, is that each Solos looks as if Jeremiah had painted it himself. Each has his themes, his inspirations, his perspective. Yet, he didn’t paint them, and there’s no AI here, no GAN networks, no rendering.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A0sacMqsIuZ8b6Lp95_PFQ.png" /><figcaption>Solos Saturnalia #2590</figcaption></figure><p>Solos break ground by combining the techniques that artists have worked with for centuries: painting, collage, composition, layering, to create something truly new: Prints of an Artist, not just his work. The vision of the artist themselves, captured in a way that lets anyone own a unique Jeremiah Palecek, without, actually, ever owning a painting</p><p>The leap from the canvas to digital for artists is a challenging one. One that Jeremiah detailed in his Medium post, <a href="https://jeremiahpalecek.medium.com/my-muses-arent-imaginary-edc43ef0ab7b">My Muses aren’t imaginary</a>. Most artists go the poster route: take a painting, print a hundred copies, sell for $50 a pop. Many NFT’s from artists are much of the same, take a work, mint and NFT, make 100 versions. Call it a day.</p><p>But the result isn’t the same. Posters try to mimic the experience of owning a work of art while conveying upon the possessor, none of the magic of having the “real thing”.</p><p>What Solos has done is very different. Solos has made the act of possessing a digital <em>replica </em>of the art, a unique piece of art itself. Jeremiah has painted hundreds of canvases in the past decades and for admirers, many of them are in private collections locked away.</p><p>With Solos, Jeremiah offers collectors the opportunity to own a work <em>that he could have painted</em> but hasn’t. Solos suggests a future for traditional painters looking to make the leap into the digital realm in a way that doesn’t cheapen the physical element, yet allows artists to capture the enthusiasm of their collector base. Imagine a gallery showing Jeremiah&#39;swork, where every guest could purchase their own, unique, print- every bit as beautiful and detailed as an original work, except, of course, the original work, <em>does not exist</em>. Collectors can own an <em>impression</em> of the artist, possibly even as valuable as the tangible artwork itself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y-qNnDqaAEsecsEsuddhEA.png" /><figcaption>Solos Edition One: Saturnalia</figcaption></figure><p>In the past two weeks, the team behind Solos has been inundated by requests from painters eager to understand the process. Solos has also been trail-blazing in other ways as well. The Solos community of collectors hold voting tokens that allow it to decide on different aspects of the project, creating a forum in which the collectors communicate with artist and vice versa. Recently a MultiSig has been set up, stocked with fifty thousand Solos ERC20 tokens to represent a grants committee, with a board chosen by a governance poll.</p><p>With nearly 3000 portraits sold, the inaugural edition, Saturnalia, is coming to a close, to be followed by Evolution, Edition #2, also by Jeremiah. It’s early days for Solos and Digital art, but exciting times lay ahead.</p><p>Purchase existing Solos at <a href="https://rarible.com/solos?tab=collectibles">Rarible</a>, or mint your own at <a href="http://www.solos.so/">www.solos.so</a>.</p><p>To learn more about Solos, <a href="/service/mailto://dennison@dennisonbertram.com">contact us</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e304c5348f29" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A brief history of Ethereums’ near future.]]></title>
            <link>https://dennisonbertram.medium.com/a-brief-history-of-ethereums-near-future-3b1d672d08bd?source=rss-ce7746cc56ef------2</link>
            <guid isPermaLink="false">https://medium.com/p/3b1d672d08bd</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[defi]]></category>
            <dc:creator><![CDATA[Dennison Bertram]]></dc:creator>
            <pubDate>Wed, 01 Jul 2020 13:54:56 GMT</pubDate>
            <atom:updated>2020-07-01T13:54:56.374Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/666/0*XW4_OLt36AOZ9ruN" /></figure><p><em>Note: This article is a thought exercise.</em></p><h3>1: Gas prices will scale with the value of the transactions and will continue to be expensive and trend upwards.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/679/1*EyUKeH9kPLqyTkv8yKRphA.png" /><figcaption>It’s getting pricy out there.</figcaption></figure><p>The explosion of Defi has changed the value proposition of the idea of a “world computer”. In one vision the idea was that Ethereum would be populated by a rainbow of interesting diverse smart contracts deployed by a diverse array of actors all interested in leveraging decentralized compute.</p><p>The success of Defi has changed the narrative of Ethereum and brought new users interested in higher-value transactions who are willing to pay higher gas prices as a function of their transactions being more valuable and the speed of their confirmation being more important.</p><p>The introduction of the concept of <a href="https://www.forbes.com/sites/leeorshimron/2020/06/22/defi-yield-farmers-and-crypto-investors-are-raking-in-100-annualized-yields/#1cda7fbd5eb5">Yield Farming</a> as potentially the “new ICO” may only accelerate the rate at which Defi transactions consume the network.</p><p>The effect of a sustained gas price rise will push lower value transactions or non-monetary transactions off the main network (L1) as they become too expensive in Gas to justify.</p><p>While it would seem like layer two solutions (L2) would be ideal for these lower-value transactions, the majority of L2 solutions are currently engineered primarily (not exclusively) for “cheapFi”, or Cheaper Defi, and focus on things like high-speed, low-cost token transfers of some sort or another. Even Reddit Tokens I perceive as a kind of “cheapFi” where people are able to earn some sort of “equity share” in the “social capital” of being on Reddit. I am sure there will be ways to build non-Defi applications on Layer 2, but really I expect them to capture the interactions that individually aren’t valuable enough to compete with the gas fees of L1.</p><p>I expect that L1 will trend towards becoming a new kind of “interchange banking backbone” for soon to be extremely large and extremely valuable transactions.</p><h3>2: Application-specific blockchains instead of Layer 2</h3><p>For large non-Defi projects like CryptoKitties and Aragon, the incentive is to build an entirely new blockchain. The majority of L2 solutions on the market today are not community projects, but rather VC funded companies looking to capture the speculative value of an L2 project gaining market share.</p><p>Why should a project like Aragon bring its customer base to an L2 solution, only to have a different group of people capture the upside value of their audience? It makes more sense to build an entirely new blockchain so that value can be captured at both the protocol AND application layer. Hence we see Flow and Aragon chain. (They also built these blockchains to satisfy technical requirements that were important, but I think my point is still valid).</p><p>For smaller non-Defi projects, collectible tokens, small DAO’s, etc… It seems hard to imagine what the true value of an L2 solution will be. Technically they enable cheaper transactions with interoperability, but will interoperability with L1 be very important if it’s incredibly expensive? Why would users ever move their digital cat back to L1 if it costs a fortune to do so and when all the other digital cats are on the L2 layer anyway? It seems more likely that if Flow or AragonChain catch on for their respective use cases, they might simply each become the application-specific blockchains with Digital Cats and non-money-DAO’s leaving L1 Ethereum for good.</p><p>I don’t yet have an opinion on how ETH2.0 might change this dynamic.</p><h3>2: MetaTransactions and Wallet on Layer 1</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*VIUMyozs5gUpAnC-" /><figcaption>*Update* Argent has notified customers they will stop paying gas fees for Compound.</figcaption></figure><p>As great of a proponent of MetaTransactions as I have been, right now it seems like their near term future application is limited. Originally MetaTransactions was billed as the solution to user onboarding, for users who don’t have immediate access to Eth to pay for Gas or as a tool to allow users to pay in their native token or with credit cards.</p><p>As gas fees rise, customer acquisition cost becomes prohibitively expensive. One thought is to simply charge the user for their gas fees via credit cards, but if fees continue to rise we can quickly arrive at a point where no one is willing to cover the fee: neither the platform, nor the user, nor the wallet.</p><p>This again will most likely kill the non-Defi consumer-facing applications on Ethereum. Already popular composable applications such as <a href="https://qz.com/1239486/cryptokitties-are-racing-for-prize-money-on-the-ethereum-blockchain/">KittyRace</a>, which allowed you to pit your CryptoKitties against one another in a car race, <a href="https://kittyrace.com/">appear to be gone</a> but which would have been prohibitively expensive to use anyway.</p><p>On an infrastructure level, I am coming to think the appropriate layer for Meta transactions to live is at the <em>smart-contract wallet layer</em>. As the value of Defi increases so will the danger of incorporating dependencies into your codebase as a smart contract developer. I think this will lead projects to avoid building dependencies like MetaTransactions into their codebase because it makes their system fragile, and requires additional considerations regarding upgradability (to account for MetaTxn providers going out of business or being compromised, etc..) which itself brings substantial danger.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6VTHWc8cmHvsxmGt" /><figcaption>Wallet sponsorship deals?</figcaption></figure><p>The simpler solution is to simply recommend their users to use a specific smart-contract wallet, and if they want to subsidize their user’s gas fees, they can simply refund the wallet providers for their user’s transaction fees. This method completely insulates Defi protocols from dependencies on third parties and lets smart contract wallets focus on the security of their users while protocols focus on the security of their protocols.</p><p>However, if Defi becomes the primary use case of Ethereum, even this narrative seems to struggle. As the value of transactions goes up and the price of transactions goes up, the less likely applications on Ethereum are to be consumer-facing and the more cautious and experienced the users of Defi will become. How likely is it that users transacting large amounts of value on Ethereum will be comfortable using 3rd party wallet providers, especially smart contract wallet providers? And how likely is it that people willing to pay $100 to construct complex Defi schemes aren’t going to have the ETH to pay the gas?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*S5pK7wTtZ7CXLcgV" /><figcaption>$100 in gas. That&#39;s no joke.</figcaption></figure><p>It seems unlikely that 3rd party wallets have a compelling use case on L1 once the balance of a user’s account exceeds a certain threshold. This doesn’t mean they won’t have users, but it’s possible the vast majority of value is captured by a small number of high-end users who most likely can’t or won’t trust third parties for managing their funds.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CPnlIqXsQpJBBdiGLhfJcw.png" /><figcaption>Do these groups overlap?</figcaption></figure><h3>3. A shift in Topology: Developers</h3><p>For a number of years, Ethereum was Defined by smart contracts with limited complexity. Most tokens were relatively simple contracts and most applications were fairly simple to interact with.</p><p>The simplicity of working with Ethereum lead to a large number of developers interested in building in the space, and they built a variety of different types of projects and smart contracts.</p><p>As the composability of Defi increases, so does it’s complexity, and today interacting with popular smart contracts has become genuinely complicated. This professionalization of the space means that new developers are required to have a deeper understanding of financial primitives and a clearer idea of what they are interested in building. This specificity and complexity will accelerate the trend towards innovation in financial tools and will shift the accessibility of Ethereum away from general interest developers to more skill-specific and experienced developers with an interest in financial tools.</p><h3>4. A Shift in Topology: Protocol Diversity</h3><p>The sudden explosive growth of Compounds’ $COMP token implies a coming new opportunity for raising capital in non-traditional ways. What it also suggests is that the delta between the amount of value captured between protocols is also likely to significantly increase. As network effects begin to accumulate in specific protocols it starts to look like a very real possibility that a small number of Defi protocols on Ethereum will end up capturing the majority of value transacted on it. The composability of protocols will only accelerate the accumulation of network effects as base layer components become permanent base level components of new derived products. As liquidity begins to pool substantially in specific protocols/markets and the gas fee’s for aggregation of liquidity increase, L1 Ethereum will exist to support a small number of high-value protocols and transactions, with everything else pushed to L2 and beyond.</p><h3>My take away:</h3><p>I have come to the conclusion that in our near future Ethereum will start to look more and more like the backend infrastructure of a new kind of banking system. This is a good thing and means Ethereum is winning. I personally am a little nostalgic, because I think this means the new developers entering the space will be more professionals interested in custom tech solutions solving specific problems around financial innovation. I suspect it means fewer folks building wild experiments for new ways to organize society on Ethereum Layer 1 however.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eFxgDH_vDGIrhPKZeUlWng.png" /><figcaption>This feels unlikely as liquidity begets liquidity. But who knows…</figcaption></figure><p>Finally, I think most, if not all non-Defi, or non “value-first” applications will either leave for other blockchains, use layer two solutions, or potentially cease to exist. This isn’t necessarily a problem though, a natural evolution of technology and markets. For the time being it might make sense to focus resources on Layer 2 solutions and Defi services.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3b1d672d08bd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ZepKit + Skale Labs: Quickly build and deploy a DApp on an elastic sidechain.]]></title>
            <link>https://dennisonbertram.medium.com/zepkit-skale-labs-quickly-build-and-deploy-a-dapp-on-an-elastic-sidechain-265ef42075cb?source=rss-ce7746cc56ef------2</link>
            <guid isPermaLink="false">https://medium.com/p/265ef42075cb</guid>
            <category><![CDATA[zeppelinos]]></category>
            <category><![CDATA[zepkit]]></category>
            <category><![CDATA[openzeppelin]]></category>
            <category><![CDATA[ethereum]]></category>
            <dc:creator><![CDATA[Dennison Bertram]]></dc:creator>
            <pubDate>Wed, 19 Jun 2019 15:41:00 GMT</pubDate>
            <atom:updated>2019-06-19T15:41:00.909Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*W-hheQCIIvZSQ1UZjZYfXA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@polina_art?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Polina Rytova</a> on <a href="https://unsplash.com/search/photos/side-road?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>As developer advocate at <a href="https://zeppelinos.org/">Zeppelin</a> I am a huge fan of our product <a href="https://zepkit.zeppelinos.org/">ZepKit</a>, it allows developers to build out ethereum backed applications very quickly by abstracting away all the boiler plate necessary to get started. I’m constantly trying out new technologies to see what they feel like, how they work, and before ZepKit a lot of the effort that went into testing new things was boilerplate.</p><p>Not fun.</p><p>This tutorial is the start of what i hope to be a series of tutorials following my own experiments in the ecosystem of building on ZepKit with other products. I’d like to show developers how easy it is to test new products and technologies using ZepKit as the base to abstract away the huge amount of boiler plate that is usually required to get a project started.</p><p><strong>SkaleLabs and Elastic sidechains</strong></p><p>One of the technologies I have been keeping an eye on recently is <a href="https://skalelabs.com/">SkaleLabs</a>. The project offers <a href="https://medium.com/skale/getting-started-with-skale-part-1-5d6a025c95fd">elastic sidechains</a>, and even <a href="https://skalelabs.com/blog/skale_decentralized_storage/">EVM based storage</a>.</p><p>So naturally, I wanted to try it out with ZepKit. :-)</p><p>First you need to <em>GET</em> a Skale chain, for now you will need to request a custom endpoint as well as test Skale tokens.</p><p><a href="https://developers.skalelabs.com/getting-started">SKALE Developer Documentation</a></p><p>Next get <a href="https://docs.zeppelinos.org/docs/start.html#getting-started">ZeppelinOS</a>:</p><p><a href="https://github.com/zeppelinos/zos">zeppelinos/zos</a></p><p>npm install -g zos</p><p>(You don’t have to install it globally, but you’ll need to prefix commands with npx if you install locally. I prefer global for convenience. I’m just like that.)</p><p>Create and enter your directory:</p><p>mkdir SkaleKit</p><p>cd SkaleKit</p><p>Now unpack a brand new ZepKit.</p><p>zos unpack zepkit</p><p>Enter your truffle-config.json and alter it to add the SkaleEndpoint, privateKey, and your Skale chain network config information. It should look like this: (I’ve deleted the public ethereum networks that ZepKit comes pre-populated with, as we don’t need them for this demo)</p><pre>const path = require(&quot;path&quot;);</pre><pre>require(&#39;dotenv&#39;).config();</pre><pre>const mnemonic = process.env.MNENOMIC;</pre><pre>const HDWalletProvider = require(&quot;truffle-hdwallet-provider&quot;);</pre><pre>// Create your own key for Production environments (https://infura.io/)</pre><pre>const INFURA_ID = &#39;d6760e62b67f4937ba1ea2691046f06d&#39;;</pre><pre>let privateKey = &quot;[YOUR_PRIVATE_KEY]&quot;;</pre><pre>//Provide your SKALE endpoint address</pre><pre>let skale = &quot;[YOUR_SKALE_CHAIN_ENDPOINT]&quot;;</pre><pre>module.exports = {</pre><pre>// See &lt;http://truffleframework.com/docs/advanced/configuration&gt;</pre><pre>// to customize your Truffle configuration!</pre><pre>networks: {</pre><pre>development: {</pre><pre>host: &quot;127.0.0.1&quot;,</pre><pre>port: 8545,</pre><pre>network_id: &quot;*&quot;,</pre><pre>},</pre><pre>skale: {</pre><pre>provider: () =&gt; new HDWalletProvider(privateKey, skale),</pre><pre>gasPrice: 0,</pre><pre>network_id: &quot;*&quot;</pre><pre>}</pre><pre>}</pre><pre>};</pre><p>Now will need your <a href="https://developers.skalelabs.com/getting-started">Skale endpoint</a>, and the private key of your ethereum key pair that you will be using. Personally I normally keep a development Metamask around that I export my private key from to work with. This way once I have my project running, I can easily send/receive eth to my address without needing to use truffle console.</p><p>Lets create a simple contract:</p><pre>pragma solidity ^0.5.0;</pre><pre>contract HelloWorld {</pre><pre>event message(string message, address user, uint timestamp);</pre><pre>function postMessage(string memory _msg) public {</pre><pre>emit message(_msg, msg.sender, now);</pre><pre>}</pre><pre>}</pre><p>This is a stateless contract, all it does is emit messages in logs. It’s fine to get started. I got the idea awhile ago from <a href="https://medium.com/@childsmaidment/stateless-smart-contracts-21830b0cd1b6">Peepeth</a>.</p><p>Lets initialize our zos project:</p><p>zos init skale</p><p>and start a session:</p><p>zos session --network skale</p><p>then we add our HelloWorld contract:</p><p>zos add HelloWorld</p><p>and push it to our Skale chain:</p><p>zos push</p><p>You should see the following output from the console: (with a different sender address)</p><pre>Compiling contracts with Truffle...</pre><pre>Compiling your contracts...<br>===========================<br>&gt; Compiling ./contracts/HelloWorld.sol<br>&gt; Artifacts written to /Users/dennison/Documents/SkaleKit/build/contracts<br>&gt; Compiled successfully using:<br>   - solc: 0.5.8+commit.23d335f2.Emscripten.clang</pre><pre>Using session with network skale, sender address 0xC2cE5805dDCa1287435fF41c5f2eF5ef93BaeC43, timeout 3600 seconds<br>Validating contract HelloWorld<br>Uploading HelloWorld contract as HelloWorld<br>Deploying logic contract for HelloWorld<br>Created zos.mainnet.json</pre><p>Now let’s create an instance of our contract:</p><p>zos create HelloWorld</p><p>Hopefully that went well and you were like, “Whoa, easy!”. Keep a note of the address that zos returns, we will need it handy.</p><p>So now that we have an upgradable contract (thanks zos! ) published to our own Skale sidechain (cool!), let us enter truffle console to test it before we head to our front-end.</p><p>truffle console --network skale</p><p>let instance = await HelloWorld.at(&#39;&lt;&lt;that address you were keeping handy&gt;&gt;&#39;)</p><p>Lets get some accounts ready:</p><p>let accounts = await web3.eth.getAccounts()</p><p>let account = accounts[0]</p><p>So try to send a message!</p><p>let tx = await instance.postMessage(&quot;Hello World!&quot;)</p><p>Now lets look at that transaction:</p><p>tx</p><p>This will list the transaction, but lets see just our message:</p><p>tx.logs[0].args.message</p><p>The result should be:</p><p>&#39;Hello World!&#39;</p><p>It works! Sidechain chatting galore! (okay, maybe not just yet)</p><h3>The Front End</h3><p>Let’s head over to our front end. I’ve prepared basic ‘chat application’ that I use as a quick example, you can clone the entire project here:</p><p><a href="https://github.com/crazyrabbitLTC/Skale-ZepKit">https://github.com/crazyrabbitLTC/Skale-ZepKit</a></p><p>Enter into your client folder and:</p><p>npm run start</p><p>This will start up your client server. First step is to make sure MetaMask is connected to your SkaleEndpoint our sidechain is an <a href="https://medium.com/skale/getting-started-with-skale-part-1-5d6a025c95fd">entirely different network </a>so we need to connect to it like it’s a new network.</p><p>Once you point MetaMask to the right network, refresh the page and you should see your application pop up.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/886/1*iVV2n5k6CyZ8HR1zi16W-A.png" /><figcaption>Simple, but effective.</figcaption></figure><p>If you make a transaction, you’ll need to confirm with MetaMask as usual. Your MetaMask address will need to have Skale Eth however and will need to request test eth from the <a href="http://faucet.skalelabs.com/">Skale Eth Faucet</a>.</p><p>On the front end, I haven’t made too many changes to the stock ZepKit App.js file. I have imported the contract artifact and made sure componentDidMount creates an instance of the contract and sets it on state. Then my various component manage the interface of the chat application itself. Feel free to poke around, it’s pretty easy.</p><p>If I continue this tutorial, I’ll look into using Skale’s native EVM storage, but I’ll save that for next time!</p><p>Learn more:</p><p><a href="https://forum.zeppelin.solutions/">Join us in the forum</a></p><p>Learn about <a href="https://zepkit.zeppelinos.org/">Zepkit</a></p><p>Learn about <a href="https://zeppelinos.org/">ZeppelinOS</a></p><p>Learn about <a href="https://skalelabs.com/">Skale labs</a></p><p>-Dennison</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=265ef42075cb" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>