Note: Please pause voting now, or remove vote if you have already voted. I am working on getting this whitelisted by the fellowship before this referendum is enacted.

Summary

Referendum 664 has been waiting in the Root track queue since relay block 35,318,657. The Root track allows one deciding referendum at a time. Its counter, DecidingCount(0), reads 1, but no Root referendum is deciding, so 664 can never start.

This referendum calls referenda.one_fewer_deciding(0) as Root, through the Whitelisted Caller track. With 664 alone in the queue, the call starts 664's decision period. The counter stays at 1 and from then on counts a real referendum.

The call

Why the Whitelisted Caller track

A Root-track referendum would queue behind 664 on the same blocked track and never start. The Fellowship whitelists the hash, and this track 1 referendum dispatches the call as Root.

Testing

On a Chopsticks fork of live Kusama Asset Hub (block 22,276,769), this exact call went through submission, the Fellowship's whitelist XCM, voting and enactment. It moved 664 from the Root queue into Deciding. The live relay chain's dry run confirms the Fellowship sends the same whitelist message.

Full test report, with steps to verify everything yourself: Link

Verify in two minutes

1. Paste 0x5e035c060000 into Polkadot.js Apps → Extrinsics → Decode. It should decode to referenda.oneFewerDeciding(track: 0) wrapped in whitelist.dispatchWhitelistedCallWithPreimage.
2. In Chain state, referenda.decidingCount(0) returns 1 and referenda.trackQueue(0) holds only 664.

Out of scope

Track 1 (Whitelisted Caller) is also off by one: its counter reads 1 with no referendum deciding. With 100 slots it blocks nothing, and this referendum does not touch it.