Skip to content

CIP-44: Adjust Validator Commission Bounds#368

Merged
rootulp merged 3 commits into
mainfrom
cal/commission-cip
Jan 14, 2026
Merged

CIP-44: Adjust Validator Commission Bounds#368
rootulp merged 3 commits into
mainfrom
cal/commission-cip

Conversation

@cmwaters
Copy link
Copy Markdown
Contributor

Summary

  • Increase maximum validator commission from 25% to 60%
  • Increase minimum validator commission from 10% to 20%
  • Effective immediately upon next major network upgrade

🤖 Generated with Claude Code

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello @cmwaters, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces CIP-44, a proposal to modify the validator commission rate bounds. The primary goal is to enhance the sustainability and health of the validator network by providing validators with greater flexibility to set their commission rates, ensuring they are adequately compensated for their services and infrastructure provision.

Highlights

  • Maximum Validator Commission Increase: The maximum validator commission rate is proposed to increase from 25% to 60%.
  • Minimum Validator Commission Increase: The minimum validator commission rate is proposed to increase from 10% to 20%.
  • Automatic Commission Adjustment: Validators with commission rates below 20% will be automatically adjusted to 20% during the next major network upgrade.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request introduces CIP-44, a proposal to adjust validator commission bounds by increasing the maximum to 60% and the minimum to 20%. The new CIP document is well-structured, clear, and provides sufficient detail regarding the motivation, specification, and implications of the change. I have one suggestion to improve the document's completeness.

Comment thread cips/cip-044.md Outdated
🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
@rootulp rootulp self-requested a review January 14, 2026 14:25
Copy link
Copy Markdown
Collaborator

@rootulp rootulp left a comment

Choose a reason for hiding this comment

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

LGTM with one change to make these params non governance modifiable

Comment thread cips/cip-044.md Outdated
Co-authored-by: Rootul P <rootulp@gmail.com>
@rootulp rootulp merged commit 9a7236f into main Jan 14, 2026
4 checks passed
@jcstein
Copy link
Copy Markdown
Member

jcstein commented Jan 14, 2026

I'll make a FLUP PR to add this to README.md and SUMMARY.md so it ends up rendering on the site

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