How we choose the Hatch parameters

So we have come to it.

The TEC Test Hatch DAO was launched and we have a full implementation specification for it, confirming what parameters and permissions need to be determined by the community to complete the Hatch.

@YGG has been leading the effort to create a beautiful cadCAD model to make it easy for anyone (even non-devs) to choose their own Hatch Params holistically, and understand the impact their choices will have.

Tokenlog from @Wslyv is ready for us to play with and will allow us to vote on the various parameters proposed by the community.

The main pieces are in place, but the devil is in the details. We need to formally decide exactly how the Hatch Params will be chosen.

The Hatch Param Proposal Submission Process

  1. We will create videos and forum posts explaining this process in detail.

  2. We will have a website that uses our cadCAD model to enable you, whether you are a dev or a non-technical user to choose the design Parameters for the TEC Hatch DAO.

  3. Once you are happy with your parameters, you would make an issue in this Github at this Github repo with a link to the output of your design. You will want to explain your choices in the github issue.

  4. Once you have made your issue you will want to make note of it in a dedicated Forum thread for further discussion.

What will these cadCAD models look like? Here is a sneak peak of the visualization of what it will take to pass a proposal using Dandelion Voting:

Voting on the various proposed Hatch Params

  1. As a community, we will support @Wslyv in improving Tokenlog for our usecase. He has already made several improvements, for more details check out: Tokenlog for the Prime Time Vote

  2. Any one that has earned CSTK tokens or Impact Hours will be able to vote on the Token Log Repo.

  3. Voting power will be split 50% to CSTK Holders and 50% to Impact Hours

  4. Voting will be quadratic, as in, to allocate more voting power to your favorite set of Parameters it will take more tokens.

  5. Once everything is set on the cultural and technical sides, A date and time will be chosen by the Community Stewards and the set of parameters with the most votes at moment will be the Parameters we use.

How does this sound? How can we improve this process?

6 Likes

In The Hatch Param Proposal Submission Process, is #4 - making a forum post necessary? I think the github issue itself might be a better place for dialougue on the proposal.

The comments sections on GitHub issues are 🪙 🪙 🪙

2 Likes

I would agree, there is no reason to REQUIRE an individual forum post, as the github issue is the forum post… and ideally all discussion about the individual merit of the stand alone proposal should happen in the github issue.

But! For the Voters, there will be a forum thread to discuss the various parameter proposals…

In that thread, the voters can discuss their choices and compare and contrast the various proposals against each other. This would be harder to do within the individual discussions in github. The dream is that this forum thread will be where people can discuss their favorite sets of parameters, and it is in the best interest of the designer to promote their proposal to the community of voters in this thread.

BTW… its starting to look really good :smiley:

(Give it a few moments to load)

Lots of issues being worked on, but Jake, YGG, Vitor, and Fabio are killing it!

Here they are:

1 Like
Do you support the proposed strategy above to choose our Hatch Parameters?
  • Yes :smiley:
  • No :expressionless:
  • Block :no_entry_sign:

0 voters

Yeah!! Unanimous! :partying_face: :partying_face: :partying_face:

1 Like

the voting session is closed and this proposal was approved :smiley:

1 Like