An 5336/gnosis standardization

models/doc_descriptions/fsc_evm/blocks.md

@@ -0,0 +1,143 @@
+{% docs evm_blocks_table_doc %}
+
+This table contains block level data for this EVM blockchain. This table can be used to analyze trends at a block level, for example gas fees vs. total transactions over time. For more information, please see [Etherscan Resources](https://etherscan.io/directory/Learning_Resources/Ethereum) or [The Ethereum Organization](https://ethereum.org/en/developers/docs/blocks/)
+
+{% enddocs %}
+
+{% docs evm_block_header_json %}
+
+This JSON column contains the block header details.
+
+{% enddocs %}
+
+{% docs evm_blockchain %}
+
+The blockchain on which transactions are being confirmed.
+
+{% enddocs %}
+
+{% docs evm_blocks_hash %}
+
+The hash of the block header for a given block.
+
+{% enddocs %}
+
+{% docs evm_blocks_nonce %}
+
+Block nonce is a value used during mining to demonstrate proof of work for a given block.
+
+{% enddocs %}
+
+{% docs evm_difficulty %}
+
+The effort required to mine the block.
+
+{% enddocs %}
+
+{% docs evm_extra_data %}
+
+Any data included by the miner for a given block.
+
+{% enddocs %}
+
+{% docs evm_gas_limit %}
+
+Total gas limit provided by all transactions in the block.
+
+{% enddocs %}
+
+{% docs evm_gas_used %}
+
+Total gas used in the block.
+
+{% enddocs %}
+
+{% docs evm_network %}
+
+The network on the blockchain used by a transaction.
+
+{% enddocs %}
+
+{% docs evm_parent_hash %}
+
+The hash of the block from which a given block is generated. Also known as the parent block.
+
+{% enddocs %}
+
+{% docs evm_receipts_root %}
+
+The root of the state trie.
+
+{% enddocs %}
+
+{% docs evm_sha3_uncles %}
+
+The mechanism which Ethereum Javascript RLP encodes an empty string.
+
+{% enddocs %}
+
+{% docs evm_size %}
+
+Block size, which is determined by a given block's gas limit.
+
+{% enddocs %}
+
+{% docs evm_total_difficulty %}
+
+Total difficulty of the chain at a given block.
+
+{% enddocs %}
+
+{% docs evm_tx_count %}
+
+Total number of transactions within a block.
+
+{% enddocs %}
+
+{% docs evm_uncle_blocks %}
+
+Uncle blocks occur when two blocks are mined and broadcasted at the same time, with the same block number. The block validated across the most nodes will be added to the primary chain, and the other one becomes an uncle block. Miners do receive rewards for uncle blocks.
+
+{% enddocs %}
+
+{% docs evm_miner %}
+
+The address of the beneficiary to whom the mining rewards were given
+
+{% enddocs %}
+
+{% docs evm_state_root %}
+
+The root of the final state trie of the block
+
+{% enddocs %}
+
+{% docs evm_transactions_root %}
+
+The root of the transaction trie of the block
+
+{% enddocs %}
+
+{% docs evm_logs_bloom %}
+
+The bloom filter for the logs of the block.
+
+{% enddocs %}
+
+{% docs evm_mix_hash %}
+
+A string of a 256-bit hash encoded as a hexadecimal
+
+{% enddocs %}
+
+{% docs evm_base_fee_per_gas %}
+
+A string of the base fee encoded in hexadecimal format. Please note that this response field will not be included in a block requested before the EIP-1559 upgrade
+
+{% enddocs %}
+
+{% docs evm_withdrawals_root %}
+
+The root of the withdrawals trie.
+
+{% enddocs %}

models/doc_descriptions/fsc_evm/complete_general.md

@@ -0,0 +1,65 @@
+{% docs evm_block_number %}
+
+Also known as block height. The block number, which indicates the length of the blockchain, increases after the addition of each new block.
+
+{% enddocs %}
+
+{% docs evm_block_timestamp %}
+
+The date and time at which the block was produced.
+
+{% enddocs %}
+
+{% docs evm_from_address %}
+
+The sending address of this transaction.
+
+{% enddocs %}
+
+{% docs evm_ingested_at %}
+
+Internal column.
+
+{% enddocs %}
+
+{% docs evm_to_address %}
+
+The receiving address of this transaction. This can be a contract address.
+
+{% enddocs %}
+
+{% docs evm_pk %}
+
+The unique identifier for each row in the table.
+
+{% enddocs %}
+
+{% docs evm_inserted_timestamp %}
+
+The UTC timestamp at which the row was inserted into the table.
+
+{% enddocs %}
+
+{% docs evm_modified_timestamp %}
+
+The UTC timestamp at which the row was last modified.
+
+{% enddocs %}
+
+{% docs evm_precise_amount_unadjusted %}
+
+The precise, unadjusted amount of the transaction. This is returned as a string to avoid precision loss.
+
+{% enddocs %}
+
+{% docs evm_precise_amount_adjusted %}
+
+The precise, adjusted amount of the transaction. This is returned as a string to avoid precision loss.
+
+{% enddocs %}
+
+{% docs evm_value_hex %}
+
+The value of the transaction in hexadecimal format.
+
+{% enddocs %}

models/doc_descriptions/fsc_evm/event_logs.md

@@ -0,0 +1,83 @@
+{% docs evm_logs_table_doc %}
+
+This table contains flattened event logs from transactions on this EVM blockchain. Transactions may have multiple events, which are denoted by the event index for a transaction hash. Therefore, this table is unique on the combination of transaction hash and event index. Please see `fact_decoded_event_logs` or `ez_decoded_event_logs` for the decoded event logs.
+
+{% enddocs %}
+
+{% docs evm_event_index %}
+
+Event number within a transaction.
+
+{% enddocs %}
+
+{% docs evm_event_inputs %}
+
+The decoded event inputs for a given event.
+
+{% enddocs %}
+
+{% docs evm_event_removed %}
+
+Whether the event has been removed from the transaction.
+
+{% enddocs %}
+
+{% docs evm_log_id_events %}
+
+This is the primary key for this table. This is a concatenation of the transaction hash and the event index at which the event occurred. This field can be used within other event based tables such as `fact_transfers` & `ez_token_transfers`.
+
+{% enddocs %}
+
+{% docs evm_logs_contract_address %}
+
+The address interacted with for a given event.
+
+{% enddocs %}
+
+{% docs evm_logs_contract_name %}
+
+The name of the contract or token, where possible.
+
+{% enddocs %}
+
+{% docs evm_logs_data %}
+
+The un-decoded event data.
+
+{% enddocs %}
+
+{% docs evm_logs_tx_hash %}
+
+Transaction hash is a unique 66-character identifier that is generated when a transaction is executed. This field will not be unique in this table, as a given transaction can include multiple events.
+
+{% enddocs %}
+
+{% docs evm_topics %}
+
+The un-decoded event input topics.
+
+{% enddocs %}
+
+{% docs evm_topic_0 %}
+
+The first topic of the event, which is a unique identifier for the event.
+
+{% enddocs %}
+
+{% docs evm_topic_1 %}
+
+The second topic of the event, if applicable.
+
+{% enddocs %}
+
+{% docs evm_topic_2 %}
+
+The third topic of the event, if applicable.
+
+{% enddocs %}
+
+{% docs evm_topic_3 %}
+
+The fourth topic of the event, if applicable.
+
+{% enddocs %}