We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Not sure if this something you want to implement, but since the official lisk-service has issues you could use the forger plugin built in to lisk-core. It provides always accurate data since it collects the data from local lisk-core node. You can read about it here: https://lisk.com/documentation/lisk-sdk/references/lisk-framework/forger-plugin.html#actions
The communication with the plugin is through WS. It has two actions that returns everything you want. The aggregated votes and rewards.
forger:getVoters forger:getForgingInfo
The user would have to run his lisk-core with --enable-forger-plugin parameter. It's not a feature request :) Just something for you to consider.
--enable-forger-plugin
The text was updated successfully, but these errors were encountered:
Not sure if this something you want to implement, but since the official lisk-service has issues you could use the forger plugin built in to lisk-core. It provides always accurate data since it collects the data from local lisk-core node. You can read about it here: https://lisk.com/documentation/lisk-sdk/references/lisk-framework/forger-plugin.html#actions The communication with the plugin is through WS. It has two actions that returns everything you want. The aggregated votes and rewards. forger:getVoters forger:getForgingInfo The user would have to run his lisk-core with --enable-forger-plugin parameter. It's not a feature request :) Just something for you to consider.
That's a good idea to overcome lisk-service issue; if implemented, I will let the user to choose how to get the data.
Sorry, something went wrong.
No branches or pull requests
Not sure if this something you want to implement, but since the official lisk-service has issues you could use the forger plugin built in to lisk-core. It provides always accurate data since it collects the data from local lisk-core node. You can read about it here: https://lisk.com/documentation/lisk-sdk/references/lisk-framework/forger-plugin.html#actions
The communication with the plugin is through WS. It has two actions that returns everything you want. The aggregated votes and rewards.
forger:getVoters
forger:getForgingInfo
The user would have to run his lisk-core with
--enable-forger-plugin
parameter.It's not a feature request :) Just something for you to consider.
The text was updated successfully, but these errors were encountered: