<?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>happyhourDAO (🍸,🍸)</title>
        <link>https://paragraph.com/@happyhourlabs</link>
        <description>A community owned Drink-To-Earn decentralized network for web3.</description>
        <lastBuildDate>Sun, 10 May 2026 20:41:29 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>https://github.com/jpmonette/feed</generator>
        <language>en</language>
        <image>
            <title>happyhourDAO (🍸,🍸)</title>
            <url>https://storage.googleapis.com/papyrus_images/949b29310e164af0f4324d1e8595d5d8f038c0be43506fabdcca68f192535174.png</url>
            <link>https://paragraph.com/@happyhourlabs</link>
        </image>
        <copyright>All rights reserved</copyright>
        <item>
            <title><![CDATA[The F&B industry is broken]]></title>
            <link>https://paragraph.com/@happyhourlabs/the-f-b-industry-is-broken</link>
            <guid>VPuJcD0i1vfAX8ZtqoJs</guid>
            <pubDate>Tue, 17 Oct 2023 05:48:00 GMT</pubDate>
            <description><![CDATA[Transforming the F&B and Nightlife Industry: The Web3 Revolution In the era of digital innovation, our traditional industries are facing unprecedented challenges, and none more so than the Food and Beverage (F&B) and nightlife sector. The rise of Web3 technologies offers a revolutionary solution to revitalize and reshape an industry that has long been perceived as outdated. Let&apos;s delve into the reasons why the current state of F&B and nightlife is seen as broken and explore how Web3 can ...]]></description>
            <content:encoded><![CDATA[<p><strong>Transforming the F&amp;B and Nightlife Industry: The Web3 Revolution</strong></p><p>In the era of digital innovation, our traditional industries are facing unprecedented challenges, and none more so than the Food and Beverage (F&amp;B) and nightlife sector. The rise of Web3 technologies offers a revolutionary solution to revitalize and reshape an industry that has long been perceived as outdated. Let&apos;s delve into the reasons why the current state of F&amp;B and nightlife is seen as broken and explore how Web3 can be the key to its survival and prosperity.</p><p><strong>The Broken System</strong></p><ul><li><p><strong>High Costs and Margins</strong>: Running a restaurant or a nightlife establishment is notoriously expensive. High rents, staffing costs, and operational expenses often translate into higher menu prices. This, in turn, limits accessibility and can hinder growth.</p></li><li><p><strong>Middlemen and Excessive Fees</strong>: Intermediaries, such as food delivery platforms, often charge hefty commissions, leaving both customers and businesses paying more. These platforms control a significant portion of the market, limiting the choices for consumers and restricting the profitability of establishments.</p></li><li><p><strong>Lack of Transparency</strong>: Customers often have limited visibility into the supply chain of the F&amp;B industry. Questions about the origin of ingredients, ethical practices, and sustainability often go unanswered.</p></li><li><p><strong>Dependency on Reviews</strong>: The industry relies heavily on centralized review platforms, which can sometimes be manipulated or biased. Authentic customer feedback can get lost in the noise, making it challenging for consumers to make informed decisions.</p></li></ul><p><strong>The Web3 Solution</strong></p><ul><li><p><strong>Decentralization</strong>: Web3 introduces decentralized systems that operate without a central authority. Applying this to the F&amp;B industry can eliminate unnecessary intermediaries, reducing costs for both businesses and consumers.</p></li><li><p><strong>Smart Contracts for Fair Transactions</strong>: Through smart contracts, transactions can be executed automatically when predefined conditions are met. This ensures that businesses get paid promptly, and consumers are guaranteed the services they pay for, reducing disputes and fraud.</p></li><li><p><strong>Tokenized Incentives</strong>: Introducing a token economy can incentivize customer loyalty. Restaurants and nightlife establishments can create their own tokens that customers can earn through purchases, referrals, or engagement. These tokens can then be redeemed for discounts, special events, or even exclusive menu items.</p></li><li><p><strong>Supply Chain Transparency with Blockchain</strong>: Blockchain technology can provide a transparent and traceable supply chain. Customers can verify the origin and quality of ingredients, promoting trust and ethical practices.</p></li><li><p><strong>Community Governance</strong>: Web3 allows for decentralized autonomous organizations (DAOs) where stakeholders have a say in decision-making processes. In the F&amp;B industry, this could mean involving both customers and employees in crucial decisions, fostering a sense of community.</p></li><li><p><strong>NFTs for Unique Experiences</strong>: Non-fungible tokens (NFTs) can be used to create unique experiences or memberships for customers. This could include exclusive events, virtual tastings, or limited edition menu items, adding a new layer of excitement to the dining and nightlife experience.</p></li></ul><p><strong>Conclusion</strong></p><p>The F&amp;B and nightlife industry is ripe for disruption, and the advent of Web3 technologies provides a unique opportunity for its transformation. Decentralization, transparency, and tokenization can breathe new life into an industry burdened by legacy systems. As we embrace the future, envision a world where your favorite restaurant is not just a place to dine but a community-driven entity, and where the nightlife experience goes beyond the physical walls of a club. Web3 is not just a technological upgrade; it&apos;s a promise of a more inclusive, transparent, and exciting future for the F&amp;B and nightlife scene. The time to embrace this revolution is now.</p>]]></content:encoded>
            <author>happyhourlabs@newsletter.paragraph.com (happyhourDAO (🍸,🍸))</author>
        </item>
        <item>
            <title><![CDATA[ELI5: What is happyhourDAO?]]></title>
            <link>https://paragraph.com/@happyhourlabs/eli5-what-is-happyhourdao</link>
            <guid>keDrtishRxpudmazpZ7H</guid>
            <pubDate>Wed, 05 Apr 2023 13:40:16 GMT</pubDate>
            <description><![CDATA[What the hell is happyhourDAO? What the hell is Drink-To-Earn? What the hell is the $HOUR token and $DRNK token? Your questions answered below in an easy to digest read. No code shown. Just simple to read words.What is the purpose of happyhourDAO?The happyhourDAO aims to provide an open, web3 community connecting the post-pandemic recovering F&B industry with plebs in the metaverse through its native ERC20 token, $HOUR. Not only do drinkers and F&B merchants have the opportunity to earn from ...]]></description>
            <content:encoded><![CDATA[<p>What the hell is happyhourDAO?</p><p>What the hell is Drink-To-Earn?</p><p>What the hell is the $HOUR token and $DRNK token?</p><p>Your questions answered below in an easy to digest read. No code shown. Just simple to read words.</p><h2 id="h-what-is-the-purpose-of-happyhourdao" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">What is the purpose of happyhourDAO?</h2><p>The happyhourDAO aims to provide an open, web3 community connecting the post-pandemic recovering F&amp;B industry with plebs in the metaverse through its native ERC20 token, $HOUR. Not only do drinkers and F&amp;B merchants have the opportunity to earn from their engagement in the traditional social gathering we sometimes coin as &quot;happy hour&quot;, but also to provision a grassroots fundraising network in envisioning what the new F&amp;B industry should look like. It shouldn’t be that people have earned the right to attend happy hour from their relentless hard work they put in at the office, but rather their happy hour attendance should also be rewarded.</p><h3 id="h-what-weve-been-seeing" class="text-2xl font-header !mt-6 !mb-4 first:!mt-0 first:!mb-0">What we’ve been seeing…</h3><p>Food &amp; Beverage (F&amp;B) establishments have been hit hard during the past 2 years of the global pandemic. Many were shuttered in the face of government imposed lockdowns and social distancing measures. The usual bar goers resorted to at-home drinking with many setting up their own makeshift bar to emulate the feeling of going out. The customary happy hour slowly faded away as friends and colleagues were no longer able to drink together in person and enjoy one’s company.</p><p>But as we see the global economy slowly opening back up with pandemic restrictions becoming obsolete, people are starting to go back to normal. But it’s not the same anymore. Favorite bars and nightlife venues are no longer around. It’s safe to say the F&amp;B industry is still struggling.</p><p>What is needed is a modern incentive to connect post-pandemic F&amp;B establishments to the new post-pandemic modern drinker. What is needed is an infinite positive feedback loop between happy hour goers and F&amp;B establishments through cryptography.</p><p>The new modern happy hour goers need the incentive to hit the bars again…</p><p>…and the same can be said for those bars themselves.</p><p>In this community, we propose a solution to the lack of incentive for engaging in the once blissful, customary happy hour and to further web3 adoption amongst F&amp;B merchants so that any future arbitrary lockdowns won’t affect their cash flows ever again. Because every web2 bar needs itself a web3 bar.</p><h3 id="h-what-we-envision" class="text-2xl font-header !mt-6 !mb-4 first:!mt-0 first:!mb-0">What we envision…</h3><p><strong>$HOUR being the official currency within the global F&amp;B industry.</strong></p><p>The global F&amp;B industry has traditionally been a fragmented market for obvious purposes. Brick and mortar bars, clubs, and restaurants only serve their local markets. But what if these same businesses can conduct transactions with other customers not served in their local markets? Could there be an incentive system devised so that the same local F&amp;B merchants can sell their specialty tastes as a white label to other F&amp;B merchants located across the globe from them? Could there be a payment network allowing drifters and travelers to still be able to buy a drink at spot in a foreign country without having to exchange for the local fiat currency? Could there be a method to get on a premier whitelist for a new club opening party just by depositing a certain amount of tokens to an address instantly? Could there be a way for you and your friends to reserve your favorite table at the city&apos;s hottest rooftop lounge without the uncertainty of a no show for the lounge? The architecture of the $HOUR token was designed and engineered to fill those needs posed above in a seamless, efficient, web3 manner. Whether it be used for loyalty tokens, membership tokens, reservations, payments, bottle deposits, or etc., $HOUR is represented to allow all F&amp;B merchants to speak the same language, regardless of geographic region/culture. We all want to enjoy the good times with our friends. We all don&apos;t want to have to worry about small nuances and friction that come along with a night of drinking. We all just want to be able to kick back at happy hour.</p><p><strong>An open, organic DAO community for web3 natives interested in raising strategic investments/funding for their local F&amp;B merchants.</strong></p><p>The demographics of web3 are statistically skewed towards the millennial generation with some outliers in the Gen X and Gen Z. This demographic do have a high tendency in the outgoing lifestyle of being the club-goer and trendy nightlife chaser. There is a huge connection between web3/crypto natives and the F&amp;B industry. The population is changing and new expectations from the F&amp;B industry need to be able to adapt to what new market demands call for. Millennials are reshaping the food and beverage scene and these establishments need to be able to resonate with what they want and their own technological behavior.</p><p>The traditional music-based entertainment bars aren&apos;t cutting it these days for millennials. They yearn for something more interactive and engaging. Social media has been shaping the way millennials frequent bars as they seek the most eye popping aesthetic bar as there way of deciding on bar stops. The millennial population is altering and expanding the very definition of entertainment for bars. Some bars has transformed into a paint and sip classroom…or even a yoga studio.</p><p>But unfortunately, we see time and time again our favorite bars shutting down. This was especially true during the pandemic era. But as we see the economy open back up again, why not give more empowerment to the bar goers to decide on what F&amp;B merchants need financial help and what new F&amp;B merchants can they invest in. This is what the happyhourDAO is positioned to be. An open, organic DAO community for web3 natives interested in raising strategic investments/funding for their local F&amp;B merchants. Giving millennials and web3 natives more of a say in what they want to see in the F&amp;B scene.</p><p><strong>An increased adoption of web3 by the F&amp;B industry and a push for those same F&amp;B merchants in galvanizing their digital representation in the metaverse.</strong></p><p>There&apos;s no doubt that the emerging metaverse, which the term itself has already been around for many years, is now recently starting to becoming a reality due to many technological factors maturing and coming together. The crux of it all is the decentralized blockchain technology which presumably makes the metaverse less controlled by a certain entity.</p><p>Just as significant a factor in the metaverse trend is the coronavirus pandemic, which has radically altered lifestyles across the planet. With people spending so long in Zoom meetings for work, and with soaring use of video games as people seek to enter more colorful and exciting environments without leaving the comfort and safety of their homes, it’s natural for tech companies to look for ways to capitalize on the situation by bridging these two needs.</p><p>Traditional companies and industry have already entered the space with a splash. Everything thing from fashion, to beauty tech, to sports, and etc. have already created some form of their brand in the metaverse. Virtual 3D worlds such as Decentraland and SandBox have been popular metaverse structures allowing the random web3 native to take stroll through a new world.</p><p>It&apos;s time for the F&amp;B industry to also cross the chasm into the metaverse. Giving metaverse-goers a chance to enter their digital representation as a virtual club or restaurant will not only be good business, but also good for brand exposure. Wouldn&apos;t you want to have your self-avatar virtually visit your favorite bar in the metaverse?</p><h2 id="h-how-to-get-involved-in-happyhourdao" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">How to get involved in happyhourDAO?</h2><p>The happyhourDAO will be powered by the Happy Hour Protocol Engine, which is the heart and soul of the whole ecosystem. This is what will glue together the drinkers, Participating Drinking Establishments (PDEs), devs, investors, and other stakeholders. All the interaction will be done through the Happy Hour Protocol Engine which will be deployed as a smart contract on the Ethereum network.</p><p>Breakdown of participants in the happyhourDAO ecosystem:</p><ul><li><p><strong><em>Drinkers (holders of $HOUR):</em></strong>* These are the users and community members interacting with the Happy Hour Protocol Engine. These are the happy hour goers, nightlife fist-pumpers, bartenders, and all other alcoholics who make it a priority to support the F&amp;B industry.*</p></li><li><p><strong><em>Participating Drinking Establishments (PDE):</em></strong>* These are the F&amp;B merchants and businesses hosting drinkers. The local bar, the city’s premier club, the skyline lounge, the speakeasy, the hotel restaurant, and etc. All these F&amp;B merchants would be considered a PDE in the happyhourDAO ecosystem.*</p></li><li><p><strong><em>Drunkards (holders of $DRNK):</em></strong>* These are the all-star drinkers who have been able to accumulate enough $HOUR tokens to burn and mint $DRNK tokens, which fully enable them to be official members of the happyhourDAO.*</p></li></ul><p>F&amp;B merchants are at the brink of something new with web3. The happyhourDAO is in position to ready traditional F&amp;B brick and mortar merchants in participating in the internet’s next frontier. The Happy Hour Protocol Engine is geared up with provisions with an open and permissionless onboarding for F&amp;B merchants to be valid PDEs. Each PDEs in the network are eligible for a % of HOUR earned by every drinker. This % rate will start at 10% with the ability for future alterations based on the community’s decisions.</p><p>As a PDE grows in popularity in the network, the happyhourDAO is positioned to further fund that PDE in applicable business aspects the community seems viable. This funding also includes support for web3 onboarding into metaverse realms such as in Decentraland, The Sandbox, Otherside, and others.</p><h2 id="h-who-are-the-drinkers" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">Who are the Drinkers?</h2><p>The local dive bar goer, the fist pumping clubber, the high class fancy rooftop lounger, or the occasional casual drinker, this is the DAO for you.</p><p>Drinkers (holders of $HOUR): These are the users and community members interacting with the Happy Hour Protocol Engine. These are the happy hour goers, nightlife fist-pumpers, bartenders, and all other alcoholics who make it a priority to support the F&amp;B industry.</p><p>Simply locate a PDE, stake 0.01 ETH, input the PDE’s ID &amp; access code via the happyhourDAO virtual interface (aka app), and start earning $HOUR by the hour. It’s that simple.</p><h2 id="h-what-is-the-purpose-of-dollarhour" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">What is the purpose of $HOUR?</h2><p>Based on real-time hours spent at happy hour, drinkers can earn $HOUR tokens via the Happy Hour Protocol Engine. In exchange, these earned $HOUR tokens have a multi-functional utility such as being able to use those $HOUR tokens in purchasing discounted beverages at participating bars/nightclubs. They also can allow drinkers to exchange them into other tokens of their choosing. And with the metaverse spawning nightlife entrepreneurs to take their venues digitally online, $HOUR tokens can also be used at those web3 nightlife venues.</p><p>We envision the novel Drink-To-Earn model as an infinite positive feedback loop. As drinkers earn $HOUR by the hour, drinking establishments can earn a commission of the $HOUR earned by drinker. Freshly earned $HOUR tokens can then be used at other participating drinking establishments in purchasing deeply discounted drinks or to be burned to earn the happyhourDAO’s governance token, $DRNK.</p><p>The $HOUR token will conduct a fair launch with zero issuance at contract deployment. Issuance rate will vary based on network growth and $HOUR earned. The ratios of both $HOUR/hour and $HOUR to $DRNK burn minimum threshold will all be adjustable based on the consensus of the community’s outlook.</p><h2 id="h-who-are-the-pdes" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">Who are the PDEs?</h2><p>The local bar, the city’s premier club, the skyline lounge, the speakeasy, the hotel restaurant, and etc.</p><p>Participating Drinking Establishments (PDE): These are the F&amp;B merchants and businesses hosting drinkers. The local bar, the city’s premier club, the skyline lounge, the speakeasy, the hotel restaurant, and etc. All these F&amp;B merchants would be considered a PDE in the happyhourDAO ecosystem.</p><h2 id="h-and-what-about-that-dollardrnk-token" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">And what about that $DRNK token?</h2><p>The $DRNK governance token is the official membership token of the happyhourDAO. Any amount of $DRNK governance token will be accepted and considered sufficient to be part of the happyhourDAO. The larger amount of $DRNK governance tokens owned allows for a larger percentage of influence you can have on any happyhourDAO participation. The below outlines the types of privileges and events you can participate in.</p><h2 id="h-whats-the-end-goal-of-happyhourdao" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">What’s the end goal of happyhourDAO?</h2><p>The ultimate goal of the happyhourDAO is to facilitate a healthy ecosystem between web3 users and real world F&amp;B partners, or what we will refer to as PDEs. The model of Drink-To-Earn is not to solely encourage endless amounts of drinking, but rather a healthy and rewarding experience while attending happy hour events. This reward also needs to be mirrored by the PDEs as well and encourage improvement in business by the PDE.</p><p>The happyhourDAO VC venture aims to foster the ecosystem of PDEs as well as encourage and onboard web3 adoption amongst these merchants. Their business model shouldn’t just be limited to the four walls they are grounded in.</p><p>The happyhourDAO VC will be grounded in 3 pillars:</p><ol><li><p><em>Fostering the new re-envisioned modern F&amp;B industry</em></p></li><li><p><em>Supporting pandemic stricken F&amp;B merchants</em></p></li><li><p><em>Advising F&amp;B merchants on web3 development</em></p></li></ol><h2 id="h-wen-airdrop" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">Wen airdrop?</h2><p>There is none.</p><p>Start earning $HOUR yourself by getting #LITT at your next happy hour.</p><hr><p>The Random House Dictionary of American Slang dates “Happy hour,” as a term for afternoon drinks in a bar, to a Saturday Evening Post article on military life in 1959. The article detailed the lives of government contractors and military personnel who worked at missile-tracking facilities in the Caribbean and the Atlantic. “Except for those who spend too much during ‘happy hour’ at the bar — and there are few of these — the money mounts up fast.”</p><p>Happy-hour-goers shouldn’t always have to feel bad when splurging their money at the bar, let alone seeing the result of rounds and rounds of shots. They deserve incentives for just being able to live and be merry. The $HOUR token is that incentive for happy-hour-goers and all types of drinking establishments. Let’s aim to bring this untapped demographic to web3.</p><p>Let’s bring happy hour to the metaverse.</p>]]></content:encoded>
            <author>happyhourlabs@newsletter.paragraph.com (happyhourDAO (🍸,🍸))</author>
        </item>
        <item>
            <title><![CDATA[Drink-To-Earn]]></title>
            <link>https://paragraph.com/@happyhourlabs/drink-to-earn</link>
            <guid>4wznSoTHFS9UGPPreZr3</guid>
            <pubDate>Sun, 12 Mar 2023 11:02:33 GMT</pubDate>
            <description><![CDATA[Self-explanatory enough?]]></description>
            <content:encoded><![CDATA[<p>Self-explanatory enough?</p>]]></content:encoded>
            <author>happyhourlabs@newsletter.paragraph.com (happyhourDAO (🍸,🍸))</author>
        </item>
        <item>
            <title><![CDATA[F&B 2 PDE.]]></title>
            <link>https://paragraph.com/@happyhourlabs/f-b-2-pde</link>
            <guid>FWTbttaqbIG2X3Wnggij</guid>
            <pubDate>Wed, 08 Mar 2023 13:06:25 GMT</pubDate>
            <description><![CDATA[What does it take to morph your F&B spot into a virtual establishment on the happyhourDAO Drink-To-Earn network? How can you branch into the spawning web3 world and tap into new market strategies by leveraging the metaverse, NFTs, and much more? How can you prep your F&B brick & mortar spot for the next global pandemic? Become a PDE. But wtf is a PDE?! Participating Drinking Establishments (PDE): These are the F&B merchants and businesses hosting drinkers. The local bar, the city’s premier cl...]]></description>
            <content:encoded><![CDATA[<p>What does it take to morph your F&amp;B spot into a virtual establishment on the happyhourDAO Drink-To-Earn network?</p><p>How can you branch into the spawning web3 world and tap into new market strategies by leveraging the metaverse, NFTs, and much more?</p><p>How can you prep your F&amp;B brick &amp; mortar spot for the next global pandemic?</p><p>Become a PDE.</p><p>But wtf is a PDE?!</p><p><strong>Participating Drinking Establishments (PDE)</strong>: These are the F&amp;B merchants and businesses hosting drinkers. The local bar, the city’s premier club, the skyline lounge, the speakeasy, the hotel restaurant, and etc. All these F&amp;B merchants would be considered a PDE in the happyhourDAO ecosystem.</p><p>By onboarding your F&amp;B location as a PDE, you now open the doors for patrons and Drinkers to step inside your physical location and earn the $HOUR token. As they earn $HOUR, you also earn a commission rate from their earnings. It’s a two way street in this relationship with yourself and your patrons.</p><p>Drinkers simply need to know your PDE ID and access code upon arrival of your location in order to start an eligible LITT session, earning $HOUR by the hour.</p><p>The $HOUR token, as is being dubbed web3’s big Drink-To-Earn token, will empower all F&amp;B spots to embrace the decentralized movement of digital economics. The benefits of the $HOUR token is too much to cram into this explainer, but you can imagine it being the digital currency for F&amp;B activity on and offline.</p><hr><h2 id="h-a-technical-breakdown-of-a-pde" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">A technical breakdown of a PDE.</h2><p><em>Architectural structure of a PDE.</em></p><pre data-type="codeBlock" text="    struct PDE {
        string _name;
        string _location;
        address _address;
        uint _accessCode;
        uint _PDEid;
    }

    PDE[] public pdes;

    mapping (uint =&gt; address) public PDEtoOwner;
"><code>    <span class="hljs-keyword">struct</span> <span class="hljs-title">PDE</span> {
        <span class="hljs-keyword">string</span> _name;
        <span class="hljs-keyword">string</span> _location;
        <span class="hljs-keyword">address</span> _address;
        <span class="hljs-keyword">uint</span> _accessCode;
        <span class="hljs-keyword">uint</span> _PDEid;
    }

    PDE[] <span class="hljs-keyword">public</span> pdes;

    <span class="hljs-keyword">mapping</span> (<span class="hljs-keyword">uint</span> <span class="hljs-operator">=</span><span class="hljs-operator">></span> <span class="hljs-keyword">address</span>) <span class="hljs-keyword">public</span> PDEtoOwner;
</code></pre><p><em>Public onboarding function for PDE. Name, Location, ETH address, and a temporary Access Code are required.</em></p><pre data-type="codeBlock" text="    function onboardPDE(string memory _name, string memory _location, address _address, uint _accessCode) public {
        uint PDEid = uint(keccak256(abi.encodePacked(_name, _location, _address)));
        pdes.push(PDE(_name, _location, _address, _accessCode, PDEid));
        uint PDEindexNum = pdes.length - 1;
        PDEtoOwner[PDEindexNum] = msg.sender;
        emit newPDEonboarded(_name, _location, _address, PDEid, PDEindexNum, _accessCode);
    }
"><code>    <span class="hljs-function"><span class="hljs-keyword">function</span> <span class="hljs-title">onboardPDE</span>(<span class="hljs-params"><span class="hljs-keyword">string</span> <span class="hljs-keyword">memory</span> _name, <span class="hljs-keyword">string</span> <span class="hljs-keyword">memory</span> _location, <span class="hljs-keyword">address</span> _address, <span class="hljs-keyword">uint</span> _accessCode</span>) <span class="hljs-title"><span class="hljs-keyword">public</span></span> </span>{
        <span class="hljs-keyword">uint</span> PDEid <span class="hljs-operator">=</span> <span class="hljs-keyword">uint</span>(<span class="hljs-built_in">keccak256</span>(<span class="hljs-built_in">abi</span>.<span class="hljs-built_in">encodePacked</span>(_name, _location, _address)));
        pdes.<span class="hljs-built_in">push</span>(PDE(_name, _location, _address, _accessCode, PDEid));
        <span class="hljs-keyword">uint</span> PDEindexNum <span class="hljs-operator">=</span> pdes.<span class="hljs-built_in">length</span> <span class="hljs-operator">-</span> <span class="hljs-number">1</span>;
        PDEtoOwner[PDEindexNum] <span class="hljs-operator">=</span> <span class="hljs-built_in">msg</span>.<span class="hljs-built_in">sender</span>;
        <span class="hljs-keyword">emit</span> newPDEonboarded(_name, _location, _address, PDEid, PDEindexNum, _accessCode);
    }
</code></pre><p><em>Every new PDE will fire a new event on-chain.</em></p><pre data-type="codeBlock" text="event newPDEonboarded(string _name, string _location, address _address, uint _PDEid, uint PDEindexNum, uint accessCode);
"><code><span class="hljs-function"><span class="hljs-keyword">event</span> <span class="hljs-title">newPDEonboarded</span>(<span class="hljs-params"><span class="hljs-keyword">string</span> _name, <span class="hljs-keyword">string</span> _location, <span class="hljs-keyword">address</span> _address, <span class="hljs-keyword">uint</span> _PDEid, <span class="hljs-keyword">uint</span> PDEindexNum, <span class="hljs-keyword">uint</span> accessCode</span>)</span>;
</code></pre><p><em>Enables PDEs to change their Access Code anytime.</em></p><pre data-type="codeBlock" text="    function _changeAccessCode(uint _PDEindexNum, uint _newAccessCode) public {
        require(PDEtoOwner[_PDEindexNum] == msg.sender);
        pdes[_PDEindexNum]._accessCode = _newAccessCode;
    }
"><code>    <span class="hljs-function"><span class="hljs-keyword">function</span> <span class="hljs-title">_changeAccessCode</span>(<span class="hljs-params"><span class="hljs-keyword">uint</span> _PDEindexNum, <span class="hljs-keyword">uint</span> _newAccessCode</span>) <span class="hljs-title"><span class="hljs-keyword">public</span></span> </span>{
        <span class="hljs-built_in">require</span>(PDEtoOwner[_PDEindexNum] <span class="hljs-operator">=</span><span class="hljs-operator">=</span> <span class="hljs-built_in">msg</span>.<span class="hljs-built_in">sender</span>);
        pdes[_PDEindexNum]._accessCode <span class="hljs-operator">=</span> _newAccessCode;
    }
</code></pre><p><em>Tracking live commissions earned by PDEs.</em></p><pre data-type="codeBlock" text="event endHOURresults(uint hoursSpentDrinking, uint HOURearned, uint PDEcommissionEarned, uint PDEindex);
"><code><span class="hljs-function"><span class="hljs-keyword">event</span> <span class="hljs-title">endHOURresults</span>(<span class="hljs-params"><span class="hljs-built_in">uint</span> hoursSpentDrinking, <span class="hljs-built_in">uint</span> HOURearned, <span class="hljs-built_in">uint</span> PDEcommissionEarned, <span class="hljs-built_in">uint</span> PDEindex</span>)</span>;
</code></pre><p><em>Querying for the total amount of PDEs in the network.</em></p><pre data-type="codeBlock" text="    function totalPDE() public view returns (uint) {
        return pdes.length;
    }
"><code>    <span class="hljs-function"><span class="hljs-keyword">function</span> <span class="hljs-title">totalPDE</span>(<span class="hljs-params"></span>) <span class="hljs-title"><span class="hljs-keyword">public</span></span> <span class="hljs-title"><span class="hljs-keyword">view</span></span> <span class="hljs-title"><span class="hljs-keyword">returns</span></span> (<span class="hljs-params"><span class="hljs-keyword">uint</span></span>) </span>{
        <span class="hljs-keyword">return</span> pdes.<span class="hljs-built_in">length</span>;
    }
</code></pre><p>All contract methods listed above are now available on mainnet.</p><hr><h2 id="h-the-logical-web3-pathway-for-an-fandb-merchant" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">The logical web3 pathway for an F&amp;B merchant</h2><p>Where do we envision F&amp;B merchants evolving into? For decades, F&amp;B merchants have been siloed by their own physical brick &amp; mortar. Sure many have adopted digital marketing and influencer marketing. But taking the next leap into the decentralized web3 world is a no-brainer and an obvious untapped market to be looked into.</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://storage.googleapis.com/papyrus_images/d31bd836fea2b00a9cb8549a036f8243610929f5e20c938a00295af1ec150ffa.png" alt="" blurdataurl="data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=" nextheight="600" nextwidth="800" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="hide-figcaption"></figcaption></figure><p>F&amp;B merchants are at the brink of something new with web3. The happyhourDAO is in position to ready traditional F&amp;B brick and mortar merchants in participating in the internet’s next frontier. The Happy Hour Protocol Engine is geared up with provisions with an open and permissionless onboarding for F&amp;B merchants to be valid PDEs. Each PDEs in the network are eligible for a % of HOUR earned by every drinker. This % rate will start at 10% with the ability for future alterations based on the community’s decisions.</p><p>As a PDE grows in popularity in the network, the happyhourDAO is positioned to further fund that PDE in applicable business aspects the community seems viable. This funding also includes support for web3 onboarding into metaverse realms such as in Decentraland, The Sandbox, Otherside, and others.</p><p>Cheers.</p>]]></content:encoded>
            <author>happyhourlabs@newsletter.paragraph.com (happyhourDAO (🍸,🍸))</author>
        </item>
        <item>
            <title><![CDATA[The Anatomy of Getting LITT.]]></title>
            <link>https://paragraph.com/@happyhourlabs/the-anatomy-of-getting-litt</link>
            <guid>fprWCKVMxn2TIPTWXrX2</guid>
            <pubDate>Mon, 06 Mar 2023 14:40:17 GMT</pubDate>
            <description><![CDATA[As we embark on mainnet, it is only our duty to explain in more detail how one can earn the $HOUR token during their precious happy hour moments. After all, there’s got to be something you can get in return during happy hour besides throwing dough on shot after shot and getting wasted. Think of the $HOUR token as your reward for partaking in happy hour. In order to starting earning $HOUR, you must start a LITT session, or better phrased as: Getting LITT. What does LITT stand for?Latent Initia...]]></description>
            <content:encoded><![CDATA[<p>As we embark on mainnet, it is only our duty to explain in more detail how one can earn the $HOUR token during their precious happy hour moments. After all, there’s got to be something you can get in return during happy hour besides throwing dough on shot after shot and getting wasted.</p><p>Think of the $HOUR token as your reward for partaking in happy hour.</p><p>In order to starting earning $HOUR, you must start a LITT session, or better phrased as:</p><p><em>Getting LITT.</em></p><p>What does LITT stand for?</p><h3 id="h-latent-initialization-of-token-truss-litt" class="text-2xl font-header !mt-6 !mb-4 first:!mt-0 first:!mb-0">Latent Initialization of Token Truss (LITT)</h3><p>In simplest terms, getting LITT doesn’t start until a Drinker initiates a LITT session at a PDE.</p><p>We’re sure everyone is familiar with the concept of staking and POS chains. Staking is when token holders pledge a certain quantity of tokens to the protocol to be selected as validators for the blockchain and validate transactions. The validators would receive staking rewards from the new tokens minted from new blocks and the POS chain gets network security from the validator community. </p><p>The happyhourDAO decided to take things to the next level with Latent Initialization of Token Truss (LITT) model of staking. LITT describes the pre-manifested state of staking when the drinkers are ready to take their 0.01 ETH to the network to earn $HOUR. Let’s break this term down word for word.</p><p><strong>Latent</strong> - The act of staking is the underlying security model for the protocol. Therefore by definition it is always subtlety running in the background, providing security for the network and rewards for the validators.</p><p><strong>Initialization</strong> - LITT describes the initial activation process of earning $HOUR by staking 0.01 ETH to the network.</p><p><strong>Token</strong> - Pretty self explanatory, gotta stake tokens to earn tokens!</p><p><strong>Truss</strong> - Truss is traditionally defined as an assemblage of members (such as beams) forming a rigid framework, usually used in the context of a bridge. In the Web3 context it refers to the act of securing a network with individual token locks. In similar fashion as a number of beams can come together and form a rigid framework, a series of individual token locks secures the happyhourDAO network and provides the crucial protocol security required for $HOUR token distributions.</p><p>Plain simple token staking will be replaced in the future by Latent Initialization of Token Truss as it is a more accurate and precise description of the process. HappyHourDAO is set on the path to convert the Web3 world to get LITT one drink at a time.</p><p><em>So how does a Drinker initiate a LITT session then?</em></p><p>When using the happyhourDAO <em>Dashboard</em>, the <strong>Start LITT</strong> functionality will prompt a Drinker to input the said PDE’s PDE ID and secret access code in order to call the HOURv3’s solidity contract’s <code>.startHOUR()</code> method. The inputted PDE ID and access code must be valid and compatible in order to successfully call the method. On top of that, a Drinker must stake at least 0.01 ETH during their LITT session. Consider this amount as a deposit or their “proof of stake” amount to be used as collateral.</p><p>As mentioned above, Drinkers need to start a LITT session by calling the <code>.startHOUR()</code> method in the <em>Dashboard.</em> This method will run through the required checks to make sure the Drinker is not currently in an existing LITT session, their inputted PDE ID &amp; access code are valid, and that they have at least 0.01 ETH staked.</p><pre data-type="codeBlock" text="    function startHOUR(uint _PDEid, uint _accessCode) public payable {

        bool validPDE = false;

        for (uint i = 0; i &lt; pdes.length; i++) {
            if (pdes[i]._PDEid == _PDEid &amp;&amp; pdes[i]._accessCode == _accessCode) {
                validPDE = true;
            }
        }

        require(validPDE == true);
        require(msg.value == happyHourFee * (10 ** 16), &quot;Invalid Happy Hour Fee.&quot;);
        givePoolDrinkingId();
        drinkingIDtoPDEid[drinkingID[msg.sender]] = _PDEid;
        happyHourFeePool += 1;
        timeIN = block.timestamp;
    }
"><code>    <span class="hljs-function"><span class="hljs-keyword">function</span> <span class="hljs-title">startHOUR</span>(<span class="hljs-params"><span class="hljs-keyword">uint</span> _PDEid, <span class="hljs-keyword">uint</span> _accessCode</span>) <span class="hljs-title"><span class="hljs-keyword">public</span></span> <span class="hljs-title"><span class="hljs-keyword">payable</span></span> </span>{

        <span class="hljs-keyword">bool</span> validPDE <span class="hljs-operator">=</span> <span class="hljs-literal">false</span>;

        <span class="hljs-keyword">for</span> (<span class="hljs-keyword">uint</span> i <span class="hljs-operator">=</span> <span class="hljs-number">0</span>; i <span class="hljs-operator">&#x3C;</span> pdes.<span class="hljs-built_in">length</span>; i<span class="hljs-operator">+</span><span class="hljs-operator">+</span>) {
            <span class="hljs-keyword">if</span> (pdes[i]._PDEid <span class="hljs-operator">=</span><span class="hljs-operator">=</span> _PDEid <span class="hljs-operator">&#x26;</span><span class="hljs-operator">&#x26;</span> pdes[i]._accessCode <span class="hljs-operator">=</span><span class="hljs-operator">=</span> _accessCode) {
                validPDE <span class="hljs-operator">=</span> <span class="hljs-literal">true</span>;
            }
        }

        <span class="hljs-built_in">require</span>(validPDE <span class="hljs-operator">=</span><span class="hljs-operator">=</span> <span class="hljs-literal">true</span>);
        <span class="hljs-built_in">require</span>(<span class="hljs-built_in">msg</span>.<span class="hljs-built_in">value</span> <span class="hljs-operator">=</span><span class="hljs-operator">=</span> happyHourFee <span class="hljs-operator">*</span> (<span class="hljs-number">10</span> <span class="hljs-operator">*</span><span class="hljs-operator">*</span> <span class="hljs-number">16</span>), <span class="hljs-string">"Invalid Happy Hour Fee."</span>);
        givePoolDrinkingId();
        drinkingIDtoPDEid[drinkingID[<span class="hljs-built_in">msg</span>.<span class="hljs-built_in">sender</span>]] <span class="hljs-operator">=</span> _PDEid;
        happyHourFeePool <span class="hljs-operator">+</span><span class="hljs-operator">=</span> <span class="hljs-number">1</span>;
        timeIN <span class="hljs-operator">=</span> <span class="hljs-built_in">block</span>.<span class="hljs-built_in">timestamp</span>;
    }
</code></pre><p>How does a Drinker obtain a PDE’s PDE ID and access code?</p><p>All PDEs will be required to keep their PDE ID public and in sight upon arrival of said PDE. The secret access code can only be obtained verbally from a bartender of the PDE. So for example, upon arrival and entry of the PDE, a Drinker can scan a QR code in sight up on the main entrance area. This QR code will be one of the details included in a PDE Card, which will also contain basic information of the PDE. The access code will then need to be given to the Drinker by a bartender upon request. This access code is what will prevent Drinker that are not physically at a PDE to game the network. PDE owners also have the ability to change their PDE’s access code whenever.</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://storage.googleapis.com/papyrus_images/e0d7d989dcc55649c4fe4c423d292a9b32277fd233b61dc085143aba46dd3d00.png" alt="Example PDE Card to be placed at the entrance of all PDEs." blurdataurl="data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=" nextheight="600" nextwidth="800" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="">Example PDE Card to be placed at the entrance of all PDEs.</figcaption></figure><p>A LITT session is only valid for 8 hours in order to earn the standard $HOUR per hour rate of 100 $HOUR. If a Drinker ends their LITT session before 8 hours, they will receive the normal rate. If a Drinker leaves their session open for more than 8 hours, they will be “penalized” by only earning a flat amount of 100 $HOUR. Again, the network needs a penalty system in place to prevent Drinkers from gaming the system and earning unfair amount of $HOUR. A Drinker can only ever open one LITT session at a time. If for example, a Drinker wants to leave PDE A and bar hop to PDE B, the Drinker will need to end their LITT session at PDE A first in order to start a new LITT session at PDE B. This is logical and also fair play for the PDE. A Drinker shouldn’t be earning commission for PDE A if they are having a ball at PDE B.</p><p>A session can be ended at any time by navigating to the <em>Dashboard,</em> having your public address verified, and the Dashboard will call the <code>.endHOUR()</code> method from the smart contract.</p><pre data-type="codeBlock" text="    function endHOUR(address payable wiped) public {

        uint PDEindex;
        address PDEcommission;
        require(msg.sender == wiped);
        timeOUT = block.timestamp;
        hoursSpentDrinking = (timeOUT - timeIN) / 60 / 60;

        for (uint i = 0; i &lt; pdes.length; i++) {
            if (pdes[i]._PDEid == drinkingIDtoPDEid[drinkingID[msg.sender]]) {
                PDEcommission = pdes[i]._address;
                PDEindex = i;
            }
        }

        if (hoursSpentDrinking &lt; 8) {
            nullPoolDrinkingId();
            happyHourFeePool -= 1;
            wiped.transfer(happyHourFee * (10 ** 16));
            uint HOURearned = hoursSpentDrinking * (HOURperhour * (10 ** 18));
            uint PDEcommissionEarned = HOURearned / PDEcommissionRate;
            _mint(wiped, HOURearned);
            _mint(PDEcommission, PDEcommissionEarned);
            emit endHOURresults(hoursSpentDrinking, HOURearned, PDEcommissionEarned, PDEindex);
        } else {
            nullPoolDrinkingId();
            happyHourFeePool -= 1;
            wiped.transfer(happyHourFee * (10 ** 16));
            uint PDEcommissionEarned = (HOURperhour * (10 ** 18)) / PDEcommissionRate;
            uint penalHOURearned = HOURperhour * (10 ** 18);
            _mint(wiped, penalHOURearned);
            _mint(PDEcommission, PDEcommissionEarned);
            emit endHOURresults(hoursSpentDrinking, penalHOURearned, PDEcommissionEarned, PDEindex);
        }

        
    }
"><code>    <span class="hljs-function"><span class="hljs-keyword">function</span> <span class="hljs-title">endHOUR</span>(<span class="hljs-params"><span class="hljs-keyword">address</span> <span class="hljs-keyword">payable</span> wiped</span>) <span class="hljs-title"><span class="hljs-keyword">public</span></span> </span>{

        <span class="hljs-keyword">uint</span> PDEindex;
        <span class="hljs-keyword">address</span> PDEcommission;
        <span class="hljs-built_in">require</span>(<span class="hljs-built_in">msg</span>.<span class="hljs-built_in">sender</span> <span class="hljs-operator">=</span><span class="hljs-operator">=</span> wiped);
        timeOUT <span class="hljs-operator">=</span> <span class="hljs-built_in">block</span>.<span class="hljs-built_in">timestamp</span>;
        hoursSpentDrinking <span class="hljs-operator">=</span> (timeOUT <span class="hljs-operator">-</span> timeIN) <span class="hljs-operator">/</span> <span class="hljs-number">60</span> <span class="hljs-operator">/</span> <span class="hljs-number">60</span>;

        <span class="hljs-keyword">for</span> (<span class="hljs-keyword">uint</span> i <span class="hljs-operator">=</span> <span class="hljs-number">0</span>; i <span class="hljs-operator">&#x3C;</span> pdes.<span class="hljs-built_in">length</span>; i<span class="hljs-operator">+</span><span class="hljs-operator">+</span>) {
            <span class="hljs-keyword">if</span> (pdes[i]._PDEid <span class="hljs-operator">=</span><span class="hljs-operator">=</span> drinkingIDtoPDEid[drinkingID[<span class="hljs-built_in">msg</span>.<span class="hljs-built_in">sender</span>]]) {
                PDEcommission <span class="hljs-operator">=</span> pdes[i]._address;
                PDEindex <span class="hljs-operator">=</span> i;
            }
        }

        <span class="hljs-keyword">if</span> (hoursSpentDrinking <span class="hljs-operator">&#x3C;</span> <span class="hljs-number">8</span>) {
            nullPoolDrinkingId();
            happyHourFeePool <span class="hljs-operator">-</span><span class="hljs-operator">=</span> <span class="hljs-number">1</span>;
            wiped.<span class="hljs-built_in">transfer</span>(happyHourFee <span class="hljs-operator">*</span> (<span class="hljs-number">10</span> <span class="hljs-operator">*</span><span class="hljs-operator">*</span> <span class="hljs-number">16</span>));
            <span class="hljs-keyword">uint</span> HOURearned <span class="hljs-operator">=</span> hoursSpentDrinking <span class="hljs-operator">*</span> (HOURperhour <span class="hljs-operator">*</span> (<span class="hljs-number">10</span> <span class="hljs-operator">*</span><span class="hljs-operator">*</span> <span class="hljs-number">18</span>));
            <span class="hljs-keyword">uint</span> PDEcommissionEarned <span class="hljs-operator">=</span> HOURearned <span class="hljs-operator">/</span> PDEcommissionRate;
            _mint(wiped, HOURearned);
            _mint(PDEcommission, PDEcommissionEarned);
            <span class="hljs-keyword">emit</span> endHOURresults(hoursSpentDrinking, HOURearned, PDEcommissionEarned, PDEindex);
        } <span class="hljs-keyword">else</span> {
            nullPoolDrinkingId();
            happyHourFeePool <span class="hljs-operator">-</span><span class="hljs-operator">=</span> <span class="hljs-number">1</span>;
            wiped.<span class="hljs-built_in">transfer</span>(happyHourFee <span class="hljs-operator">*</span> (<span class="hljs-number">10</span> <span class="hljs-operator">*</span><span class="hljs-operator">*</span> <span class="hljs-number">16</span>));
            <span class="hljs-keyword">uint</span> PDEcommissionEarned <span class="hljs-operator">=</span> (HOURperhour <span class="hljs-operator">*</span> (<span class="hljs-number">10</span> <span class="hljs-operator">*</span><span class="hljs-operator">*</span> <span class="hljs-number">18</span>)) <span class="hljs-operator">/</span> PDEcommissionRate;
            <span class="hljs-keyword">uint</span> penalHOURearned <span class="hljs-operator">=</span> HOURperhour <span class="hljs-operator">*</span> (<span class="hljs-number">10</span> <span class="hljs-operator">*</span><span class="hljs-operator">*</span> <span class="hljs-number">18</span>);
            _mint(wiped, penalHOURearned);
            _mint(PDEcommission, PDEcommissionEarned);
            <span class="hljs-keyword">emit</span> endHOURresults(hoursSpentDrinking, penalHOURearned, PDEcommissionEarned, PDEindex);
        }

        
    }
</code></pre><p>As a reminder, all PDEs will automatically be earning 10% of your total $HOUR earned. Consider this as a “tip” for the PDE.</p><hr><h3 id="h-dollarhour-tokenomics" class="text-2xl font-header !mt-6 !mb-4 first:!mt-0 first:!mb-0">$HOUR tokenomics</h3><p>So what can one do with $HOUR tokens after earning them?</p><p>Based on real-time hours spent at happy hour, drinkers can earn $HOUR tokens via the Happy Hour Protocol Engine. In exchange, these earned $HOUR tokens have a multi-functional utility such as being able to use those $HOUR tokens in purchasing discounted beverages at participating bars/nightclubs. They also can allow drinkers to exchange them into other tokens of their choosing. And with the metaverse spawning nightlife entrepreneurs to take their venues digitally online, $HOUR tokens can also be used at those web3 nightlife venues.</p><p>When enough $HOUR tokens have been accumulated, drinkers can then burn them in exchange for $DRNK, which is the governance token of the happyhourDAO. The governance token of $DRNK will enable voting rights, HHIP (happy hour improvement proposals) requests and approvals, premium access to other whitelist nightlife events, and other premium benefits.</p><p>We envision the novel Drink-To-Earn model as an infinite positive feedback loop. As drinkers earn $HOUR by the hour, drinking establishments can earn a commission of the $HOUR earned by drinker. Freshly earned $HOUR tokens can then be used at other participating drinking establishments in purchasing deeply discounted drinks or to be burned to earn the happyhourDAO’s governance token, $DRNK.</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://storage.googleapis.com/papyrus_images/7b9a64fd2fb419797859fbcd6762dcd4925e3057c2efac62ccdb92be1a3299c6.png" alt="The flows and synergy between all parties is like the perfect cocktail on a Friday evening." blurdataurl="data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=" nextheight="600" nextwidth="800" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="">The flows and synergy between all parties is like the perfect cocktail on a Friday evening.</figcaption></figure><p>The $DRNK governance token, with all its benefits, can then in turn steer the happyhourDAO in building a larger engaged ecosystem amongst F&amp;B establishments. The happyhourDAO will be equipped with a VC arm in funding drinking establishments to attract more drinkers to their spot. As more drinkers are attracted to better developed drinking establishments, the more $HOUR tokens are earned which leads to more activity in the happyhourDAO. It’s a positive feedback loop we hope will lead to more real-life use cases in the physical world.</p><hr><p>In conclusion, what’s there to not love about getting LITT?!</p><p>You get to enjoy happy hour the way it usually is, and at the same time, earn the $HOUR token, which will become web3’s first Drink-To-Earn token powering the F&amp;B industry.</p><p>Cheers.</p>]]></content:encoded>
            <author>happyhourlabs@newsletter.paragraph.com (happyhourDAO (🍸,🍸))</author>
        </item>
        <item>
            <title><![CDATA[We've got a new look.]]></title>
            <link>https://paragraph.com/@happyhourlabs/we-ve-got-a-new-look</link>
            <guid>TuUg21FWntThM0MwtH6l</guid>
            <pubDate>Mon, 20 Feb 2023 14:31:46 GMT</pubDate>
            <description><![CDATA[Stunning dApp UI designs and eye-popping logos are just a fraction that goes into building a web3 brand. Finding the right designer to create the most bleeding edge of web3 design is far and few. Sometimes even the most simplest design can work wonders as compared to spending hundreds of thousands of dollars on design agencies. We’re not afraid to admit that our previous brand logo and theme were a bit lacking. Especially considering the factors of our DAO being 100% community driven with ZER...]]></description>
            <content:encoded><![CDATA[<p>Stunning dApp UI designs and eye-popping logos are just a fraction that goes into building a web3 brand. Finding the right designer to create the most bleeding edge of web3 design is far and few. Sometimes even the most simplest design can work wonders as compared to spending hundreds of thousands of dollars on design agencies.</p><p>We’re not afraid to admit that our previous brand logo and theme were a bit lacking. Especially considering the factors of our DAO being 100% community driven with ZERO VC funding, ZERO premine, &amp; ZERO marketing budget.</p><p>Before formally presenting the new look &amp; feel of the happyhourDAO brand, we want to opine on the elements that we felt were necessary in our concluding work.</p><h3 id="h-we-wanted-something-akin-to-the-nightlife-vibe" class="text-2xl font-header !mt-6 !mb-4 first:!mt-0 first:!mb-0">We wanted something akin to the nightlife vibe.</h3><p>The one thing that we noticed works well with organized clubbing events and club promotions is the ability to create eye-catching flyers that exhibit a coolness factor. We wanted to do the same thing, because we also are cool. Or at least that’s the vibe we want to give off. The happyhourDAO is a web3 extension of the IRL brick and mortar bar/club venue. By retaining some of the elements, new Drinkers to the community could have an immediate understanding of the trail we are trying to blaze.</p><h3 id="h-we-wanted-something-web3-ish" class="text-2xl font-header !mt-6 !mb-4 first:!mt-0 first:!mb-0">We wanted something web3-ish.</h3><p>Nothing screams web3 than with some splash of neon and gradient variations. You’ll see more gradient coloration on the mainnet app (coming soon!).</p><h3 id="h-we-wanted-something-sleek-and-clean" class="text-2xl font-header !mt-6 !mb-4 first:!mt-0 first:!mb-0">We wanted something sleek and clean.</h3><p>If you haven’t noticed over the past 5 years, brands from any industry have been re-inventing their logo to look more simplistic rather than complicated.</p><hr><p>So without further ado, ta-da!</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://storage.googleapis.com/papyrus_images/baeacd4dc5ecb4887c39d56958ca1dd89f96d2f150cb8d15227948b3bd2facc6.png" alt="(happyhourDAO&apos;s new brand spanking look)" blurdataurl="data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=" nextheight="600" nextwidth="800" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="">(happyhourDAO&apos;s new brand spanking look)</figcaption></figure><p>The above image will officially be adopted as our new full brand logo, meaning it includes not only the martini glass icon but also happyhourDAO written out on the right side of the icon.</p><p>Initially our brand icon did include a slightly different martini glass icon but the new one embodies a more web3 feel to it with its curved corners and partially dotted parallel lines. Sticking with the martini glass icon was important and a fairly obvious choice. We wanted a icon that people can quickly interpret and resonate with. The icon variation might seem frivolous, but upon looking closer, the newer icon just vibes better.</p><p>The icon was also agreed upon due to its flexibility in its avatar-ness. All of the social platforms happyhourDAO has been utilizing requires an avatar. This icon popped out the most when performing A/B tests.</p><p>The icon is also structured in a manner that welcomes animative motions.</p><p>The typefont for “happyhourDAO” is using the Smooch typefont which aptly embodies the elegant nightlife typefont you’d see at your city center’s plush lounge. The letters of “happyhour” were purposely all lower-cased in providing stark contrast to the letters of “DAO”. It’s a fancy script, but not exactly script. It’s carrying some elements of graffiti art but in a more classy manner.</p><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://storage.googleapis.com/papyrus_images/5c689cdb1e426cc189a2be0e2d2b5de50ea09a20379d21641f617d7b611bf32d.png" alt="(oh the possibilities...)" blurdataurl="data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=" nextheight="600" nextwidth="800" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="">(oh the possibilities...)</figcaption></figure><p>We hope the new brand look &amp; feel is emblematic in what a true Drink-To-Earn protocol should emanate. But at the end of the day what matters most is that our DAO community strives on its mission in bringing back the fun of going out. Covid lockdowns, rise in crime, &amp; rampant culture change has spread like wildfire over the past 3 years. If our brand assets emanate good times, then let’s bring back the good times shall we.</p><p>Cheers.</p>]]></content:encoded>
            <author>happyhourlabs@newsletter.paragraph.com (happyhourDAO (🍸,🍸))</author>
        </item>
        <item>
            <title><![CDATA[v3.]]></title>
            <link>https://paragraph.com/@happyhourlabs/v3</link>
            <guid>61j9BZKFcEvGzEgi2eHL</guid>
            <pubDate>Sun, 13 Nov 2022 05:57:00 GMT</pubDate>
            <description><![CDATA[It’s already been a few months since we’ve deployed the Happy-Hour-Protocol-Engine-v2 (v2) to the Ropsten testnet this summer along with its interactive application. So much has happened since then, not only in the crypto markets but also within the happyhourLabs team. If you haven’t noticed or not, we’ve been relatively quiet and mute on the socials due to a myriad of reasons. So why are we upgrading the smart contract? Well for many reasons listed below that we’ll get into, but the main rea...]]></description>
            <content:encoded><![CDATA[<p>It’s already been a few months since we’ve deployed the Happy-Hour-Protocol-Engine-v2 (v2) to the Ropsten testnet this summer along with its interactive application. So much has happened since then, not only in the crypto markets but also within the happyhourLabs team. If you haven’t noticed or not, we’ve been relatively quiet and mute on the socials due to a myriad of reasons.</p><p>So why are we upgrading the smart contract? Well for many reasons listed below that we’ll get into, but the main reason is that we wanted to give it a more robust architect before going to mainnet. And considering that the previously deployed testnet app was leveraging the now deprecated testnet, Ropsten network, it’s only natural that we re-deploy to another testnet.</p><p>But nevertheless, we’re back in full force and ready to serve up a banger of a whisky cocktail.</p><hr><h2 id="h-lets-first-start-with-whats-happened-so-far" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">Let’s first start with what’s happened so far?</h2><p><strong>-Word of Mouth</strong></p><p>We cannot be more grateful for the few individuals and supporters of this project for the past few months. Just seeing others on the internet whisper their piqued curiosity is more than enough to get the team at happyhourLabs excited all over again. Sure we might not have gone viral yet but the organic enthusiasm that started this industry is all that’s needed for us to push this forward. We’re not doing this for money or fame, but rather to see two colassol industries (web3 x F&amp;B) move together for a single goal.</p><p>Word of mouth is going to continue driving this project forward. Whether it be from the average plebs like us or from the owners of established F&amp;B spots, the communication between the two is our only bridge that makes sense for this all to work.</p><p>There is no premine, no VC fundraising, no affinity marketing hype bloated with bots, but rather pure altruism.</p><p><strong>-PDE Onboarding</strong></p><p>A few local F&amp;B spots have expressed interest in becoming a PDE on the testnet application. Well, why not, right? The benefit is mutual for both parties.</p><p>If you have a F&amp;B spot in mind that you think would benefit from this protocol, chat with them about the protocol.</p><p><strong>-Digital Media Assets</strong></p><p>We’re looking to ramp up our marketing efforts in the next coming months. Our current portfolio of digital media assets, i.e., logos, banners, graphics, ads, etc., are a bit light in KBs. Most of these already existing assets can be found on our website.</p><p>If you are interested in contributing to the project and banging out some awesome designs utilizing the existing assets, by all means feel free too.</p><p><strong>-Constructive Community Feedback</strong></p><p><em>More $HOUR for those who spend more? Allowing the rich to get richer?</em></p><p>Over the past few months, we’ve received many great feedback from our community on what they saw wrong and what they saw right about the tokenomics of the happyhourDAO. One of the biggest flaws is one’s ability to endlessly earn $HOUR, which we will address below.</p><p>Another suggestion we got back was the minting design of $HOUR. The question that was posed verbatim was: <em>Why not allow drinkers who spend more at a PDE during their session to earn more $HOUR?</em> Essentially basing the $HOUR earned in proportion to the drinks/food you order. On initial thought, this was reasonable and logical in fairness to those who can contribute more financially to a PDE. It’s like with any economy. Those who contribute more to society should be rewarded more. We could even compare this with Bitcoin’s PoW consensus algorithm, which allocates a higher chance of being rewarded with bitcoin if more hashrates is supplied by a miner.</p><p>We get it. It makes sense.</p><p>But.</p><p>Are we allowing the rich to get richer? Are we underestimating the value that a drinker can bring to a PDE besides having to “ball out” at the counter? Would we be looking at this model in a singular frame of view that your financial contributions is that only thing a PDE is looking for?</p><p>Let’s think of an example. Would a PDE want a solo drinker to just come in, order drink after drink by themselves, and end up obliterated by the end of the night looking like a pathetic drunkard? Or would a PDE value one that does not relatively order too many drinks, but is able to pull in many other Drinkers and is conducive to the social vibes and environment of the PDE?</p><p>Earning $HOUR should not be considered a degenerate flex-off competition. The uniformed minting rate of 100 $HOUR per hour is for equality and uniformity across the board. And anyways, this wouldn’t have any bearing or disincentivize a Drinker that was already planning on “ballin’ out” for the night.</p><p>Just be YOU at happy hour.</p><p><strong>-Out With The Old</strong></p><p>If you haven’t noticed already, we’re using Mirror instead of Medium for publishing our blogs. Because f*ck web2.</p><hr><h2 id="h-so-whats-new-with-v3" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">So what’s new with v3?</h2><p><strong>-Penalized $HOUR</strong></p><p>Unfortunately, there was a loophole in the previous v2 contract that basically allowed any Drinker to continuously earn $HOUR over an infinite period of time. Sure, there is a loyalty/enforcement system in place assuming PDE’s force a Drinker to end their current session before they leave that particular PDE location, but a Drinker could always just sneak out the back and never end their session. Leaving them with hundreds, potentially thousands, of freshly minted $HOUR tokens.</p><p>A new if/else implementation was added that essentially “penalizes” a Drinker if they leave their opened sessions for over 8 hours. If a session is left over 8 hours, a Drinker will only receive 1 hour’s worth of $HOUR tokens as a penalty. Because let’s be real, we’re not trying to encourage raging for over 8 hours and doing something that you’ll regret later in life. And eventually a PDE will have to close shop for the night.</p><pre data-type="codeBlock" text="    function endHOUR(address payable wiped) public {

        address PDEcommission;
        require(msg.sender == wiped);
        timeOUT = block.timestamp;
        hoursSpentDrinking = (timeOUT - timeIN) / 60 / 60;

        for (uint i = 0; i &lt; pdes.length; i++) {
            if (pdes[i]._PDEid == drinkingIDtoPDEid[drinkingID[msg.sender]]) {
                PDEcommission = pdes[i]._address;
            }
        }

        if (hoursSpentDrinking &lt; 8) {
            nullPoolDrinkingId();
            happyHourFeePool -= 1;
            wiped.transfer(happyHourFee * (10 ** 16));
            uint HOURearned = hoursSpentDrinking * (HOURperhour * (10 ** 18));
            uint PDEcommissionEarned = HOURearned / PDEcommissionRate;
            _mint(wiped, HOURearned);
            _mint(PDEcommission, PDEcommissionEarned);
            emit endHOURresults(hoursSpentDrinking, HOURearned, PDEcommissionEarned);
        } else {
            nullPoolDrinkingId();
            happyHourFeePool -= 1;
            wiped.transfer(happyHourFee * (10 ** 16));
            uint PDEcommissionEarned = (HOURperhour * (10 ** 18)) / PDEcommissionRate;
            uint penalHOURearned = HOURperhour * (10 ** 18);
            _mint(wiped, penalHOURearned);
            _mint(PDEcommission, PDEcommissionEarned);
            emit endHOURresults(hoursSpentDrinking, penalHOURearned, PDEcommissionEarned);
        }
"><code>    <span class="hljs-function"><span class="hljs-keyword">function</span> <span class="hljs-title">endHOUR</span>(<span class="hljs-params"><span class="hljs-keyword">address</span> <span class="hljs-keyword">payable</span> wiped</span>) <span class="hljs-title"><span class="hljs-keyword">public</span></span> </span>{

        <span class="hljs-keyword">address</span> PDEcommission;
        <span class="hljs-built_in">require</span>(<span class="hljs-built_in">msg</span>.<span class="hljs-built_in">sender</span> <span class="hljs-operator">=</span><span class="hljs-operator">=</span> wiped);
        timeOUT <span class="hljs-operator">=</span> <span class="hljs-built_in">block</span>.<span class="hljs-built_in">timestamp</span>;
        hoursSpentDrinking <span class="hljs-operator">=</span> (timeOUT <span class="hljs-operator">-</span> timeIN) <span class="hljs-operator">/</span> <span class="hljs-number">60</span> <span class="hljs-operator">/</span> <span class="hljs-number">60</span>;

        <span class="hljs-keyword">for</span> (<span class="hljs-keyword">uint</span> i <span class="hljs-operator">=</span> <span class="hljs-number">0</span>; i <span class="hljs-operator">&#x3C;</span> pdes.<span class="hljs-built_in">length</span>; i<span class="hljs-operator">+</span><span class="hljs-operator">+</span>) {
            <span class="hljs-keyword">if</span> (pdes[i]._PDEid <span class="hljs-operator">=</span><span class="hljs-operator">=</span> drinkingIDtoPDEid[drinkingID[<span class="hljs-built_in">msg</span>.<span class="hljs-built_in">sender</span>]]) {
                PDEcommission <span class="hljs-operator">=</span> pdes[i]._address;
            }
        }

        <span class="hljs-keyword">if</span> (hoursSpentDrinking <span class="hljs-operator">&#x3C;</span> <span class="hljs-number">8</span>) {
            nullPoolDrinkingId();
            happyHourFeePool <span class="hljs-operator">-</span><span class="hljs-operator">=</span> <span class="hljs-number">1</span>;
            wiped.<span class="hljs-built_in">transfer</span>(happyHourFee <span class="hljs-operator">*</span> (<span class="hljs-number">10</span> <span class="hljs-operator">*</span><span class="hljs-operator">*</span> <span class="hljs-number">16</span>));
            <span class="hljs-keyword">uint</span> HOURearned <span class="hljs-operator">=</span> hoursSpentDrinking <span class="hljs-operator">*</span> (HOURperhour <span class="hljs-operator">*</span> (<span class="hljs-number">10</span> <span class="hljs-operator">*</span><span class="hljs-operator">*</span> <span class="hljs-number">18</span>));
            <span class="hljs-keyword">uint</span> PDEcommissionEarned <span class="hljs-operator">=</span> HOURearned <span class="hljs-operator">/</span> PDEcommissionRate;
            _mint(wiped, HOURearned);
            _mint(PDEcommission, PDEcommissionEarned);
            <span class="hljs-keyword">emit</span> endHOURresults(hoursSpentDrinking, HOURearned, PDEcommissionEarned);
        } <span class="hljs-keyword">else</span> {
            nullPoolDrinkingId();
            happyHourFeePool <span class="hljs-operator">-</span><span class="hljs-operator">=</span> <span class="hljs-number">1</span>;
            wiped.<span class="hljs-built_in">transfer</span>(happyHourFee <span class="hljs-operator">*</span> (<span class="hljs-number">10</span> <span class="hljs-operator">*</span><span class="hljs-operator">*</span> <span class="hljs-number">16</span>));
            <span class="hljs-keyword">uint</span> PDEcommissionEarned <span class="hljs-operator">=</span> (HOURperhour <span class="hljs-operator">*</span> (<span class="hljs-number">10</span> <span class="hljs-operator">*</span><span class="hljs-operator">*</span> <span class="hljs-number">18</span>)) <span class="hljs-operator">/</span> PDEcommissionRate;
            <span class="hljs-keyword">uint</span> penalHOURearned <span class="hljs-operator">=</span> HOURperhour <span class="hljs-operator">*</span> (<span class="hljs-number">10</span> <span class="hljs-operator">*</span><span class="hljs-operator">*</span> <span class="hljs-number">18</span>);
            _mint(wiped, penalHOURearned);
            _mint(PDEcommission, PDEcommissionEarned);
            <span class="hljs-keyword">emit</span> endHOURresults(hoursSpentDrinking, penalHOURearned, PDEcommissionEarned);
        }
</code></pre><p>So there you have it. No more endless streams of unearned $HOUR tokens flowing your way. Sure we’d all love more $HOUR tokens but eventually the party’s gotta’ end. As the cliche phrase goes: Drink Responsibly.</p><p><strong>-Leaner Smart Contract</strong></p><p>Cut out some unnecessary fat in the smart contract. For example, previously there was some functionality for whitelisting opportunities but the dev team figured, “we fair launching this m<em>ther</em>f<em>ckers</em>!”</p><p><strong>-Separated Solidity Source Files</strong></p><p>The previous <code>HOURv2.sol</code> source file comingled all the contracts together. In v3, we’ve separated it into two different files: <code>HOURv3.sol</code> and <code>DRNKv3.sol</code>. Not much of a major change but just keeping align with best practices.</p><p>Deployed and verified <code>HappyHourProtocolv3</code> contract on the Goerli testnet:</p><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://goerli.etherscan.io/address/0x55f8558d9b7dfffa286015b8376db1a50a0c4ff9">https://goerli.etherscan.io/address/0x55f8558d9b7dfffa286015b8376db1a50a0c4ff9</a></p><p>Deployed and verified <code>DRNKgovernance</code> contract on the Goerli testnet:</p><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://goerli.etherscan.io/address/0x89f1a702eecfb47cf9289b3481349e1f38367c44">https://goerli.etherscan.io/address/0x89f1a702eecfb47cf9289b3481349e1f38367c44</a></p><p><strong>-Improved Front End App</strong></p><p>React will be the weapon of choice for the Goerli testnet app and the mainnet app. The previous app utilized ExpressJS and its corresponding ejs syntax, which were all perfectly fine, but for certain design resigns, React will once again be used for this DAO project.</p><p>We are still undecided if we will use the same revamped front end for both the Goerli testnet and when it launches on mainnet.</p><hr><p>That’s wraps up the updates with what’s going on with v3. Again, contracts have been deployed and verified on the Goerli testnet for <code>read</code> and <code>write</code> functionality.</p><p>So go ahead and stop by your local PDE and <code>startHOUR()</code> at your next happy hour!</p><hr><h2 id="h-drink-with-us-and-join-the-conversation" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">Drink with us and join the conversation</h2><p>Twitter: <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://twitter.com/happyhourDAO">https://twitter.com/happyhourDAO</a></p><p>Discord: <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://discord.gg/XegjVTGmyR">https://discord.gg/XegjVTGmyR</a></p><p>Github: <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://github.com/happyhourDAO/Happy-Hour-Protocol-Engine">https://github.com/happyhourDAO/Happy-Hour-Protocol-Engine</a></p><p>Gitbook: <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://happy-hour-1.gitbook.io/happyhourdao/">https://happy-hour-1.gitbook.io/happyhourdao/</a></p>]]></content:encoded>
            <author>happyhourlabs@newsletter.paragraph.com (happyhourDAO (🍸,🍸))</author>
            <enclosure url="https://storage.googleapis.com/papyrus_images/eb3525d2264c8bf693f2de19eb7f3ba4181d1300b3fccfe9b9a41eec3a76c009.png" length="0" type="image/png"/>
        </item>
        <item>
            <title><![CDATA[Introducing happyhourDAO]]></title>
            <link>https://paragraph.com/@happyhourlabs/introducing-happyhourdao</link>
            <guid>6FH1TQzksccYZHTUqzvT</guid>
            <pubDate>Sat, 12 Nov 2022 06:35:28 GMT</pubDate>
            <description><![CDATA[A community owned Drink-To-Earn decentralized network for web3 Because it’s 5 o’clock somewhere…happyhourDAO whitepaper(originally published May 3, 2022 on Medium.com) Table of Contents /Abstract /What is the happyhourDAO /happyhourDAO network mechanics /$HOUR tokenomics /$DRNK governance tokenomics /happyhourDAO VC venture /happyhourDAO roadmap /$HOUR mint and release schedule /TeamAbstractFood & Beverage (F&B) establishments have been hit hard during the past 2 years of the global pandemic....]]></description>
            <content:encoded><![CDATA[<p>A community owned Drink-To-Earn decentralized network for web3</p><p><em>Because it’s 5 o’clock somewhere…</em></p><hr><h1 id="h-happyhourdao-whitepaper" class="text-4xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">happyhourDAO whitepaper</h1><p>(originally published May 3, 2022 on Medium.com)</p><p><strong>Table of Contents</strong></p><p><em>/Abstract /What is the happyhourDAO /happyhourDAO network mechanics /$HOUR tokenomics /$DRNK governance tokenomics /happyhourDAO VC venture /happyhourDAO roadmap /$HOUR mint and release schedule /Team</em></p><hr><h2 id="h-abstract" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">Abstract</h2><p>Food &amp; Beverage (F&amp;B) establishments have been hit hard during the past 2 years of the global pandemic. Many were shuttered in the face of government imposed lockdowns and social distancing measures. The usual bar goers resorted to at-home drinking with many setting up their own makeshift bar to emulate the feeling of going out. The customary happy hour slowly faded away as friends and colleagues were no longer able to drink together in person and enjoy one’s company.</p><p>But as we see the global economy slowly opening back up with pandemic restrictions becoming obsolete, people are starting to go back to normal. But it’s not the same anymore. Favorite bars and nightlife venues are no longer around. It’s safe to say the F&amp;B industry is still struggling.</p><p>What is needed is a modern incentive to connect post-pandemic F&amp;B establishments to the new post-pandemic modern drinker. What is needed is an infinite positive feedback loop between happy hour goers and F&amp;B establishments through cryptography.</p><p>The new modern happy hour goers need the incentive to hit the bars again…</p><p>…and the same can be said for those bars themselves.</p><p>In this paper, we propose a solution to the lack of incentive for engaging in the once blissful, customary happy hour and to further web3 adoption amongst F&amp;B merchants so that any future arbitrary lockdowns won’t affect their cash flows ever again. Because every web2 bar needs itself a web3 bar.</p><h2 id="h-what-is-the-happyhourdao" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">What is the happyhourDAO</h2><p>Introducing the happyhourDAO.</p><p>The first decentralized, community-owned Drink-To-Earn web3 network enabling all happy-hour-goers alike to be rewarded in the metaverse.</p><p>First, let’s define what is “happy hour”?</p><p>Happy hour is that time of day you and your colleagues can take a breather from work. Happy hour is that time of day where you and your colleagues can rant about other colleagues without retribution. Happy hour is that time of day where you can tell your girlfriend you have to work overtime while flirting with chicks at the bar. Happy hour is that time of day where you can completely flip the switch from being a corporate, white-collar robot to the savage filthy animal that you are. Happy hour is that time of day where you deserve that refreshing long island iced tea from the shit duties your imcompetent manager gives you.</p><p>Happy hour is that time of day during the week where we all look forward to just… releasing.</p><p>According to wiki, “Happy hour is a marketing term for a time when a venue such as a restaurant or bar offers reduced prices on alcoholic drinks. Discounted menu items like appetizers are often served during happy hour. This is a way for bars and restaurants to draw in more business before or after peak business hours”.</p><p>We’ve all engaged in happy hour outings at least more than once in our lifetime. It’s as natural as grabbing a cup of coffee first thing in the morning. We need to just get our drink on during the week and let loose with the goose as they say.</p><p>The happyhourDAO aims to bridge the gap between happy-hour-goers in the real physical world and traditional F&amp;B merchants with plebs in the metaverse through its native ERC20 token, $HOUR. For once, drinkers have the opportunity to earn from their engagement in happy hour. It shouldn’t be that people have earned the right to attend happy hour from their relentless hard work they put in at the office, but rather their happy hour attendance should also be rewarded.</p><h2 id="h-happyhourdao-ecosystem" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">happyhourDAO ecosystem</h2><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://storage.googleapis.com/papyrus_images/7b9a64fd2fb419797859fbcd6762dcd4925e3057c2efac62ccdb92be1a3299c6.png" alt="" blurdataurl="data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=" nextheight="600" nextwidth="800" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="hide-figcaption"></figcaption></figure><p>The happyhourDAO will be powered by the Happy Hour Protocol Engine, which is the heart and soul of the whole ecosystem. This is what will glue together the drinkers, Participating Drinking Establishments (PDEs), devs, investors, and other stakeholders. All the interaction will be done through the Happy Hour Protocol Engine which will be deployed as a smart contract on the Ethereum network.</p><p>Breakdown of participants in the happyhourDAO ecosystem:</p><ul><li><p><em>Drinkers (holders of $HOUR): These are the users and community members interacting with the Happy Hour Protocol Engine. These are the happy hour goers, nightlife fist-pumpers, bartenders, and all other alcoholics who make it a priority to support the F&amp;B industry.</em></p></li><li><p><em>Participating Drinking Establishments (PDE): These are the F&amp;B merchants and businesses hosting drinkers. The local bar, the city’s premier club, the skyline lounge, the speakeasy, the hotel restaurant, and etc. All these F&amp;B merchants would be considered a PDE in the happyhourDAO ecosystem.</em></p></li><li><p><em>Drunkards (holders of $DRNK): These are the all-star drinkers who have been able to accumulate enough $HOUR tokens to burn and mint $DRNK tokens, which fully enable them to be official members of the happyhourDAO.</em></p></li></ul><figure float="none" data-type="figure" class="img-center" style="max-width: null;"><img src="https://storage.googleapis.com/papyrus_images/d31bd836fea2b00a9cb8549a036f8243610929f5e20c938a00295af1ec150ffa.png" alt="" blurdataurl="data:image/gif;base64,R0lGODlhAQABAIAAAP///wAAACwAAAAAAQABAAACAkQBADs=" nextheight="600" nextwidth="800" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="hide-figcaption"></figcaption></figure><p>F&amp;B merchants are at the brink of something new with web3. The happyhourDAO is in position to ready traditional F&amp;B brick and mortar merchants in participating in the internet’s next frontier. The Happy Hour Protocol Engine is geared up with provisions with an open and permissionless onboarding for F&amp;B merchants to be valid PDEs. Each PDEs in the network are eligible for a % of HOUR earned by every drinker. This % rate will start at 10% with the ability for future alterations based on the community’s decisions.</p><p>As a PDE grows in popularity in the network, the happyhourDAO is positioned to further fund that PDE in applicable business aspects the community seems viable. This funding also includes support for web3 onboarding into metaverse realms such as in Decentraland, The Sandbox, Otherside, and others.</p><h2 id="h-dollarhour-tokenomics" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">$HOUR tokenomics</h2><p>Based on real-time hours spent at happy hour, drinkers can earn $HOUR tokens via the Happy Hour Protocol Engine. In exchange, these earned $HOUR tokens have a multi-functional utility such as being able to use those $HOUR tokens in purchasing discounted beverages at participating bars/nightclubs. They also can allow drinkers to exchange them into other tokens of their choosing. And with the metaverse spawning nightlife entrepreneurs to take their venues digitally online, $HOUR tokens can also be used at those web3 nightlife venues.</p><pre data-type="codeBlock" text="function startHOUR(uint _PDEid, uint _accessCode) public payable {
    uint validPDE;
    for (uint i = 0; i &lt; pdes.length; i++) {
        if (pdes[i]._PDEid == _PDEid &amp;&amp; pdes[i]._accessCode ==          _accessCode) {
            validPDE = 1;
        } else {
            validPDE = 0;
        }
    }
    require(validPDE == 1);
    require(msg.value == happyHourFee, &quot;Invalid Happy Hour Fee.&quot;);
    givePoolDrinkingId();
    drinkingIDtoPDEid[drinkingID[msg.sender]] = _PDEid;
    happyHourFeePool += 1;
    timeIN = block.timestamp;
}
"><code><span class="hljs-function"><span class="hljs-keyword">function</span> <span class="hljs-title">startHOUR</span>(<span class="hljs-params"><span class="hljs-keyword">uint</span> _PDEid, <span class="hljs-keyword">uint</span> _accessCode</span>) <span class="hljs-title"><span class="hljs-keyword">public</span></span> <span class="hljs-title"><span class="hljs-keyword">payable</span></span> </span>{
    <span class="hljs-keyword">uint</span> validPDE;
    <span class="hljs-keyword">for</span> (<span class="hljs-keyword">uint</span> i <span class="hljs-operator">=</span> <span class="hljs-number">0</span>; i <span class="hljs-operator">&#x3C;</span> pdes.<span class="hljs-built_in">length</span>; i<span class="hljs-operator">+</span><span class="hljs-operator">+</span>) {
        <span class="hljs-keyword">if</span> (pdes[i]._PDEid <span class="hljs-operator">=</span><span class="hljs-operator">=</span> _PDEid <span class="hljs-operator">&#x26;</span><span class="hljs-operator">&#x26;</span> pdes[i]._accessCode <span class="hljs-operator">=</span><span class="hljs-operator">=</span>          _accessCode) {
            validPDE <span class="hljs-operator">=</span> <span class="hljs-number">1</span>;
        } <span class="hljs-keyword">else</span> {
            validPDE <span class="hljs-operator">=</span> <span class="hljs-number">0</span>;
        }
    }
    <span class="hljs-built_in">require</span>(validPDE <span class="hljs-operator">=</span><span class="hljs-operator">=</span> <span class="hljs-number">1</span>);
    <span class="hljs-built_in">require</span>(<span class="hljs-built_in">msg</span>.<span class="hljs-built_in">value</span> <span class="hljs-operator">=</span><span class="hljs-operator">=</span> happyHourFee, <span class="hljs-string">"Invalid Happy Hour Fee."</span>);
    givePoolDrinkingId();
    drinkingIDtoPDEid[drinkingID[<span class="hljs-built_in">msg</span>.<span class="hljs-built_in">sender</span>]] <span class="hljs-operator">=</span> _PDEid;
    happyHourFeePool <span class="hljs-operator">+</span><span class="hljs-operator">=</span> <span class="hljs-number">1</span>;
    timeIN <span class="hljs-operator">=</span> <span class="hljs-built_in">block</span>.<span class="hljs-built_in">timestamp</span>;
}
</code></pre><p>When enough $HOUR tokens have been accumulated, drinkers can then burn them in exchange for $DRNK, which is the governance token of the happyhourDAO. The governance token of $DRNK will enable voting rights, HHIP (happy hour improvement proposals) requests and approvals, premium access to other whitelist nightlife events, and other premium benefits.</p><p>We envision the novel Drink-To-Earn model as an infinite positive feedback loop. As drinkers earn $HOUR by the hour, drinking establishments can earn a commission of the $HOUR earned by drinker. Freshly earned $HOUR tokens can then be used at other participating drinking establishments in purchasing deeply discounted drinks or to be burned to earn the happyhourDAO’s governance token, $DRNK.</p><p>The $DRNK governance token, with all its benefits, can then in turn steer the happyhourDAO in building a larger engaged ecosystem amongst F&amp;B establishments. The happyhourDAO will be equipped with a VC arm in funding drinking establishments to attract more drinkers to their spot. As more drinkers are attracted to better developed drinking establishments, the more $HOUR tokens are earned which leads to more activity in the happyhourDAO. It’s a positive feedback loop we hope will lead to more real-life use cases in the physical world.</p><h2 id="h-dollardrnk-governance-tokenomics" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">$DRNK governance tokenomics</h2><p>$HOUR/$DRNK exchange ratio will be hardcoded at the initial rate of 10/1. All $DRNK governance tokens will be fairly minted, meaning there will be no pre-mined $DRNK to certain individuals.</p><p>The $DRNK governance token is the official membership token of the happyhourDAO. Any amount of $DRNK governance token will be accepted and considered sufficient to be part of the happyhourDAO. The larger amount of $DRNK governance tokens owned allows for a larger percentage of influence you can have on any happyhourDAO participation. The below outlines the types of privileges and events you can participate in.</p><p>Membership into the happyhourDAO grants you access to:</p><ul><li><p><em>Voting mechanisms</em></p></li><li><p><em>Happy Hour Improvement Proposals (HHIP) submissions and approvals</em></p></li><li><p><em>Special airdrops</em></p></li><li><p><em>Real world exclusive VIP hosted events</em></p></li><li><p><em>happyhourDAO VC arm investments</em></p></li><li><p><em>happyhourNFTs exclusive whitelist</em></p></li><li><p><em>Exclusive access to Web3 version of PDEs</em></p></li><li><p><em>Merchandise</em></p></li></ul><h2 id="h-happyhourdao-roadmap" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">happyhourDAO roadmap</h2><ol><li><p><em>May 2022 Whitepaper release Testnet deployment</em></p></li><li><p><em>June 2022 Website release Onboarding of PDEs globally</em></p></li><li><p><em>August 2022 Mainnet contract deployment Happy Hour Protocol Engine release $DRNK governance token release</em></p></li><li><p><em>September 2022 happyhourDAO launch happyhourDAO launch party</em></p></li><li><p><em>December 2022 happyhourNFTs</em></p></li><li><p><em>Summer 2023 Grand opening of physical happyhourDAO bar/restaurant</em></p></li></ol><h2 id="h-team" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">Team</h2><p>The team behind the Happy Hour Protocol Engine and happyhourDAO are all anonymous. Anonymity in an environment where decentralization is a merit always prevails and stays true to the ethos of this industry.</p><h2 id="h-dollarhourdollardrnk-mint-and-release-schedule" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">$HOUR/$DRNK mint and release schedule</h2><p>The $HOUR token will conduct a fair launch with zero issuance at contract deployment. Issuance rate will vary based on network growth and $HOUR earned. The ratios of both $HOUR/hour and $HOUR to $DRNK burn minimum threshold will all be adjustable based on the consensus of the community’s outlook.</p><h2 id="h-conclusion" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">Conclusion</h2><p>The Random House Dictionary of American Slang dates “Happy hour,” as a term for afternoon drinks in a bar, to a Saturday Evening Post article on military life in 1959. The article detailed the lives of government contractors and military personnel who worked at missile-tracking facilities in the Caribbean and the Atlantic. “Except for those who spend too much during ‘happy hour’ at the bar — and there are few of these — the money mounts up fast.”</p><p>Happy-hour-goers shouldn’t always have to feel bad when splurging their money at the bar. They deserve incentives for just being able to live and be merry. The $HOUR token is that incentive for happy-hour-goers and all types of drinking establishments. Let’s aim to bring this untapped demographic to web3.</p><p>Let’s bring happy hour to the metaverse.</p><hr><h3 id="h-drink-with-us-and-join-the-conversation" class="text-2xl font-header !mt-6 !mb-4 first:!mt-0 first:!mb-0">Drink with us and join the conversation</h3><p>Twitter: <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://twitter.com/happyhourDAO">https://twitter.com/happyhourDAO</a></p><p>Discord: <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://discord.gg/XegjVTGmyR">https://discord.gg/XegjVTGmyR</a></p><p>Github: <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://github.com/happyhourDAO/Happy-Hour-Protocol-Engine">https://github.com/happyhourDAO/Happy-Hour-Protocol-Engine</a></p><p>Gitbook: <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://happy-hour-1.gitbook.io/happyhourdao/">https://happy-hour-1.gitbook.io/happyhourdao/</a></p>]]></content:encoded>
            <author>happyhourlabs@newsletter.paragraph.com (happyhourDAO (🍸,🍸))</author>
            <enclosure url="https://storage.googleapis.com/papyrus_images/b103ec5c7183249778b4fc93acdbe7f1c72e61a2438d61193934ee0847f92dd8.png" length="0" type="image/png"/>
        </item>
    </channel>
</rss>