Whitelist & Genesis Voting

Genesis in the Hubble Protocol is preceded by a structured whitelisting and voting process that establishes the initial distribution of emissions. This democratic approach gives stakeholders direct influence over the protocol's early development.

The whitelist contract (0xf40B50b8d3467240D09080f993ED1644C41C7D2B) allows tokens to be submitted for consideration in Genesis emissions. A minimum threshold of 42 $xHUBBLE is required to whitelist a token, creating a balanced approach that prevents excessive fragmentation while maintaining accessibility.

After the whitelisting phase concludes, the voting phase begins, allowing $xHUBBLE holders to stake in Mission Control and allocate their support to preferred tokens. The Genesis Voting Module (0xf9Ad65801f4E5257cc3e098d3C61f3AfE228E4a2) manages this process, ensuring transparent distribution of emissions based on community preferences.

Every community pool requires at least 42 $xHUBBLE votes for it to receive any emissions. Once Genesis begins, users cannot increase their votes, though unstaking from Mission Control will remove existing votes. This creates a fixed voting structure that provides stability through the Genesis period.