ClientConstants.js missing entries

[gregscullard]

Description

A transaction generated by a node.js backend fails to be processed by a wallet with an 'invalid node account id' error.
The transaction specified node account id 0.0.18 which is a valid consensus node, however the ClientConstants.js doesn't have an entry for this node accountId, it goes from 17 to 19, skipping 18 altogether

https://github.com/hashgraph/hedera-sdk-js/blob/develop/src/constants/ClientConstants.js

    "https://node14.swirldslabs.com:443": new AccountId(17),
    "https://node16.swirldslabs.com:443": new AccountId(19),

Also note that the list of consensus nodes https://docs.hedera.com/hedera/networks/mainnet/mainnet-nodes goes up to node account id 0.0.31, the constants file stops at 0.0.29.

Steps to reproduce

Generate a transaction which specifies account id 0.0.18 for the node_account_id, attempt to sign and execute the transaction in a web client, it will fail.

Additional context

No response

Hedera network

mainnet

Version

2.29

Operating system

None

[SimiHunjan]

Noting here that 0.0.31 and 0.0.30 do not currently have a gRPC web proxy set up. Once this service is available we will add them to the SDKs. DevOps will note when available.