Vishal Chintham
    • Create new note
    • Create a note from template
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Write
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
    • Invite by email
      Invitee

      This note has no invitees

    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Note Insights New
    • Engagement control
    • Make a copy
    • Transfer ownership
    • Delete this note
    • Save as template
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Note Insights Versions and GitHub Sync Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Engagement control Make a copy Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Write
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee

    This note has no invitees

  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       Owned this note    Owned this note      
    Published Linked with GitHub
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    # Questions (8th May) 1. What is the stake fee and why is it being used to buy shares in the active pool? What does this line mean: `- distribute them together with the `active` rewards when this epoch ends// in order to appreciate all shares on the active pool atomically` ? ![](https://hackmd.io/_uploads/S1LPIeI4n.png) 2. The 'add_stake' function indicates that shares are purchased instantly and stake is added to the stake pool and active pool of the delegation pool. Does this stake immediately begin producing rewards, or will rewards only be minted from the following epoch, as the stake is in a 'pending_active' state? 3. The understanding of the flow of rewards distribution we have is: 1. The rewards are added to the active pool when synchronisation happens. 2. The commission amount is computed commission_amount = rewards * commission_percentage 3. The left over rewards (after removing the commission amount) is added to the stake of active pool. `total_stake_in_active_pool += (rewards -commission_amount)` 4. After the addition, shares are bought for the validator with the commission amount. Is this understanding accurate? Did we miss out on anything ? 4. Questions on the [PR](https://github.com/aptos-labs/aptos-core/pull/7961) that you have tagged ? 1. The current_delegated_staking_pool_balances is giving only the current data and is there any way, we could get the historical data (data of previous epochs) ? 2. Using the rewards formula given in the Aptos docs and the formula `shares / total shares * total coins` present in the PR, Can we calculate the total rewards earned by the delegator from a pool till time t using the following formula ? Or are there any edge cases that we are missing out on ? ``` // assuming currBalance only gives (active + pending_inactive stake) const currBalance = shares / total shares * total coins totalRewardsEarnedByTheDelegator = currBalance - (activePrincipal + pendingInactivePrincipal) ``` ![](https://hackmd.io/_uploads/S1Z4bWUVh.png) 4. Our requirement of rewards are: 1. Reward earned by a delegator per day 2. Total Rewards earned by a delegator at time t 3. Total Rewards that are available to be withdrawn at any time t. The approaches that we thought of using are: 1. Tracking the shares, stake of delegators in the active pool at the end of each epoch and get the rewards earned by the end of each epoch and distribute it based on the stake-share ratio of the delegators after removing the commission. But in this approach we need to even track the lockup periods for tracking the inactive stake and that is going to be complex. 2. The formula for totalRewardsEarnedByTheDelegator mentioned in the above question would be computed at the end of each epoch and get the rewards earned. We can just subtract the rewards of day d1 from day d2 to get the rewards earned per day. Can you tell us if these approaches are correct way of populating the data for the requirements? Are we missing any edge cases ? Are there any other approaches that you can think of for populating the data for our requirements ? <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> <br> # Old Questions 1. The steps in the flow of delegation pool mentioned in the [github repo](https://github.com/aptos-labs/aptos-core/blob/main/aptos-move/framework/aptos-framework/sources/delegation_pool.move#L51) considers that comission percentage of the validator is 0%: ![](https://i.imgur.com/uOm3qDN.png) If the commission percentage of the validator is X%, could you tell us what changes would occur in these calculations? Also, does the validator receive shares of the pool due to the commission?" **The commission would be subtracted from the rewards and the operator receives the commission as shares of the pool** 2. Is there a way to get all the delegator addresses of a delegation pool directly, or should we continuously track the events (add_stake, unlock_stake, etc.) to obtain the delegator addresses whose delegation is greater than 0? **only by indexing the AddStakeEvent and WithdrawStakeEvent and updating the delegators set** 3. Is there a way to obtain the historical data (data at the end of past epochs) of all the data items returned by this [view function](https://github.com/aptos-labs/aptos-core/blob/main/aptos-move/framework/aptos-framework/sources/delegation_pool.move#L321)? 4. We want to track the rewards earned by all the delegators for each epoch due to their delegation to our delegation pool. One of the approaches that we found is: 1. Using this [endpoint](https://fullnode.mainnet.aptoslabs.com/v1/accounts/0xff3e9c10dd3781a1e0750a75ae9e5b04133cd7e8ca18b9936ffcf3b2a2538a49/events/0x1::stake::StakePool/distribute_rewards_events?start=0&limit=100), we can find the rewards_amount (which is the reward generated by our pool at all epochs). 2. We can get the stakes (in different states) of each delegator at the end of each epoch using the [view function](https://github.com/aptos-labs/aptos-core/blob/main/aptos-move/framework/aptos-framework/sources/delegation_pool.move#L321). 3. Using the add_stake, unlock_stake, withdraw_stake ... we can maintain the state of stakes of all the delegators and also the number of shares in the active and pending_inactive states. 4. We can obtain the state of the delegations of the delegators at each epoch, as well as the number of shares held by each delegator in the pool and their respective rewards by following steps (2) and (3) and step (1), respectively. With these three pieces of data, we can calculate the amount of reward received by a delegator at the epoch. - The issue we face with this approach is that we can't obtain historical data on the stake states of the delegators, and step 3 may also be a little complex to implement. - Do you find any inconsistencies with our approach? And are there any other easier direct or indirect approaches to calculate the rewards awarded to the delegators at each epoch because of their delegation to our pool? **You can use this formula to calculate rewards: https://aptos.dev/nodes/validator-node/operator/delegation-pool-operations#compute-delegation-pool-rewards-earned**

    Import from clipboard

    Paste your markdown or webpage here...

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password

    or

    By clicking below, you agree to our terms of service.

    Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub
        • Please sign in to GitHub and install the HackMD app on your GitHub repo.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully