Submit a legacy Zilliqa transaction (migration escrow only)
deprecatedAuthorizations
ApiKeyAuthApiKeyAuthapi-key string
NOWNodes API key passed in the api-key header.
DEPRECATED / RESTRICTED.
CreateTransaction submits legacy Zilliqa transactions signed with the legacy Schnorr scheme.
In zq2 v0.21.9 the method is still registered in the RPC surface; it is not removed.
Behaviour depends on the migration state:
- Before the escrow migration flag is active, the handler rejects the call with JSON-RPC error code -32 (RpcMethodDeprecated) and message "CreateTransaction is disabled".
- After the escrow migration flag is active, the handler processes the legacy transaction, but network validation only accepts transactions addressed to the designated migration escrow contract.
- A legacy transaction targeting any other address is rejected with JSON-RPC error code -26 (RpcVerifyRejected) and message "Zilliqa transactions are only accepted when addressed to the escrow contract".
For normal Zilliqa EVM transaction submission, use eth_sendRawTransaction.
This entry documents a behavioural migration change. It does not represent removal of the CreateTransaction RPC method.
Body
jsonrpcstring2.0requiredJSON-RPC version.
methodstringCreateTransactionrequiredRPC method name.
idinteger<int64>requiredJSON-RPC request ID.
paramsArray<LegacyZilliqaTransaction>requiredLegacy Zilliqa transaction parameters.
Response
Native zq2 JSON-RPC response. Application-level success and rejection responses are returned as JSON-RPC envelopes.
Gateway-level response observed on the NOWNodes endpoint on 2026-09-14: {"error":"ECONNREFUSED"}.
This is not the native zq2 CreateTransaction JSON-RPC error contract and should not be treated as the permanent response of the RPC method.