AI & ML
An Empirical Study of Undisclosed Charges in Hook-Based Decentralized Exchanges
arXiv cs.CR0 views
arXiv:2610.36682v1 Announce Type: new Abstract: Many decentralized exchanges use automated market makers (AMMs) to trade assets against liquidity pools. Modern AMMs allow third-party contracts, called Hooks, to customize this process. However, Hooks can impose additional deductions that fee breakdowns based on standard pool parameters do not itemize. We present, to the best of our knowledge, the first large-scale empirical study of the production Hook ecosystem, focusing on these undisclosed settlement charges. Our study covers 7,873 Hook deployments, 50,011 pools, and 296M pool events on Uniswap v4 and PancakeSwap Infinity across Ethereum and BNB Smart Chain (BSC) through August 1, 2026. We develop a bytecode analysis that reconstructs how Hooks change traders' payments and receipts, separating charges from exchanged assets and standard fees. We then reconstruct historical settlements to measure charging frequency and economic burden. We find that direct settlement adjustment is the dominant Hook capability, supported by 71.37% of registered Hooks. Charging capability is widespread and often exercised: 24.30% of Hooks can impose undisclosed deductions, and these deductions occur in 59.23% of accounted swaps involving such Hooks. These charges generate millions of dollars in revenue, with $3.97M recorded across Hooks with available token prices. These findings reveal a gap between standard fee displays and actual trading costs, motivating explicit disclosure of Hook deductions alongside standard fees.
Source:https://arxiv.org/abs/2610.36682PreviousSilent Blindness: Fault Vulnerability of Hardware Malware DetectorsNextQuantifying and Prioritizing Stealthy Source-Manipulation Threats Against Multi-Source Anomaly Detectors
Related posts
Building an Agent Evaluation CI/CD Pipeline: Architecture, Budgets, and Regression Gates
0dev.to Testing
Truncado silencioso: cuando un verificador de LLM da el mismo puntaje a una respuesta correcta y a una incorrecta
0dev.to Testing
Your CI is red because of code you didn't write
0dev.to OpenSource
Summer 2026 Internships: 8 New Openings This Week (Nov 2)
0dev.to Programming
Ruby Receptionist Alternatives: 5 Options Compared (2026)
0dev.to Programming
Why coding agents break prompt caching (and how to fix it)
0dev.to Programming