How do the Hatch Param Proposals Stack Up?

Token Engineering Commons
4 min readMay 21, 2021


BREAKING: The Hatch-Run off Vote deadline has been extended by another week! You now have until June 1st to get your votes in! Go to TokenLog and cast your vote.


Over the last month the community has come together to design the parameters of the Hatch. Economies were designed, debated and voted on producing excellent dialogue and iteration upon iteration of proposals. We saw a wide variety of proposals, wrapping it up last week when the votes were cast on TokenLog. Out of the many great Hatch parameter configurations, it has come down to a final run-off of the top 4 proposals. The names have been changed, and the authors made anonymous. If you have voting power, now is the time to use it! 💯

The Proposals

The Raw Data

Here is the data we used to generate most of the tables in this post.

We also pulled data directly from the Hatch Config Dashboard:

❗️Know what you like best? Vote Now! ☑️


These describe the minimum, maximum and target funding goals for each proposal.

Comparing the Proposals 👀

Total Supply Minted for Backers (%)

Note: The proposals refer to the total supply held by Builders. Here we discuss the percent of the total supply of the Hatch tokens minted for the Backers.

Comparing the Proposals 👀

Impact Hour Rate (wxDai/IH)

The Impact Hour Rate (wxDai/IH) sets the minting rate for Builders. If the Impact Hour Rate is 80 wxDai/hr, then having 1 Impact Hour will get the equivalent number of tokens as sending 80 wxDai into the Hatch.

Comparing the Proposals 👀

Backers RageQuit (%)

The Backers RageQuit percentage describes the amount of funds that Backers are able to remove during the Hatch period. Each proposal offers a unique percentage of redeemable funds at each funding level.

Comparing the Proposals 👀

❗️Know what you like best? Vote Now! ☑️

Control over wxDai in the Hatch DAO

The following charts illustrate the amount of redeemable funds controlled by the Backers (yellow) and the Builders (blue) at the minimum, target and maximum goals for each proposal. The non-redeemable portion (black) represents the Hatch Tribute (%) of each proposal and is consistent at each funding level.

Support and Quorum

The Support Required (%) is the percentage of YES votes from the vote-total required for a proposal to pass.

The Minimum Quorum (%) is the percentage of YES votes from the total supply of TECH tokens that are required for a proposal to pass.

The Vote Duration (days) is the number of days people can vote on a proposal.

Comparing the Proposals 👀

Dandelion Voting

Membership Ratio

The membership ratio determines how much wxDai Trusted Seed members can send to the Hatch per CSTK.

The lowest CSTK score possible for Trusted Seed members is 1,125 CSTK.

For people who have not been actively contributing to the Commons Stack and Token Engineering Commons communities and have a low CSTK Score, if they want to send more wxDai into the Hatch then their score permits, they can increase their score by paying more membership dues to the Trusted Seed.

Comparing the Proposals 👀

Troll Rate

The Vote Proposal Buffer is the amount of time that must pass between the start of subsequent votes, and the Tollgate Fee is the amount of wxDAI that is required to submit a proposal.

The Troll Rate (wxDai/hr) is the cost of spamming the Hatch DAO with proposals.

Comparing the Proposals 👀

Get to know the proposals better! Join us for a Debate!

You can check out when the Debates are happening on the TEC Calendar:

Voting remains open until Tuesday, June 1st! “Your Economy; Your Choice” has never been more true than now. The whole TEC community has been hard at work, ‘round the clock across nearly every time zone on the planet leading up to the Hatch Phase. WE ARE SO CLOSE! 🎉 It’s time to vote, make your voice heard, and arm yourself with critical knowledge as we come ever close to the opening of the Hatch.

❗️Know what you like best? Vote Now! ☑️

Not sure how Voting Works? Check out this forum post:

How to ROCK THE VOTE with Tokenlog’s Quadratic Voting

This article was written by Mitch with edits by Griff, Nate, Vitor, Juan & Suga.