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

Staking rewards 9.62 ZETA #489

Merged
merged 1 commit into from
Oct 10, 2024
Merged

Staking rewards 9.62 ZETA #489

merged 1 commit into from
Oct 10, 2024

Conversation

fadeev
Copy link
Member

@fadeev fadeev commented Oct 10, 2024

Summary by CodeRabbit

  • New Features

    • Updated "Staking Rewards" document with enhanced details on reward distribution and calculation.
    • Introduced a fixed staking reward amount of 9.62 ZETA.
    • Revised URL for the emissions pool address.
  • Bug Fixes

    • Removed outdated information regarding manual funding of the emission pool and inflation statements.

Copy link

vercel bot commented Oct 10, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
docs-v2 ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 10, 2024 3:28pm

Copy link
Contributor

coderabbitai bot commented Oct 10, 2024

📝 Walkthrough

Walkthrough

The document "Staking Rewards" has been revised to enhance clarity on the distribution of staking rewards among validators, emphasizing the role of voting power. The formula for calculating rewards has been updated to a fixed value of 9.62 ZETA, replacing the previous variable formula. Additionally, the emissions pool address URL has been updated, and minor textual adjustments have been made, including the removal of a bullet point regarding manual funding and a statement on network inflation.

Changes

File Path Change Summary
src/pages/developers/architecture/rewards.mdx Updated to clarify staking rewards distribution, modified formula to a fixed 9.62 ZETA, updated emissions pool URL, and made minor text adjustments.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Validator
    participant Protocol

    User->>Protocol: Stake Tokens
    Protocol->>Validator: Distribute Rewards
    Validator->>Protocol: Calculate Rewards (9.62 ZETA)
    Protocol->>User: Provide Staking Rewards
Loading

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>, please review it.
    • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @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.
    • @coderabbitai help me debug CodeRabbit configuration file.

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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration 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.

Copy link
Contributor

@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

🧹 Outside diff range and nitpick comments (2)
src/pages/developers/architecture/rewards.mdx (2)

18-19: Approval: Updated reward formula with suggestion.

The simplification of the staking rewards formula to a fixed amount enhances clarity. However, to improve precision, consider adding units to the TransactionFees term in the equation.

Suggested improvement:

$$ StakingRewards = TransactionFees_{ZETA} + 9.62 \text{ ZETA} $$

This change explicitly indicates that transaction fees are also in ZETA, maintaining consistency with the fixed reward amount.


20-22: Approval: Source code reference added with suggestion for improvement.

The addition of a link to the source code where the fixed amount is defined is commendable, as it enhances transparency and allows for easy verification. However, to ensure long-term maintainability, consider the following suggestion:

Instead of linking to a specific commit, which may become outdated, consider using a link to the main branch or implementing a dynamic link that always points to the latest version of the file. This approach would ensure that the documentation remains current without requiring frequent updates.

Example implementation:

The fixed amount (9.62 ZETA) is defined [in the source code](https://github.com/zeta-chain/node/blob/main/x/emissions/types/keys.go) of the protocol.
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 93464d6 and b55ddf4.

📒 Files selected for processing (1)
  • src/pages/developers/architecture/rewards.mdx (1 hunks)
🧰 Additional context used
🔇 Additional comments (3)
src/pages/developers/architecture/rewards.mdx (3)

15-16: Approval: Clear explanation of reward distribution.

The addition of this sentence provides crucial information about how staking rewards are distributed among validators. This clarification enhances the overall understanding of the staking mechanism.


Line range hint 1-35: Address removal of information about manual funding and network inflation.

It's noted that two bullet points have been removed from the document:

  • The statement about the emission pool being funded manually
  • The statement about the absence of inflation in the network

While these removals may reflect changes in the system or a desire for brevity, they represent potentially significant aspects of the tokenomics.

Please confirm:

  1. Has the emission pool funding mechanism changed?
  2. Is the statement about network inflation still accurate?

If these aspects have indeed changed, consider adding brief explanations about the current state of emission pool funding and network inflation to maintain comprehensive documentation.


25-25: Approval: Updated emissions pool address URL with request for clarification.

The update to the emissions pool address URL is noted. This change likely provides more specific information about the emissions pool addresses.

To ensure the correctness and functionality of this URL, please clarify:

  1. Is this an API endpoint or a web page?
  2. What specific information does this URL provide?
  3. Is there any authentication required to access this resource?

Additionally, to verify the URL's functionality, please run the following command:

This will check the HTTP response and confirm that the resource is accessible.

✅ Verification successful

Verified: Emissions pool address URL is functional and accessible.

The GET request to https://zetachain.blockpi.network/lcd/v1/public/zeta-chain/emissions/list_addresses successfully returned the expected JSON data containing the relevant emission addresses. This confirms that the updated URL is correctly configured and provides the necessary information.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

curl -I https://zetachain.blockpi.network/lcd/v1/public/zeta-chain/emissions/list_addresses

Length of output: 975


Script:

#!/bin/bash
curl -X GET https://zetachain.blockpi.network/lcd/v1/public/zeta-chain/emissions/list_addresses

Length of output: 659

@CharlieMc0 CharlieMc0 merged commit 33ae75a into main Oct 10, 2024
6 checks passed
@CharlieMc0 CharlieMc0 deleted the staking-rewards branch October 10, 2024 15:33
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