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

Does an incorrect implementation of ConsensusDataProvider pose a risk of vulnerabilities? #1535

Open
jyaymusk opened this issue Oct 29, 2024 · 1 comment
Labels

Comments

@jyaymusk
Copy link

Does an incorrect implementation of ConsensusDataProvider pose a risk of vulnerabilities? What is the most serious incident associated with it?

I noticed that there is a lack of BABE consensus-related implementations here, but I found it in a community project. If you have time, I hope you can take a look at its implementation for any potential issues.

community BabeConsensusDataProvider

Also, thank you very much for your contributions to the open-source code, it has saved us a lot of time!

@jyaymusk
Copy link
Author

jyaymusk commented Oct 30, 2024

In addition, I found the implementation of debug here, but did not see the RPC support of trace. What is the reason? Because I found that moonbean has trace support, I think this is a common demand. Thanks again

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant