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 
  • No labels