Shared and Independent re-staking option for selected roles

[salman01zp]

Summary of changes

The validator can now create the profile by selecting roles he is interested in and with the option to stake independently for each role to be shared across all the roles.

New extrinsic:

• Create Profile

  • Creates a new profile for the validator.

• Update Profile:

  • User can update profile from shared to independent or vice versa.
  • User can remove the role from the profile given that the user has completed all the jobs related to the given role.
  • User can add a new role to the profile given it meets min staking requirements.

• Delete Profile:

  • Submits a request to remove all the jobs
  • Deletes profile if there are no pending jobs

• Remove Role:

  • Submits requests to remove jobs related to the given role
  • Remove role profile once there are no pending jobs related to the given role

pub struct RoleStakingLedger<T: Config> {
	/// The stash account whose balance is actually locked and at stake.
	pub stash: T::AccountId,
	/// The total amount of the stash's balance that is re-staked for all selected roles.
	/// This re-staked balance we are currently accounting for new slashing conditions.
	#[codec(compact)]
	pub total: BalanceOf<T>,
	/// Re staking Profile
	pub profile: Profile,
}

pub enum Profile {
        Independent(IndependentReStakeProfile),
        Shared(SharedReStakeProfile),
}

pub struct Record {
        pub metadata: RoleTypeMetadata,
        pub amount: Option<u64>,
}

pub struct IndependentReStakeProfile {
        pub records: Vec<Record>,
}

pub struct SharedReStakeProfile {
        pub records: Vec<Record>,
        pub amount: u64,
}

Task Checklist

• Update tests
• Update docs

Reference issue to close (if applicable)

Closes #306
Closes #330

[drewstone]

Looks good @salman01zp would suggest a few style changes/spelling/naming and otherwise looks good! I think we will need to properly review this 1:1 if you can book time and we can try to audit/break the mechanism