-
Notifications
You must be signed in to change notification settings - Fork 23
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
Fields missing from voter_info in get_account API response on WAX #77
Comments
Voter rewards like this are unique to WAX and not natively a part of Antelope system contracts, which is why we didn't include these fields in the base response. Telos also has a few unique fields (different than WAX) I believe too. Some examples: EOS{
"owner": "teamgreymass",
"proxy": "greymassvote",
"producers": [],
"staked": 100202,
"last_vote_weight": "863265464502.93908691406250000",
"proxied_vote_weight": "0.00000000000000000",
"is_proxy": 0,
"flags1": 0,
"reserved2": 0,
"reserved3": "0.0000 EOS"
} Telos{
"owner": "teamgreymass",
"proxy": "",
"producers": [],
"staked": "6682315286",
"last_stake": 0, // Variation, new field
"last_vote_weight": "0.00000000000000000",
"proxied_vote_weight": "0.00000000000000000",
"is_proxy": 0,
"flags1": 0,
"reserved2": 0,
"reserved3": "0 " // Variation, not an Asset
} WAX{
"owner": "teamgreymass",
"proxy": "",
"producers": [],
"staked": "9039133084986",
"unpaid_voteshare": "0.00000000000000000", // Variation, new field
"unpaid_voteshare_last_updated": "2023-08-18T17:24:12.000", // Variation, new field
"unpaid_voteshare_change_rate": "84871176772458765566336581970335981633536.00000000000000000", // Variation, new field
"last_claim_time": "2023-08-18T17:24:12.000", // Variation, new field
"last_vote_weight": "84871176772458765566336581970335981633536.00000000000000000",
"proxied_vote_weight": "0.00000000000000000",
"is_proxy": 0,
"flags1": 0,
"reserved2": 0,
"reserved3": "0 " // Variation, not an asset
} Because of this, I think what we're going to do is break apart the |
Just a note related to this and to have a record outside of Telegram. These are |
Closing this here, since this work is now being done in https://github.com/wharfkit/account and was completed here wharfkit/account#15 |
Summary:
The get_account API response on WAX differs slightly from the base response of Antelope.
These include the following fields:
Steps to Reproduce:
.v1.chain.get_account()
against a WAX node.Expected Results:
Actual Results:
Additional Information:
I consider this a bug because the available data is not passed through to the object.
These missing fields are required to calculate voter rewards.
I am unaware of any other way to calculate voter rewards without this data, which surprises me that these are missing from the base Antelope response.
The text was updated successfully, but these errors were encountered: