TransactionId toString not returning the same value as the mirror nodes

[SamCullin]

Description

We are running CONSENSUSSUBMITMESSAGE transactions then we then query from the mirror nodes to find out the message sequence number. However, we randomly found that some messages could not be found. After some digging, we found that the TransactionId.toString() function was returning a timestamp string that did not match the values returned by the mirror node. This made searching for the generated message impossible without creating a custom toString for the TransactionIds.

This only happened when the transaction's nanoseconds begin with a 0.

Example transaction:
https://testnet.mirrornode.hedera.com/api/v1/transactions/0.0.2180436-1681876267-054802581

Example Messages:
https://testnet.mirrornode.hedera.com/api/v1/topics/0.0.4250176/messages?limit=100&order=desc&timestamp=gte%3A1681876267.054802581
Sequence number: 5

Looks like the culprit is this line:
https://github.com/hashgraph/hedera-sdk-js/blob/develop/src/transaction/TransactionId.js#L165
The nanoseconds need to be left padded with 0s for 9 chars

Steps to reproduce

const transactionId_str = '[email protected]'

const transactionId_class = TransactionId.fromString(transactionId_str);

const transactionId_str2 = transactionId_class.toString();

let working = transactionId_str == transactionId_str2;

console.log(working);

Additional context

No response

Hedera network

mainnet, testnet, previewnet, other

Version

v2.23.0

Operating system

Linux

[ochikov]

Hello @SamCullin and thank you for your issue. We are going to schedule it for fixing for our next release. Will keep you updated.

[Neurone]

Padding to 9 chars in the SDK seems a good idea.

As a side note, you can retrieve the sequence number of the message directly using the consensus timestamp instead of searching for the TransacionId, in your example it would be https://testnet.mirrornode.hedera.com/api/v1/topics/messages/1681876277.308591360