Organization
The WiHi builder program is a mechanism to grow WiHi’s community of active supporters (see DAO Onion in WHIP-2).
It is intended to be a pool of active individuals that regularly build out the WiHi platform.
This WHIP-10 specifies the structure, goals and mechanisms of the Builder program.
Builders must regularly build out the WiHi platform.
For this, they receive WiHi rewards which are taken from a community fund (see WHIP-3) that is filled with tokens from the treasury. Fiat payouts are not possible and are only used to cover expenses that have been agreed on a priori.
In order to become a builder, the individual has to be nominated by:
- a supporter
- contributor
- core team member (the promoter).
In case the nomination has support of at least 2 community fund multi-sig members, the promoter negotiates the terms and condition of the individuals builder role, summarizes them in an one-Pager that illustrates:
- goals
- reward amount
- contact details of the builder
and stores the one-pager in the open proposals folder. The naming of the one-pager is
builder-iota-NameOfBuilder, whereiotais an incremented integer index. If the necessary minimum of supporting community fund multi-sig members support the proposal (supporting members need to be named in the one-pager, the decision is taken by voting on-chain on a respective proposal within the community treasury multi-sig once established), the builder is accepted (which is signaled by storing the pdf of the one-pager in the accepted supporter folder) and the details are entered in the list.
Different reward schemes are possible and can be combined on a case-by-case basis:
- Grants
- Examples
- Airdrops [optional]
- Monthly / yearly / one-time token distribution that may be vested [optional]
- Monthly / yearly / one time token compensation that are locked and vested similar to team compensation [required]
- Monthly pool of hours that can be drawn from at some agreed-on hourly rate
- Prizes
- Received for specific contributions (defined, discussed, approved during community build-up calls) and agreed to with a builder in writing
- Related to the builders contribution
- Award amounts are directly related to benefit accrued to WiHi; rewards amounts can be paid out in proportion to the benefit or a one-time payout for achieving a certain goal
Builders have the right to:
- call themselves a “WiHi Builder”
- access the Logo and CIs (corporate identity) folder of WiHi
- access the WiHi supporter folder
- have the supporter status on discord (and see the corresponding channels)
- view the accepted supporters folder
- view the WiHi supporter drive
- gain access to specific competence area channels that are located in the contributor category if decided by the corresponding competence area
Builders have the duty to:
- actively build out the WiHi platform
- make sure that they are not perceived as official representatives of WiHi but as active community members. In particular, it has to be clear that the views shared of them are their own and do not represent WiHi.
Everyone supporting/contributing to WiHi are part of the DAO. Everyone having a token can be part of the DAO. Those who actively and regularly support WiHi are at least supporters within our DAOonion (see WHIP-2). Hence those building out WiHi who are neither contributors nor core team members require an own role within the supporter layer. This WHIP fills the gap.
Builders, even if in the beginning contributing on a fully contractual/ rational/ token-seeking motivation, are members of our DAO as they a) have a bi-directional relationship with us, and b) own tokens. Hence, for on-boarding new builders we can use the on-boarding mechanisms we have already in place for other supporter roles. In particular, in future this can scale (as supporters can suggest new supporters, etc.) and thus accelerate WiHi's platform build out.