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 club, the skyline lounge, the speakeasy, the hotel restaurant, and etc. All these F&B merchants would be considered a PDE in the happyhourDAO ecosystem.
By onboarding your F&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.
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.
The $HOUR token, as is being dubbed web3’s big Drink-To-Earn token, will empower all F&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&B activity on and offline.
Architectural structure of a PDE.
struct PDE {
string _name;
string _location;
address _address;
uint _accessCode;
uint _PDEid;
}
PDE[] public pdes;
mapping (uint => address) public PDEtoOwner;
Public onboarding function for PDE. Name, Location, ETH address, and a temporary Access Code are required.
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);
}
Every new PDE will fire a new event on-chain.
event newPDEonboarded(string _name, string _location, address _address, uint _PDEid, uint PDEindexNum, uint accessCode);
Enables PDEs to change their Access Code anytime.
function _changeAccessCode(uint _PDEindexNum, uint _newAccessCode) public {
require(PDEtoOwner[_PDEindexNum] == msg.sender);
pdes[_PDEindexNum]._accessCode = _newAccessCode;
}
Tracking live commissions earned by PDEs.
event endHOURresults(uint hoursSpentDrinking, uint HOURearned, uint PDEcommissionEarned, uint PDEindex);
Querying for the total amount of PDEs in the network.
function totalPDE() public view returns (uint) {
return pdes.length;
}
All contract methods listed above are now available on mainnet.
Where do we envision F&B merchants evolving into? For decades, F&B merchants have been siloed by their own physical brick & 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.
F&B merchants are at the brink of something new with web3. The happyhourDAO is in position to ready traditional F&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&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.
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.
Cheers.