Checklist for reporting privacy issues - Besu - LF Decentralized Trust


    
        
            
                
                                

        


        
            

            






Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
PreferencesOnly necessaryAccept all









LF Decentralized Trust

LF Decentralized Trust

Spaces

Apps
Templates

Create
























Besu




	All content



Shortcuts



	Meetings

Meetings


 This trigger is hidden

	How-to articles

How-to articles


 This trigger is hidden






Content







Results will update as you type.

	Code of Conduct





	Contributing





	Developing and Conventions




	Besu CLI Style Guide





	Coding Conventions





	Changelog





	Testing





	Debugging Besu in IntelliJ





	Releasing





	Bug Triage Process





	Policies





	Plugin Services





	Tools we use





	Advanced





	Repositories and other projects





	Archive (Dev)




	GitHub Merge Queue





	[ACCEPTED] DEBUG Log Improvement Proposal





	Checklist for reporting privacy issues





	Shandong Testnet





	Using Postman with Besu







	Changelog Improvement Proposal





	Logging





	Building from source







	Documentation





	Community





	Governance





	Programs & Grants





	Meetings





	Design Documents





	Security





	Audits





	Start Here





	Performance & Stability





	How-to articles





	Incident Reports





	Besu Roadmap & Planning





	How to Contribute



















You‘re viewing this with anonymous access, so some content might be blocked.
Close













Besu

/
Checklist for reporting privacy issues












More actions







Checklist for reporting privacy issues

	Sally MacFarlane





Owned by Sally MacFarlane


Jan 21, 2021










In order for us to be able to investigate your issue, we first need to be able to reproduce it. The more information you can provide, the easier this will be, enabling us to more efficiently investigate the cause of the issue. 
Please provide the following information
	Versions of Besu, Orion and any other relevant software (as per Besu issue template)
	Instructions for how to reproduce the scenario 

	As much specific detail as possible. All required solidity contracts, deploy scripts, supporting contracts, any other prerequisites.
	If the original contracts or deployment scripts can’t be provided, we need a minimal version of them that causes the same issue.

	Have you verified that the same scenario works in Besu without privacy ie as a public contract

	Including instructions on how to deploy the scenario - eg Truffle deploy scripts

	Orion logs
	Enable revert reason on Besu CLI 
	Ensure in the solidity code you are using strings with require/revert statements to make it possible to track where the revert is happening
	Besu log with EVM at trace level 

	Enable trace logging for the EVM org.hyperledger.besu.ethereum.vm.EVM - this will log all EVM operations in the besu log which will give more info about where it is halting 








, multiple selections available,



























































        

    


    {"serverDuration": 13, "requestCorrelationId": "e9b675427f9848a4aa2df5c411102ed8"}