[Service Notice] Decoded Input Format Update for Array & Tuple Parameters

Posted on December 30, 2025

To improve the readability and clarity of decoded transaction inputs,
an update has been applied to the decodedInput response format for specific parameter types.

This change affects array and tuple parameters used in certain smart contract functions.

What Changed

The representation of decodedInput.args[].value has been updated for parameters
that use array or tuple types, in order to make their structure more explicit.

The overall response structure (name, type, value) remains unchanged, and the value field continues to be returned as a string.

Below are examples illustrating the change.

1. Array Parameters

as-is

{
  "name": "b",
  "type": "uint256[2][2]",
  "value": "2009254268261311487...,7643877054716201339...,1543499001004952746...,1241379852416348769..."
}

to-be

{
  "name": "b",
  "type": "uint256[2][2]",
  "value": "[[\"2009254268261311487...\",\"7643877054716201339...\"],[\"1543499001004952746...\",\"1241379852416348769...\"]]"
}

2. Tuple Parameters

as-is

{
  "name": "circomData",
  "type": "tuple",
  "value": "2110507...,,,...,0xA0b8...,50256,35,1767059459,..."
}

to-be

{
  "name": "circomData",
  "type": "tuple",
  "value": "{\"rootHashHinkal\":\"2110507...\",\"erc20TokenAddresses\":[],\"feeStructure\":{\"feeToken\":\"0xA0b8...\",\"flatFee\":\"50256\",\"variableRate\":\"35\"},...}"
}

Affected APIs

The following APIs may return array or tuple parameters in decodedInput
and are affected by this update:

• Get Transactions By Account

• Get Transactions In Block

• Get Transaction By Hash

• Get Transactions By Hashes

Affected Networks

This update applies only on the following networks:

• Arbitrum
• Base
• Chiliz
• Ethereum
• Ethereumclassic
• GIWA
• Kaia
• Optimism
• Polygon
• Luniverse
• Tron

Additional Notes

• Only parameters with array or tuple types are affected by this change
• Single-value parameters (uint256, address, etc.) are not affected
• This update preserves backward compatibility with existing integrations

If you have any questions or require further clarification, please feel free to reach out.