Ever since we created the Epirus blockchain explorer, we wanted to ensure it works seamlessly with several different Enterprise Ethereum (and of course regular Ethereum) blockchain clients.
Until recently, Quorum was the only enterprise client that we fully supported along with its privacy features. We’re pleased to say that from September 2019, Epirus supports the Hyperledger Besu (formerly Pantheon) project too.
We’re pleased to see Besu in Hyperledger. The team at Web3 Labs have been contributing to Besu for some time, working on their privacy features and also ensuring first-class support in Web3j.
We’ve tried to keep things as simple as possible for our users — Epirus works out of the box with either Besu or Quorum — you don’t need to tell it which you’re using when you start it. If you want to check it out, simply run:
git clone https://github.com/blk-io/epirus-free.git
NODE_ENDPOINT=http://<node_endpoint> docker-compose up
Or, if you’d like to run up the full version in Azure, you can head here to get started.
If you want to check out the transaction privacy support, find a contract or transaction that your blockchain node is privy to.
Then when you open the specific transaction in Epirus, you’ll be able to view the input bytecode for the transaction.
Of course if the Besu node is not privy to the private transaction this information will not be available.
That’s all for now, stay tuned for some more big updates on both Epirus and Web3j.