flow-models/models/evm/descriptions/blocks/uncle_blocks.md
Jack Forgash 88df737fa2
AN-5203/Deploy flowEVM (#343)
* flow evm init

* flow evm testnet - blocks

* deploy dev udfs, update typo

* send block height as hex

* dev limit

* use stg external table

* some links

* add query to side doc

* upd external tbl to stg & testnet

* silver and evm txs

* testnet silver models pt1

* testnet events final, decode hash udf

* udf get evm chainhead

* upd resource list

* new udf. receipts pipeline. upd testnet model cols. expand readme

* receipts silver

* traces

* vault

* reorg to evm dir

* rm testnet, blocks lookback

* lookbacks, move qualify

* macro and align naming

* del testnet, reset namespace to gen

* silver_evm - receipts and txs

* core_evm fact_blocks & fact_transactions

* fix vault path in get blocks. Logs v1 (need sample)

* core_evm fact_logs

* CR updates

* del readme and add workflow

* upd vault path, batch size

* incr logic on modified to core_evm

* use local utils.udf, add blockNumber col to complete blocks check

* rm col

* correct _invocation_id

* upd nv csv

* incr batch limit due to late start

* add evm tag to model run
2024-09-05 20:43:33 -06:00

318 B

{% docs flowevm_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 %}