Slash Strategy

[readlnh]

Slashing is performed according the exposure (or more precisely, historical exposure), not the current balance in Substrate. However, our slashing is performed according to the current balance, not the exposure, is this what we want?

[aurexav]

Yes, go #198 for more detail.

Store the RING/KTON value in Exposure.

Slash will base on the Exposure in #218.

[aurexav]

Although we store RING/KTON in Exposure, Power still needed.

// This might reasonably saturate and we cannot do much about it. The sum of
// someone's stake might exceed the balance type if they have the maximum amount
// of balance and receive some support. This is super unlikely to happen, yet
// we simulate it in some tests.

[aurexav]

for slash currency percisely, Exposure shoule be a snapshot of the ledger at that time which is build from Support

/// Means a particular `AccountId` was backed by `Votes` of a nominator's stake.
pub struct PhragmenStakedAssignment<AccountId, RingBalance, KtonBalance> {
	pub account_id: AccountId,
	pub ring_balance: RingBalance,
	pub kton_balance: KtonBalance,
}

/// A structure to demonstrate the phragmen result from the perspective of the candidate, i.e. how
/// much support each candidate is receiving.
///
/// This complements the [`PhragmenResult`] and is needed to run the equalize post-processing.
///
/// This, at the current version, resembles the `Exposure` defined in the staking SRML module, yet
/// they do not necessarily have to be the same.
#[derive(Default, RuntimeDebug)]
#[cfg_attr(feature = "std", derive(serde::Serialize, serde::Deserialize))]
pub struct Support<AccountId, RingBalance, KtonBalance> {
	/// The amount of support as the effect of self-vote.
	pub own_votes: Votes,
	pub own_ring: RingBalance,
	pub own_kton: KtonBalance,
	/// Total support.
	pub total: Votes,
	pub total_ring: RingBalance,
	pub total_kton: KtonBalance,
	/// Support from voters.
	pub others: Vec<PhragmenStakedAssignment<AccountId, RingBalance, KtonBalance>>,
}