Skip to main content
Ethereum

Return to Question

Removed the "hash" tag since it's not related
Link
FranLegon
FranLegon
  • 3
  • 2
Corrected "hashed" for "hexed"
Source Link
FranLegon
FranLegon
  • 3
  • 2

This is what I have so far, please correct me if I'm wrong:

The data parameter of a transaction is where we tell a deployed smart contract how we want to interact with it. It contains a hashedhexed JSON containing all the input for all the functions of the contract we want to interact with. This JSON is coded using the contract's ABI, which is kind of a manual on what formats the contract can take and will return. To fit in the data parameter, the JSON we want to send must be hashedturned into hex.

Assuming all this is right, I'm looking for examples of non-hashedhexed data JSONs to get a grasp on what I'm suposed to write using the ABI.

This is what I have so far, please correct me if I'm wrong:

The data parameter of a transaction is where we tell a deployed smart contract how we want to interact with it. It contains a hashed JSON containing all the input for all the functions of the contract we want to interact with. This JSON is coded using the contract's ABI, which is kind of a manual on what formats the contract can take and will return. To fit in the data parameter, the JSON we want to send must be hashed.

Assuming all this is right, I'm looking for examples of non-hashed data JSONs to get a grasp on what I'm suposed to write using the ABI.

This is what I have so far, please correct me if I'm wrong:

The data parameter of a transaction is where we tell a deployed smart contract how we want to interact with it. It contains a hexed JSON containing all the input for all the functions of the contract we want to interact with. This JSON is coded using the contract's ABI, which is kind of a manual on what formats the contract can take and will return. To fit in the data parameter, the JSON we want to send must be turned into hex.

Assuming all this is right, I'm looking for examples of non-hexed data JSONs to get a grasp on what I'm suposed to write using the ABI.

Source Link
FranLegon
FranLegon
  • 3
  • 2

ABI derived JSON in the "data" parameter of a raw transaction

This is what I have so far, please correct me if I'm wrong:

The data parameter of a transaction is where we tell a deployed smart contract how we want to interact with it. It contains a hashed JSON containing all the input for all the functions of the contract we want to interact with. This JSON is coded using the contract's ABI, which is kind of a manual on what formats the contract can take and will return. To fit in the data parameter, the JSON we want to send must be hashed.

Assuming all this is right, I'm looking for examples of non-hashed data JSONs to get a grasp on what I'm suposed to write using the ABI.