Time-Varying Bidirectional Causal Relationships between Transaction Fees and Economic Activity of Subsystems Utilizing the Ethereum Blockchain Network
Bibliographic record
Abstract
The Ethereum blockchain network enables transaction processing and smart-contract execution through levies of transaction fees, commonly known as gas fees. This framework mediates economic participation via a market-based mechanism for gas fees, permitting users to offer higher gas fees to expedite processing. Historically, the ensuing gas fee volatility led to critical disequilibria between supply and demand for block space, presenting stakeholder challenges. This study examines the dynamic causal interplay between transaction fees and economic subsystems leveraging the network. By utilizing data related to unique active wallets and transaction volume of each subsystem and applying time-varying Granger causality analysis, we reveal temporal heterogeneity in causal relationships between economic activity and transaction fees across all subsystems. This includes (a) a bidirectional causal feedback loop between cross-blockchain bridge user activity and transaction fees, which diminishes over time, potentially signaling user migration; (b) a bidirectional relationship between centralized cryptocurrency exchange deposit and withdrawal transaction volume and fees, indicative of increased competition for block space; (c) decentralized exchange volumes causally influence fees, while fees causally influence user activity, although this relationship is weakening, potentially due to the diminished significance of decentralized finance; (d) intermittent causal relationships with maximal extractable value bots; (e) fees causally influence non-fungible token transaction volumes; and (f) a highly significant and growing causal influence of transaction fees on stablecoin activity and transaction volumes highlight its prominence. These results inform strategic considerations for stakeholders to more effectively plan, utilize, and advocate for economic activities on Ethereum, enhancing the understanding and optimization of within the rapidly evolving economy.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.002 | 0.018 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.002 |
| Science and technology studies | 0.000 | 0.001 |
| Scholarly communication | 0.002 | 0.002 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.000 | 0.001 |
| Insufficient payload (model declined to judge) | 0.006 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".