Xode Staking

[hgminerva]

Staking Process

1. registerCandidate: A candidate must register their address.
2. bondCandidate: After registration, they must bond/reserve their XON tokens (with a minimum bond amount).
3. updateCandidates: Updates the list of candidates and sorts them based on the Total Bond Amount. If amounts are equal, priority is given to the first to bond.
4. stakeCandidate: A delegator can bond/reserve their XON tokens to a candidate. The staked tokens will be added to the candidate's Total Bond Amount. Once staking is successful, the list of candidates will be updated.
5. removeCandidateBond: A candidate can remove their bond. The removal will take effect in the next session, and the bond and all staked XON will be unreserved.
6. removeCandidateStake: A delegator can remove their staked XON. The amount to be removed must not exceed the current staked XON. If the entire amount is removed, the delegator will be removed.

[hgminerva]

We are now done with the author side of the staking and these are the new processes and extrinsic:

[hgminerva]

ProposedCandidates: Storage for newly proposed candidates.

DesiredCandidates: These are candidates desired by the runtime to be included in the authorship to guarantee a minimum number of Xode authors.

registerProposedCandidates: Any address can become a candidate; upon registration, the default bond value is zero.

bondProposedCandidates: After registration, the address can bond. There is no minimum bond amount. This extrinsic can be called at any time. If the new bond amount exceeds the existing bond, it will add to the reserve balance; otherwise, it will deduct from the reserve balance. A proposed candidate with zero balance in the next session will be removed from the storage.

updateProposedCandidates: When updating the bond, stake amount, and last update block number, the list will be sorted immediately.

addXaverNodes: At the initial instantiation of the runtime, the Xaver nodes will be added to the desired candidates.

assembleCollators: Assembling collators involves consolidating the desired candidates and the sorted proposed candidates with bond values. After assembling the collators, those with zero bond value will be removed from the list.

Last commit: b984afc
Test Case Scenario: https://docs.google.com/document/d/1pFfLfOIhcjxA2wIhRfnM-bNw0-MIuz53HQ8tv4GB7uQ/edit?pli=1&tab=t.0

[hgminerva]

Leaving from the proposed candidate process.

[hgminerva]

WaitingCandidates: A storage that houses the consolidated list of desired and proposed candidates. The merging of these candidates occurs at the onset of each new session. Initially, during runtime instantiation, only the desired candidates populate this list. This storage also functions as a control mechanism for candidates intending to leave the authorship. A candidate cannot simply set their bond to zero and leave while still present in the WaitingCandidates list. They must first execute a dedicated "leave" extrinsic so that in the subsequent session, the candidate can then set their bond to 0, formally exiting the authorship.

Commit: a2ee6c9

[hgminerva]

Update on the staking process since we are done with delegation and setup of commission:

[hgminerva]

Xode Staking Process Table: https://docs.google.com/spreadsheets/d/1xSMzUbkV7sl1g-G5n7-inF9vypxb5ulMLUGyh6weaX0/edit?usp=sharing

[hgminerva]

I am closing this discussion and open a new discussion on the updated process of pallet-xode-staking v1.0.0 #60