This is only a test.

I am in favor but voting Nay to test the system. Just making sure tokens are locked on losing votes and still receive staking 'action points' 

This proposal, if approved, will:

- Authorize runtime upgrade to release `v22` runtime version `hydradx/201`
    - **feat: referrals** by @enthusiastmartin in #708
    - full release notes can be found [here](https://github.com/galacticcouncil/HydraDX-node/releases/tag/v22.0.0)
    
- Create the following on-chain remark: `Withdraw all WBTC (MRL) (19) and iBTC (11) Omnipool positions, create stablepool containing WBTC MRL and iBTC, add the asset shares into Omnipool and fast-track the respective addToken referendum`

-----
Referrals pallet will allow the creation of referral codes - which, once bound to trader accounts, will generate trading fees for:
- the referrer account
- the trader
- HDX stakers

Recently, asset (LP) dynamic fees were "unleashed" and now 50% of all asset (LP) fees will go to the referral pot to be split between the above parties, dependent on the "tier" of the referral codes in use - more information coming in our docs soon.

This initiative is intended to drive considerably higher volumes to HydraDX.


HydraDX is making some changes to their system which will help bring more people to use it. These changes include:

- Upgrading to a new version of their system called `v22`
- Creating a way for people to refer others to use HydraDX and earn rewards for doing so
- Changing the way fees are collected so that some of the money goes towards the referral program
- The goal is to get more people to use HydraDX and make it even better!

#137·Authorize runtime upgrade & on-chain remark