Snapshot Vote Web3 Block for Solid

Every ballot ranks the options. A round counts each ballot for its highest-ranked option that is still in play, weighted by the voter's power. If one option holds more than half of the weight still in play it wins; otherwise the option with the fewest votes drops out, its ballots move to their next choice and the count repeats. A tie for last drops the option listed later.

Because a first-choice count ignores second choices. In the demo Tooling grants leads round one with 35 % but never reaches a majority, and the ballots of the options that drop out move to Education grants, which wins in round 3. Add your ballot with Tooling grants first and the result flips, which is the point of showing both.

Off-chain votes are weighted by what each voter held at a fixed block, so moving tokens after the snapshot changes nothing. Here the block and your 1,240 votes are typed; each of the nine other ballots carries its own typed weight, and a ballot can rank only some options.

All of it. Ballots, weights and the count are typed constants and one pure function, and submitting changes local state; nothing is signed or sent. In your app sign the ballot as an off-chain message with the connected wallet, post it to your voting service, and load every ballot with its weight at the snapshot to run the same count on the server.

Yes. The ranking is an ordered list, each button names the option it moves, focus follows the option you moved, and the buttons that cannot move stay focusable and explain why. The rounds are a table with column and row headings in a named scroll region. One polite status message reports each move and the result.

The ballot rows keep their three columns, the table scrolls sideways inside its own region with the option names kept first, and the foot with Submit ballot stays pinned to the bottom of the screen.