You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some additional endpoints are needed to support IOTA 2.0:
read_committee
Accepts an epochs index and returns the validator committee at that epoch.
Usage expectation: Tracking committee per epoch for analytics.
read_output_mana_rewards
Accepts an output ID and slot index and returns the mana rewards.
Usage expectation:
Analytics tracking per epoch
Determining burned mana in transactions (something like burned_mana = output_mana - (input_mana + rewards)
Questions: Is this calculation even possible? Can rewards be partially claimed, or not claimed?
read_account_ledger
Not sure about this one, but we need a way to track, at minimum, the size of the account ledger.
Usage expectation: UTXO ledger size vs Account ledger size analytics
The text was updated successfully, but these errors were encountered:
Description
Some additional endpoints are needed to support IOTA 2.0:
read_committee
Accepts an epochs index and returns the validator committee at that epoch.
Usage expectation: Tracking committee per epoch for analytics.
read_output_mana_rewards
Accepts an output ID and slot index and returns the mana rewards.
Usage expectation:
burned_mana = output_mana - (input_mana + rewards
)Questions: Is this calculation even possible? Can rewards be partially claimed, or not claimed?
read_account_ledger
Not sure about this one, but we need a way to track, at minimum, the size of the account ledger.
Usage expectation: UTXO ledger size vs Account ledger size analytics
The text was updated successfully, but these errors were encountered: