Skip to content

chore: fix some comments#20119

Merged
tac0turtle merged 3 commits into
cosmos:mainfrom
seay404:main
Apr 22, 2024
Merged

chore: fix some comments#20119
tac0turtle merged 3 commits into
cosmos:mainfrom
seay404:main

Conversation

@seay404

@seay404 seay404 commented Apr 22, 2024

Copy link
Copy Markdown
Contributor

Description

Closes: #XXXX


Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

  • included the correct type prefix in the PR title
  • confirmed ! in the type prefix if API or client breaking change
  • targeted the correct branch (see PR Targeting)
  • provided a link to the relevant issue or specification
  • reviewed "Files changed" and left comments if necessary
  • included the necessary unit and integration tests
  • added a changelog entry to CHANGELOG.md
  • updated the relevant documentation or specification, including comments for documenting Go code
  • confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

  • confirmed the correct type prefix in the PR title
  • confirmed all author checklist items have been addressed
  • reviewed state machine logic, API design and naming, documentation is accurate, tests and test coverage

Summary by CodeRabbit

  • Documentation
    • Corrected typos in the documentation comments and README files to enhance clarity and correctness.

@seay404 seay404 requested a review from a team April 22, 2024 03:56
@coderabbitai

coderabbitai Bot commented Apr 22, 2024

Copy link
Copy Markdown
Contributor
Walkthrough

Walkthrough

The changes across the files primarily involve correcting typographical errors in documentation and comments. These corrections enhance clarity and ensure accuracy in the descriptions and instructions provided within the codebase. The modifications are straightforward and pertain to text adjustments without altering the underlying functionality of the software.

Changes

File Path Change Summary
crypto/keys/ed25519/... Corrected a typo in the documentation comment.
x/auth/client/cli/... Fixed a typo in a code comment.
x/staking/README.md Corrected a typo in the documentation related to key mapping.

Recent Review Details

Configuration used: .coderabbit.yml

Commits Files that changed from the base of the PR and between f31a6a3 and b9771b9.
Files selected for processing (3)
  • crypto/keys/ed25519/doc.go (1 hunks)
  • x/auth/client/cli/tx_sign.go (1 hunks)
  • x/staking/README.md (1 hunks)
Files skipped from review due to trivial changes (2)
  • crypto/keys/ed25519/doc.go
  • x/auth/client/cli/tx_sign.go
Additional Context Used
LanguageTool (857)
x/staking/README.md (857)

Near line 9: Only proper nouns start with an uppercase character (there are exceptions for headlines).
Context: ... ## Abstract This paper specifies the Staking module of the Cosmos SDK that was first...


Near line 10: Possible spelling mistake found.
Context: ...that was first described in the [Cosmos Whitepaper](https://cosmos.network/about/whitepape...


Near line 14: Possible spelling mistake found.
Context: ... to support an advanced Proof-of-Stake (PoS) system. In this system, holders of the...


Near line 25: Possible spelling mistake found.
Context: ...ate](#state) * Pool * LastTotalPower * [UnbondingID](#...


Near line 26: Possible spelling mistake found.
Context: ...LastTotalPower](#lasttotalpower) * UnbondingID * Params ...


Near line 27: Possible spelling mistake found.
Context: ... * UnbondingID * Params * Validator...


Near line 30: Possible spelling mistake found.
Context: ... * Delegation * UnbondingDelegation * [Redelegat...


Near line 31: Possible spelling mistake found.
Context: ...elegation](#unbondingdelegation) * Redelegation * Queues...


Near line 33: Possible spelling mistake found.
Context: ...egation) * Queues * HistoricalInfo * [ConsPubkeyRota...


Near line 34: Possible spelling mistake found.
Context: ...HistoricalInfo](#historicalinfo) * ConsPubkeyRotation * [State Transiti...


Near line 41: Possible spelling mistake found.
Context: ...culated) * Messages * MsgCreateValidator * [MsgEditVal...


Near line 42: Possible spelling mistake found.
Context: ...eValidator](#msgcreatevalidator) * MsgEditValidator * [MsgDelegate]...


Near line 43: Possible spelling mistake found.
Context: ...ditValidator](#msgeditvalidator) * MsgDelegate * [MsgUndelegate](#m...


Near line 44: Possible spelling mistake found.
Context: ... * MsgDelegate * MsgUndelegate * [MsgCancelUnbond...


Near line 45: Possible spelling mistake found.
Context: ... MsgUndelegate * MsgCancelUnbondingDelegation * [...


Near line 46: Possible spelling mistake found.
Context: ...](#msgcancelunbondingdelegation) * MsgBeginRedelegate * [MsgUpdateP...


Near line 47: Possible spelling mistake found.
Context: ...Redelegate](#msgbeginredelegate) * MsgUpdateParams * [MsgRotateCons...


Near line 48: Possible spelling mistake found.
Context: ...gUpdateParams](#msgupdateparams) * MsgRotateConsPubkey * [Begin-Block](...


Near line 56: Possible spelling mistake found.
Context: ...oks](#hooks) * Events * EndBlocker * Msg's * [P...


Near line 70: Possible spelling mistake found.
Context: ...n supply of the bond denomination. ### LastTotalPower LastTotalPower tracks the total amount...


Near line 71: Possible spelling mistake found.
Context: ...bond denomination. ### LastTotalPower LastTotalPower tracks the total amounts of bonded toke...


Near line 73: Possible spelling mistake found.
Context: ...with "Last" must remain unchanged until EndBlock. * LastTotalPower: `0x12 -> ProtocolBu...


Near line 75: Possible spelling mistake found.
Context: ...ust remain unchanged until EndBlock. * LastTotalPower: 0x12 -> ProtocolBuffer(math.Int) ##...


Near line 77: Possible spelling mistake found.
Context: ...0x12 -> ProtocolBuffer(math.Int) ### UnbondingID UnbondingID stores the ID of the lates...


Near line 78: Possible spelling mistake found.
Context: ...ocolBuffer(math.Int)` ### UnbondingID UnbondingID stores the ID of the latest unbonding o...


Near line 79: Possible spelling mistake found.
Context: ...UnbondingID stores the ID of the latest unbonding operation. It enables creating unique I...


Near line 79: Possible spelling mistake found.
Context: ...ion. It enables creating unique IDs for unbonding operations, i.e., UnbondingID is increm...


Near line 79: Possible spelling mistake found.
Context: ...que IDs for unbonding operations, i.e., UnbondingID is incremented every time a new unbondi...


Near line 79: Possible spelling mistake found.
Context: ...ndingID is incremented every time a new unbonding operation (validator unbonding, unbondi...


Near line 79: Possible spelling mistake found.
Context: ...me a new unbonding operation (validator unbonding, unbonding delegation, redelegation) is...


Near line 79: Possible spelling mistake found.
Context: ...bonding operation (validator unbonding, unbonding delegation, redelegation) is initiated....


Near line 79: Possible spelling mistake found.
Context: ...idator unbonding, unbonding delegation, redelegation) is initiated. * UnbondingID: `0x37 ->...


Near line 81: Possible spelling mistake found.
Context: ...egation, redelegation) is initiated. * UnbondingID: 0x37 -> uint64 ### Params The stak...


Near line 83: Possible spelling mistake found.
Context: .... * UnbondingID: 0x37 -> uint64 ### Params The staking module stores its params i...


Near line 85: Possible spelling mistake found.
Context: ...# Params The staking module stores its params in state with the prefix of 0x51, it ...


Near line 88: Possible spelling mistake found.
Context: ...nance or the address with authority. * Params: 0x51 | ProtocolBuffer(Params) ```pr...


Near line 98: Loose punctuation mark.
Context: ...have one of three statuses * Unbonded: The validator is not in the active set....


Near line 100: Loose punctuation mark.
Context: ...They can receive delegations. * Bonded: Once the validator receives sufficient ...


Near line 101: Possible spelling mistake found.
Context: ...omatically join the active set during EndBlock and their sta...


Near line 101: Possible typo: you repeated a whitespace
Context: ...nd their status is updated to Bonded. They are signing blocks and receiving re...


Near line 102: Possible typo: you repeated a whitespace
Context: .... They can receive further delegations. They can be slashed for misbehavior. Del...


Near line 103: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...They can receive further delegations. They can be slashed for misbehavior. Delegat...


Near line 103: Possible spelling mistake found.
Context: ... They can be slashed for misbehavior. Delegators to this validator who unbond their dele...


Near line 103: Possible spelling mistake found.
Context: ...avior. Delegators to this validator who unbond their delegation must wait the durati...


Near line 104: Possible spelling mistake found.
Context: ...egation must wait the duration of the UnbondingTime, a chain-specific param, during which t...


Near line 104: Possible spelling mistake found.
Context: ... of the UnbondingTime, a chain-specific param, during which time they are still sla...


Near line 105: Possible spelling mistake found.
Context: ...ram, during which time they are still slashable for offences of the source validator if...


Near line 105: Possible spelling mistake. ‘offences’ is British English.
Context: ...ich time they are still slashable for offences of the source validator if those offenc...


Near line 105: Possible spelling mistake. ‘offences’ is British English.
Context: ...fences of the source validator if those offences were committed during the period of t...


Near line 107: Loose punctuation mark.
Context: ...at the tokens were bonded. * Unbonding: When a validator leaves the active set,...


Near line 108: Possible spelling mistake found.
Context: ...choice or due to slashing, jailing or tombstoning, an unbonding of all their delegations ...


Near line 108: Possible spelling mistake found.
Context: ... slashing, jailing or tombstoning, an unbonding of all their delegations begins. All de...


Near line 108: Possible spelling mistake found.
Context: ...ins. All delegations must then wait the UnbondingTime before their tokens are moved to thei...


Near line 109: Possible spelling mistake found.
Context: ...ns are moved to their accounts from the BondedPool. :::warning Tombstoning is permanent,...


Near line 112: Possible spelling mistake found.
Context: ...:warning Tombstoning is permanent, once tombstoned a validator's consensus key can not be ...


Near line 112: Unless you want to emphasize “not”, use “cannot” which is more common.
Context: ... tombstoned a validator's consensus key can not be reused within the chain where the to...


Near line 112: Possible spelling mistake found.
Context: ...ot be reused within the chain where the tombstoning happened. ::: Validators objects shoul...


Near line 115: Possible spelling mistake found.
Context: ...be primarily stored and accessed by the OperatorAddr, an SDK validator address for the oper...


Near line 117: Consider a shorter alternative to avoid wordiness.
Context: ...ces are maintained per validator object in order to fulfill required lookups for slashing a...


Near line 119: Possible spelling mistake found.
Context: ...tor-set updates. A third special index (LastValidatorPower) is also maintained which however rema...


Near line 119: Consider adding two commas here.
Context: ...alidatorPower`) is also maintained which however remains constant throughout each block,...


Near line 124: Possible spelling mistake found.
Context: ...torAddr -> ProtocolBuffer(validator)* ValidatorsByConsAddr:0x22 | ConsAddrLen (1 byte) | ConsAdd...


Near line 125: Possible spelling mistake found.
Context: ... (1 byte) | ConsAddr -> OperatorAddr* ValidatorsByPower:0x23 | BigEndian(ConsensusPower) | Op...


Near line 126: Possible spelling mistake found.
Context: ...byte) | OperatorAddr -> OperatorAddr* LastValidatorsPower:0x11 | OperatorAddrLen (1 byte) | Ope...


Near line 127: Possible spelling mistake found.
Context: ...dr -> ProtocolBuffer(ConsensusPower)* ValidatorsByUnbondingID:0x38 | UnbondingID -> 0x21 | Operato...


Near line 129: This sentence does not start with an uppercase letter.
Context: ... (1 byte) | OperatorAddr Validators` is the primary index - it ensures that eac...


Near line 131: Possible spelling mistake found.
Context: ...hat validator can change in the future. Delegators can refer to the immutable operator of ...


Near line 134: This sentence does not start with an uppercase letter.
Context: ... public key. ValidatorsByUnbondingID is an additional index that enables lookup...


Near line 135: Possible spelling mistake found.
Context: ... enables lookups for validators by the unbonding IDs corresponding to their current unbo...


Near line 135: Possible spelling mistake found.
Context: ...ding IDs corresponding to their current unbonding. ValidatorByConsAddr is an additiona...


Near line 137: This sentence does not start with an uppercase letter.
Context: ...rrent unbonding. ValidatorByConsAddr is an additional index that enables lookup...


Near line 138: Possible spelling mistake found.
Context: ...that enables lookups for slashing. When CometBFT reports evidence, it provides the valid...


Near line 139: Possible spelling mistake found.
Context: ...ded to find the operator. Note that the ConsAddr corresponds to the address which can b...


Near line 140: Possible spelling mistake found.
Context: ...ich can be derived from the validator's ConsPubKey. ValidatorsByPower is an additional...


Near line 142: This sentence does not start with an uppercase letter.
Context: ...or's ConsPubKey. ValidatorsByPower is an additional index that provides a sor...


Near line 143: Possible spelling mistake found.
Context: ... determine the current active set. Here ConsensusPower is validator.Tokens/10^6 by default. No...


Near line 144: Is an article like ‘a’ or ‘an’ missing?
Context: ...current active set. Here ConsensusPower is validator.Tokens/10^6 by default. Note ...


Near line 144: Add a space between sentences.
Context: ...e set. Here ConsensusPower is validator.Tokens/10^6 by default. Note that all validato...


Near line 147: This sentence does not start with an uppercase letter.
Context: ...thin this index. LastValidatorsPower is a special index that provides a histori...


Near line 149: Possible spelling mistake found.
Context: ...set update process which takes place in EndBlock. Each validator's state ...


Near line 163: Possible spelling mistake found.
Context: ...Delegations are identified by combining DelegatorAddr (the address of the delegator) with th...


Near line 163: Possible spelling mistake found.
Context: ...ing DelegatorAddr (the address of the delegator) with the ValidatorAddr Delegators ar...


Near line 164: Possible spelling mistake found.
Context: ...(the address of the delegator) with the ValidatorAddr Delegators are indexed in the store as...


Near line 164: Possible spelling mistake found.
Context: ...the delegator) with the ValidatorAddr Delegators are indexed in the store as follows: *...


Near line 167: This noun is normally spelled as one word.
Context: ...torAddr -> ProtocolBuffer(delegation)` Stake holders may delegate coins to validators; under...


Near line 169: Possible spelling mistake found.
Context: ...ion` data structure. It is owned by one delegator, and is associated with the shares for ...


Near line 171: You can shorten this phrase to avoid wordiness.
Context: ...alidator. The sender of the transaction is the owner of the bond. ```protobuf reference https:...


Near line 177: Possible spelling mistake found.
Context: ...beta1/staking.proto#L198-L216 ``` #### Delegator Shares When one delegates tokens to a ...


Near line 179: Possible spelling mistake found.
Context: ... Validator, they are issued a number of delegator shares based on a dynamic exchange rate...


Near line 185: Possible spelling mistake found.
Context: ...ber of shares received is stored on the DelegationEntry. When a delegator then Undelegates, the...


Near line 185: Possible spelling mistake found.
Context: ...s stored on the DelegationEntry. When a delegator then Undelegates, the token amount they...


Near line 185: Possible spelling mistake found.
Context: ... DelegationEntry. When a delegator then Undelegates, the token amount they receive is calcu...


Near line 194: Possible spelling mistake found.
Context: ...ively reducing the value of each issued delegator share. ### UnbondingDelegation Shares...


Near line 196: Possible spelling mistake found.
Context: ...ue of each issued delegator share. ### UnbondingDelegation Shares in a Delegation can be unbond...


Near line 198: Possible spelling mistake found.
Context: ...gation Shares in a Delegation can be unbonded, but they must for some time exist as a...


Near line 199: Possible spelling mistake found.
Context: ...but they must for some time exist as an UnbondingDelegation, where shares can be reduced if Byzant...


Near line 202: This sentence does not start with an uppercase letter.
Context: ...ior is detected. UnbondingDelegation are indexed in the store as: * UnbondingDe...


Near line 204: Possible spelling mistake found.
Context: ...gationare indexed in the store as: * UnbondingDelegation:0x32 | DelegatorAddrLen (1 byte) | De...


Near line 205: Possible spelling mistake found.
Context: ... ProtocolBuffer(unbondingDelegation)* UnbondingDelegationsFromValidator:0x33 | ValidatorAddrLen (1 byte) | Va...


Near line 206: Possible spelling mistake found.
Context: ...rLen (1 byte) | DelegatorAddr -> nil* UnbondingDelegationByUnbondingId:0x38 | UnbondingId -> 0x32 | Delegato...


Near line 206: Do you wish to insert an arrow?
Context: ...il* UnbondingDelegationByUnbondingId:0x38 | UnbondingId -> 0x32 | DelegatorAddrLen (1 byte) | Dele...


Near line 206: Possible spelling mistake found.
Context: ...idatorAddrLen (1 byte) | ValidatorAddr UnbondingDelegation` is used in queries, to lookup all unbo...


Near line 207: The word “lookup” is a noun. The verb is spelled with a white space.
Context: ...ndingDelegation` is used in queries, to lookup all unbonding delegations for a given ...


Near line 207: Possible spelling mistake found.
Context: ...tionis used in queries, to lookup all unbonding delegations for a given delegator. U...


Near line 208: Possible spelling mistake found.
Context: ... all unbonding delegations for a given delegator. UnbondingDelegationsFromValidator i...


Near line 210: This sentence does not start with an uppercase letter.
Context: ...r. UnbondingDelegationsFromValidator is used in slashing, to lookup all unbond...


Near line 210: The word “lookup” is a noun. The verb is spelled with a white space.
Context: ...sFromValidator` is used in slashing, to lookup all unbonding delegations associated w...


Near line 211: Possible spelling mistake found.
Context: ...or` is used in slashing, to lookup all unbonding delegations associated with a given val...


Near line 214: This sentence does not start with an uppercase letter.
Context: ...d. UnbondingDelegationByUnbondingId is an additional index that enables looku...


Near line 215: Possible spelling mistake found.
Context: ...itional index that enables lookups for unbonding delegations by the unbonding IDs of the...


Near line 215: Possible spelling mistake found.
Context: ...ookups for unbonding delegations by the unbonding IDs of the containing unbonding delega...


Near line 216: Possible spelling mistake found.
Context: ...by the unbonding IDs of the containing unbonding delegation entries. A UnbondingDelega...


Near line 219: Possible spelling mistake found.
Context: ...ning unbonding delegation entries. A UnbondingDelegation object is created every time an unbondi...


Near line 219: Possible spelling mistake found.
Context: ...egation object is created every time an unbonding is initiated. ```protobuf reference ht...


Near line 225: Possible spelling mistake found.
Context: ...1beta1/staking.proto#L218-L261 ``` ### Redelegation The bonded tokens worth of a `Delegati...


Near line 227: Possible spelling mistake found.
Context: ...orth of a Delegation may be instantly redelegated from a source validator to a different ...


Near line 228: A comma may be missing after the conjunctive/linking adverb ‘However’.
Context: ...rent validator (destination validator). However when this occurs they must be tracked i...


Near line 229: Possible spelling mistake found.
Context: ...n this occurs they must be tracked in a Redelegation object, whereby their shares can be sl...


Near line 233: This sentence does not start with an uppercase letter.
Context: ...y the source validator. Redelegation are indexed in the store as: * Redelegatio...


Near line 235: Possible spelling mistake found.
Context: ...gationare indexed in the store as: * Redelegations:0x34 | DelegatorAddrLen (1 byte) | De...


Near line 236: Possible spelling mistake found.
Context: ...Addr -> ProtocolBuffer(redelegation)* RedelegationsBySrc:0x35 | ValidatorSrcAddrLen (1 byte) |...


Near line 237: Possible spelling mistake found.
Context: ...rLen (1 byte) | DelegatorAddr -> nil* RedelegationsByDst:0x36 | ValidatorDstAddrLen (1 byte) |...


Near line 238: Possible spelling mistake found.
Context: ...rLen (1 byte) | DelegatorAddr -> nil* RedelegationByUnbondingId:0x38 | UnbondingId -> 0x34 | Delegato...


Near line 240: This sentence does not start with an uppercase letter.
Context: ...r | ValidatorDstAddr Redelegations` is used for queries, to lookup all redeleg...


Near line 240: The word “lookup” is a noun. The verb is spelled with a white space.
Context: ...Redelegations is used for queries, to lookup all redelegations for a given delegato...


Near line 240: Possible spelling mistake found.
Context: ...onsis used for queries, to lookup all redelegations for a given delegator. Redelegation...


Near line 241: Possible spelling mistake found.
Context: ...o lookup all redelegations for a given delegator. RedelegationsBySrc is used for sla...


Near line 243: This sentence does not start with an uppercase letter.
Context: ...iven delegator. RedelegationsBySrc is used for slashing based on the `Validat...


Near line 243: Possible spelling mistake found.
Context: ...ySrcis used for slashing based on theValidatorSrcAddr. RedelegationsByDst` is used for sl...


Near line 245: This sentence does not start with an uppercase letter.
Context: ...lidatorSrcAddr. RedelegationsByDstis used for slashing based on theValidat...


Near line 247: The word “lookup” is a noun. The verb is spelled with a white space.
Context: ... first map here is used for queries, to lookup all redelegations for a given delegator...


Near line 247: Possible spelling mistake found.
Context: ...here is used for queries, to lookup all redelegations for a given delegator. The second map i...


Near line 247: Possible spelling mistake found.
Context: ...to lookup all redelegations for a given delegator. The second map is used for slashing ba...


Near line 248: Possible spelling mistake found.
Context: ...d map is used for slashing based on the ValidatorSrcAddr, while the third map is for slashing b...


Near line 249: Possible spelling mistake found.
Context: ... third map is for slashing based on the ValidatorDstAddr. RedelegationByUnbondingId is an ad...


Near line 251: This sentence does not start with an uppercase letter.
Context: ...rDstAddr. RedelegationByUnbondingId` is an additional index that enables looku...


Near line 252: Possible spelling mistake found.
Context: ...itional index that enables lookups for redelegations by the unbonding IDs of the containing ...


Near line 252: Possible spelling mistake found.
Context: ...ables lookups for redelegations by the unbonding IDs of the containing redelegation ent...


Near line 253: Possible spelling mistake found.
Context: ...by the unbonding IDs of the containing redelegation entries. A redelegation object is crea...


Near line 255: Possible spelling mistake found.
Context: ...he containing redelegation entries. A redelegation object is created every time a redelega...


Near line 255: Possible spelling mistake found.
Context: ...legation object is created every time a redelegation occurs. To prevent "redelegation hoppin...


Near line 256: Possible spelling mistake found.
Context: ...time a redelegation occurs. To prevent "redelegation hopping" redelegations may not occur un...


Near line 256: Possible spelling mistake found.
Context: ...curs. To prevent "redelegation hopping" redelegations may not occur under the situation that:...


Near line 258: This sentence does not start with an uppercase letter.
Context: ... not occur under the situation that: * the (re)delegator already has another immat...


Near line 258: Possible spelling mistake found.
Context: ...ur under the situation that: * the (re)delegator already has another immature redelegati...


Near line 258: Possible spelling mistake found.
Context: ...)delegator already has another immature redelegation in progress with a destination to a v...


Near line 259: The comma may be misplaced. Try moving it before ‘and’, or removing it altogether.
Context: ... validator (let's call it Validator X) * and, the (re)delegator is attempting to crea...


Near line 260: Possible spelling mistake found.
Context: ...s call it Validator X) * and, the (re)delegator is attempting to create a new redeleg...


Near line 260: Possible spelling mistake found.
Context: ...legator is attempting to create a new redelegation where the source validator for this n...


Near line 261: Possible spelling mistake found.
Context: ...where the source validator for this new redelegation is Validator X. ```protobuf referenc...


Near line 267: Possible spelling mistake found.
Context: ...v1beta1/staking.proto#L263-L308 ``` ## ConsPubkeyRotation The ConsPubkey of a validator will b...


Near line 269: Possible spelling mistake found.
Context: ...63-L308 ``` ## ConsPubkeyRotation The ConsPubkey of a validator will be instantly rotat...


Near line 269: Possible spelling mistake found.
Context: ...or will be instantly rotated to the new ConsPubkey. The rotation will be tracked to only ...


Near line 269: Possible spelling mistake found.
Context: ...a limited number of rotations within an unbonding period of time. ConsPubkeyRotation a...


Near line 271: This sentence does not start with an uppercase letter.
Context: ...g period of time. ConsPubkeyRotation are indexed in the store as: ValidatorCons...


Near line 272: Possible spelling mistake found.
Context: ...Rotationare indexed in the store as: ValidatorConsPubKeyRotationHistoryKey:101 | valAddr | rotatedHeight -> Prot...


Near line 273: Do you wish to insert an arrow?
Context: ... ValidatorConsPubKeyRotationHistoryKey: `101 | valAddr | rotatedHeight -> ProtocolBuffer(ConsPubKeyRotationHistor...


Near line 274: Possible spelling mistake found.
Context: ...ffer(ConsPubKeyRotationHistory)555682 BlockConsPubKeyRotationHistoryKey (index): 102 | rotatedHeight | valAddr...


Near line 276: Possible spelling mistake found.
Context: ...ocolBuffer(ConsPubKeyRotationHistory) ValidatorConsensusKeyRotationRecordQueueKey:103 | format(time) -> ProtocolBuffer(...


Near line 278: Possible spelling mistake found.
Context: ...ocolBuffer(ValAddrsOfRotatedConsKeys) ValidatorConsensusKeyRotationRecordIndexKey:104 | valAddr | format(time) -> Protoc...


Near line 280: Possible spelling mistake found.
Context: ...mat(time) -> ProtocolBuffer([]Byte{}) OldToNewConsKeyMap:105 | byte(oldConsKey) -> byte(newCons...


Near line 282: Possible spelling mistake found.
Context: ... byte(oldConsKey) -> byte(newConsKey) NewToOldConsKeyMap:106 | byte(newConsKey) -> byte(oldCons...


Near line 287: This sentence does not start with an uppercase letter.
Context: ...atorConsensusKeyRotationRecordQueueKey` is to keep track of the rotation across th...


Near line 287: Possible spelling mistake found.
Context: ...o keep track of the rotation across the unbonding period (waiting period in the queue), t...


Near line 287: Possible spelling mistake found.
Context: ...e queue), this will be pruned after the unbonding period of waiting time. `ValidatorCons...


Near line 289: This sentence does not start with an uppercase letter.
Context: ...atorConsensusKeyRotationRecordIndexKey` is to keep track of a validator that how m...


Near line 289: Possible spelling mistake found.
Context: ...hat how many rotations were made inside unbonding period. This will be pruned after the u...


Near line 289: Possible spelling mistake found.
Context: ...g period. This will be pruned after the unbonding period of waiting time. A `ConsPubKeyR...


Near line 291: Possible spelling mistake found.
Context: ...he unbonding period of waiting time. A ConsPubKeyRotationHistory object is created every time a consens...


Near line 291: Possible spelling mistake found.
Context: ...bject is created every time a consensus pubkey rotation occurs. An entry is added in ...


Near line 293: Possible spelling mistake found.
Context: ... rotation occurs. An entry is added in OldToNewConsKeyMap collection for every rotation (Note: t...


Near line 295: Possible spelling mistake found.
Context: ...th old cons key). An entry is added in NewToOldConsKeyMap collection for every rotation, this en...


Near line 299: The modal verb ‘will’ requires the verb’s base form.
Context: ...o prevent the spam: * There will only limited number of rotations can be done within ...


Near line 299: Possible spelling mistake found.
Context: ... number of rotations can be done within unbonding period of time. * A non-negligible fee...


Near line 305: Possible missing comma found.
Context: ...onverted to UTC, rounded to the nearest nanosecond then sorted. The sortable time format u...


Near line 307: Consider adding a comma after ‘Notably’ for more clarity.
Context: ...ring "2006-01-02T15:04:05.000000000". Notably this format: * right pads all zeros * ...


Near line 315: Possible spelling mistake found.
Context: ...ration time of the queue element. #### UnbondingDelegationQueue For the purpose of tracking progress o...


Near line 317: Possible spelling mistake found.
Context: ...For the purpose of tracking progress of unbonding delegations the unbonding delegations q...


Near line 317: Possible spelling mistake found.
Context: ...g progress of unbonding delegations the unbonding delegations queue is kept. * Unbonding...


Near line 320: Possible spelling mistake found.
Context: ...unbonding delegations queue is kept. * UnbondingDelegation: 0x41 | format(time) -> []DVPair ```...


Near line 326: Possible spelling mistake found.
Context: ...beta1/staking.proto#L162-L172 ``` #### RedelegationQueue For the purpose of tracking progress o...


Near line 328: Possible spelling mistake found.
Context: ...For the purpose of tracking progress of redelegations the redelegation queue is kept. * Rede...


Near line 328: Possible spelling mistake found.
Context: ... tracking progress of redelegations the redelegation queue is kept. * RedelegationQueue: `0...


Near line 331: Possible spelling mistake found.
Context: ...ions the redelegation queue is kept. * RedelegationQueue: 0x42 | format(time) -> []DVVTriplet ...


Near line 337: Possible spelling mistake found.
Context: ...beta1/staking.proto#L179-L191 ``` #### ValidatorQueue For the purpose of tracking progress o...


Near line 339: Possible spelling mistake found.
Context: ...For the purpose of tracking progress of unbonding validators the validator queue is kept....


Near line 339: Possible missing comma found.
Context: ...rpose of tracking progress of unbonding validators the validator queue is kept. * Validat...


Near line 342: Possible spelling mistake found.
Context: ...idators the validator queue is kept. * ValidatorQueueTime: `0x43 | format(time) -> []sdk.ValAddre...


Near line 345: Consider adding a comma after ‘Typically’ for more clarity.
Context: ...h the validator object can be accessed. Typically it is expected that only a single valid...


Near line 346: Possible missing comma found.
Context: ... record will be associated with a given timestamp however it is possible that multiple va...


Near line 346: For conciseness, try rephrasing this sentence.
Context: ...sociated with a given timestamp however it is possible that multiple validators exist in the queue at the same location. ###...


Near line 349: Possible spelling mistake found.
Context: ...n the queue at the same location. #### ValidatorConsensusKeyRotationRecordQueueKey For the purpose of tracking progress o...


Near line 351: Possible spelling mistake found.
Context: ...rpose of tracking progress or consensus pubkey rotations the `ValidatorConsensusKeyRot...


Near line 351: Possible missing comma found.
Context: ...f tracking progress or consensus pubkey rotations the `ValidatorConsensusKeyRotationRecor...


Near line 351: Possible spelling mistake found.
Context: ...gress or consensus pubkey rotations the ValidatorConsensusKeyRotationRecordQueueKey kept. * ValidatorConsensusKeyRotation...


Near line 353: Possible spelling mistake found.
Context: ...nsusKeyRotationRecordQueueKeykept. * ValidatorConsensusKeyRotationRecordQueueKey:103 | format(time) -> types.ValAddrsO...


Near line 356: Possible spelling mistake found.
Context: ...with the current block time adding with unbonding period), Whenever the next item with th...


Near line 358: Possible spelling mistake found.
Context: ...t the present store info and append the ValAddress to the array and set it back in the st...


Near line 364: Possible spelling mistake found.
Context: ...1beta1/staking.proto#L429-L433 ``` ### HistoricalInfo HistoricalInfo objects are stored and ...


Near line 365: Possible spelling mistake found.
Context: ...roto#L429-L433 ``` ### HistoricalInfo HistoricalInfo objects are stored and pruned at each b...


Near line 367: Possible spelling mistake found.
Context: ...fo defined by staking module parameter: HistoricalEntries. ```go reference https://github.com/c...


Near line 373: Possible spelling mistake found.
Context: ...eta1/staking.proto#L17-L24 ``` At each BeginBlock, the staking keeper will persist the cu...


Near line 374: Possible spelling mistake found.
Context: ...s that committed the current block in a HistoricalInfo object. The Validators are sorted on t...


Near line 376: Possible spelling mistake found.
Context: ...re in a deterministic order. The oldest HistoricalEntries will be pruned to ensure that there onl...


Near line 383: Possible spelling mistake found.
Context: ...ns in validators are performed on every EndBlock in order to c...


Near line 383: Consider a shorter alternative to avoid wordiness.
Context: ...ry EndBlock in order to check for changes in the active `Valida...


Near line 384: Possible spelling mistake found.
Context: ...rder to check for changes in the active ValidatorSet. A validator can be Unbonded, `Unbo...


Near line 386: Possible spelling mistake found.
Context: ...ive ValidatorSet. A validator can be Unbonded, Unbonding or Bonded. Unbonded a...


Near line 386: Possible spelling mistake found.
Context: ...orSet. A validator can be Unbonded, UnbondingorBonded. UnbondedandUnbonding...


Near line 386: Possible spelling mistake found.
Context: ...be Unbonded, Unbonding or Bonded. Unbonded and Unbonding are collectively calle...


Near line 387: Possible spelling mistake found.
Context: ...Unbonding or Bonded. Unbonded and Unbonding are collectively called Not Bonded. ...


Near line 388: Possible spelling mistake found.
Context: ...the states, except for from Bonded to Unbonded. #### Not bonded to Bonded The follo...


Near line 392: Possible spelling mistake found.
Context: ...ccurs when a validator's ranking in the ValidatorPowerIndex surpasses that of the LastValidator....


Near line 393: Possible spelling mistake found.
Context: ...idatorPowerIndexsurpasses that of theLastValidator. * set validator.StatustoBonded`...


Near line 395: This sentence does not start with an uppercase letter.
Context: ...rpasses that of the LastValidator. * set validator.Status to Bonded * send t...


Near line 395: Add a space between sentences.
Context: ...ses that of the LastValidator. * set validator.Status to Bonded * send the `validator.Toke...


Near line 396: Add a space between sentences.
Context: ...alidator.StatustoBonded* send thevalidator.Tokensfrom theNotBondedTokensto theBon...


Near line 396: Possible spelling mistake found.
Context: ... * send the validator.Tokens from the NotBondedTokens to the BondedPool ModuleAccount * ...


Near line 396: Possible spelling mistake found.
Context: ...kensfrom theNotBondedTokensto theBondedPool ModuleAccount` * delete the existing ...


Near line 400: Possible spelling mistake found.
Context: ...is validator * if it exists, delete any ValidatorQueue record for this validator #### Bonded...


Near line 402: Possible spelling mistake found.
Context: ...cord for this validator #### Bonded to Unbonding When a validator begins the unbonding ...


Near line 404: Possible spelling mistake found.
Context: ... Unbonding When a validator begins the unbonding process the following operations occur:...


Near line 406: This sentence does not start with an uppercase letter.
Context: ...cess the following operations occur: * send the validator.Tokens from the `Bonded...


Near line 406: Add a space between sentences.
Context: ...following operations occur: * send the validator.Tokens from the BondedPool to the `NotBonde...


Near line 406: Possible spelling mistake found.
Context: ... * send the validator.Tokens from the BondedPool to the NotBondedTokens `ModuleAccoun...


Near line 406: Possible spelling mistake found.
Context: ...or.Tokensfrom theBondedPoolto theNotBondedTokens ModuleAccount* setvalidator.Statu...


Near line 407: Add a space between sentences.
Context: ...NotBondedTokens ModuleAccount * set validator.Status to Unbonding * delete the existing r...


Near line 411: ‘new record’ might be wordy. Consider a shorter alternative.
Context: ...robject for this validator * insert a new record into theValidatorQueue` for this vali...


Near line 411: Possible spelling mistake found.
Context: ...alidator * insert a new record into the ValidatorQueue for this validator #### Unbonding to ...


Near line 413: Possible spelling mistake found.
Context: ...alidatorQueue` for this validator #### Unbonding to Unbonded A validator moves from unb...


Near line 413: Possible spelling mistake found.
Context: ...` for this validator #### Unbonding to Unbonded A validator moves from unbonding to un...


Near line 415: Possible spelling mistake found.
Context: ...ing to Unbonded A validator moves from unbonding to unbonded when the ValidatorQueue o...


Near line 415: Possible spelling mistake found.
Context: ...ed A validator moves from unbonding to unbonded when the ValidatorQueue object moves ...


Near line 415: Possible spelling mistake found.
Context: ...ves from unbonding to unbonded when the ValidatorQueue object moves from bonded to unbonded ...


Near line 416: Possible spelling mistake found.
Context: ...datorQueueobject moves from bonded to unbonded * update theValidator` object for th...


Near line 418: This sentence does not start with an uppercase letter.
Context: ...object moves from bonded to unbonded * update the Validator object for this validat...


Near line 419: Add a space between sentences.
Context: ...idatorobject for this validator * setvalidator.StatustoUnbonded` #### Jail/Unjail when ...


Near line 421: Possible spelling mistake found.
Context: ...idator.StatustoUnbonded` #### Jail/Unjail when a validator is jailed it is effec...


Near line 422: This sentence does not start with an uppercase letter.
Context: ...tatustoUnbonded` #### Jail/Unjail when a validator is jailed it is effectively...


Near line 423: Possible spelling mistake found.
Context: ...iled it is effectively removed from the CometBFT set. this process may be also be revers...


Near line 423: This sentence does not start with an uppercase letter.
Context: ...ectively removed from the CometBFT set. this process may be also be reversed. the fo...


Near line 424: The word ‘be’ seems to be repeated accidentally.
Context: ...from the CometBFT set. this process may be also be reversed. the following operations occur: * set...


Near line 424: This sentence does not start with an uppercase letter.
Context: .... this process may be also be reversed. the following operations occur: * set `Val...


Near line 426: This sentence does not start with an uppercase letter.
Context: ...sed. the following operations occur: * set Validator.Jailed and update object * ...


Near line 426: Add a space between sentences.
Context: ... the following operations occur: * set Validator.Jailed and update object * if jailed delete r...


Near line 428: Possible spelling mistake found.
Context: ...ecord from ValidatorByPowerIndex * if unjailed add record to ValidatorByPowerIndex ...


Near line 438: Possible missing comma found.
Context: ...tions #### Delegate When a delegation occurs both the validator and the delegation o...


Near line 440: This sentence does not start with an uppercase letter.
Context: ... the delegation objects are affected * determine the delegators shares based on tokens d...


Near line 440: Possible spelling mistake found.
Context: ...n objects are affected * determine the delegators shares based on tokens delegated and th...


Near line 443: Possible spelling mistake found.
Context: ...to a created validator object * add new delegator shares and update the Validator objec...


Near line 444: Add a space between sentences.
Context: ...e the Validator object * transfer the delegation.Amount from the delegator's account to the `B...


Near line 444: Possible spelling mistake found.
Context: ...ansfer the delegation.Amount from the delegator's account to the BondedPool or the `N...


Near line 444: Possible spelling mistake found.
Context: ...ntfrom the delegator's account to theBondedPoolor theNotBondedPool ModuleAccount`...


Near line 444: Possible spelling mistake found.
Context: ...or's account to the BondedPool or the NotBondedPool ModuleAccount depending if the `vali...


Near line 444: Possible spelling mistake found.
Context: ...the BondedPool or the NotBondedPool ModuleAccount depending if the validator.Status is...


Near line 444: The verb ‘depend’ requires the preposition ‘on’ (or ‘upon’).
Context: ... or the NotBondedPool ModuleAccount depending if the validator.Status is Bonded o...


Near line 444: Add a space between sentences.
Context: ...dPool ModuleAccountdepending if thevalidator.StatusisBonded` or not * delete the existi...


Near line 446: Use “a” instead of ‘an’ if the following word doesn’t start with a vowel sound, e.g. ‘a sentence’, ‘a university’.
Context: ...cord from ValidatorByPowerIndex * add an new updated record to the `ValidatorByP...


Near line 448: Possible spelling mistake found.
Context: ...the ValidatorByPowerIndex #### Begin Unbonding As a part of the Undelegate and Comple...


Near line 450: Possible spelling mistake found.
Context: ... #### Begin Unbonding As a part of the Undelegate and Complete Unbonding state transition...


Near line 450: Possible spelling mistake found.
Context: ...s a part of the Undelegate and Complete Unbonding state transitions Unbond Delegation may...


Near line 450: Possible spelling mistake found.
Context: ...nd Complete Unbonding state transitions Unbond Delegation may be called. * subtract t...


Near line 453: This sentence does not start with an uppercase letter.
Context: ...ons Unbond Delegation may be called. * subtract the unbonded shares from delegator * ad...


Near line 453: Possible spelling mistake found.
Context: ...legation may be called. * subtract the unbonded shares from delegator * add the unbonde...


Near line 453: Possible spelling mistake found.
Context: ...d. * subtract the unbonded shares from delegator * add the unbonded tokens to an `Unbond...


Near line 454: Possible spelling mistake found.
Context: ...nbonded shares from delegator * add the unbonded tokens to an UnbondingDelegationEntry...


Near line 457: Possible spelling mistake found.
Context: ...* update the validator with removed the delegator shares and associated coins * if the va...


Near line 458: Possible spelling mistake found.
Context: ...ded, transfer the Coinsworth of the unbonded shares from theBondedPoolto the...


Near line 459: Possible spelling mistake found.
Context: ...worth of the unbonded shares from the BondedPool to the NotBondedPool ModuleAccount...


Near line 459: Possible spelling mistake found.
Context: ...d shares from the BondedPool to the NotBondedPool ModuleAccount * remove the validator...


Near line 460: Possible spelling mistake found.
Context: ...ccount` * remove the validator if it is unbonded and there are no more delegation shares...


Near line 461: This sentence does not start with an uppercase letter.
Context: ... there are no more delegation shares. * remove the validator if it is unbonded and the...


Near line 461: Possible spelling mistake found.
Context: ...shares. * remove the validator if it is unbonded and there are no more delegation shares...


Near line 462: Possible spelling mistake found.
Context: ...o more delegation shares * get a unique unbondingId and map it to the `UnbondingDelegation...


Near line 462: Possible spelling mistake found.
Context: ... unique unbondingId and map it to the UnbondingDelegationEntry in UnbondingDelegationByUnbondingId ...


Near line 464: Possible spelling mistake found.
Context: ...gInitiated(unbondingId)hook * add the unbonding delegation toUnbondingDelegationQueue...


Near line 464: Possible spelling mistake found.
Context: ... hook * add the unbonding delegation to UnbondingDelegationQueue with the completion time set to `Unbon...


Near line 466: Possible spelling mistake found.
Context: ... set to UnbondingTime #### Cancel an UnbondingDelegation Entry When a `cancel unbond delegatio...


Near line 468: Possible spelling mistake found.
Context: ... an UnbondingDelegation Entry When a cancel unbond delegation occurs both the validator...


Near line 468: Possible missing comma found.
Context: ...ntry When a cancel unbond delegation occurs both the validator, the delegation ...


Near line 468: Possible spelling mistake found.
Context: ...he validator, the delegation and an UnbondingDelegationQueue state will be updated. * if cancel un...


Near line 470: This sentence does not start with an uppercase letter.
Context: ...egationQueue` state will be updated. * if cancel unbonding delegation amount equa...


Near line 470: Possible spelling mistake found.
Context: ...uestate will be updated. * if cancel unbonding delegation amount equals to theUnbond...


Near line 470: Possible spelling mistake found.
Context: ...bonding delegation amount equals to the UnbondingDelegation entry balance, then the `UnbondingDe...


Near line 470: Possible spelling mistake found.
Context: ...ngDelegationentrybalance, then the UnbondingDelegationentry deleted fromUnbondingDelegatio...


Near line 470: Possible spelling mistake found.
Context: ...UnbondingDelegationentry deleted fromUnbondingDelegationQueue. * if the cancel unbonding delegation...


Near line 471: This sentence does not start with an uppercase letter.
Context: ...eted from UnbondingDelegationQueue. * if the `cancel unbonding delegation amount...


Near line 471: Possible spelling mistake found.
Context: ...om UnbondingDelegationQueue. * if the cancel unbonding delegation amount is less than the Unb...


Near line 471: Possible spelling mistake found.
Context: ...ing delegation amount is less than the UnbondingDelegation entry balance, then the `UnbondingDele...


Near line 471: Possible spelling mistake found.
Context: ...ingDelegationentry balance, then theUnbondingDelegation` entry will be updated with new balance...


Near line 471: Possible spelling mistake found.
Context: ...ill be updated with new balance in the UnbondingDelegationQueue. * cancel amount is [Delegated](#del...


Near line 472: This sentence does not start with an uppercase letter.
Context: ...ce in the UnbondingDelegationQueue. * cancel amount is Delegated b...


Near line 472: It seems like there are too many consecutive spaces here.
Context: ...ntis [Delegated](#delegations) back to the originalvalidator`. #### Complete...


Near line 474: Possible spelling mistake found.
Context: ...he original validator. #### Complete Unbonding For undelegations which do not complet...


Near line 476: Possible spelling mistake found.
Context: ...lidator`. #### Complete Unbonding For undelegations which do not complete immediately, the ...


Near line 477: Possible spelling mistake found.
Context: ...the following operations occur when the unbonding delegation queue element matures: * re...


Near line 479: Possible spelling mistake found.
Context: ...t matures: * remove the entry from the UnbondingDelegation object * transfer the tokens from the ...


Near line 480: Possible spelling mistake found.
Context: ...object * transfer the tokens from theNotBondedPool ModuleAccountto the delegatorAcco...


Near line 480: Possible spelling mistake found.
Context: ...fer the tokens from the NotBondedPool ModuleAccount to the delegator Account #### Begin...


Near line 480: Possible spelling mistake found.
Context: ... NotBondedPool ModuleAccount to the delegator Account #### Begin Redelegation Red...


Near line 482: Possible spelling mistake found.
Context: ... to the delegator Account #### Begin Redelegation Redelegations affect the delegation, s...


Near line 483: Possible spelling mistake found.
Context: ...tor Account #### Begin Redelegation Redelegations affect the delegation, source and desti...


Near line 486: This sentence does not start with an uppercase letter.
Context: ..., source and destination validators. * perform an unbond delegation from the source ...


Near line 486: Possible spelling mistake found.
Context: ...d destination validators. * perform an unbond delegation from the source validator t...


Near line 486: Possible spelling mistake found.
Context: ...tor to retrieve the tokens worth of the unbonded shares * using the unbonded tokens, `De...


Near line 487: Possible spelling mistake found.
Context: ...orth of the unbonded shares * using the unbonded tokens, Delegate them to the destinat...


Near line 488: Add a space between sentences.
Context: ...m to the destination validator * if the sourceValidator.Status is Bonded, and the `destinationValid...


Near line 488: Possible spelling mistake found.
Context: ...eValidator.StatusisBonded, and the destinationValidator` is not, transfer the newly delegated...


Near line 489: Possible spelling mistake found.
Context: ...fer the newly delegated tokens from the BondedPool to the NotBondedPool ModuleAccount...


Near line 489: Possible spelling mistake found.
Context: ...ted tokens from the BondedPool to the NotBondedPool ModuleAccount * otherwise, if the `s...


Near line 490: Add a space between sentences.
Context: ...ol ModuleAccount* otherwise, if thesourceValidator.Statusis notBonded, and the destinationV...


Near line 490: Possible spelling mistake found.
Context: ...idator.Statusis notBonded, and the destinationValidator isBonded`, transfer the newly dele...


Near line 491: Possible spelling mistake found.
Context: ...fer the newly delegated tokens from the NotBondedPool to the BondedPool ModuleAccount * ...


Near line 491: Possible spelling mistake found.
Context: ... tokens from the NotBondedPool to the BondedPool ModuleAccount * record the token amo...


Near line 492: Use “a” instead of ‘an’ if the following word doesn’t start with a vowel sound, e.g. ‘a sentence’, ‘a university’.
Context: ...leAccount* record the token amount in an new entry in the relevantRedelegation...


Near line 494: Possible spelling mistake found.
Context: ...he relevant Redelegation From when a redelegation begins until it completes, the delegato...


Near line 494: Possible spelling mistake found.
Context: ...legation begins until it completes, the delegator is in a state of "pseudo-unbonding", an...


Near line 494: Possible spelling mistake found.
Context: ...pletes, the delegator is in a state of "pseudo-unbonding", and can still be slashed for infracti...


Near line 495: Possible spelling mistake found.
Context: ...or infractions that occurred before the redelegation began. #### Complete Redelegation Whe...


Near line 497: Possible spelling mistake found.
Context: ... the redelegation began. #### Complete Redelegation When a redelegations complete the foll...


Near line 499: Possible spelling mistake found.
Context: ...an. #### Complete Redelegation When a redelegations complete the following occurs: * remov...


Near line 501: Possible spelling mistake found.
Context: ...ng occurs: * remove the entry from the Redelegation object #### Consensus pubkey rotation...


Near line 503: Possible spelling mistake found.
Context: ...e Redelegation object #### Consensus pubkey rotation When a ConsPubkeyRotation o...


Near line 505: Possible spelling mistake found.
Context: ... #### Consensus pubkey rotation When a ConsPubkeyRotation occurs the validator and the `Validato...


Near line 505: Possible missing comma found.
Context: ...y rotation When a ConsPubkeyRotation occurs the validator and the `ValidatorConsens...


Near line 505: Possible spelling mistake found.
Context: ...yRotationoccurs the validator and theValidatorConsensusKeyRotationRecordQueueKey` are updated: * the old consensus pubk...


Near line 507: This sentence does not start with an uppercase letter.
Context: ...RotationRecordQueueKey` are updated: * the old consensus pubkey address will be re...


Near line 507: Possible spelling mistake found.
Context: ...eKey` are updated: * the old consensus pubkey address will be removed from state and ...


Near line 507: Possible spelling mistake found.
Context: ...be removed from state and new consensus pubkey address will be added in place. * trans...


Near line 508: This sentence does not start with an uppercase letter.
Context: ...ubkey address will be added in place. * transfers the voting power to the new consensus p...


Near line 508: Possible spelling mistake found.
Context: ...s the voting power to the new consensus pubkey address. * and triggers the hooks to up...


Near line 509: This sentence does not start with an uppercase letter.
Context: ... to the new consensus pubkey address. * and triggers the hooks to update the `signi...


Near line 518: Possible spelling mistake found.
Context: ...hed, the following occurs: * The total slashAmount is calculated as the slashFactor (a ...


Near line 518: Possible spelling mistake found.
Context: ...otal slashAmount is calculated as the slashFactor (a chain parameter) * `TokensFromCons...


Near line 518: Possible spelling mistake found.
Context: ...he slashFactor (a chain parameter) * TokensFromConsensusPower, the total number of tokens bonded t...


Near line 520: Possible spelling mistake found.
Context: ... at the time of the infraction. * Every unbonding delegation and pseudo-unbonding redeleg...


Near line 520: Possible spelling mistake found.
Context: ...ction. * Every unbonding delegation and pseudo-unbonding redelegation such that the infraction o...


Near line 520: Possible spelling mistake found.
Context: ...bonding delegation and pseudo-unbonding redelegation such that the infraction occurred befor...


Near line 520: Possible spelling mistake found.
Context: ...that the infraction occurred before the unbonding or redelegation began from the valida...


Near line 521: Possible spelling mistake found.
Context: ...tion occurred before the unbonding or redelegation began from the validator are slashed by...


Near line 521: Possible spelling mistake found.
Context: ...n from the validator are slashed by the slashFactor percentage of the initialBalance. * Ea...


Near line 521: Possible spelling mistake found.
Context: ... by the slashFactor percentage of the initialBalance. * Each amount slashed from redelegatio...


Near line 522: Possible spelling mistake found.
Context: ...tialBalance. * Each amount slashed from redelegations and unbonding delegations is subtracted...


Near line 522: Possible spelling mistake found.
Context: ...h amount slashed from redelegations and unbonding delegations is subtracted from the to...


Near line 524: Possible spelling mistake found.
Context: ...ed from the total slash amount. * The remaingSlashAmount is then slashed from the validator's t...


Near line 524: Possible spelling mistake found.
Context: ...shed from the validator's tokens in the BondedPool or NonBondedPool depending on the ...


Near line 524: Possible spelling mistake found.
Context: ...lidator's tokens in the BondedPool or NonBondedPool depending on the validator's status. T...


Near line 531: Possible spelling mistake found.
Context: ... only when they are caught. #### Slash Unbonding Delegation When a validator is slashed...


Near line 533: Possible spelling mistake found.
Context: ...en a validator is slashed, so are those unbonding delegations from the validator that beg...


Near line 533: Possible spelling mistake found.
Context: ...legations from the validator that began unbonding after the time of the infraction. Every...


Near line 534: Possible spelling mistake found.
Context: ...of the infraction. Every entry in every unbonding delegation from the validator is slashe...


Near line 535: Possible spelling mistake found.
Context: ...gation from the validator is slashed by slashFactor. The amount slashed is calculated from...


Near line 535: Possible spelling mistake found.
Context: ...e amount slashed is calculated from the InitialBalance of the delegation and is capped to pre...


Near line 536: Possible spelling mistake found.
Context: ...negative balance. Completed (or mature) unbondings are not slashed. #### Slash Redelegati...


Near line 538: Possible spelling mistake found.
Context: ...unbondings are not slashed. #### Slash Redelegation When a validator is slashed, so are al...


Near line 540: Possible spelling mistake found.
Context: ...When a validator is slashed, so are all redelegations from the validator that began after the...


Near line 541: Possible spelling mistake found.
Context: ...idator that began after the infraction. Redelegations are slashed by slashFactor. Redelegat...


Near line 541: Possible spelling mistake found.
Context: ...nfraction. Redelegations are slashed by slashFactor. Redelegations that began before the i...


Near line 541: Possible spelling mistake found.
Context: ...legations are slashed by slashFactor. Redelegations that began before the infraction are no...


Near line 543: Possible spelling mistake found.
Context: ...e amount slashed is calculated from the InitialBalance of the delegation and is capped to pre...


Near line 545: Possible spelling mistake found.
Context: ...nt a resulting negative balance. Mature redelegations (that have completed pseudo-unbonding) ...


Near line 545: Possible spelling mistake found.
Context: ...ture redelegations (that have completed pseudo-unbonding) are not slashed. ### How Shares are c...


Near line 549: This phrase is redundant. Consider writing “point” or “time”.
Context: ...How Shares are calculated At any given point in time, each validator has a number of tokens,...


Near line 550: Possible spelling mistake found.
Context: ...as a number of shares issued, S. Each delegator, i, holds a number of shares, S_i. ...


Near line 553: Possible spelling mistake found.
Context: ...us the rewards, minus the slashes. The delegator is entitled to a portion of the underly...


Near line 554: Possible spelling mistake found.
Context: ...ional to their proportion of shares. So delegator i is entitled to T * S_i / S of the...


Near line 556: Possible spelling mistake found.
Context: .../ S` of the validator's tokens. When a delegator delegates new tokens to the validator, ...


Near line 557: Possible spelling mistake found.
Context: ...ortional to their contribution. So when delegator j delegates T_j tokens, they receiv...


Near line 562: Possible spelling mistake found.
Context: ... undefined. For the initial delegation, delegator j who delegates T_j tokens receive ...


Near line 567: It appears that a comma is missing.
Context: ...ill have T = S. ## Messages In this section we describe the processing of the staki...


Near line 569: Possible spelling mistake found.
Context: ...ithin the state section. ### MsgCreateValidator A validator is created using the `MsgC...


Near line 571: Possible spelling mistake found.
Context: ...dator A validator is created using the MsgCreateValidator message. The validator must be created...


Near line 585: Possible spelling mistake found.
Context: ...egistered * another validator with this pubkey is already registered * the initial sel...


Near line 586: Possible spelling mistake found.
Context: ...initial self-delegation tokens are of a denom not specified as the bonding denom * th...


Near line 586: Possible spelling mistake found.
Context: ...of a denom not specified as the bonding denom * the commission parameters are faulty,...


Near line 590: Possible spelling mistake found.
Context: ...gative or > MaxRate * the initial MaxChangeRate is either negative or > MaxRate * th...


Near line 593: A comma may be missing after the conjunctive/linking adverb ‘Additionally’.
Context: ...lidator` object at appropriate indexes. Additionally a self-delegation is made with the init...


Near line 595: Possible spelling mistake found.
Context: ...gation`. The validator always starts as unbonded but may be bonded in the first end-bloc...


Near line 595: Possible missing comma found.
Context: ... The validator always starts as unbonded but may be bonded in the first end-block. ...


Near line 598: Possible spelling mistake found.
Context: ... be bonded in the first end-block. ### MsgEditValidator The Description, CommissionRate of...


Near line 600: Possible spelling mistake found.
Context: ...## MsgEditValidator The Description, CommissionRate of a validator can be updated using th...


Near line 600: Possible spelling mistake found.
Context: ...of a validator can be updated using the MsgEditValidator message. ```protobuf reference https:...


Near line 613: Possible spelling mistake found.
Context: ... is expected to fail if: * the initial CommissionRate is either negative or > MaxRate * th...


Near line 614: Possible spelling mistake found.
Context: ...is either negative or > MaxRate * the CommissionRate has already been updated within the pr...


Near line 615: Possible spelling mistake found.
Context: ...ated within the previous 24 hours * the CommissionRate is > MaxChangeRate * the description...


Near line 620: Possible spelling mistake found.
Context: ...es the updated Validator object. ### MsgDelegate Within this message the delegator prov...


Near line 622: It appears that a comma is missing.
Context: ...` object. ### MsgDelegate Within this message the delegator provides coins, and in re...


Near line 622: Possible spelling mistake found.
Context: ...## MsgDelegate Within this message the delegator provides coins, and in return receives ...


Near line 623: Possible spelling mistake found.
Context: ...nt of their validator's (newly created) delegator-shares that are assigned to `Delegation.Shares...


Near line 624: Add a space between sentences.
Context: ...) delegator-shares that are assigned to Delegation.Shares. ```protobuf reference https://github...


Near line 637: Did you mean ‘different from’? ‘Different than’ is often considered colloquial style.
Context: ...nt Coinhas a denomination different than one defined byparams.BondDenom` * the...


Near line 645: Possible spelling mistake found.
Context: ...include the newly received shares. The delegator receives newly minted shares at the cur...


Near line 649: Possible spelling mistake found.
Context: ...okens. The validator is updated in the ValidatorByPower index, and the delegation is tracked i...


Near line 653: Possible spelling mistake found.
Context: ...be added to the power index until it is unjailed. ![Delegation sequence](https://raw.gi...


Near line 657: Possible spelling mistake found.
Context: ...s/uml/svg/delegation_sequence.svg) ### MsgUndelegate The MsgUndelegate message allows del...


Near line 659: Possible spelling mistake found.
Context: ...n_sequence.svg) ### MsgUndelegate The MsgUndelegate message allows delegators to undelegat...


Near line 659: Possible spelling mistake found.
Context: ...ate The MsgUndelegate message allows delegators to undelegate their tokens from validat...


Near line 659: Possible spelling mistake found.
Context: ...ndelegate` message allows delegators to undelegate their tokens from validator. ```protob...


Near line 670: Possible spelling mistake found.
Context: ...e containing the completion time of the undelegation: ```protobuf reference https://github....


Near line 680: Did you mean “fewer”? The noun “shares” is countable.
Context: ...ator doesn't exist * the delegation has less shares than the ones worth of Amount ...


Near line 681: Possible spelling mistake found.
Context: ...n the ones worth of Amount * existing UnbondingDelegation has maximum entries as defined by `par...


Near line 682: Did you mean ‘different from’? ‘Different than’ is often considered colloquial style.
Context: ...e Amount has a denomination different than one defined by params.BondDenom When...


Near line 686: This sentence does not start with an uppercase letter.
Context: ...ocessed the following actions occur: * validator's DelegatorShares and the delegation'...


Near line 686: Possible spelling mistake found.
Context: ...following actions occur: * validator's DelegatorShares and the delegation's Shares are both...


Near line 687: Using ‘plenty’ without ‘of’ is considered to be informal.
Context: ...e token worth of the shares remove that amount tokens held within the validator * with those ...


Near line 689: Possible spelling mistake found.
Context: ... * Bonded - add them to an entry in UnbondingDelegation (create UnbondingDelegation if it do...


Near line 689: Possible spelling mistake found.
Context: ... entry in UnbondingDelegation (create UnbondingDelegation if it doesn't exist) with a completion...


Near line 689: Possible spelling mistake found.
Context: ...'t exist) with a completion time a full unbonding period from the current time. Update po...


Near line 689: Possible spelling mistake found.
Context: ...rent time. Update pool shares to reduce BondedTokens and increase NotBondedTokens by token w...


Near line 689: Possible spelling mistake found.
Context: ...res to reduce BondedTokens and increase NotBondedTokens by token worth of the shares. * `Un...


Near line 690: Possible spelling mistake found.
Context: ...* Unbonding - add them to an entry in UnbondingDelegation (create UnbondingDelegation if it do...


Near line 690: Possible spelling mistake found.
Context: ... entry in UnbondingDelegation (create UnbondingDelegation if it doesn't exist) with the same com...


Near line 690: Possible spelling mistake found.
Context: ... same completion time as the validator (UnbondingMinTime). * Unbonded - then send the coi...


Near line 697: Possible spelling mistake found.
Context: .../docs/uml/svg/unbond_sequence.svg) ### MsgCancelUnbondingDelegation The MsgCancelUnbondingDelegation mes...


Near line 699: Possible spelling mistake found.
Context: ... ### MsgCancelUnbondingDelegation The MsgCancelUnbondingDelegation message allows delegators to cancel th...


Near line 699: Possible spelling mistake found.
Context: ...ncelUnbondingDelegationmessage allows delegators to cancel theunbondingDelegation` ent...


Near line 699: Possible spelling mistake found.
Context: ...message allows delegators to cancel the unbondingDelegation entry and delegate back to a previous ...


Near line 699: Possible spelling mistake found.
Context: ...this feature does not support canceling unbond delegations from jailed validators. ``...


Near line 711: This sentence does not start with an uppercase letter.
Context: ...This message is expected to fail if: * the unbondingDelegation entry is already ...


Near line 711: Possible spelling mistake found.
Context: ... message is expected to fail if: * the unbondingDelegation entry is already processed. * the `can...


Near line 712: This sentence does not start with an uppercase letter.
Context: ...legationentry is already processed. * thecancel unbonding delegation` amount is...


Near line 712: Possible spelling mistake found.
Context: ...tionentry is already processed. * thecancel unbonding delegation` amount is greater than the ...


Near line 712: Possible spelling mistake found.
Context: ... delegationamount is greater than theunbondingDelegationentry balance. * thecancel unbonding...


Near line 713: This sentence does not start with an uppercase letter.
Context: ... unbondingDelegation entry balance. * the cancel unbonding delegation height do...


Near line 713: Possible spelling mistake found.
Context: ...bondingDelegationentry balance. * thecancel unbonding delegation` height doesn't exist in the...


Near line 713: Possible spelling mistake found.
Context: ...delegationheight doesn't exist in theunbondingDelegationQueueof the delegator. * theunbondingDele...


Near line 713: Possible spelling mistake found.
Context: ...n the unbondingDelegationQueue of the delegator. * the unbondingDelegation is from a ...


Near line 714: This sentence does not start with an uppercase letter.
Context: ...ingDelegationQueueof the delegator. * theunbondingDelegation` is from a jailed ...


Near line 714: Possible spelling mistake found.
Context: ...elegationQueueof the delegator. * theunbondingDelegation` is from a jailed validator. When this...


Near line 718: This sentence does not start with an uppercase letter.
Context: ...ocessed the following actions occur: * if the unbondingDelegation Entry balance...


Near line 718: Possible spelling mistake found.
Context: ... the following actions occur: * if the unbondingDelegation Entry balance is zero * in this co...


Near line 719: Possible spelling mistake found.
Context: ...balance is zero * in this condition unbondingDelegation entry will be removed from `unbondingD...


Near line 719: Possible spelling mistake found.
Context: ...gDelegationentry will be removed fromunbondingDelegationQueue. * otherwise unbondingDelegationQ...


Near line 720: This sentence does not start with an uppercase letter.
Context: ... from unbondingDelegationQueue. * otherwise unbondingDelegationQueue will be upda...


Near line 720: Possible spelling mistake found.
Context: ...ondingDelegationQueue. * otherwise unbondingDelegationQueuewill be updated with newunbondingDel...


Near line 720: Possible spelling mistake found.
Context: ...legationQueuewill be updated with newunbondingDelegation` entry balance and initial balance * th...


Near line 721: Possible spelling mistake found.
Context: ...e and initial balance * the validator's DelegatorShares and the delegation's Shares are both...


Near line 723: Possible spelling mistake found.
Context: ...increased by the message Amount. ### MsgBeginRedelegate The redelegation command allows delega...


Near line 725: Possible spelling mistake found.
Context: ... Amount. ### MsgBeginRedelegate The redelegation command allows delegators to instantly ...


Near line 725: Possible spelling mistake found.
Context: ...legate The redelegation command allows delegators to instantly switch validators. Once th...


Near line 726: Possible spelling mistake found.
Context: ...o instantly switch validators. Once the unbonding period has passed, the redelegation is ...


Near line 726: Possible spelling mistake found.
Context: ...ce the unbonding period has passed, the redelegation is automatically completed in the EndBl...


Near line 727: Possible spelling mistake found.
Context: ...ation is automatically completed in the EndBlocker. ```protobuf reference https://github....


Near line 737: Possible spelling mistake found.
Context: ...e containing the completion time of the redelegation: ```protobuf reference https://github....


Near line 747: Did you mean “fewer”? The noun “shares” is countable.
Context: ...dators don't exist * the delegation has less shares than the ones worth of Amount ...


Near line 748: Possible spelling mistake found.
Context: ... * the source validator has a receiving redelegation which is not matured (aka. the redelega...


Near line 748: Possible spelling mistake found.
Context: ...legation which is not matured (aka. the redelegation may be transitive) * existing `Redelega...


Near line 749: Possible spelling mistake found.
Context: ...elegation may be transitive) * existing Redelegation has maximum entries as defined by `par...


Near line 750: Did you mean ‘different from’? ‘Different than’ is often considered colloquial style.
Context: ...nt Coinhas a denomination different than one defined byparams.BondDenom` When...


Near line 754: This sentence does not start with an uppercase letter.
Context: ...ocessed the following actions occur: * the source validator's DelegatorShares an...


Near line 754: Possible spelling mistake found.
Context: ...ctions occur: * the source validator's DelegatorShares and the delegations Shares are both ...


Near line 755: Possible missing preposition found.
Context: ...reduced by the message SharesAmount * calculate the token worth of the shares remove th...


Near line 755: Possible missing comma found.
Context: ...unt` * calculate the token worth of the shares remove that amount tokens held within t...


Near line 755: Possible missing preposition found.
Context: ...calculate the token worth of the shares remove that amount tokens held within the sour...


Near line 755: Using ‘plenty’ without ‘of’ is considered to be informal.
Context: ...e token worth of the shares remove that amount tokens held within the source validator. * if ...


Near line 756: This sentence does not start with an uppercase letter.
Context: ...ens held within the source validator. * if the source validator is: * Bonded...


Near line 757: Possible spelling mistake found.
Context: ...s: * Bonded - add an entry to the Redelegation (create Redelegation if it doesn't e...


Near line 757: Possible spelling mistake found.
Context: ... an entry to the Redelegation (create Redelegation if it doesn't exist) with a completion...


Near line 757: Possible spelling mistake found.
Context: ...'t exist) with a completion time a full unbonding period from the current time. Update po...


Near line 757: Possible spelling mistake found.
Context: ...rent time. Update pool shares to reduce BondedTokens and increase NotBondedTokens by token w...


Near line 757: Possible spelling mistake found.
Context: ...res to reduce BondedTokens and increase NotBondedTokens by token worth of the shares (this may ...


Near line 758: Possible spelling mistake found.
Context: ... * Unbonding - add an entry to the Redelegation (create Redelegation if it doesn't e...


Near line 758: Possible spelling mistake found.
Context: ... an entry to the Redelegation (create Redelegation if it doesn't exist) with the same com...


Near line 758: Possible spelling mistake found.
Context: ... same completion time as the validator (UnbondingMinTime). * Unbonded - no action require...


Near line 760: Possible missing preposition found.
Context: ...ed` - no action required in this step * Delegate the token worth to the destination vali...


Near line 761: This sentence does not start with an uppercase letter.
Context: ...ving tokens back to the bonded state. * if there are no more Shares in the sourc...


Near line 767: Possible spelling mistake found.
Context: .../begin_redelegation_sequence.svg) ### MsgUpdateParams The MsgUpdateParams update the staki...


Near line 769: Possible spelling mistake found.
Context: ...equence.svg) ### MsgUpdateParams The MsgUpdateParams update the staking module parameters. ...


Near line 770: Possible spelling mistake found.
Context: ...date the staking module parameters. The params are updated through a governance propos...


Near line 771: Possible spelling mistake found.
Context: ...he gov module account address. When the MinCommissionRate is updated, all validators with a lowe...


Near line 771: Possible spelling mistake found.
Context: ...with a lower (max) commission rate than MinCommissionRate will be updated to MinCommissionRate...


Near line 771: Possible spelling mistake found.
Context: ... MinCommissionRate will be updated to MinCommissionRate. ```protobuf reference https://github...


Near line 779: This sentence does not start with an uppercase letter.
Context: ...` The message handling can fail if: * signer is not the authority defined in the sta...


Near line 781: Possible spelling mistake found.
Context: ... (usually the gov module account). ### MsgRotateConsPubKey The MsgRotateConsPubKey updates the ...


Near line 783: Possible spelling mistake found.
Context: ...account). ### MsgRotateConsPubKey The MsgRotateConsPubKey updates the consensus pubkey of a vali...


Near line 783: Possible spelling mistake found.
Context: ...RotateConsPubKey` updates the consensus pubkey of a validator with a new pubkey, the v...


Near line 784: Possible spelling mistake found.
Context: ...sensus pubkey of a validator with a new pubkey, the validator must pay rotation fees (...


Near line 784: Possible spelling mistake found.
Context: ...e 1000000stake) to rotate the consensus pubkey. ```protobuf reference https://github....


Near line 792: Possible spelling mistake found.
Context: ...essage handling can fail if: * The new pubkey is not a cryptotypes.PubKey. * The ne...


Near line 792: Add a space between sentences.
Context: ...can fail if: * The new pubkey is not a cryptotypes.PubKey. * The new pubkey is already associate...


Near line 793: Possible spelling mistake found.
Context: ...s not a cryptotypes.PubKey. * The new pubkey is already associated with another vali...


Near line 794: Possible spelling mistake found.
Context: ...iated with another validator. * The new pubkey is already present in the cons pubkey r...


Near line 794: Possible spelling mistake found.
Context: ...w pubkey is already present in the cons pubkey rotation history. * The validator addre...


Near line 796: Possible spelling mistake found.
Context: ...ddress is not in validators list. * The max_cons_pubkey_rotations limit reached within unbondi...


Near line 796: Possible spelling mistake found.
Context: ..._pubkey_rotations` limit reached within unbonding period. * The validator doesn't have en...


Near line 801: Possible spelling mistake found.
Context: ...for the rotation. ## Begin-Block Each abci begin block call, the historical info w...


Near line 802: Possible spelling mistake found.
Context: ... get stored and pruned according to the HistoricalEntries parameter. ### Historical Info Tracki...


Near line 806: Possible spelling mistake found.
Context: .... ### Historical Info Tracking If the HistoricalEntries parameter is 0, then the BeginBlock ...


Near line 806: Possible spelling mistake found.
Context: ...oricalEntriesparameter is 0, then theBeginBlock` performs a no-op. Otherwise, the late...


Near line 808: Possible spelling mistake found.
Context: ...historical info is stored under the key historicalInfoKey|height, while any entries older than `...


Near line 808: Possible spelling mistake found.
Context: ...y|height, while any entries older than height - HistoricalEntries` is deleted. In most cases, this result...


Near line 810: Possible spelling mistake found.
Context: ...ed per block. However, if the parameter HistoricalEntries has changed to a lower value there wil...


Near line 810: Consider adding a comma.
Context: ...calEntries` has changed to a lower value there will be multiple entries in the store t...


Near line 814: Possible spelling mistake found.
Context: ...hat must be pruned. ## End-Block Each abci end block call, the operations to updat...


Near line 820: Possible missing comma found.
Context: ...e end of every block. As a part of this process any updated validators are also returne...


Near line 821: Consider using just “returned”.
Context: ...process any updated validators are also returned back to CometBFT for inclusion in the CometB...


Near line 821: Possible spelling mistake found.
Context: ...ed validators are also returned back to CometBFT for inclusion in the CometBFT validator...


Near line 821: Possible spelling mistake found.
Context: ...d back to CometBFT for inclusion in the CometBFT validator set which is responsible for ...


Near line 822: Possible spelling mistake found.
Context: ...set which is responsible for validating CometBFT messages at the consensus layer. Operat...


Near line 825: This sentence does not start with an uppercase letter.
Context: ... layer. Operations are as following: * the new validator set is taken as the top `...


Near line 825: Add a space between sentences.
Context: ...e new validator set is taken as the top params.MaxValidators number of validators retrieved from ...


Near line 826: Possible spelling mistake found.
Context: ...mber of validators retrieved from the ValidatorsByPower index * the previous validator set is ...


Near line 828: Possible spelling mistake found.
Context: ...tor set: * missing validators begin unbonding and their Tokens are transferred from...


Near line 828: Possible spelling mistake found.
Context: ...their Tokens are transferred from the BondedPool to the NotBondedPool ModuleAccount...


Near line 829: Possible spelling mistake found.
Context: ...ferred from the BondedPool to the NotBondedPool ModuleAccount * new validators a...


Near line 830: Possible spelling mistake found.
Context: ...their Tokens are transferred from the NotBondedPool to the BondedPool ModuleAccount I...


Near line 831: Possible spelling mistake found.
Context: ...red from the NotBondedPool to the BondedPool ModuleAccount In all cases, any val...


Near line 835: Possible missing comma found.
Context: ...e message reporting their new consensus power which is passed back to CometBFT. The ...


Near line 835: Possible spelling mistake found.
Context: ...consensus power which is passed back to CometBFT. The LastTotalPower and `LastValidat...


Near line 837: Possible spelling mistake found.
Context: ... which is passed back to CometBFT. The LastTotalPower and LastValidatorsPower hold the sta...


Near line 837: Possible spelling mistake found.
Context: ... to CometBFT. The LastTotalPower and LastValidatorsPower hold the state of the total power and ...


Near line 839: Possible spelling mistake found.
Context: ...check for changes that have occurred in ValidatorsByPower and the total new power, which is calc...


Near line 840: Possible spelling mistake found.
Context: ...l new power, which is calculated during EndBlock. ### Queues Within staking, certain ...


Near line 845: Possible spelling mistake found.
Context: ... over a duration of time (typically the unbonding period). When these transitions are mat...


Near line 846: Possible missing comma found.
Context: ...ing period). When these transitions are mature certain operations must take place in o...


Near line 846: Consider a shorter alternative to avoid wordiness.
Context: ...ture certain operations must take place in order to complete the state operation. This is a...


Near line 847: Possible missing comma found.
Context: ...on. This is achieved through the use of queues which are checked/processed at the end ...


Near line 850: Possible spelling mistake found.
Context: ...ocessed at the end of each block. #### Unbonding Validators When a validator is kicked ...


Near line 853: Possible spelling mistake found.
Context: ...sufficient bonded tokens) it begins the unbonding process along with all its delegations ...


Near line 854: Possible missing preposition found.
Context: ... process along with all its delegations begin unbonding (while still being delegated ...


Near line 854: Possible spelling mistake found.
Context: ...ss along with all its delegations begin unbonding (while still being delegated to this va...


Near line 855: It appears that a comma is missing.
Context: ...g delegated to this validator). At this point the validator is said to be an "unbondi...


Near line 856: Possible spelling mistake found.
Context: ...s point the validator is said to be an "unbonding validator", whereby it will mature to b...


Near line 856: Possible spelling mistake found.
Context: ...", whereby it will mature to become an "unbonded validator" after the unbonding period h...


Near line 857: Possible spelling mistake found.
Context: ...ecome an "unbonded validator" after the unbonding period has passed. Each block the vali...


Near line 859: Possible spelling mistake found.
Context: ...dator queue is to be checked for mature unbonding validators (namely with a completion ti...


Near line 860: Do you wish to insert an arrow?
Context: ...lidators (namely with a completion time <= current time and completion height <= c...


Near line 860: Do you wish to insert an arrow?
Context: ...e <= current time and completion height <= current block height). At this point an...


Near line 861: It appears that a comma is missing.
Context: ...eight <= current block height). At this point any mature validators which do not have...


Near line 862: Possible spelling mistake found.
Context: ...eleted from state. For all other mature unbonding validators that still have remaining de...


Near line 863: Add a space between sentences.
Context: ...t still have remaining delegations, the validator.Status is switched from types.Unbonding to ...


Near line 864: Add a space between sentences.
Context: ...the validator.Status is switched from types.Unbonding to types.Unbonded. Unbonding operat...


Near line 864: Add a space between sentences.
Context: ...is switched fromtypes.Unbondingtotypes.Unbonded`. Unbonding operations can be put on h...


Near line 866: Possible spelling mistake found.
Context: ...types.Unbonding to types.Unbonded. Unbonding operations can be put on hold by extern...


Near line 868: Possible spelling mistake found.
Context: ...(unbondingId)` method. As a result, an unbonding operation (e.g., an unbonding delegatio...


Near line 868: Possible spelling mistake found.
Context: ...esult, an unbonding operation (e.g., an unbonding delegation) that is on hold, cannot com...


Near line 869: Possible spelling mistake found.
Context: ...te even if it reaches maturity. For an unbonding operation with unbondingId to eventua...


Near line 869: Possible spelling mistake found.
Context: ...turity. For an unbonding operation with unbondingId to eventually complete (after it reac...


Near line 873: Possible spelling mistake found.
Context: ...bondingCanComplete(unbondingId)`. #### Unbonding Delegations Complete the unbonding of ...


Near line 875: Possible spelling mistake found.
Context: ...### Unbonding Delegations Complete the unbonding of all mature `UnbondingDelegations.Ent...


Near line 875: Add a space between sentences.
Context: ...s Complete the unbonding of all mature UnbondingDelegations.Entries within the UnbondingDelegations queu...


Near line 875: Possible spelling mistake found.
Context: ...nbondingDelegations.Entrieswithin theUnbondingDelegations` queue with the following procedure: *...


Near line 878: This sentence does not start with an uppercase letter.
Context: ... queue with the following procedure: * transfer the balance coins to the delegator's wa...


Near line 878: Possible spelling mistake found.
Context: ...e: * transfer the balance coins to the delegator's wallet address * remove the mature en...


Near line 880: Possible spelling mistake found.
Context: ...bondingDelegation.Entries* remove theUnbondingDelegation` object from the store if there are no ...


Near line 883: Possible spelling mistake found.
Context: ...there are no remaining entries. #### Redelegations Complete the unbonding of all mature `...


Near line 885: Possible spelling mistake found.
Context: ...ries. #### Redelegations Complete the unbonding of all mature Redelegation.Entries wi...


Near line 885: Add a space between sentences.
Context: ...s Complete the unbonding of all mature Redelegation.Entries within the Redelegations queue with ...


Near line 885: Possible spelling mistake found.
Context: ...ature Redelegation.Entries within the Redelegations queue with the following procedure: *...


Near line 888: This sentence does not start with an uppercase letter.
Context: ... queue with the following procedure: * remove the mature entry from `Redelegation.Ent...


Near line 889: Possible spelling mistake found.
Context: ...rom Redelegation.Entries * remove the Redelegation object from the store if there are no ...


Near line 892: Possible spelling mistake found.
Context: ...there are no remaining entries. #### ConsPubKeyRotations After the completion of the unbonding ...


Near line 894: Possible spelling mistake found.
Context: ...yRotations After the completion of the unbonding period, matured rotations will be remov...


Near line 896: This sentence does not start with an uppercase letter.
Context: ...e validator for the next iterations. * remove the mature entry from state of `Validat...


Near line 905: The modal verb ‘can’ requires the verb’s base form.
Context: ...the hook name). The following hooks can registered with staking: * `AfterValidatorCreated...


Near line 916: Possible spelling mistake found.
Context: ...r * called when a validator begins unbonding *BeforeDelegationCreated(Context, Acc...


Near line 926: Possible spelling mistake found.
Context: ...ext, UnbondingID)` * called when an unbonding operation (validator unbonding, unbondi...


Near line 926: Possible spelling mistake found.
Context: ... when an unbonding operation (validator unbonding, unbonding delegation, redelegation) wa...


Near line 926: Possible spelling mistake found.
Context: ...bonding operation (validator unbonding, unbonding delegation, redelegation) was initiated...


Near line 926: Possible spelling mistake found.
Context: ...idator unbonding, unbonding delegation, redelegation) was initiated * `AfterConsensusPubKeyU...


Near line 928: This sentence does not start with an uppercase letter.
Context: ...bkey types.PubKey, fee sdk.Coin)` * called when a consensus pubkey rotation of a v...


Near line 928: Possible spelling mistake found.
Context: ...dk.Coin)` * called when a consensus pubkey rotation of a validator is initiated. ...


Near line 935: Possible spelling mistake found.
Context: ...module emits the following events: ### EndBlocker | Type | Attribute Ke...


Near line 937: Possible typo: you repeated a whitespace
Context: ...ollowing events: ### EndBlocker | Type | Attribute Key | Attribute Valu...


Near line 937: Possible typo: you repeated a whitespace
Context: ... | Type | Attribute Key | Attribute Value | | --------...


Near line 937: Possible typo: you repeated a whitespace
Context: ... Attribute Key | Attribute Value | | --------------------- | ------------...


Near line 939: Possible spelling mistake found.
Context: ... ------------------------- | | complete_unbonding | amount | {totalUnbo...


Near line 939: Possible typo: you repeated a whitespace
Context: ...----------------- | | complete_unbonding | amount | {totalUnbondin...


Near line 939: Possible typo: you repeated a whitespace
Context: ...----- | | complete_unbonding | amount | {totalUnbondingAmount} | | complete...


Near line 939: Possible typo: you repeated a whitespace
Context: ... | {totalUnbondingAmount} | | complete_unbonding | validator ...


Near line 940: Possible spelling mistake found.
Context: ... {totalUnbondingAmount} | | complete_unbonding | validator | {validator...


Near line 940: Possible typo: you repeated a whitespace
Context: ...bondingAmount} | | complete_unbonding | validator | {validatorAddr...


Near line 940: Possible typo: you repeated a whitespace
Context: ... | | complete_unbonding | validator | {validatorAddress} | | complete...


Near line 940: Possible typo: you repeated a whitespace
Context: ...lidator | {validatorAddress} | | complete_unbonding | delegator ...


Near line 941: Possible spelling mistake found.
Context: ... {validatorAddress} | | complete_unbonding | delegator | {delegator...


Near line 941: Possible typo: you repeated a whitespace
Context: ...orAddress} | | complete_unbonding | delegator | {delegatorAddr...


Near line 941: Possible spelling mistake found.
Context: ...ess} | | complete_unbonding | delegator | {delegatorAddress} ...


Near line 941: Possible typo: you repeated a whitespace
Context: ... | | complete_unbonding | delegator | {delegatorAddress} | | complete...


Near line 941: Possible typo: you repeated a whitespace
Context: ...legator | {delegatorAddress} | | complete_redelegation | amount ...


Near line 942: Possible spelling mistake found.
Context: ... {delegatorAddress} | | complete_redelegation | amount | {totalRedeleg...


Near line 942: Possible typo: you repeated a whitespace
Context: ... | | complete_redelegation | amount | {totalRedelegationAmount} | | complete...


Near line 943: Possible spelling mistake found.
Context: ... {totalRedelegationAmount} | | complete_redelegation | source_validator | {srcValidator...


Near line 943: Possible typo: you repeated a whitespace
Context: ...complete_redelegation | source_validator | {srcValidatorAddress} | | complete...


Near line 943: Possible typo: you repeated a whitespace
Context: ...e_validator | {srcValidatorAddress} | | complete_redelegation | destination_...


Near line 944: Possible spelling mistake found.
Context: ... {srcValidatorAddress} | | complete_redelegation | destination_validator | {dstValidator...


Near line 944: Possible typo: you repeated a whitespace
Context: ...nation_validator | {dstValidatorAddress} | | complete_redelegation | delegator ...


Near line 945: Possible spelling mistake found.
Context: ... {dstValidatorAddress} | | complete_redelegation | delegator | {delegatorAdd...


Near line 945: Possible spelling mistake found.
Context: ...ddress} | | complete_redelegation | delegator | {delegatorAddress} ...


Near line 945: Possible typo: you repeated a whitespace
Context: ... | | complete_redelegation | delegator | {delegatorAddress} | ## Msg's ...


Near line 945: Possible typo: you repeated a whitespace
Context: ...legator | {delegatorAddress} | ## Msg's ### MsgCreateValidator | T...


Near line 949: Possible spelling mistake found.
Context: ...legatorAddress} | ## Msg's ### MsgCreateValidator | Type | Attribute Key | A...


Near line 951: Possible typo: you repeated a whitespace
Context: ...## Msg's ### MsgCreateValidator | Type | Attribute Key | Attribute Value | |...


Near line 951: Possible typo: you repeated a whitespace
Context: ... | Attribute Key | Attribute Value | | ---------------- | ------------- | -...


Near line 953: Possible typo: you repeated a whitespace
Context: ...------- | | create_validator | validator | {validatorAddress} | | create_validato...


Near line 954: Possible typo: you repeated a whitespace
Context: ...orAddress} | | create_validator | amount | {delegationAmount} | | message ...


Near line 955: Possible typo: you repeated a whitespace
Context: ... | {delegationAmount} | | message | module | staking | |...


Near line 955: Possible typo: you repeated a whitespace
Context: ...ionAmount} | | message | module | staking | | message ...


Near line 955: Possible typo: you repeated a whitespace
Context: ...ssage | module | staking | | message | action | c...


Near line 956: Possible typo: you repeated a whitespace
Context: ... | staking | | message | action | create_validator | |...


Near line 956: Possible typo: you repeated a whitespace
Context: ... | | message | action | create_validator | | message ...


Near line 956: Possible typo: you repeated a whitespace
Context: ... | action | create_validator | | message | sender | {...


Near line 957: Possible typo: you repeated a whitespace
Context: ... | create_validator | | message | sender | {senderAddress} | ...


Near line 957: Possible typo: you repeated a whitespace
Context: ...alidator | | message | sender | {senderAddress} | ### MsgEditValid...


Near line 957: Possible typo: you repeated a whitespace
Context: ... | sender | {senderAddress} | ### MsgEditValidator | Type ...


Near line 959: Possible spelling mistake found.
Context: ...nder | {senderAddress} | ### MsgEditValidator | Type | Attribute Key ...


Near line 961: Possible typo: you repeated a whitespace
Context: ...ress} | ### MsgEditValidator | Type | Attribute Key | Attribute Value ...


Near line 961: Possible typo: you repeated a whitespace
Context: ...idator | Type | Attribute Key | Attribute Value | | --------------...


Near line 961: Possible typo: you repeated a whitespace
Context: ... | Attribute Key | Attribute Value | | -------------- | -------------------...


Near line 963: Possible typo: you repeated a whitespace
Context: ...--- | | edit_validator | commission_rate | {commissionRate} | | edit_validator...


Near line 963: Possible typo: you repeated a whitespace
Context: ...| commission_rate | {commissionRate} | | edit_validator | min_self_delegation...


Near line 965: Possible typo: you repeated a whitespace
Context: ...gation | {minSelfDelegation} | | message | module | staking ...


Near line 965: Possible typo: you repeated a whitespace
Context: ...fDelegation} | | message | module | staking | | message ...


Near line 965: Possible typo: you repeated a whitespace
Context: ...e | module | staking | | message | action ...


Near line 966: Possible typo: you repeated a whitespace
Context: ... | staking | | message | action | edit_validator ...


Near line 966: Possible typo: you repeated a whitespace
Context: ... | | message | action | edit_validator | | message ...


Near line 966: Possible typo: you repeated a whitespace
Context: ... | action | edit_validator | | message | sender ...


Near line 967: Possible typo: you repeated a whitespace
Context: ... | edit_validator | | message | sender | {senderAddress} ...


Near line 967: Possible typo: you repeated a whitespace
Context: ...lidator | | message | sender | {senderAddress} | ### MsgDelegate...


Near line 967: Possible typo: you repeated a whitespace
Context: ... | sender | {senderAddress} | ### MsgDelegate | Type | Attribu...


Near line 969: Possible spelling mistake found.
Context: ... | {senderAddress} | ### MsgDelegate | Type | Attribute Key | Attribute...


Near line 971: Possible typo: you repeated a whitespace
Context: ...rAddress} | ### MsgDelegate | Type | Attribute Key | Attribute Value | |...


Near line 971: Possible typo: you repeated a whitespace
Context: ...pe | Attribute Key | Attribute Value | | -------- | ------------- | ---------...


Near line 973: Possible typo: you repeated a whitespace
Context: ...--------------- | | delegate | validator | {validatorAddress} | | delegate | amou...


Near line 974: Possible typo: you repeated a whitespace
Context: ...{validatorAddress} | | delegate | amount | {delegationAmount} | | message | modu...


Near line 975: Possible typo: you repeated a whitespace
Context: ... | {delegationAmount} | | message | module | staking | |...


Near line 975: Possible typo: you repeated a whitespace
Context: ...{delegationAmount} | | message | module | staking | | message | acti...


Near line 975: Possible typo: you repeated a whitespace
Context: ...} | | message | module | staking | | message | action | delegate ...


Near line 976: Possible typo: you repeated a whitespace
Context: ... | staking | | message | action | delegate | |...


Near line 976: Possible typo: you repeated a whitespace
Context: ...staking | | message | action | delegate | | message | send...


Near line 976: Possible typo: you repeated a whitespace
Context: ... | | message | action | delegate | | message | sender | {senderAd...


Near line 977: Possible typo: you repeated a whitespace
Context: ... | delegate | | message | sender | {senderAddress} | ...


Near line 977: Possible typo: you repeated a whitespace
Context: ...delegate | | message | sender | {senderAddress} | ### MsgUndelegat...


Near line 977: Possible typo: you repeated a whitespace
Context: ...ssage | sender | {senderAddress} | ### MsgUndelegate | Type | Attrib...


Near line 979: Possible spelling mistake found.
Context: ...nder | {senderAddress} | ### MsgUndelegate | Type | Attribute Key | Attr...


Near line 981: Possible typo: you repeated a whitespace
Context: ...Address} | ### MsgUndelegate | Type | Attribute Key | Attribute Value ...


Near line 981: Possible typo: you repeated a whitespace
Context: ...MsgUndelegate | Type | Attribute Key | Attribute Value | | ------- | -----...


Near line 981: Possible typo: you repeated a whitespace
Context: ... | Attribute Key | Attribute Value | | ------- | ------------------- | ----...


Near line 983: Possible spelling mistake found.
Context: ...-------------- | ------------------ | | unbond | validator | {validatorAddr...


Near line 983: Possible typo: you repeated a whitespace
Context: ...-------- | ------------------ | | unbond | validator | {validatorAddres...


Near line 983: Possible typo: you repeated a whitespace
Context: ...---------------- | | unbond | validator | {validatorAddress} | | unbond | amoun...


Near line 984: Possible spelling mistake found.
Context: ...ator | {validatorAddress} | | unbond | amount | {unbondAmount}...


Near line 984: Possible typo: you repeated a whitespace
Context: ... | {validatorAddress} | | unbond | amount | {unbondAmount} ...


Near line 984: Possible typo: you repeated a whitespace
Context: ... {validatorAddress} | | unbond | amount | {unbondAmount} | | unbond | compl...


Near line 984: Possible typo: you repeated a whitespace
Context: ... | amount | {unbondAmount} | | unbond | completion_time [0] | {com...


Near line 985: Possible spelling mistake found.
Context: ...t | {unbondAmount} | | unbond | completion_time [0] | {completionTim...


Near line 985: Possible typo: you repeated a whitespace
Context: ... | {unbondAmount} | | unbond | completion_time [0] | {completionTime}...


Near line 985: Possible typo: you repeated a whitespace
Context: ...| completion_time [0] | {completionTime} | | message | module | stak...


Near line 986: Possible typo: you repeated a whitespace
Context: ... {completionTime} | | message | module | staking | | message | actio...


Near line 986: Possible typo: you repeated a whitespace
Context: ... message | module | staking | | message | action | begi...


Near line 987: Possible typo: you repeated a whitespace
Context: ... staking | | message | action | begin_unbonding | | message | sende...


Near line 987: Possible spelling mistake found.
Context: ...| message | action | begin_unbonding | | message | sender | ...


Near line 987: Possible typo: you repeated a whitespace
Context: ... | action | begin_unbonding | | message | sender | {sen...


Near line 988: Possible typo: you repeated a whitespace
Context: ... begin_unbonding | | message | sender | {senderAddress} | * [0] Time is fo...


Near line 988: Possible typo: you repeated a whitespace
Context: ... | sender | {senderAddress} | * [0] Time is formatted in the RFC333...


Near line 992: Possible spelling mistake found.
Context: ... formatted in the RFC3339 standard ### MsgCancelUnbondingDelegation | Type | Attr...


Near line 994: Possible typo: you repeated a whitespace
Context: ...### MsgCancelUnbondingDelegation | Type | Attribute Key | Attribute Value ...


Near line 994: Possible typo: you repeated a whitespace
Context: ... | Attribute Key | Attribute Value | ...


Near line 994: Possible typo: you repeated a whitespace
Context: ... | Attribute Key | Attribute Value | | ----------------------------- | ----...


Near line 995: Possible typo: you repeated a whitespace
Context: ...------------------- | ------------------ | ------------------------------------| ...


Near line 996: Possible spelling mistake found.
Context: ...-----------------------------| | cancel_unbonding_delegation | validator | {v...


Near line 996: Possible typo: you repeated a whitespace
Context: ...---------| | cancel_unbonding_delegation | validator | {validatorAddres...


Near line 996: Possible typo: you repeated a whitespace
Context: ...ancel_unbonding_delegation | validator | {validatorAddress} | ...


Near line 996: Possible typo: you repeated a whitespace
Context: ...validator | {validatorAddress} | | cancel_unbonding_delegation | dele...


Near line 997: Possible spelling mistake found.
Context: ...torAddress} | | cancel_unbonding_delegation | delegator | {d...


Near line 997: Possible typo: you repeated a whitespace
Context: ... | | cancel_unbonding_delegation | delegator | {delegatorAddres...


Near line 997: Possible spelling mistake found.
Context: ... | | cancel_unbonding_delegation | delegator | {delegatorAddress} ...


Near line 997: Possible typo: you repeated a whitespace
Context: ...ancel_unbonding_delegation | delegator | {delegatorAddress} | ...


Near line 997: Possible typo: you repeated a whitespace
Context: ...delegator | {delegatorAddress} | | cancel_unbonding_delegation | amou...


Near line 998: Possible spelling mistake found.
Context: ...torAddress} | | cancel_unbonding_delegation | amount | {c...


Near line 998: Possible typo: you repeated a whitespace
Context: ... | | cancel_unbonding_delegation | amount | {cancelUnbonding...


Near line 998: Possible typo: you repeated a whitespace
Context: ...| cancel_unbonding_delegation | amount | {cancelUnbondingDelegationAmount} | ...


Near line 998: Possible typo: you repeated a whitespace
Context: ... | {cancelUnbondingDelegationAmount} | | cancel_unbonding_delegation | crea...


Near line 999: Possible spelling mistake found.
Context: ...UnbondingDelegationAmount} | | cancel_unbonding_delegation | creation_height | {u...


Near line 999: Possible typo: you repeated a whitespace
Context: ...mount} | | cancel_unbonding_delegation | creation_height | {unbondingCreati...


Near line 999: Possible typo: you repeated a whitespace
Context: ...unbonding_delegation | creation_height | {unbondingCreationHeight} | ...


Near line 999: Possible typo: you repeated a whitespace
Context: ...n_height | {unbondingCreationHeight} | | message | modu...


Near line 1000: Possible typo: you repeated a whitespace
Context: ...ingCreationHeight} | | message | module | staking ...


Near line 1000: Possible typo: you repeated a whitespace
Context: ...| message | module | staking | ...


Near line 1000: Possible typo: you repeated a whitespace
Context: ... | module | staking | | message | acti...


Near line 1001: Possible typo: you repeated a whitespace
Context: ... | | message | action | cancel_unbond ...


Near line 1001: Possible typo: you repeated a whitespace
Context: ...| message | action | cancel_unbond | ...


Near line 1001: Possible spelling mistake found.
Context: ... | action | cancel_unbond | | message ...


Near line 1001: Possible typo: you repeated a whitespace
Context: ... | action | cancel_unbond | | message | send...


Near line 1002: Possible typo: you repeated a whitespace
Context: ...unbond | | message | sender | {senderAddress} ...


Near line 1002: Possible typo: you repeated a whitespace
Context: ...| message | sender | {senderAddress} | ...


Near line 1002: Possible typo: you repeated a whitespace
Context: ... | sender | {senderAddress} | ### MsgBeginRedelegate | Type ...


Near line 1004: Possible spelling mistake found.
Context: ...nderAddress} | ### MsgBeginRedelegate | Type | Attribute Key |...


Near line 1006: Possible typo: you repeated a whitespace
Context: ... | ### MsgBeginRedelegate | Type | Attribute Key | Attribute Valu...


Near line 1006: Possible typo: you repeated a whitespace
Context: ...Redelegate | Type | Attribute Key | Attribute Value | | ---------- |...


Near line 1006: Possible typo: you repeated a whitespace
Context: ... Attribute Key | Attribute Value | | ---------- | --------------------- |...


Near line 1008: Possible spelling mistake found.
Context: ...----------- | --------------------- | | redelegate | source_validator | {srcValidator...


Near line 1008: Possible typo: you repeated a whitespace
Context: ...------ | | redelegate | source_validator | {srcValidatorAddress} | | redelegate |...


Near line 1009: Possible spelling mistake found.
Context: ...idator | {srcValidatorAddress} | | redelegate | destination_validator | {dstValidator...


Near line 1010: Possible spelling mistake found.
Context: ...n_validator | {dstValidatorAddress} | | redelegate | amount | {unbondAmount...


Near line 1010: Possible typo: you repeated a whitespace
Context: ...alidatorAddress} | | redelegate | amount | {unbondAmount} | | redelegate |...


Near line 1010: Possible typo: you repeated a whitespace
Context: ...| amount | {unbondAmount} | | redelegate | completion_time [0] |...


Near line 1011: Possible spelling mistake found.
Context: ... | {unbondAmount} | | redelegate | completion_time [0] | {completionTi...


Near line 1011: Possible typo: you repeated a whitespace
Context: ... | | redelegate | completion_time [0] | {completionTime} | | message |...


Near line 1011: Possible typo: you repeated a whitespace
Context: ...completion_time [0] | {completionTime} | | message | module |...


Near line 1012: Possible typo: you repeated a whitespace
Context: ...0] | {completionTime} | | message | module | staking ...


Near line 1012: Possible typo: you repeated a whitespace
Context: ...letionTime} | | message | module | staking | | message |...


Near line 1012: Possible typo: you repeated a whitespace
Context: ...age | module | staking | | message | action |...


Near line 1013: Possible typo: you repeated a whitespace
Context: ... | staking | | message | action | begin_redelega...


Near line 1013: Possible typo: you repeated a whitespace
Context: ...ng | | message | action | begin_redelegate | | message |...


Near line 1013: Possible spelling mistake found.
Context: ...sage | action | begin_redelegate | | message | sender ...


Near line 1013: Possible typo: you repeated a whitespace
Context: ...action | begin_redelegate | | message | sender |...


Near line 1014: Possible typo: you repeated a whitespace
Context: ... | begin_redelegate | | message | sender | {senderAddress...


Near line 1014: Possible typo: you repeated a whitespace
Context: ..._redelegate | | message | sender | {senderAddress} | * [0] Time is...


Near line 1014: Possible typo: you repeated a whitespace
Context: ... sender | {senderAddress} | * [0] Time is formatted in the RFC333...


Near line 1022: Possible typo: you repeated a whitespace
Context: ...ontains the following parameters: | Key | Type | Example ...


Near line 1022: Possible typo: you repeated a whitespace
Context: ...meters: | Key | Type | Example | |------------...


Near line 1022: Possible typo: you repeated a whitespace
Context: ... | Type | Example | |------------------- |------------...


Near line 1023: Possible typo: you repeated a whitespace
Context: ...le | |------------------- |------------------|--------------------...


Near line 1024: Possible spelling mistake found.
Context: ...-----------|------------------------| | UnbondingTime | string (time ns) | "25920000...


Near line 1024: Possible typo: you repeated a whitespace
Context: ...-----------------------| | UnbondingTime | string (time ns) | "259200000000000" ...


Near line 1024: Possible spelling mistake found.
Context: ...| UnbondingTime | string (time ns) | "259200000000000" | | MaxValida...


Near line 1024: Possible typo: you repeated a whitespace
Context: ... | string (time ns) | "259200000000000" | | MaxValidators | uint16 ...


Near line 1025: Possible spelling mistake found.
Context: ... (time ns) | "259200000000000" | | MaxValidators | uint16 | 100 ...


Near line 1025: Possible typo: you repeated a whitespace
Context: ..."259200000000000" | | MaxValidators | uint16 | 100 ...


Near line 1025: Possible typo: you repeated a whitespace
Context: ... | | MaxValidators | uint16 | 100 | | KeyMaxEntri...


Near line 1025: Possible typo: you repeated a whitespace
Context: ...dators | uint16 | 100 | | KeyMaxEntries | uint16 ...


Near line 1026: Possible spelling mistake found.
Context: ... | 100 | | KeyMaxEntries | uint16 | 7 ...


Near line 1026: Possible typo: you repeated a whitespace
Context: ...100 | | KeyMaxEntries | uint16 | 7 ...


Near line 1026: Possible typo: you repeated a whitespace
Context: ... | | KeyMaxEntries | uint16 | 7 | | HistoricalE...


Near line 1026: Possible typo: you repeated a whitespace
Context: ...xEntries | uint16 | 7 | | HistoricalEntries | uint16 ...


Near line 1027: Possible spelling mistake found.
Context: ... | 7 | | HistoricalEntries | uint16 | 3 ...


Near line 1027: Possible typo: you repeated a whitespace
Context: ... | | HistoricalEntries | uint16 | 3 ...


Near line 1027: Possible typo: you repeated a whitespace
Context: ... | | HistoricalEntries | uint16 | 3 | | BondDenom ...


Near line 1027: Possible typo: you repeated a whitespace
Context: ...ricalEntries | uint16 | 3 | | BondDenom | string ...


Near line 1028: Possible spelling mistake found.
Context: ... | 3 | | BondDenom | string | "stak...


Near line 1028: Possible typo: you repeated a whitespace
Context: ... | 3 | | BondDenom | string | "stake" ...


Near line 1028: Possible typo: you repeated a whitespace
Context: ... | | BondDenom | string | "stake" | | MinCommissi...


Near line 1028: Possible typo: you repeated a whitespace
Context: ... | string | "stake" | | MinCommissionRate | string ...


Near line 1029: Possible spelling mistake found.
Context: ... | "stake" | | MinCommissionRate | string | "0.0000000000...


Near line 1029: Possible typo: you repeated a whitespace
Context: ...ke" | | MinCommissionRate | string | "0.0000000000000000...


Near line 1029: Possible typo: you repeated a whitespace
Context: ... | | MinCommissionRate | string | "0.000000000000000000" | | KeyRotation...


Near line 1030: Possible spelling mistake found.
Context: ... | "0.000000000000000000" | | KeyRotationFee | sdk.Coin | "1000000st...


Near line 1030: Possible typo: you repeated a whitespace
Context: ...0.000000000000000000" | | KeyRotationFee | sdk.Coin | "1000000stake" ...


Near line 1030: Possible spelling mistake found.
Context: ...000000000" | | KeyRotationFee | sdk.Coin | "1000000stake" |...


Near line 1030: Add a space between sentences.
Context: ...00000" | | KeyRotationFee | sdk.Coin | "1000000stake" | | Ma...


Near line 1030: Possible typo: you repeated a whitespace
Context: ...0" | | KeyRotationFee | sdk.Coin | "1000000stake" | | MaxConsPubk...


Near line 1030: Possible typo: you repeated a whitespace
Context: ... | sdk.Coin | "1000000stake" | | MaxConsPubkeyRotations | int ...


Near line 1031: Possible spelling mistake found.
Context: ...in | "1000000stake" | | MaxConsPubkeyRotations | int | 1 ...


Near line 1031: Possible typo: you repeated a whitespace
Context: ... | | MaxConsPubkeyRotations | int | 1 | :::warning M...


Near line 1031: Possible typo: you repeated a whitespace
Context: ...nsPubkeyRotations | int | 1 | :::warning Manually updating the `Min...


Near line 1034: Possible spelling mistake found.
Context: ... | :::warning Manually updating the MinCommissionRate parameter will not affect the commissi...


Near line 1034: Possible spelling mistake found.
Context: ...w validators. Update the parameter with MsgUpdateParams to affect the commission rate of the e...


Near line 1051: This sentence does not start with an uppercase letter.
Context: ...sh simd query staking --help ``` ##### delegation The delegation command allows users ...


Near line 1053: Possible spelling mistake found.
Context: ... to query delegations for an individual delegator on an individual validator. Usage: ``...


Near line 1081: Possible spelling mistake found.
Context: ... to query delegations for an individual delegator on all validators. Usage: ```bash sim...


Near line 1222: Possible spelling mistake found.
Context: ...time: "1970-01-01T00:00:00Z" ``` ##### params The params command allows users to q...


Near line 1224: Possible spelling mistake found.
Context: ...01-01T00:00:00Z" ``` ##### params The params command allows users to query values s...


Near line 1271: Possible spelling mistake found.
Context: ...0000" not_bonded_tokens: "0" ``` ##### redelegation The redelegation command allows user...


Near line 1273: Possible spelling mistake found.
Context: ...okens: "0" ``` ##### redelegation The redelegation command allows users to query a redele...


Near line 1273: Possible spelling mistake found.
Context: ...gation` command allows users to query a redelegation record based on delegator and a source ...


Near line 1273: Possible spelling mistake found.
Context: ...to query a redelegation record based on delegator and a source and destination validator ...


Near line 1312: Possible spelling mistake found.
Context: ...kuv9k8qzq6lrm9taddae7fpx59wm ``` ##### redelegations The redelegations command allows use...


Near line 1314: Possible spelling mistake found.
Context: ...e7fpx59wm ``` ##### redelegations The redelegations command allows users to query all rede...


Near line 1314: Possible spelling mistake found.
Context: ...ions` command allows users to query all redelegation records for an individual delegator. U...


Near line 1314: Possible spelling mistake found.
Context: ... redelegation records for an individual delegator. Usage: ```bash simd query staking re...


Near line 1367: Possible spelling mistake found.
Context: ...ta5cquje8ndkpz0rs046m7zqxrpp ``` ##### redelegations-from The redelegations-from command allow...


Near line 1369: Possible spelling mistake found.
Context: ...xrpp ``` ##### redelegations-from The redelegations-from command allows users to query delegati...


Near line 1369: Possible spelling mistake found.
Context: ...ows users to query delegations that are redelegating from a validator. Usage: ```bash si...


Near line 1422: Possible spelling mistake found.
Context: ...eyhzt6gse2k7ej3zgwmngeleucjy ``` ##### unbonding-delegation The unbonding-delegation command all...


Near line 1424: Possible spelling mistake found.
Context: ...jy ``` ##### unbonding-delegation The unbonding-delegation command allows users to query unbondin...


Near line 1424: Possible spelling mistake found.
Context: ...legation` command allows users to query unbonding delegations for an individual delegator...


Near line 1424: Possible spelling mistake found.
Context: ...unbonding delegations for an individual delegator on an individual validator. Usage: ``...


Near line 1450: Possible spelling mistake found.
Context: ...8ay0zduzj64hwre2fxs9ldmqhffj ``` ##### unbonding-delegations The unbonding-delegations command al...


Near line 1452: Possible spelling mistake found.
Context: ...j ``` ##### unbonding-delegations The unbonding-delegations command allows users to query all unbo...


Near line 1452: Possible spelling mistake found.
Context: ...ions` command allows users to query all unbonding-delegations records for one delegator. Usage: ```...


Near line 1452: Possible spelling mistake found.
Context: ...l unbonding-delegations records for one delegator. Usage: ```bash simd query staking un...


Near line 1483: Possible spelling mistake found.
Context: ...3ejzkjtntcyrqwvmvuknzmvtaaa ``` ##### unbonding-delegations-from The unbonding-delegations-from comma...


Near line 1485: Possible spelling mistake found.
Context: ... ##### unbonding-delegations-from The unbonding-delegations-from command allows users to query delegati...


Near line 1485: Possible spelling mistake found.
Context: ...ows users to query delegations that are unbonding from a validator. Usage: ```bash si...


Near line 1648: Possible spelling mistake found.
Context: ...T00:00:00Z" ``` #### Transactions The tx commands allows users to interact with...


Near line 1654: This sentence does not start with an uppercase letter.
Context: ...bash simd tx staking --help ``` ##### create-validator The command create-validator` allows ...


Near line 1675: Possible spelling mistake found.
Context: ...0.025stake" \ --from=mykey where `validator.json` contains: json { "pubkey": {"@ty...


Near line 1691: This sentence does not start with an uppercase letter.
Context: ...1", "min-self-delegation": "1" } ``` and pubkey can be obtained by using `simd t...


Near line 1692: Possible spelling mistake found.
Context: ... "min-self-delegation": "1" } ``` and pubkey can be obtained by using `simd tendermi...


Near line 1692: Possible spelling mistake found.
Context: ...`` and pubkey can be obtained by using simd tendermint show-validator command. ##...


Near line 1694: This sentence does not start with an uppercase letter.
Context: ...dermint show-validatorcommand. ##### delegate The commanddelegate` allows users to...


Near line 1726: Possible spelling mistake found.
Context: ...ew_website_url" --from mykey ``` ##### redelegate The command redelegate allows users ...


Near line 1728: Possible spelling mistake found.
Context: ...ykey ``` ##### redelegate The command redelegate allows users to redelegate illiquid to...


Near line 1728: Possible spelling mistake found.
Context: ...he command redelegate allows users to redelegate illiquid tokens from one validator to a...


Near line 1742: Possible spelling mistake found.
Context: ...px59wm 100stake --from mykey ``` ##### unbond The command unbond allows users to u...


Near line 1744: Possible spelling mistake found.
Context: ...om mykey ``` ##### unbond The command unbond allows users to unbond shares from a v...


Near line 1744: Possible spelling mistake found.
Context: ...d The command unbond allows users to unbond shares from a validator. Usage: ```ba...


Near line 1758: Possible spelling mistake found.
Context: ...100stake --from mykey ``` ##### cancel unbond The command cancel-unbond allow user...


Near line 1760: Possible spelling mistake found.
Context: ...y ``` ##### cancel unbond The command cancel-unbond allow users to cancel the unbonding de...


Near line 1760: Possible spelling mistake found.
Context: ...ancel-unbond` allow users to cancel the unbonding delegation entry and delegate back to t...


Near line 1774: Possible spelling mistake found.
Context: ...123 --from mykey ``` ##### rotate cons pubkey The command rotate-cons-pubkey allow...


Near line 1776: Possible spelling mistake found.
Context: ... ##### rotate cons pubkey The command rotate-cons-pubkey allows validators to rotate the associ...


Near line 1776: Possible spelling mistake found.
Context: ...tors to rotate the associated consensus pubkey to the new consensus pubkey. Usage: `...


Near line 1776: Possible spelling mistake found.
Context: ...d consensus pubkey to the new consensus pubkey. Usage: ```bash simd tx staking rotat...


Near line 1882: Possible spelling mistake found.
Context: ...minSelfDelegation": "1" } } ``` #### ValidatorDelegations The ValidatorDelegations endpoint qu...


Near line 1884: Possible spelling mistake found.
Context: ...} } ``` #### ValidatorDelegations The ValidatorDelegations endpoint queries delegate information ...


Near line 1920: Possible spelling mistake found.
Context: ...on": { "total": "1" } } ``` #### ValidatorUnbondingDelegations The ValidatorUnbondingDelegations en...


Near line 1922: Possible spelling mistake found.
Context: ...#### ValidatorUnbondingDelegations The ValidatorUnbondingDelegations endpoint queries delegate information ...


Near line 1974: Possible missing article found.
Context: ...dpoint queries delegate information for given validator delegator pair. ```bash cosm...


Near line 1974: Possible spelling mistake found.
Context: ...elegate information for given validator delegator pair. ```bash cosmos.staking.v1beta1.Q...


Near line 2009: Possible spelling mistake found.
Context: ...":"25083119936" } } } ``` #### UnbondingDelegation The UnbondingDelegation endpoint que...


Near line 2011: Possible spelling mistake found.
Context: ... } } ``` #### UnbondingDelegation The UnbondingDelegation endpoint queries unbonding information...


Near line 2011: Possible spelling mistake found.
Context: ... UnbondingDelegation endpoint queries unbonding information for given validator delegat...


Near line 2011: Possible missing article found.
Context: ...point queries unbonding information for given validator delegator. ```bash cosmos.st...


Near line 2011: Possible spelling mistake found.
Context: ...bonding information for given validator delegator. ```bash cosmos.staking.v1beta1.Query/...


Near line 2050: Possible spelling mistake found.
Context: ...85000000" } ] } } ``` #### DelegatorDelegations The DelegatorDelegations endpoint qu...


Near line 2052: Possible spelling mistake found.
Context: ...} } ``` #### DelegatorDelegations The DelegatorDelegations endpoint queries all delegations of a ...


Near line 2052: Possible spelling mistake found.
Context: ...oint queries all delegations of a given delegator address. ```bash cosmos.staking.v1beta...


Near line 2080: Possible spelling mistake found.
Context: ... null, "total": "1" } } ``` #### DelegatorUnbondingDelegations The DelegatorUnbondingDelegations en...


Near line 2082: Possible spelling mistake found.
Context: ...#### DelegatorUnbondingDelegations The DelegatorUnbondingDelegations endpoint queries all unbonding delegat...


Near line 2082: Possible spelling mistake found.
Context: ...ondingDelegations` endpoint queries all unbonding delegations of a given delegator addres...


Near line 2082: Possible spelling mistake found.
Context: ...es all unbonding delegations of a given delegator address. ```bash cosmos.staking.v1beta...


Near line 2127: Possible spelling mistake found.
Context: ... null, "total": "1" } } ``` #### Redelegations The Redelegations endpoint queries r...


Near line 2129: Possible spelling mistake found.
Context: ... "1" } } ``` #### Redelegations The Redelegations endpoint queries redelegations of give...


Near line 2129: Possible spelling mistake found.
Context: ...s The Redelegations endpoint queries redelegations of given address. ```bash cosmos.staki...


Near line 2172: Possible spelling mistake found.
Context: ...} ], "pagination": null } ``` #### DelegatorValidators The DelegatorValidators endpoint que...


Near line 2174: Possible spelling mistake found.
Context: ...ll } ``` #### DelegatorValidators The DelegatorValidators endpoint queries all validators inform...


Near line 2174: An apostrophe may be missing.
Context: ...legatorValidators` endpoint queries all validators information for given delegator. ```ba...


Near line 2174: Possible spelling mistake found.
Context: ...es all validators information for given delegator. ```bash cosmos.staking.v1beta1.Query/...


Near line 2230: Possible spelling mistake found.
Context: ... null, "total": "1" } } ``` #### DelegatorValidator The DelegatorValidator endpoint quer...


Near line 2232: Possible spelling mistake found.
Context: ... } } ``` #### DelegatorValidator The DelegatorValidator endpoint queries validator information...


Near line 2232: Possible spelling mistake found.
Context: ...queries validator information for given delegator validator ```bash cosmos.staking.v1bet...


Near line 2282: Possible spelling mistake found.
Context: ...n_self_delegation": "1" } } #### HistoricalInfo bash cosmos.staking.v1beta1.Query/H...


Near line 2385: Possible spelling mistake found.
Context: ...kens": "15657192425623" } } ``` #### Params The Params endpoint queries the pool...


Near line 2387: Possible spelling mistake found.
Context: ...7192425623" } } ``` #### Params The Params endpoint queries the pool information....


Near line 2417: Possible spelling mistake found.
Context: ...ingmodule using REST endpoints. #### DelegatorDelegations TheDelegtaorDelegations` REST endpoi...


Near line 2419: Possible spelling mistake found.
Context: ...points. #### DelegatorDelegations The DelegtaorDelegations REST endpoint queries all delegations ...


Near line 2419: Possible spelling mistake found.
Context: ...oint queries all delegations of a given delegator address. ```bash /cosmos/staking/v1bet...


Near line 2466: Possible spelling mistake found.
Context: ... null, "total": "2" } } ``` #### Redelegations The Redelegations REST endpoint quer...


Near line 2468: Possible spelling mistake found.
Context: ... "2" } } ``` #### Redelegations The Redelegations REST endpoint queries redelegations of...


Near line 2468: Possible spelling mistake found.
Context: ...e Redelegations REST endpoint queries redelegations of given address. ```bash /cosmos/stak...


Near line 2511: Possible spelling mistake found.
Context: ...} ], "pagination": null } ``` #### DelegatorUnbondingDelegations The DelegatorUnbondingDelegations RE...


Near line 2513: Possible spelling mistake found.
Context: ...#### DelegatorUnbondingDelegations The DelegatorUnbondingDelegations REST endpoint queries all unbonding de...


Near line 2513: Possible spelling mistake found.
Context: ...gDelegations` REST endpoint queries all unbonding delegations of a given delegator addres...


Near line 2513: Possible spelling mistake found.
Context: ...es all unbonding delegations of a given delegator address. ```bash /cosmos/staking/v1bet...


Near line 2552: Possible spelling mistake found.
Context: ... null, "total": "1" } } ``` #### DelegatorValidators The DelegatorValidators REST endpoin...


Near line 2554: Possible spelling mistake found.
Context: ... } } ``` #### DelegatorValidators The DelegatorValidators REST endpoint queries all validators i...


Near line 2554: An apostrophe may be missing.
Context: ...orValidators` REST endpoint queries all validators information for given delegator address...


Near line 2554: Possible spelling mistake found.
Context: ...es all validators information for given delegator address. ```bash /cosmos/staking/v1bet...


Near line 2610: Possible spelling mistake found.
Context: ... null, "total": "1" } } ``` #### DelegatorValidator The DelegatorValidator REST endpoint...


Near line 2612: Possible spelling mistake found.
Context: ... } } ``` #### DelegatorValidator The DelegatorValidator REST endpoint queries validator inform...


Near line 2612: Possible missing article found.
Context: ...point queries validator information for given delegator validator pair. ```bash /cos...


Near line 2612: Possible spelling mistake found.
Context: ...queries validator information for given delegator validator pair. ```bash /cosmos/stakin...


Near line 2662: Possible spelling mistake found.
Context: ...n_self_delegation": "1" } } ``` #### HistoricalInfo The HistoricalInfo REST endpoint que...


Near line 2664: Possible spelling mistake found.
Context: ..."1" } } ``` #### HistoricalInfo The HistoricalInfo REST endpoint queries the historical i...


Near line 2960: Possible spelling mistake found.
Context: ...n_self_delegation": "1" } } ``` #### ValidatorDelegations The ValidatorDelegations REST endpoi...


Near line 2962: Possible spelling mistake found.
Context: ...} } ``` #### ValidatorDelegations The ValidatorDelegations REST endpoint queries delegate informa...


Near line 3044: Possible missing article found.
Context: ...dpoint queries delegate information for given validator delegator pair. ```bash /cos...


Near line 3044: Possible spelling mistake found.
Context: ...elegate information for given validator delegator pair. ```bash /cosmos/staking/v1beta1/...


Near line 3076: Possible spelling mistake found.
Context: ...unt": "500000000" } } } ``` #### UnbondingDelegation The UnbondingDelegation REST endpoin...


Near line 3078: Possible spelling mistake found.
Context: ... } } ``` #### UnbondingDelegation The UnbondingDelegation REST endpoint queries unbonding inform...


Near line 3078: Possible spelling mistake found.
Context: ...ondingDelegation` REST endpoint queries unbonding information for given validator delegat...


Near line 3078: Possible missing article found.
Context: ...point queries unbonding information for given validator delegator pair. ```bash /cos...


Near line 3078: Possible spelling mistake found.
Context: ...bonding information for given validator delegator pair. ```bash /cosmos/staking/v1beta1/...


Near line 3111: Possible spelling mistake found.
Context: ... "525111" } ] } } ``` #### ValidatorUnbondingDelegations The ValidatorUnbondingDelegations RE...


Near line 3113: Possible spelling mistake found.
Context: ...#### ValidatorUnbondingDelegations The ValidatorUnbondingDelegations REST endpoint queries unbonding delega...


Near line 3113: Possible spelling mistake found.
Context: ...ndingDelegations` REST endpoint queries unbonding delegations of a validator. ```bash /c...

Path-based Instructions (1)
x/staking/README.md (1)

Pattern **/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness"


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

Comment thread x/staking/README.md
An entry is added in `OldToNewConsKeyMap` collection for every rotation (Note: this is to handle the evidences when submitted with old cons key).

An entry is added in `NewToOldConsKeyMap` collection for every rotation, this entry is to block the rotation if the validator is rotating to the cons key which is invovled in the history.
An entry is added in `NewToOldConsKeyMap` collection for every rotation, this entry is to block the rotation if the validator is rotating to the cons key which is involved in the history.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ensure there are no trailing spaces at the end of this line.

- An entry is added in `NewToOldConsKeyMap` collection for every rotation, this entry is to block the rotation if the validator is rotating to the cons key which is involved in the history. 
+ An entry is added in `NewToOldConsKeyMap` collection for every rotation, this entry is to block the rotation if the validator is rotating to the cons key which is involved in the history.

Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.

Suggested change
An entry is added in `NewToOldConsKeyMap` collection for every rotation, this entry is to block the rotation if the validator is rotating to the cons key which is involved in the history.
An entry is added in `NewToOldConsKeyMap` collection for every rotation, this entry is to block the rotation if the validator is rotating to the cons key which is involved in the history.

@tac0turtle tac0turtle enabled auto-merge April 22, 2024 06:35
@tac0turtle tac0turtle added this pull request to the merge queue Apr 22, 2024
Merged via the queue into cosmos:main with commit 63f386e Apr 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants