Runtime #1186 added the possibility to change the salary asset of the Fellowship.
At the same time, ref #526 acquired Hollar into the Fellowship salary account.

As next step we have to change the salary asset of the Fellowship and adjust the decimals of the raw values such that the intended values stay the same.

This is done by the following call (hash=0xaad105818f673e9a5307cb79a33d3b3bfc082d933419bccc58a804994ea48c99, len=351). It does three things:

• Changes the salary asset to:
  • Location: ../Para(1000)
  • AssetId: ../Para(2034)/Id(222)
• Sets the budget to: 400,000 HOLLAR (up from 250k USDT)
• Sets the following salary values per rank (active/passive) in HOLLAR:
  • I: 833.333333 / 416.666666
  • II: 1666.666666 / 833.333333
  • III: 6,666.666666 / 3,333.333333
  • IV: 10,000 / 5,000
  • V: 13,333.333333 / 6,666.666666
  • VI+: 16,666.666666 / 8,333.333333

Enactment Block

The enactment block is set to exactly 9,247,655 which is the beginning of the next cycle.
Current cycle start: 9,031,655
Register + Payout period: 216,000

9,031,655 + 216,000 = 9,247,655

The collectives chain uses local block number provider in its scheduler and FellowshipReferenda pallet so this will be accurate.
It must enact exactly at cycle start since otherwise a change in params would split the cycle in two.

Testing

Manual testing verification can be reproduced here.

Direct execution of the proposal via Karols tool:

npx github:karolk91/polkadot-referenda-tester \
  test \
  --fellowship-chain-url wss://polkadot-collectives-rpc.polkadot.io  \
  --call-to-create-fellowship-referendum 0x3d003e0202aad105818f673e9a5307cb79a33d3b3bfc082d933419bccc58a804994ea48c995f01000000a71b8d00 \
  --no-cleanup

Then querying FellowshipCore::Params shows the new values:

Note that HOLLAR has 18 decimals.