Fellowship Salary Budget & Period

[muharem]

Fellowship Salary Budget & Period

In alignment with the Fellowship Salary RFC, the projected total monthly budget stands at 240,833 USDt.

With this PR, I invite the Fellowship members to refine the following constant parameters:

• RegistrationPeriod - # of blocks within a cycle which accounts have to register their intent to claim.
• PayoutPeriod - # of blocks within a cycle which accounts have to claim the payout.
• Budget - the total budget per cycle.

Please be aware that the pallet does not have a visibility into the actual balance of the account holding the salary budget. If this account lacks sufficient assets, subsequent salary claims will encounter failures.

[xlc]

I am not familiar enough with the salary pallet to understand the tradeoffs so could someone explain the downside of having long RegistrationPeriod / PayoutPeriod? and the whole process if it is already documented somewhere?

[muharem]

I am not familiar enough with the salary pallet to understand the tradeoffs so could someone explain the downside of having long RegistrationPeriod / PayoutPeriod? and the whole process if it is already documented somewhere?

RegistrationPeriod + PayoutPeriod essentially establish a salary period. It's worth consider default demotion and minimum promotion periods, which determine how often a member needs to approve their current rank and how frequently they can be promoted. I suppose, the former should not occur more than once a quarter or half a year, while the latter is defined as yearly in the manifest. These settings stored on-chain and will be set through a fellowship referendum. For more details, I would refer to the salary pallet documentation.

[xlc]

Actually, we will want to make this number configurable, as obviously we need to adjust the budget every once a while. This will be a good candidate to integrate with parameters pallet, whatever it is the one in ORML, or polkadot-sdk

[bkontur]

if we want very very quick win for this release:

parameter_types! {
     pub storage Budget: u128 = 250_000 * USDT_UNITS`;
}

type Budget = Budget

and allow it for SafeCallFilter here

                // Allow to change dedicated storage items (called by governance-like)
		match call {
			RuntimeCall::System(frame_system::Call::set_storage { items })
				if items.iter().all(|(k, _)| k.eq(&Budget::key()))) => return true,
			_ => (),
		};

[xlc]

I prefer just do the correct way. the storage parameters is not in metadata and hard to work with in frontend