0

I've cloned the ethereumj codebase, and in the directory ethereumj/ run it for testnet with the following command:

./gradlew runRopsten

However, during the block synchronization process there is a discrepency between the blocks as they're described in the console, and the corresponding block number as described by etherscan.

For instance, consider Block #588712, pictured below:

enter image description here

The console asserts that it contains 70 transactions, however- on etherscan it describes that block as containing 0 transactions. See below:

enter image description here






Here is an additional example:



enter image description here

enter image description here






One can also run this client with the command

./gradlew run -PmainClass=org.ethereum.samples.RopstenSample

It results in the same error, as demonstrated here:

enter image description here

enter image description here

1 Answer 1

0

My guess is that the ethereumj client is somehow trying to access the "original ropsten" testnet whereas etherscan is displaying information from the ropsten-revival testnet, as it says here:

enter image description here

If that's the case, how can I get the ethereumj client to connect to the ropsten-revival testnet?

But if something else is going on- what is it?

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.