Developers Forum for XinFin XDC Network

Lokesh
Lokesh

Posted on

0x(twice) Prefix Issue in Apothem Network

Team -
Recently, we have been facing this address formatting issue, when we submit the trasaction and retrieve the transaction receipt.
Could see that, "getLogs" function is throwing this error and the results shows the contract address is prefixed with 0x(twice), please see below.

RPC Tried - https://rpc.apothem.network


method 'getLogs' Error: [ethjs-format] hex string '0x0xdc4df87777b667e2c7063cd41d8287c85f793988df' must be an alphanumeric 42 utf8 byte hex (chars: a-fA-F) string, is 46 bytes

Discussion (3)

Collapse
ruslan_wing profile image
ruslan wing

I think it should be XDC prefix address only as XDC Network supports XDC Prefix address only.

Collapse
lokesh profile image
Lokesh Author

In fact, the actual contract address is -> xdc4df87777b667e2c7063cd41d8287c85f793988df
But resulting value is 0x0xdc4df87777b667e2c7063cd41d8287c85f793988df

so, 0x0 is getting prefixed.

Collapse
lokesh profile image
Lokesh Author

Yes, but it is not resulting correctly