Back to collectionA voting-window correction exposes a governance configuration error
After seven questioned why the voting window showed 14 days rather than 7, Sam said the issue had been fixed. The replacement setup used a 48-hour wait and a 7-day voting period, with the proposal creation date reset to that day. He said the shorter waiting period was intended to keep the opening time largely unchanged. This was a reported configuration correction, not proof that the original schedule had always been right.
After seven questioned why the voting window showed 14 days rather than 7, Sam said the issue had been fixed. The replacement setup used a 48-hour wait and a 7-day voting period, with the proposal creation date reset to that day. He said the shorter waiting period was intended to keep the opening time largely unchanged. This was a reported configuration correction, not proof that the original schedule had always been right.
Diablo's voting guide separately required self-delegation for holders wishing to vote directly. It described confirming the delegation transaction, checking assigned vXAI voting power, and then choosing For, Against or Abstain on a proposal. Holding tokens and having usable voting power in the interface were therefore not presented as the same step. The guide explained the workflow; it was not a receipt showing that any particular participant had voted.