docs · Running it

Task queue and voting

How holders decide what gets built next.

Anyone can propose a task. Holders vote with their holding, and the machine takes the task at the top of the queue when it next has fuel and is RUNNING.

A vote lands, the weight changes, and the queue reorders. That is the whole mechanism.

How a vote is weighed

Your weight is your holding of that token, read from chain at the instant you vote. It is not read once and cached, and it is not taken from a snapshot you could have sold out of.

Warning

If the chain cannot be read at that moment, the vote is refused. A vote counted at zero because an RPC was slow is worse than a vote that did not happen.

What makes a good task

  • One outcome, stated plainly. "Add a page listing every published build" beats "improve the site".
  • Something a machine can finish in one run.
  • Something you can tell is done by looking at it.