Luxor network upgrade

[kdembler]

Description

Luxor will be 3rd runtime upgrade to Joystream network since mainnet. This upgrade is focused on minor improvements to governance and managing DAO budgets.

Timeline

We plan to submit upgrade proposal in term 31, by April 13th. That means we need to finish development and start QA April 6th at latest.

Scope

Proposal for reducing council budget

Background - https://github.com/Joystream/joystream/issues/3494 Runtime - https://github.com/Joystream/joystream/pull/5062

Vested spending from WG budgets

Background - https://github.com/Joystream/joystream/issues/4948 Runtime - https://github.com/Joystream/joystream/pull/5072

Proposal for adjusting validator rewards budget

Background - https://github.com/Joystream/joystream/issues/3702 Runtime - https://github.com/Joystream/joystream/pull/5086

Proposal for adjusting CRT pallet constraints

Background - https://github.com/Joystream/joystream/issues/5098 Runtime - https://github.com/Joystream/joystream/pull/5103

Remove Nara migrations

https://github.com/Joystream/joystream/pull/5115

Add proxy pallet

https://github.com/Joystream/joystream/issues/5107

Block AMM operations when revenue split is ongoing

https://github.com/Joystream/joystream/pull/5127

QA

#5119

[thesan]

Regarding the QA: TBH I don't fully get the damping factor logic, but in case it affects only the token rewards but not the points I'm worried it might break the reward history calculated on both Pioneer and the polkadotjs app which would be bad since AFAIK these are the 2 main sources of truth regarding validator rewards.

[kdembler]

@thesan the rewards multiplier should indeed only affect the token rewards, not the era points. Could you share more about what that would break?

[mnaamani]

I added one important item https://github.com/Joystream/joystream/pull/5115