-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Don't work with parity 1.4.9 after ETC DieHard Fork #44
Comments
What value are you seeing in the JSON-RPC transaction receipt object in the "v" field? This should be a byte value encoded as a string (Geth) or byte (Parity). I'm thinking ETC is providing a non-byte value here. See ethereum/EIPs#155 for further information. A dump of the JSON-RPC objects is fine. In order to display the HTTP requests/response, please see https://web3j.github.io/web3j/trouble.html#i-want-to-see-details-of-the-json-rpc-requests-and-responses |
|
I use Parity 1.4.9 ChainID for Ethereum Classic is 0x3d I suppose it may be issue with java byte type which you used for v field in tx |
Yes, but it looks like some of those chain id's are coming through with 0x9d which is a somewhat larger value. |
So, how we can solve it? Otherwise web3j is incompatible with Ethereum Classic :( |
@conor10 |
@conor10 see here ethereum/EIPs#155
With CHAIN_ID equal to 61 you have:
|
Yes - I'll change to an int for the next release. |
Fixed in v1.1.2. |
After 3000000 ETC block I started receive errors:
Before Die Hard Fork all was OK.
The text was updated successfully, but these errors were encountered: