feat(x/protocolpool)!: allow any coins in continuous funds #21916
Conversation
📝 Walkthrough📝 WalkthroughWalkthroughThe changes involve significant updates to the Changes
Possibly related PRs
Suggested labels
Suggested reviewers
📜 Recent review detailsConfiguration used: .coderabbit.yml 📒 Files selected for processing (3)
🧰 Additional context used📓 Path-based instructions (3)
🔇 Additional comments (10)
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? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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 using PR comments)
Other keywords and placeholders
Documentation and Community
|
…/allow-all-coins-protopool
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
| x.Amount = *clv.list | ||
| default: | ||
| if fd.IsExtension() { | ||
| panic(fmt.Errorf("proto3 declared messages do not support extensions: cosmos.protocolpool.v1.DistributionAmount")) |
Check warning
Code scanning / CodeQL
Panic in BeginBock or EndBlock consensus methods Warning
| if fd.IsExtension() { | ||
| panic(fmt.Errorf("proto3 declared messages do not support extensions: cosmos.protocolpool.v1.DistributionAmount")) | ||
| } | ||
| panic(fmt.Errorf("message cosmos.protocolpool.v1.DistributionAmount does not contain field %s", fd.FullName())) |
Check warning
Code scanning / CodeQL
Panic in BeginBock or EndBlock consensus methods Warning
facundomedica
requested review from
hieuvubk,
alpe and
a team
as code owners
|
@facundomedica your pull request is missing a changelog! |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 12
🧹 Outside diff range and nitpick comments (16)
x/protocolpool/keeper/genesis_test.go (3)
35-35: LGTM! Consider adding a constant for the coin denom.The change to use
DistributionAmountwithsdk.NewCoinsaligns well with the PR objective of allowing any coins in continuous funds. This provides more flexibility in representing different coin types.Consider defining a constant for the "stake" denom at the package level to improve maintainability:
const testDenom = "stake"Then use it in the test:
Amount: types.DistributionAmount{Amount: sdk.NewCoins(sdk.NewCoin(testDenom, math.NewInt(100)))},
43-43: LGTM! Consider using a variable for consistency.The change to use
DistributionAmountforLastBalanceis consistent with the previous change and aligns with the PR objectives.For better consistency and to make the relationship between the distributed amount and last balance clearer, consider using a variable:
distributionAmount := math.NewInt(100) lastBalanceAmount := math.NewInt(1) gs.Distributions = append(gs.Distributions, &types.Distribution{ Amount: types.DistributionAmount{Amount: sdk.NewCoins(sdk.NewCoin(testDenom, distributionAmount))}, Time: &time.Time{}, }) gs.LastBalance = types.DistributionAmount{Amount: sdk.NewCoins(sdk.NewCoin(testDenom, lastBalanceAmount))}This makes it easier to adjust the test scenario and clearly shows that the last balance is less than the distribution amount.
52-52: LGTM! Consider using a variable for the expected amount.The updated assertion correctly checks the specific coin amount in the new
LastBalancestructure.To improve clarity and maintain consistency with the earlier suggestions, consider using a variable for the expected amount:
expectedLastBalance := math.OneInt() suite.Require().Equal(expectedLastBalance, exportedGenState.LastBalance.Amount.AmountOf(testDenom))This makes the expected value more explicit and easier to update if needed.
x/protocolpool/types/genesis.go (1)
Line range hint
1-78: Overall assessment: Changes look good, but ensure comprehensive testing.The modifications to the
NewGenesisStatefunction, particularly theLastBalancefield initialization, are consistent with the PR objectives of allowing any coins in continuous funds. The changes adhere to Golang coding standards and the Uber Golang style guide.However, given that this change affects a fundamental structure (
GenesisState), it's crucial to:
- Thoroughly test the impact of this change on all components that interact with
GenesisState.- Update any relevant documentation to reflect the new
LastBalancetype and initialization.- Consider adding or updating unit tests to cover the new
LastBalancebehavior.Consider adding a comment above the
NewGenesisStatefunction explaining the rationale behind initializingLastBalancewith an empty set of coins, as this might not be immediately obvious to other developers.x/protocolpool/proto/cosmos/protocolpool/v1/types.proto (1)
46-54: LGTM: NewDistributionAmountmessage added with appropriate options.The new
DistributionAmountmessage is well-structured and aligns with the PR objective of allowing any coins in continuous funds. The use ofrepeated cosmos.base.v1beta1.Coinwith appropriate Gogoproto and Amino options ensures compatibility and consistent behavior.Consider adding a brief comment above the
amountfield to describe its purpose and any constraints (e.g., "Stores multiple coin types for distribution. Must not be empty."). This would enhance the self-documentation of the proto file.message DistributionAmount { + // Stores multiple coin types for distribution. Must not be empty. repeated cosmos.base.v1beta1.Coin amount = 1 [ (gogoproto.nullable) = false, (gogoproto.castrepeated) = "github.com/cosmos/cosmos-sdk/types.Coins", (amino.dont_omitempty) = true, (amino.encoding) = "legacy_coins" ]; }x/protocolpool/keeper/msg_server.go (1)
160-162: LGTM with a minor suggestion for clarity.The initialization of
RecipientFundDistributionwith an empty coin set is correct and aligns with the new flexibility to handle multiple coin types. This change supports the PR objective of allowing any coins in continuous funds.For improved clarity and consistency with Go conventions, consider using a composite literal directly:
err = k.RecipientFundDistribution.Set(ctx, recipient, types.DistributionAmount{Amount: sdk.Coins{}})This minor change eliminates the need for the
NewCoins()function call while achieving the same result.x/protocolpool/keeper/keeper_test.go (2)
143-150: LGTM: Updated type handling in TestIterateAndUpdateFundsDistributionThe changes correctly reflect the transition from
math.Inttotypes.DistributionAmount. The test logic has been appropriately updated to check theAmountfield of the new type.Consider adding a test case for a
DistributionAmountwith multiple coins to ensure the new type is fully exercised.
211-220: LGTM: Updated type handling in TestSetToDistributeThe changes correctly reflect the transition to using
DistributionAmount. The test logic has been appropriately updated to check theAmountfield of the new type.Consider adding a test case with multiple coins in the
DistributionAmountto ensure the new type is fully tested.x/protocolpool/keeper/genesis.go (2)
58-58: Consider renaming fields for clarityIn lines 58 and 60, the code references
distribution.Amount.Amount, which can be confusing due to the repeated use ofAmount. To improve readability and maintainability, consider renaming one of theAmountfields in theDistributionAmountstruct. For example, you could rename the innerAmountfield toCoins, resulting indistribution.Amount.Coins.Apply this diff to rename the field:
-type DistributionAmount struct { - Amount sdk.Coins -} +type DistributionAmount struct { + Coins sdk.Coins +}This change will require updating all usages of
distribution.Amount.Amounttodistribution.Amount.Coins.Also applies to: 60-60
Line range hint
121-127: Avoid variable shadowing of theerrvariable in the closureIn the anonymous function passed to
k.Distributions.Walk, the named return parametererr errorshadows theerrvariable in the outer scope. This can lead to confusion and potential errors. According to the Uber Go Style Guide, it's recommended to avoid shadowing variables.Consider removing the named return parameters or renaming them to prevent shadowing.
Apply this diff:
-err = k.Distributions.Walk(ctx, nil, func(key time.Time, value types.DistributionAmount) (stop bool, err error) { +err = k.Distributions.Walk(ctx, nil, func(key time.Time, value types.DistributionAmount) (stop bool, walkErr error) {Since the
errvariable is not used inside the function body, you could also omit the named return parameter:-err = k.Distributions.Walk(ctx, nil, func(key time.Time, value types.DistributionAmount) (stop bool, err error) { +err = k.Distributions.Walk(ctx, nil, func(key time.Time, value types.DistributionAmount) (bool, error) {This avoids shadowing the outer
errvariable and improves code clarity.x/protocolpool/keeper/keeper.go (1)
153-154: Address the TODO comment regarding allowed denominationsThere is a TODO comment indicating the need to handle cases where the balance does not contain any of the allowed denominations. Please implement this logic to ensure proper functioning and prevent potential issues with unsupported denominations.
Would you like assistance in implementing this check? I can help draft the necessary code or open a GitHub issue to track this task.
x/protocolpool/keeper/msg_server_test.go (2)
486-488: Redundant Setting of Zero Distribution AmountsIn lines 486-488, both
RecipientFundDistributionandDistributionsare set tosdk.NewCoins(), which represents an empty coin set. Since these are default zero values, consider removing these explicit initializations to reduce redundancy.
Line range hint
832-847: Optimize Redundant Initializations in Test SetupIn lines 832-847,
RecipientFundDistributionis set tosdk.NewCoins()for multiple recipients during test setup. Since the distributions default to empty, these explicit initializations might be unnecessary. Removing them could simplify the test setup.api/cosmos/protocolpool/v1/types.pulsar.go (1)
1370-1370: Avoid leading underscores and underscores in type names; prefer CamelCase.The type
_DistributionAmount_1_listbegins with an underscore and uses underscores in its name, which goes against Go naming conventions. According to the Uber Go Style Guide, underscores should be avoided in names. Consider renaming the type todistributionAmountListorDistributionAmountList.Apply this diff to rename the type:
-type _DistributionAmount_1_list struct { +type distributionAmountList struct { // fields... }Ensure all references to this type are updated accordingly.
api/cosmos/protocolpool/v1/tx.pulsar.go (2)
7467-7469: Fix the indentation of thewithdrawn_allocated_fundfield.The
withdrawn_allocated_fundfield is not properly indented. It should be aligned with the other fields in theMsgCancelContinuousFundResponsemessage.Apply this diff to fix the indentation:
- WithdrawnAllocatedFund []*v1beta1.Coin `protobuf:"bytes,4,rep,name=withdrawn_allocated_fund,json=withdrawnAllocatedFund,proto3" json:"withdrawn_allocated_fund,omitempty"` + WithdrawnAllocatedFund []*v1beta1.Coin `protobuf:"bytes,4,rep,name=withdrawn_allocated_fund,json=withdrawnAllocatedFund,proto3" json:"withdrawn_allocated_fund,omitempty"`
7561-7563: Fix the indentation of theamountfield.The
amountfield is not properly indented. It should be aligned with the other fields in theMsgWithdrawContinuousFundResponsemessage.Apply this diff to fix the indentation:
- Amount []*v1beta1.Coin `protobuf:"bytes,1,rep,name=amount,proto3" json:"amount,omitempty"` + Amount []*v1beta1.Coin `protobuf:"bytes,1,rep,name=amount,proto3" json:"amount,omitempty"`
📜 Review details
Configuration used: .coderabbit.yml
Review profile: CHILL
🔇 Files ignored due to path filters (3)
x/protocolpool/types/genesis.pb.gois excluded by!**/*.pb.gox/protocolpool/types/tx.pb.gois excluded by!**/*.pb.gox/protocolpool/types/types.pb.gois excluded by!**/*.pb.go
📒 Files selected for processing (16)
- api/cosmos/protocolpool/v1/genesis.pulsar.go (32 hunks)
- api/cosmos/protocolpool/v1/tx.pulsar.go (26 hunks)
- api/cosmos/protocolpool/v1/types.pulsar.go (6 hunks)
- x/protocolpool/depinject.go (1 hunks)
- x/protocolpool/keeper/genesis.go (2 hunks)
- x/protocolpool/keeper/genesis_test.go (2 hunks)
- x/protocolpool/keeper/keeper.go (10 hunks)
- x/protocolpool/keeper/keeper_test.go (4 hunks)
- x/protocolpool/keeper/msg_server.go (1 hunks)
- x/protocolpool/keeper/msg_server_test.go (18 hunks)
- x/protocolpool/proto/cosmos/protocolpool/v1/genesis.proto (2 hunks)
- x/protocolpool/proto/cosmos/protocolpool/v1/tx.proto (2 hunks)
- x/protocolpool/proto/cosmos/protocolpool/v1/types.proto (2 hunks)
- x/protocolpool/testutil/expected_keepers_mocks.go (0 hunks)
- x/protocolpool/types/expected_keepers.go (0 hunks)
- x/protocolpool/types/genesis.go (1 hunks)
💤 Files not reviewed due to no reviewable changes (2)
- x/protocolpool/testutil/expected_keepers_mocks.go
- x/protocolpool/types/expected_keepers.go
🧰 Additional context used
📓 Path-based instructions (11)
api/cosmos/protocolpool/v1/genesis.pulsar.go (1)
Pattern
**/*.go: Review the Golang code for conformity with the Uber Golang style guide, highlighting any deviations.api/cosmos/protocolpool/v1/tx.pulsar.go (1)
Pattern
**/*.go: Review the Golang code for conformity with the Uber Golang style guide, highlighting any deviations.api/cosmos/protocolpool/v1/types.pulsar.go (1)
Pattern
**/*.go: Review the Golang code for conformity with the Uber Golang style guide, highlighting any deviations.x/protocolpool/depinject.go (1)
Pattern
**/*.go: Review the Golang code for conformity with the Uber Golang style guide, highlighting any deviations.x/protocolpool/keeper/genesis.go (1)
Pattern
**/*.go: Review the Golang code for conformity with the Uber Golang style guide, highlighting any deviations.x/protocolpool/keeper/genesis_test.go (2)
Pattern
**/*.go: Review the Golang code for conformity with the Uber Golang style guide, highlighting any deviations.
Pattern
**/*_test.go: "Assess the unit test code assessing sufficient code coverage for the changes associated in the pull request"x/protocolpool/keeper/keeper.go (1)
Pattern
**/*.go: Review the Golang code for conformity with the Uber Golang style guide, highlighting any deviations.x/protocolpool/keeper/keeper_test.go (2)
Pattern
**/*.go: Review the Golang code for conformity with the Uber Golang style guide, highlighting any deviations.
Pattern
**/*_test.go: "Assess the unit test code assessing sufficient code coverage for the changes associated in the pull request"x/protocolpool/keeper/msg_server.go (1)
Pattern
**/*.go: Review the Golang code for conformity with the Uber Golang style guide, highlighting any deviations.x/protocolpool/keeper/msg_server_test.go (2)
Pattern
**/*.go: Review the Golang code for conformity with the Uber Golang style guide, highlighting any deviations.
Pattern
**/*_test.go: "Assess the unit test code assessing sufficient code coverage for the changes associated in the pull request"x/protocolpool/types/genesis.go (1)
Pattern
**/*.go: Review the Golang code for conformity with the Uber Golang style guide, highlighting any deviations.
📓 Learnings (1)
x/protocolpool/keeper/genesis.go (1)
Learnt from: likhita-809 PR: cosmos/cosmos-sdk#18471 File: x/protocolpool/keeper/genesis.go:12-51 Timestamp: 2023-11-22T12:32:39.368Z Learning: - The user `likhita-809` has confirmed the changes suggested in the previous interaction. - The file in question is `x/protocolpool/keeper/genesis.go` from a Cosmos SDK module. - The changes involve optimizing the `InitGenesis` function by removing redundant code and ensuring proper handling of start times for budget proposals.
🔇 Additional comments not posted (64)
x/protocolpool/keeper/genesis_test.go (1)
Line range hint
1-52: Overall, the changes effectively test the new multi-coin functionality.The updates to
TestInitGenesisalign well with the PR objective of allowing any coins in continuous funds. The test now usesDistributionAmountwithsdk.NewCoinsfor bothDistributionsandLastBalance, which provides more flexibility in representing different coin types.The test scenario effectively checks the case where the total to be distributed is greater than the last balance, and the assertion has been updated to check the specific coin amount in the new structure.
These changes ensure that the genesis functionality is properly tested with the new multi-coin support.
x/protocolpool/types/genesis.go (2)
9-10: LGTM: Import changes are appropriate and well-structured.The addition of the SDK types import is consistent with the changes in the
NewGenesisStatefunction. The import statement follows the Uber Golang style guide recommendations for import grouping and aliasing.
17-17: LGTM:LastBalanceinitialization updated correctly, but verify impact.The change from
math.ZeroInt()toDistributionAmount{Amount: sdk.NewCoins()}forLastBalanceinitialization is correct and aligns with the PR objectives of allowing any coins in continuous funds. This modification reflects the transition from a simple integer to a more flexible coin-based structure.To ensure this change doesn't introduce any issues, please run the following verification:
This will help identify any other parts of the codebase that might need to be updated to accommodate this change.
x/protocolpool/proto/cosmos/protocolpool/v1/types.proto (2)
11-11: LGTM: Import statement for Amino codec added.The addition of the Amino import is appropriate for maintaining backwards compatibility in the Cosmos SDK ecosystem. This import will allow the use of Amino-specific annotations in the protocol definitions.
Line range hint
14-54: Verify integration ofDistributionAmountwith existing messages.While the new
DistributionAmountmessage allows for multiple coin types, the existingBudgetandContinuousFundmessages still use single-coin fields (e.g.,claimed_amount,budget_per_tranche). This might lead to inconsistencies in how funds are handled across different parts of the protocol.Please review and confirm:
- Whether
BudgetandContinuousFundmessages should be updated to useDistributionAmountfor consistency.- How
DistributionAmountwill be integrated with existing functionality.To assist in this verification, you can run the following script to check for potential inconsistencies:
This script will help identify areas where the new
DistributionAmountmight need to be integrated or where existing single-coin usage might need to be reviewed.x/protocolpool/depinject.go (1)
61-61: LGTM. Verify impact on dependent modules.The removal of
StakingKeeperfrom theNewKeeperfunction call aligns with the changes in theModuleInputsstruct. This modification appears intentional and consistent with the module's new design.However, this is a breaking change that may affect other parts of the system relying on the old
Keeperstructure.To ensure this change doesn't introduce unintended side effects, please run the following script to check for any remaining references to
StakingKeeperin theprotocolpoolmodule:Additionally, verify that all dependent modules have been updated to accommodate this change in the
Keeperstructure.✅ Verification successful
Change Verified: No remaining references to
StakingKeeperinx/protocolpool.🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Check for remaining references to StakingKeeper in the protocolpool module # Test: Search for StakingKeeper references in the protocolpool module rg --type go 'StakingKeeper' x/protocolpoolLength of output: 43
Script:
#!/bin/bash # Description: Search the entire codebase for references to StakingKeeper rg --type go 'StakingKeeper'Length of output: 43919
x/protocolpool/proto/cosmos/protocolpool/v1/tx.proto (3)
158-160: Approved: Enhanced flexibility for withdrawn fundsThe change from a single coin to a repeated field of coins for
withdrawn_allocated_fundaligns well with the PR objective. This modification allows for multiple types of coins to be withdrawn when canceling a continuous fund, increasing the flexibility of the protocol.Note that this is a breaking change, as mentioned in the PR title, and will require updates to any code interacting with this message.
172-174: Approved: Multi-coin support for withdrawalsThe modification of the
amountfield to a repeated field of coins inMsgWithdrawContinuousFundResponseis consistent with the PR's goal. This change enables the withdrawal of multiple types of coins from a continuous fund, enhancing the protocol's flexibility.As with the previous change, this is a breaking change that will require updates to dependent code.
Line range hint
1-176: Verify related code updatesThe changes in this file successfully implement multi-coin support for continuous funds in both cancellation and withdrawal operations. These modifications align well with the PR objectives and are correctly implemented in the Protocol Buffers definitions.
However, as these are breaking changes, it's crucial to ensure that:
- The corresponding Go code generated from these Proto definitions is updated accordingly.
- All parts of the codebase that interact with
MsgCancelContinuousFundResponseandMsgWithdrawContinuousFundResponseare updated to handle multiple coins.- Tests are updated or added to cover these new multi-coin scenarios.
- Documentation is updated to reflect these changes.
To verify the impact of these changes, you can run the following script:
This script will help identify areas of the codebase that might need to be updated in light of these changes.
x/protocolpool/keeper/keeper_test.go (3)
38-42: LGTM: Removal of stakingKeeper fieldThe removal of the
stakingKeeperfield from theKeeperTestSuitestruct is consistent with the changes described in the AI summary. This modification streamlines the test suite by removing unnecessary dependencies.
Line range hint
231-235: LGTM: Consistent type update in TestSetToDistributeThe change to use
types.DistributionAmountin theWalkfunction is consistent with the previous modifications. The test logic remains valid and continues to provide good coverage.
Line range hint
1-238: Overall assessment: Changes are well-implemented and sufficiently testedThe modifications in this file consistently reflect the transition from using
math.Inttotypes.DistributionAmountfor handling distribution amounts. The test coverage has been appropriately updated to accommodate these changes, and the overall structure of the tests remains sound.Key points:
- Removal of
stakingKeeperdependency aligns with the PR objectives.- Test logic has been correctly updated to work with the new
DistributionAmounttype.- Existing test coverage appears sufficient for the changes made.
Suggestions for improvement:
- Consider adding test cases that exercise
DistributionAmountwith multiple coins to ensure comprehensive coverage of the new type's capabilities.The changes adhere to Golang style guidelines and maintain the overall quality of the test suite.
x/protocolpool/keeper/keeper.go (16)
24-25: LGTM!The definitions of
authKeeperandbankKeeperin theKeeperstruct are appropriate and follow standard conventions.
36-38: LGTM!The addition of
RecipientFundDistribution,Distributions, andLastBalancefields to theKeeperstruct is correctly implemented, and their types are appropriately defined using thecollectionspackage.
70-72: LGTM!The initialization of the new collections maps and items in the
NewKeeperfunction aligns with the existing code patterns and is correctly implemented.
165-168: LGTM!The calculation of
amountToDistributeusingSafeSuband the handling of potential negative results are correctly implemented.
183-188: LGTM!The logic for transferring funds to the community pool when there are no continuous funds, and resetting
LastBalance, is correctly implemented.
194-194: LGTM!Recording the distribution amount with the current block time is appropriate and correctly implemented.
199-199: LGTM!Updating
LastBalancewith the current balance ensures accurate tracking for future distributions.
221-223: LGTM!Initialization of variables
toDistribute,poolFunds, andfullAmountToDistributeis properly set up for subsequent calculations.
225-225: LGTM!Iterating over
k.Distributionsto calculate allocations is correctly implemented.
266-266: LGTM!Resetting
LastBalanceafter clearing distributions ensures consistent state for future calculations.
271-271: LGTM!Transferring
streamAmtto the stream account is correctly handled.
279-279: LGTM!Transferring
poolFundsto the community pool is appropriately implemented.
301-301: LGTM!Initializing
toClaimwith zero coins for new recipients is correct.
307-308: LGTM!Updating the recipient's claimable amount in
RecipientFundDistributionis correctly implemented.
115-135: Verify callers handle new return type ofwithdrawRecipientFundsThe
withdrawRecipientFundsfunction now returnssdk.Coinsinstead ofsdk.Coin. Ensure that all callers of this function have been updated to handle the new return type to avoid potential runtime errors.Run the following script to find all usages of
withdrawRecipientFundsand check for proper handling:#!/bin/bash # Description: Find all calls to `withdrawRecipientFunds` and verify they handle `sdk.Coins`. # Test: Search for function calls to `withdrawRecipientFunds`. Expect: Callers expect `sdk.Coins`. rg --type go 'withdrawRecipientFunds\(' -A 5
45-45: Verify thatstakingKeeperis no longer used in the codebaseThe
stakingKeeperparameter has been removed from theNewKeeperfunction signature. Ensure that all references tostakingKeeperhave been removed throughout the codebase to prevent any undefined references or build errors.Run the following script to confirm that
stakingKeeperis not referenced elsewhere:x/protocolpool/keeper/msg_server_test.go (5)
398-398: Correct Update towithdrawnAmountTypeThe variable
withdrawnAmounthas been appropriately updated fromsdk.Cointosdk.Coinsto handle multiple coin types, aligning with the new data structures introduced in the codebase.
Line range hint
426-442: Consistent Initialization ofRecipientFundDistributionThe initialization of
RecipientFundDistributionwithsdk.NewCoins()ensures that the distribution amounts are correctly represented as empty coin sets for multiple coin types. This change maintains consistency across the codebase.
628-631: Ensure Accurate Assertions After Multiple WithdrawalsAt lines 628-631, assertions are made on
toClaim.Amountforrecipient2andrecipient3. Verify that these assertions correctly reflect the expected state after withdrawals, and ensure that funds are accurately distributed among all recipients.
991-1007: Correct Handling of Expired Continuous FundsIn the
TestWithdrawExpiredFundsfunction (lines 991-1007), the logic correctly prevents withdrawal of expired funds and handles cancellations without errors. The test accurately verifies that repeated cancellations do not result in errors or unintended fund distribution.
508-508: Confirm Necessity of Empty Expiry in Test CaseIn line 508, the test case sets an empty expiry for the continuous fund. Verify whether an empty expiry is acceptable in the business logic and that it does not introduce unintended behavior.
Run the following script to search for uses of continuous funds without expiry:
api/cosmos/protocolpool/v1/genesis.pulsar.go (25)
265-266: Handling ofLastBalanceinRangemethod is appropriateThe check for
x.LastBalance != niland subsequent processing ensures that theLastBalancefield is correctly included during iteration. This follows standard practice and is compliant with the Uber Go Style Guide.
297-297: Correct implementation ofHasmethod forLastBalanceThe
Hasmethod accurately checks the presence ofLastBalanceby verifying if it is not nil. This is the appropriate way to handle optional fields in Go.
321-321: Proper clearing ofLastBalanceinClearmethodSetting
x.LastBalance = nilcorrectly clears the field, ensuring that subsequent calls recognize it as unset. This adheres to best practices for managing optional fields.
354-354: Accurate retrieval ofLastBalanceinGetmethodThe
Getmethod correctly retrieves theLastBalancefield by returning its proto message representation. This implementation is standard and effective.
390-390: Type assertion inSetmethod is safe and appropriateAssigning
x.LastBalanceafter asserting the value's type to*DistributionAmountis appropriate here, assuming correct usage of the API. There is no immediate risk of a type assertion panic in this context.
427-431: Correct initialization ofLastBalanceinMutablemethodThe method ensures that
LastBalanceis initialized when nil, which prevents potential nil pointer dereferences when accessing it later. Returning the proto message reflects standard practice.
458-459: Proper creation of newDistributionAmountinNewFieldThe creation of a new
DistributionAmountinstance and returning its proto message is correct and follows the expected pattern for this method.
544-545: Efficient size calculation ofLastBalanceinProtoMethodsThe
Sizefunction accurately includes the size ofLastBalancewhen it is not nil. This contributes to correct serialization behavior.
599-609: Correct marshaling ofLastBalanceThe code properly marshals
LastBalancewhen it is not nil, handling errors appropriately. The implementation aligns with the standard serialization process.
Line range hint
766-796: Accurate unmarshaling ofLastBalanceDuring unmarshaling, the code correctly initializes
LastBalanceif it's nil and unmarshals data into it. Error handling is properly managed, ensuring robustness.
870-870: Initialization offd_Distribution_amountis correctThe field descriptor for
amountin theDistributionmessage is properly declared and initialized, which is essential for reflection operations.Also applies to: 877-877
951-956: Appropriate handling ofAmountinRangemethod ofDistributionThe method correctly checks if
x.Amountis not nil and processes it accordingly during iteration. This conforms to best practices.
974-975: Correct implementation ofHasmethod forAmountThe
Hasmethod properly determines the presence of theAmountfield by checking for nil, which is appropriate for optional fields.
994-995: Proper clearing ofAmountinClearmethodSetting
x.Amount = nileffectively clears theAmountfield, ensuring it's unset in subsequent operations.
1040-1041: Safe type assertion inSetmethod forAmountThe assignment to
x.Amountwith type assertion to*DistributionAmountis appropriate and assumes correct usage of proto reflection.
1068-1071: Proper initialization ofAmountinMutablemethodEnsuring
x.Amountis initialized when nil prevents nil pointer exceptions and is a correct approach in theMutablemethod.
1088-1090: Correct instantiation inNewFieldmethodCreating a new
DistributionAmountinstance and returning its proto message aligns with standard implementation for creating new fields.
1164-1167: Accurate size calculation ofAmountIncluding the size of
x.Amountin the total size when not nil is essential for accurate serialization.
1197-1198: Proper marshaling ofAmountThe code marshals
x.Amountcorrectly when it is present, handling potential errors suitably.
1211-1223: Correct marshaling ofTimeinDistributionMarshaling of
x.Timeis handled appropriately, ensuring that the timestamp is correctly serialized.
Line range hint
1274-1342: Robust unmarshaling logic inDistributionThe unmarshaling code properly handles both
TimeandAmountfields, initializing them when necessary and managing errors effectively.
1406-1406: Definition ofLastBalancefield is appropriateChanging
LastBalanceto be of type*DistributionAmountallows for richer data representation and aligns with the intended functionality.
1447-1451: Correct implementation ofGetLastBalancemethodThe getter method accurately returns
x.LastBalanceand handles the case wherexis nil, ensuring reliability.
1466-1467: Proper definition ofTimeandAmountfields inDistributionDefining
TimeandAmountas pointers allows for optional fields and aligns with protobuf conventions.
1490-1499: Correct getter methods forDistributionfieldsThe
GetTimeandGetAmountmethods correctly return their respective fields, handling nil cases appropriately.api/cosmos/protocolpool/v1/tx.pulsar.go (6)
5511-5515: Verify the cardinality ofwithdrawn_allocated_fund.The
withdrawn_allocated_fundfield is defined as a repeated field. Ensure that it is semantically correct for this field to contain multiple coins. If it should only hold a single coin amount, consider changing it to a non-repeated field.
Line range hint
7511-7515: Verify the cardinality ofwithdrawn_allocated_fund.Similar to the previous comment, ensure that the
withdrawn_allocated_fundfield should indeed be a repeated field semantically. If it should only hold a single coin amount, change it to a non-repeated field.
Line range hint
7584-7588: Verify the cardinality ofamount.The
amountfield is defined as a repeated field. Ensure that it is semantically correct for this field to contain multiple coins. If it should only hold a single coin amount, consider changing it to a non-repeated field.
7728-7730: Fix the indentation of thewithdrawn_allocated_fundfield.The
withdrawn_allocated_fundfield is not properly indented. It should be aligned with the other fields in theMsgCancelContinuousFundResponsemessage.Apply this diff to fix the indentation:
- WithdrawnAllocatedFund []*v1beta1.Coin `protobuf:"bytes,4,rep,name=withdrawn_allocated_fund,json=withdrawnAllocatedFund,proto3" json:"withdrawn_allocated_fund,omitempty"` + WithdrawnAllocatedFund []*v1beta1.Coin `protobuf:"bytes,4,rep,name=withdrawn_allocated_fund,json=withdrawnAllocatedFund,proto3" json:"withdrawn_allocated_fund,omitempty"`
7746-7748: Fix the indentation of theamountfield.The
amountfield is not properly indented. It should be aligned with the other fields in theMsgWithdrawContinuousFundResponsemessage.Apply this diff to fix the indentation:
- Amount []*v1beta1.Coin `protobuf:"bytes,1,rep,name=amount,proto3" json:"amount,omitempty"` + Amount []*v1beta1.Coin `protobuf:"bytes,1,rep,name=amount,proto3" json:"amount,omitempty"`
6465-6514: 🛠️ Refactor suggestionRefactor the internal list type into a reusable utility.
Similar to the previous comment, consider extracting the
_MsgWithdrawContinuousFundResponse_1_listtype and its methods into a reusable utility type to improve code modularity and reduce duplication.
| (gogoproto.customtype) = "cosmossdk.io/math.Int", | ||
| (gogoproto.nullable) = false | ||
| ]; | ||
| DistributionAmount last_balance = 3 [(gogoproto.nullable) = false]; |
There was a problem hiding this comment.
Changing field type of last_balance may cause backward compatibility issues
Modifying the type of the last_balance field from string to DistributionAmount in the GenesisState message can lead to serialization and deserialization issues with existing clients and persisted data that expect a string. This can cause failures when parsing genesis files or communicating with nodes that haven't updated.
To preserve backward compatibility, consider deprecating the existing field and introducing a new field with a new field number and the desired type.
| (gogoproto.customtype) = "cosmossdk.io/math.Int", | ||
| (gogoproto.nullable) = false | ||
| ]; | ||
| google.protobuf.Timestamp time = 1 [(gogoproto.stdtime) = true]; |
There was a problem hiding this comment.
Altering field numbers in Protobuf messages breaks compatibility
Changing the field number of time from 6 to 1 in the Distribution message can result in data corruption or parsing errors. Field numbers in Protobuf are used to identify fields in the binary format, and modifying them disrupts compatibility with existing data and clients that use the previous numbering.
Instead of renumbering existing fields, add new fields with new field numbers, and, if necessary, deprecate the old fields to maintain backward compatibility.
|
|
||
| google.protobuf.Timestamp time = 6 [(gogoproto.stdtime) = true]; | ||
| DistributionAmount amount = 2 [(gogoproto.nullable) = false]; |
There was a problem hiding this comment.
Changing field type of amount may cause backward compatibility issues
Updating the type of the amount field from string to DistributionAmount in the Distribution message may lead to deserialization problems with existing data and clients expecting a string. This could cause runtime errors or data loss when processing distributions.
It's advisable to add a new field with a new field number and the new type DistributionAmount. You can retain the old amount field for compatibility purposes and mark it as deprecated.
| if data.LastBalance.Amount.IsAnyGT(totalToBeDistributed) || !totalToBeDistributed.DenomsSubsetOf(data.LastBalance.Amount) { | ||
| return errors.New("total to be distributed is greater than the last balance" + fmt.Sprint(data.LastBalance.Amount, totalToBeDistributed)) | ||
| } |
There was a problem hiding this comment.
Fix the logical inconsistency in the condition and error message
There's a mismatch between the condition being checked and the error message returned. The condition data.LastBalance.Amount.IsAnyGT(totalToBeDistributed) checks if the last balance amount is greater than the total to be distributed. However, the error message states "total to be distributed is greater than the last balance," which implies the opposite.
To correct this, the condition should check if totalToBeDistributed.IsAnyGT(data.LastBalance.Amount) instead.
Apply this diff to fix the condition:
-if data.LastBalance.Amount.IsAnyGT(totalToBeDistributed) || !totalToBeDistributed.DenomsSubsetOf(data.LastBalance.Amount) {
+if totalToBeDistributed.IsAnyGT(data.LastBalance.Amount) || !totalToBeDistributed.DenomsSubsetOf(data.LastBalance.Amount) {
return errors.New("total to be distributed is greater than the last balance" + fmt.Sprint(data.LastBalance.Amount, totalToBeDistributed))
}This change ensures that the error is returned when the total to be distributed exceeds the last balance, aligning the condition with the error message.
📝 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. Thoroughly test & benchmark the code to ensure it meets the requirements.
| if data.LastBalance.Amount.IsAnyGT(totalToBeDistributed) || !totalToBeDistributed.DenomsSubsetOf(data.LastBalance.Amount) { | |
| return errors.New("total to be distributed is greater than the last balance" + fmt.Sprint(data.LastBalance.Amount, totalToBeDistributed)) | |
| } | |
| if totalToBeDistributed.IsAnyGT(data.LastBalance.Amount) || !totalToBeDistributed.DenomsSubsetOf(data.LastBalance.Amount) { | |
| return errors.New("total to be distributed is greater than the last balance" + fmt.Sprint(data.LastBalance.Amount, totalToBeDistributed)) | |
| } |
There was a problem hiding this comment.
I'm confused a bit about the 1st condition, should return an error when totalToBeDistributed > lastBalance?
There was a problem hiding this comment.
@hieuvubk, you're correct. The error should be returned when totalToBeDistributed is greater than data.LastBalance.Amount. Currently, the condition:
if data.LastBalance.Amount.IsAnyGT(totalToBeDistributed) || !totalToBeDistributed.DenomsSubsetOf(data.LastBalance.Amount) {
return errors.New("total to be distributed is greater than the last balance" + fmt.Sprint(data.LastBalance.Amount, totalToBeDistributed))
}checks if data.LastBalance.Amount is greater than totalToBeDistributed, which is the opposite of the intended logic based on the error message.
To fix this inconsistency, the condition should be:
if totalToBeDistributed.IsAnyGT(data.LastBalance.Amount) || !totalToBeDistributed.DenomsSubsetOf(data.LastBalance.Amount) {
return errors.New("total to be distributed is greater than the last balance" + fmt.Sprint(data.LastBalance.Amount, totalToBeDistributed))
}This change ensures that an error is returned when totalToBeDistributed exceeds data.LastBalance.Amount, aligning the condition with the error message and the expected behavior.
/_/\
( •.• )
🚀<
A curious rabbit pondering over the code!
There was a problem hiding this comment.
Why not simply go with fmt.Errorf instead which is typically used in these scenarios? For example:
fmt.Errorf("an amount to be distributed is greater than the last balance: %s > %s", totalToBeDistributed, data.LastBalance.Amount))There was a problem hiding this comment.
Seems like the humans are having a chat. I'll hop back into my burrow for now. If you need me again, just tag @coderabbitai in a new comment, and I'll come hopping out!
There was a problem hiding this comment.
This was actually for testing, but I think it can be useful if we ever encounter this, I'll modify it.
| for _, denom := range amount.Amount.Denoms() { | ||
| am := sdk.NewCoin(denom, f.Percentage.MulInt(amount.Amount.AmountOf(denom)).TruncateInt()) | ||
| toDistribute[f.Recipient] = toDistribute[f.Recipient].Add(am) | ||
| fullAmountToDistribute = fullAmountToDistribute.Add(am) |
There was a problem hiding this comment.
Review the use of TruncateInt() in distribution calculations
When calculating each recipient's share, TruncateInt() is used after multiplying by the percentage. This could lead to loss of fractional amounts. Consider whether this aligns with the expected financial logic, or if using RoundInt() would be more appropriate to minimize discrepancies.
| suite.Require().NoError(err) | ||
| suite.mockStreamFunds(math.NewInt(0)) | ||
| }, | ||
| recipientAddress: []sdk.AccAddress{recipient}, | ||
| expErr: false, | ||
| withdrawnAmount: sdk.NewCoin(sdk.DefaultBondDenom, math.ZeroInt()), | ||
| withdrawnAmount: nil, |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Clarify Representation of Zero withdrawnAmount
The withdrawnAmount is set to nil on line 494. To maintain consistency and clarity, consider using sdk.NewCoins() to represent zero amounts instead of nil.
Apply this diff to standardize the representation:
- withdrawnAmount: nil,
+ withdrawnAmount: sdk.NewCoins(),📝 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. Thoroughly test & benchmark the code to ensure it meets the requirements.
| withdrawnAmount: nil, | |
| withdrawnAmount: sdk.NewCoins(), |
| case "cosmos.protocolpool.v1.Distribution.amount": | ||
| value := x.Amount | ||
| return protoreflect.ValueOfMessage(value.ProtoReflect()) |
There was a problem hiding this comment.
Possible copy-paste error in Get method for Distribution struct
In the Get method, the second case for "cosmos.protocolpool.v1.Distribution.time" incorrectly assigns x.Amount instead of x.Time. Additionally, there is no case handling for "cosmos.protocolpool.v1.Distribution.amount", which is required for proper functionality.
Apply the following diff to fix the issue:
func (x *fastReflection_Distribution) Get(descriptor protoreflect.FieldDescriptor) protoreflect.Value {
switch descriptor.FullName() {
case "cosmos.protocolpool.v1.Distribution.time":
value := x.Time
return protoreflect.ValueOfMessage(value.ProtoReflect())
- case "cosmos.protocolpool.v1.Distribution.time":
+ case "cosmos.protocolpool.v1.Distribution.amount":
value := x.Amount
return protoreflect.ValueOfMessage(value.ProtoReflect())
default:Committable suggestion was skipped due to low confidence.
| type _DistributionAmount_1_list struct { | ||
| list *[]*v1beta1.Coin | ||
| } |
There was a problem hiding this comment.
Avoid using pointers to slices; slices are reference types in Go.
In the struct _DistributionAmount_1_list, the field list is declared as *[]*v1beta1.Coin. Since slices in Go are reference types, using a pointer to a slice is unnecessary and adds complexity. Consider changing the field to use a slice directly.
Apply this diff to simplify the struct definition:
type _DistributionAmount_1_list struct {
- list *[]*v1beta1.Coin
+ list []*v1beta1.Coin
}Adjust the methods accordingly to reflect this change.
📝 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. Thoroughly test & benchmark the code to ensure it meets the requirements.
| type _DistributionAmount_1_list struct { | |
| list *[]*v1beta1.Coin | |
| } | |
| type _DistributionAmount_1_list struct { | |
| list []*v1beta1.Coin | |
| } |
| value := &_DistributionAmount_1_list{list: &x.Amount} | ||
| return protoreflect.ValueOfList(value) | ||
| default: | ||
| if fd.IsExtension() { | ||
| panic(fmt.Errorf("proto3 declared messages do not support extensions: cosmos.protocolpool.v1.DistributionAmount")) | ||
| } | ||
| panic(fmt.Errorf("message cosmos.protocolpool.v1.DistributionAmount does not contain field %s", fd.FullName())) | ||
| } |
There was a problem hiding this comment.
Avoid using panic for error handling; return errors instead.
Using panic in the Mutable method for handling invalid field descriptors is discouraged. Panics can cause unexpected crashes and are harder to recover from. Instead, modify the method to return an error or handle the situation gracefully without panicking.
Consider refactoring the code as follows:
func (x *fastReflection_DistributionAmount) Mutable(fd protoreflect.FieldDescriptor) protoreflect.Value {
switch fd.FullName() {
case "cosmos.protocolpool.v1.DistributionAmount.amount":
if x.Amount == nil {
x.Amount = []*v1beta1.Coin{}
}
value := &_DistributionAmount_1_list{list: &x.Amount}
return protoreflect.ValueOfList(value)
default:
if fd.IsExtension() {
- panic(fmt.Errorf("proto3 declared messages do not support extensions: %s", fd.FullName()))
+ // Handle the error appropriately without panicking
+ return protoreflect.Value{}
}
- panic(fmt.Errorf("message cosmos.protocolpool.v1.DistributionAmount does not contain field %s", fd.FullName()))
+ // Handle the error appropriately without panicking
+ return protoreflect.Value{}
}
}Adjust the method's return type and callers as necessary to handle the absence of a valid value.
Committable suggestion was skipped due to low confidence.
| var _ protoreflect.List = (*_MsgCancelContinuousFundResponse_4_list)(nil) | ||
|
|
||
| type _MsgCancelContinuousFundResponse_4_list struct { | ||
| list *[]*v1beta1.Coin | ||
| } | ||
|
|
||
| func (x *_MsgCancelContinuousFundResponse_4_list) Len() int { | ||
| if x.list == nil { | ||
| return 0 | ||
| } | ||
| return len(*x.list) | ||
| } | ||
|
|
||
| func (x *_MsgCancelContinuousFundResponse_4_list) Get(i int) protoreflect.Value { | ||
| return protoreflect.ValueOfMessage((*x.list)[i].ProtoReflect()) | ||
| } | ||
|
|
||
| func (x *_MsgCancelContinuousFundResponse_4_list) Set(i int, value protoreflect.Value) { | ||
| valueUnwrapped := value.Message() | ||
| concreteValue := valueUnwrapped.Interface().(*v1beta1.Coin) | ||
| (*x.list)[i] = concreteValue | ||
| } | ||
|
|
||
| func (x *_MsgCancelContinuousFundResponse_4_list) Append(value protoreflect.Value) { | ||
| valueUnwrapped := value.Message() | ||
| concreteValue := valueUnwrapped.Interface().(*v1beta1.Coin) | ||
| *x.list = append(*x.list, concreteValue) | ||
| } | ||
|
|
||
| func (x *_MsgCancelContinuousFundResponse_4_list) AppendMutable() protoreflect.Value { | ||
| v := new(v1beta1.Coin) | ||
| *x.list = append(*x.list, v) | ||
| return protoreflect.ValueOfMessage(v.ProtoReflect()) | ||
| } | ||
|
|
||
| func (x *_MsgCancelContinuousFundResponse_4_list) Truncate(n int) { | ||
| for i := n; i < len(*x.list); i++ { | ||
| (*x.list)[i] = nil | ||
| } | ||
| *x.list = (*x.list)[:n] | ||
| } | ||
|
|
||
| func (x *_MsgCancelContinuousFundResponse_4_list) NewElement() protoreflect.Value { | ||
| v := new(v1beta1.Coin) | ||
| return protoreflect.ValueOfMessage(v.ProtoReflect()) | ||
| } | ||
|
|
||
| func (x *_MsgCancelContinuousFundResponse_4_list) IsValid() bool { | ||
| return x.list != nil | ||
| } |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Refactor the internal list type into a reusable utility.
Consider extracting the _MsgCancelContinuousFundResponse_4_list type and its methods into a reusable utility type. This will make the code more modular and reduce duplication if similar list types are needed elsewhere.
| if data.LastBalance.Amount.IsAnyGT(totalToBeDistributed) || !totalToBeDistributed.DenomsSubsetOf(data.LastBalance.Amount) { | ||
| return errors.New("total to be distributed is greater than the last balance" + fmt.Sprint(data.LastBalance.Amount, totalToBeDistributed)) | ||
| } |
There was a problem hiding this comment.
I'm confused a bit about the 1st condition, should return an error when totalToBeDistributed > lastBalance?
There was a problem hiding this comment.
Nice work!
I am not very familiar with the module but I added some comments that may be helpful.
Are you planning to add a migration? That would be very helpful for existing chains.
You also mentioned an accept list to prevent spam. How is this going to be implemented and maintained?
|
|
||
| if data.LastBalance.Amount.IsAnyGT(totalToBeDistributed) || !totalToBeDistributed.DenomsSubsetOf(data.LastBalance.Amount) { |
There was a problem hiding this comment.
last balance should always be >= total to be distributed.
Simplest thing would be to flip the check: totalToBeDistributed.IsAnyGT(last balance)
This includes the denoms implicite so that you can drop the DenomsSubsetOf check
| if data.LastBalance.Amount.IsAnyGT(totalToBeDistributed) || !totalToBeDistributed.DenomsSubsetOf(data.LastBalance.Amount) { | ||
| return errors.New("total to be distributed is greater than the last balance" + fmt.Sprint(data.LastBalance.Amount, totalToBeDistributed)) | ||
| } |
There was a problem hiding this comment.
Why not simply go with fmt.Errorf instead which is typically used in these scenarios? For example:
fmt.Errorf("an amount to be distributed is greater than the last balance: %s > %s", totalToBeDistributed, data.LastBalance.Amount))| remaining := math.LegacyOneDec().Sub(percentageToDistribute).MulInt(amount).RoundInt() | ||
| poolFunds = poolFunds.Add(remaining) | ||
| for _, denom := range amount.Amount.Denoms() { | ||
| remaining := sdk.NewCoin(denom, math.LegacyOneDec().Sub(percentageToDistribute).MulInt(amount.Amount.AmountOf(denom)).TruncateInt()) |
There was a problem hiding this comment.
Similar code was used before but is another round down which has a rest that is not distributed.
Better remaining = amount - distributed amount
julienrbrt
added
the
backport/v0.52.x
Description
Previously only the bond denom could be used for continuous funds, now we allow any token. We might want to add a param with a whitelist of tokens to avoid spam.
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...
!in the type prefix if API or client breaking changeCHANGELOG.mdReviewers 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.
Please see Pull Request Reviewer section in the contributing guide for more information on how to review a pull request.
I have...
Summary by CodeRabbit
New Features
DistributionAmountstructure for handling multiple coins.Improvements
LastBalanceandAmountfields to utilize structured types instead of primitive strings.Bug Fixes
Chores
StakingKeeperinterface and its mock implementations, streamlining the codebase.