The `nonce` returned by `eth_getTransactionByHash` is non-compliant

[leonway336]

It should be 0x0, not 0x0000000000000000.

Match pattern: ^0x(0|[1-9a-f][0-9a-f]*)$

[waynercheung]

Thank you for reporting this issue.

After reviewing our code, I can confirm that java-tron currently returns 0x0000000000000000 for the nonce field:

nonce = ByteArray.toJsonHex(new byte[8]); // no value

This was previously modified to maintain compatibility with Graph Node.

According to the Ethereum JSON-RPC specification at https://ethereum.github.io/execution-apis/api/methods/eth_getTransactionByHash, the nonce field should match the pattern: ^0x(0|[1-9a-f][0-9a-f]*)$

This means the correct format should be 0x0 (without leading zeros), not 0x0000000000000000.

This maybe an non-compliance issue. However, since this interface is already being used in production by existing users, we need to carefully evaluate the compatibility impact before making changes. We will:

1. Assess the potential breaking changes for existing integrations
2. Consider a migration strategy if needed
3. Define a proper fix plan based on the evaluation

I appreciate your patience while we work through this compatibility assessment. I will update this issue once we have a concrete plan for the fix, and we welcome input from other developers during this process.

[lxcmyf]

@leonway336
Both 0x0000000000000000 and 0x0 will be parsed as 0, so this should not actually impact users functionally. However, for better spec compliance and standardization, we can update the return value to 0x0 in a future release.