Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: support multiple denoms for delegation rewards #176

Merged
merged 10 commits into from
May 3, 2024

Conversation

mbreithecker
Copy link
Member

@mbreithecker mbreithecker commented Apr 29, 2024

This PR adjust the delegation module and its algorithm to support multiple coin denominations for reward payouts.

Summary by CodeRabbit

  • Documentation
    • Updated API documentation to reflect changes in reward data structures.
  • New Features
    • Enhanced reward tracking and distribution to support multiple denominations.
  • Bug Fixes
    • Corrected reward-related field names for consistency across various responses.
  • Refactor
    • Streamlined reward handling and payout processes in delegation management.
  • Tests
    • Updated integration and unit tests to align with new reward structures and logic.

Copy link

coderabbitai bot commented Apr 29, 2024

Warning

Rate Limit Exceeded

@mbreithecker has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 16 minutes and 26 seconds before requesting another review.

How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.
Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.
Please see our FAQ for further information.

Commits Files that changed from the base of the PR and between 95d480e and 1b9fc6c.

Walkthrough

The recent updates involve a significant transformation in reward management, transitioning to arrays of objects or sdk.Coins to handle diverse denominations. These changes impact various system aspects like data structures, API responses, and internal mechanisms, enhancing adaptability and resilience.

Changes

Files Change Summary
docs/static/openapi.yml, proto/.../delegation.proto, proto/.../events.proto, proto/.../account.proto, proto/.../delegation.proto Fields updated to arrays of objects or sdk.Coins for managing multiple reward denominations. Added necessary imports.
testutil/integration/..., x/bundles/keeper/..., x/delegation/keeper/... Adjusted test assertions and internal logic to accommodate the new reward data structure. Enhanced minting functions to specify denominations.
x/query/keeper/... Modified GRPC responses to align with changes in reward data structures, ensuring compliance with updated protocol specifications.

🐰 Poem by CodeRabbit

In the realm of code, where logic threads weave,
A change was made, in how rewards we perceive.
From strings to coins, a leap so bold,
A tale of updates, through binaries told.
🌟🚀 Gather 'round, let's cheer, for the devs so bright,
In the dance of bits, they bring dreams to light!


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.

@mbreithecker mbreithecker marked this pull request as ready for review April 29, 2024 12:31
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Out of diff range and nitpick comments (1)
x/delegation/keeper/logic_delegation.go (1)

59-72: > 📝 NOTE

This review was outside the diff hunks and was mapped to the diff hunk with the greatest overlap. Original lines [62-79]

The updated performWithdrawal function correctly handles multiple coin denominations and introduces robust error handling.

Consider whether PanicHalt is the best approach for handling cases where no money is left in the module, as it might be beneficial to allow for a softer error recovery strategy.

shifty11
shifty11 previously approved these changes Apr 30, 2024
Copy link
Member

@troykessler troykessler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please also update the x/delegation spec files

…denoms

# Conflicts:
#	x/bundles/keeper/msg_server_submit_bundle_proposal.go
shifty11
shifty11 previously approved these changes May 2, 2024
@troykessler
Copy link
Member

Also, should the migration be implemented here or afterwards when the entire multiple coin feature is fully implemented?

testutil/integration/checks.go Outdated Show resolved Hide resolved
x/delegation/keeper/logic_f1distribution.go Outdated Show resolved Hide resolved
x/delegation/keeper/keeper_suite_test.go Show resolved Hide resolved
@mbreithecker mbreithecker merged commit 7358839 into main May 3, 2024
5 checks passed
@mbreithecker mbreithecker deleted the mbreithecker/delegation-multiple-denoms branch May 3, 2024 12:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants