Community Update #22

Your weekly update is here.

Community Update #22

Happy Wednesday Doggos! We know you're salivating at the anticipation of our launch...

Trust us, it will be worth the wait. :) Last week, we had two community calls, with a Boardroom demo on our Thursday APAC call, and IDriss on our Friday call.

Our Thursday call had our highest attendance of all time, breaking over 1K attendees!

In other news, Carolyn repped Tally Ho on the latest episode of Chris Blec's podcast, Proof Of Decentralization.

And we had our second Found Hounds of March, in what was possibly our most heartfelt session ever. Our special guest this week was Aloysius, who chatted with Kris about everything from DAO tooling to their experience navigating the web3 space with Autism, opening up a very important conversation about neurodivergence in web3 and beyond. ICYMI, you can tune into a recording here.

Boardroom

On our Thursday APAC call, Kris gave us a live demo of Boardroom. Later on Kevin Nielsen, the founder of Boardroom joined and spoke about the platform. Boardroom is a front-end for several different DAO frameworks, including Governor Bravo– the framework that we intend to deploy for the Tally Ho DAO. Users can view the treasury size proposal, voters' ballots, and the token price in the DAO’s dashboard. You can also view a breakdown of what the DAO’s governance process is, and view a history of previous proposals– including the ballots and the voters who have taken part. There’s also a glossary if there's specific stuff or community-defined terms. Everything on the dashboard is submitted by the project, and we will have a page like this for Tally Ho when the active DAO is deployed. Kris connected to MetaMask during the demo, but they are working on implementing the connection to Tally Ho as well.

IDriss

We previously had them on a Thursday APAC call, it was a pleasure to welcome them back for a Friday call!

Lennard from IDriss has been a part of the Tally Ho Community since October. They believe that we’re a community that has really important values, and it’s something they really want to be a part of. Meeting the team at ETHDenver confirmed this. 😇  Geo also applied to be a delegate!

IDriss lets you use your email, phone number, or Twitter username instead of your longer wallet address. It’s quicker and it simplifies your transaction because you don’t need to copy and paste your wallet address back and forth. It also gives you a way to organize multiple wallet addresses. It ensures safety, so you don’t make an error with an address.

They think that this solution is going to be well suited for non-crypto native people who might want to use something that they already have, like email, phone, or Twitter instead of registering a domain and maintaining it every year.

There are three key benefits to using IDriss as opposed to a domain like ENS. The first is that there’s one lifetime fee for IDriss as opposed to yearly maintenance fees with domains. The second is that gas fees with IDriss are through Polygon and a fraction of the usual price. The third difference is that you simply claim your IDriss with a one-time password, verifying you are the owner of your accounts, so no one else can claim your account.

One cool feature they’re working on is the ability to simply send funds directly to any email address or Twitter username, even if they’re not registered. Once the person registers, they’ll be able to claim what you’ve sent them.

Here's a breakdown of a Tally Ho integration use case: Say someone is going to send @chlolands ETH. You’ll be able to see the wallet address embedded in Tally Ho. There’s a pull request ready for this feature, so if the community is excited about it, we can go forward with the integration. The deeper integration is more of onboarding to both IDriss and the wallet. Where it gets interesting for the Tally Ho DAO & treasury, is that IDriss would be willing to share 50% part of the revenue with the DAO.

TIP 2 – Integration of IDriss into Tally Ho! Wallet [DRAFT]
Contributors geoist | IDriss.xyz#1520 – IDriss co-founder, Tally Ho! delegate applicant Lennard | IDriss.xyz#6152 – IDriss co-founder, Tally Ho! community member Introduction The following proposal discusses the integration of IDriss into Tally Ho! wallet, as presented on the community calls o…
Proposal in our DAO Governance forum for IDriss integration & funds allocation

Product Updates

The dev team has been working a lot on preparing for the DAO launch.
There’s been a lot of work on the claim flow, the extension, and the manifesto page. You can view the pitches from the delegates without losing your spot in the extension, which Vlad has been working on the design for.

We’ve got an earn tab in the works, which is essentially wrapped earn vaults that you can participate in right inside of the extension, which Wojciech has done a lot of work on. The token pools will also be accessible from the tab.

Henry then demoed the most important announcement... instead of showing dollar amounts for gas fees, the wallet will now show chocolate bars. How many chocolate bars can you buy with the gas fees? Definitely one of the most exciting announcements we’ve had yet, alongside our new partnership with JP Morgan...

April Fools 😜

Ok, back to real updates. Greg shared the EIP 2612. It’s an EIP for describing data and transaction structure, like Uniswap. We have already implemented a feature where we can decode transactions coming from Uniswap, and we would like to extend this to devs that implement this standard. We would like to have the community collect what should go into the whitelist and what should not, etc. Every tab that creates a transaction value will use this structure and will show the data of the signing transaction to the user. The ask for the community: provide a list of their favorite projects for that assignment!

DAO Updates

Tally Ho! DAO Structure Proposal
This proposal was created through collaboration between the following community members: beemeupnow#0342, commstark#0695, East#8544, geoist | IDriss.xyz#1520, JVK#6935, Kris#8703, Mettodo#7010, Nax#4365, Nico186#5010, ramaruro#7047, tunsky107.eth#1403, willyfox#1178, and zoz.eth#6952. There were op…

As you can see, it's a fairly long and detailed post we put together. We put quite a bit of work into making sure that we've thought this through and tried to set up things in the most effective way for organizing. This proposal was created by a number of different contributors collaborating. Make an account and comment directly on the proposal to let us know what you think!

The smart contracts and the treasury are going to be managed through Governor Bravo. Kris and others have been steadily reviewing delegate applications over the past week and reaching out to those with missing info. Make sure you have a profile picture on your Discourse account! The call for delegates is ending very soon, so get your applications in as soon as possible if you haven’t done so already!
One of the major things that we're trying to avoid here is voter apathy and making sure that folks are able to be predictably looking into proposals and making sure that they're informed. The most important thing here is giving people enough time between the announcement and the end of the voting period to read over the proposal, read over the discussion, and make an informed choice.

The main objective is to build an ecosystem of functional organization that is community-focused and autonomous, making sure people feel empowered and encouraged to make contributions– especially if they’re in line with the longer-term roadmap. We especially want to make sure that there are permissionless contributions, so no one thinks they have to come up to us and ask us permission to make a contribution.

Loose Diagram of the Current DAO Structure

The above structure was designed in a fairly simplified way, ensuring that we have oversight and transparency and also ensuring that there’s autonomy without necessarily having to go back for a downvote. It’s also organized in a way that will reduce the amount of required votes for operational things or smaller decisions– so each “nest” can autonomously make those decisions.

We propose that the compensation reward mechanism for dens at the lowest level, the working groups can coordinate circles. Kris also expects that working groups could have the autonomy to implement other awards or allocation tools if that's something that they need. For example, if there's a lot of development work or things that can be quantified. Kris is interested to see how the dens start to manage themselves as we continue through this process. There will be monthly compensation for the leads. There will be leadership roles within the packs and dens. If you have an interest in having a leadership role, those will be available!

The DAO is going to govern the treasury of course. It will be responsible for any of the funds that are in time lock and can only be distributed through downvote. The main thing the DAO treasury will be governing will be the impact budget according to each pack. Funding for the packs will not be fully liquid immediately but on a vesting schedule.