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
#6094 introduced the option to provide the calldata via the input field instead of the deprecated data field. To remain compatible with chains that have not yet implemented the updated spec, the Chainlink node will set both fields, which is working fine with all other chains so far but fails on Besu due to the strict check in the aforementioned PR:
if (input != null && data != null) {
throw new IllegalArgumentException("Only one of 'input' or 'data' should be provided");
}
Is there a specific resons why this check is this strict, or could it be relaxed to the following:
if (input != null && data != null && !input.equals(data)) {
throw new IllegalArgumentException("Only one of 'input' or 'data' should be provided");
}
The text was updated successfully, but these errors were encountered:
Hi!
#6094 introduced the option to provide the calldata via the
input
field instead of the deprecateddata
field. To remain compatible with chains that have not yet implemented the updated spec, the Chainlink node will set both fields, which is working fine with all other chains so far but fails on Besu due to the strict check in the aforementioned PR:Is there a specific resons why this check is this strict, or could it be relaxed to the following:
The text was updated successfully, but these errors were encountered: