You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the SDK level, functions crafting transactions have multiple parameters: functional parameters (such as the payload to attest, etc.) and technical parameters (such as a custom ABI, etc.).
Example: the attestV2 function in the PortalDataMapperhere.
While the functional parameters are mandatory, the technical parameters are optional and/or have a default value. And at the same time, they generate a long signature for the functions.
The goal of this ticket is to harmonize the technical parameters on all functions generating an on-chain transaction, by introducing a TransactionOptions object regrouping these parameters.
The text was updated successfully, but these errors were encountered:
At the SDK level, functions crafting transactions have multiple parameters: functional parameters (such as the payload to attest, etc.) and technical parameters (such as a custom ABI, etc.).
Example: the
attestV2
function in thePortalDataMapper
here.While the functional parameters are mandatory, the technical parameters are optional and/or have a default value. And at the same time, they generate a long signature for the functions.
The goal of this ticket is to harmonize the technical parameters on all functions generating an on-chain transaction, by introducing a
TransactionOptions
object regrouping these parameters.The text was updated successfully, but these errors were encountered: