or
or
By clicking below, you agree to our terms of service.
New to HackMD? Sign up
Syntax | Example | Reference | |
---|---|---|---|
# Header | Header | 基本排版 | |
- Unordered List |
|
||
1. Ordered List |
|
||
- [ ] Todo List |
|
||
> Blockquote | Blockquote |
||
**Bold font** | Bold font | ||
*Italics font* | Italics font | ||
~~Strikethrough~~ | |||
19^th^ | 19th | ||
H~2~O | H2O | ||
++Inserted text++ | Inserted text | ||
==Marked text== | Marked text | ||
[link text](https:// "title") | Link | ||
 | Image | ||
`Code` | Code |
在筆記中貼入程式碼 | |
```javascript var i = 0; ``` |
|
||
:smile: | ![]() |
Emoji list | |
{%youtube youtube_id %} | Externals | ||
$L^aT_eX$ | LaTeX | ||
:::info This is a alert area. ::: |
This is a alert area. |
On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?
Please give us some advice and help us improve HackMD.
Syncing
xxxxxxxxxx
Quick notes on Blocknative vs Mempool Dumpster data initiatives
by Thomas Thiery, October 19th, 2023
Thanks to Barnabé, mike and Chris for feedback and comments.
Blocknative (BN) Mempool Data Program and Flashbots Mempool Dumpster (MD) are two recent initiatives aimed at open-sourcing Ethereum mempool data. In this short report, we analyze and compare both datasets to highlight their key differences and foster data initiatives within the community.
We utilize one day of mempool data (September 21, 2023), from both the BN and MD datasets, to build upon Chris' MD analysis.
Blocknative Mempool data
BN has been archiving historical mempool data since November 2019. It collects and provides data from three regions (North America, Europe, and Asia), and its schema includes 27 fields listed here, covering all transaction information except signature data. When analyzing the data, we can use the
status
field to determine whether the transaction was pending in the mempool, rejected, evicted, canceled, sped-up, confirmed, or failed. Note that both confirmed and failed tags indicate that transactions landed onchain. Figure 1A shows the unique transactions count for everystatus
tags. On September 21st, the BN dataset included 1,422,827 unique transactions: 72.3% of transactions succesfully landed onchain (see Table 1, Nincluded = 1,029,508), and 7.3% of transactions that landed onchain were not seen in the mempool, thus representing Exclusive Orderflow (NEOF = 112419). Note that transactions confirmed onchain but not seen by the mempool can be identified by looking confirmed transactions with thetimepending
field set to 0. BN dataset also provides fields specifically created to give more details about transactions' status (see Figure 1B), such asfailurereason
(e.g.,Reverted: UniswapV2Router: INSUFFICIENT_OUTPUT_AMOUNT
),dropreason
(e.g.,replaced-txs
,low-nonce
) andrejectionreason
(e.g.,exceeds block gas limit
).- The image was uploaded to a note which you don't have access to
- The note which the image was originally uploaded to has been deleted
Learn More →We then evaluated the inclusion time for mempool transactions using
timepending
andblockspending
fields in BN dataset(Figure 2). On September 21st, we show that succesful transactions landing onchain had 73% chances of being included in the next block (Figure 2, right panel), with a median inclusion time of 8,636 ms (left panel). On the other hand, failed transactions have 68% chances of being included in the next block, with a median inclusion time of 9,277 ms.- The image was uploaded to a note which you don't have access to
- The note which the image was originally uploaded to has been deleted
Learn More →Flashbots Mempool Dumpster
The Mempool Dumpster (MD) iniative was launched on September 4th, 2023 by Flashbots. Today, it encompasses about two months' worth of data starting on September 8th, from generic EL nodes (e.g., go-ethereum, Infura), Alchemy, bloXroute, Chainbound and Eden. The dataset's schema is composed of 18 fields, inclusive of signature data, and on September 21st, it included 1,307,926 unique transactions (see breakdown in Figure 3). Out of these unique transactions, 78% were included onchain (Nincluded = 1,020,078), which can be determined by filtering on
included_at_block_height
,included_block_timestamp_ms
andinclusion_delay_ms
fields (transactions are included onchain when these fields are greater than 0). Having multiple sources allows to compare various metrics.Having multiple sources also allows to identify transactions that were exclusively seen by some entities. However, the MD dataset doesn't include an exhaustive list of all transactions that ended up landing onchain (the equivalent of
confirmed
transactions in the BN dataset), making it harder to estimate EOF accurately (here, EOF refers to transactions that landed onchain without being seen the mempool, not transactions exclusive to a particular source). To estimate EOF, we used the Dune API to retrieve the exhaustive list of all transactions that landed onchain, and identified transactions that were not seen in the mempool by any of the sources from the MD dataset. We estimated EOF and showed that 8.7% (NEOF = 113,521) of all transactions landing onchain were not seen in the mempool across all sources.Blocknative 🤝 Mempool Dumpster analyses
We combined BN, MD and Dune datasets to get additional insights on metrics we can derive from mempool data. First, we computed the difference in transactions count between BN and MD. We found that 191,812 transactions were exclusive to BN, while 76,911 transactions could only be found in MD. However, the difference was a lot smaller for transactions that ended up onchain. The BN dataset contained 115 transactions that landed onchain and were not present in MD. Conversely, only 35 transactions were only present in MD.
We then set out to compare inclusion time delays between BN and MD datasets. Suprisingly, we found large differences between both distributions, with a median inclusion time of 8,689 ms for BN and 6,837 ms for MD (see Figure 4). After further investigation, we found that these differences originated from differences in how inclusion delays are computed in BN and MD datasets. In BN, the inclusion delay refers to the actual time transactions are pending in the mempool before getting included onchain when transactions are seen in the mempool first. In MD, the inclusion delay is the difference between the transaction was seen in the mempool and the block timestamp: this can lead to very low, and negative inclusion delays for a significant number of transactions (N = 13,678), leading the differences displayed in Figure 4.
- The image was uploaded to a note which you don't have access to
- The note which the image was originally uploaded to has been deleted
Learn More →Lastly, we compared the time at which transactions were first detected BN and MD mempools. Out of 1,00,1295 transactions present in both datasets, 66.31% (N = 667,272, median BNdetecttime - MDdetecttime = 43ms) were first detected by Blocknative (see Figure 5). For more detection time results specific to MD, check out the results obtained in this analysis.
Conclusion
Blocknative Mempool Data Program and Flashbots Mempool Dumpster initiative publicly shared datasets that can be used to offer valuable insights on how and when public transactions get included in Ethereum blocks. We think this will help accelerate empirical research in key areas of the Ethereum supply network such as censorship and its impact on inclusion time, builders behavioral profiles, and more!