@@ -31,9 +31,9 @@ and Event signatures for a given smart contract. Along with [Names](/data-model/
31
31
use of ABIs goes a very long way towards making your Ethereum data much more understandable.
32
32
33
33
Similar to names of addresses, ABI files are not available on-chain which means they must be
34
- acquired somewhere. Unfortunately, the Ethereum community has not yet understand that Etherscan
34
+ acquired somewhere. Unfortunately, the Ethereum community has not yet understood that Etherscan
35
35
is not a good place to store this very important information. For this reason, TrueBlocks uses
36
- Etherscan to acquire ABI files and therefor one needs to get an Etherscan API key to use this
36
+ Etherscan to acquire ABI files and therefore one needs to get an Etherscan API key to use this
37
37
function.
38
38
39
39
The following commands produce and manage Abis:
@@ -96,9 +96,9 @@ Functions consist of the following fields:
96
96
97
97
Parameters are a constituent part of a [ Function or Event] ( /data-model/accounts/#function ) . The
98
98
parameters of a function are each individual value passed into the function. Along with the
99
- function's name, the parameters types (once canonicalized) are used to create a function's four
99
+ function's name, the parameter types (once canonicalized) are used to create a function's four
100
100
byte signature (or an event's 32-byte signature). Parameters are important to TrueBlocks because
101
- we use them as part of the ABI decoding and the ` --articulate ` process to conver the blockchain's
101
+ we use them as part of the ABI decoding and the ` --articulate ` process to convert the blockchain's
102
102
bytes into human-readable text.
103
103
104
104
The following commands produce and manage Parameters:
0 commit comments