# Slippage & Protocol Fees Whenever institutions trade on legacy decentralized exchanges, they bleed capital. This bleeding is categorized as MEV (Maximum Extractable Value), front-running, or "hidden slippage." It is the most persistent, predatory pain point in crypto trading. Why has the industry accepted this adversarial "dark forest" as a permanent cost of doing business? Because the ecosystem is trapped in a fatal architectural design: The Mempool Lottery Illusion. Legacy smart contracts (e.g., EVM models) separate a trader's *Intent* from the *Final Execution Price*. They force traders to broadcast their vulnerable intentions into a public mempool, relying entirely on miners or sequencers to execute the trade fairly. The industry falsely accepted the illusion that price discovery requires exposing your trading intent to public manipulation prior to settlement. #### The Deterministic Axiom: Cryptographically Bound Execution Nexus Protocol completely eliminates MEV at the structural layer. It proves a foundational execution truth: The execution parameters must be cryptographically finalized BEFORE hitting the network. Nexus does not rely on off-chain "grace" to honor quoted prices; it relies on cold Bitcoin cryptography. Through the use of [Partially Signed Bitcoin Transactions (PSBTs)](/protocol-architecture/psbt-engine.md), the protocol embeds the trader's exact absolute slippage tolerance directly into the UTXO constraints. If the executed state of the AMM breaches the defined slippage limit by a single Satoshi, the PSBT intrinsically and mathematically fails. The output branch cannot be unlocked, rendering the entire multi-party transaction invalid. No miner, no sequencer, and no arbitrage bot can alter the execution rate, because the underlying asset is cryptographically forbidden from moving. This guarantees that an institution will NEVER experience execution at an un-approved limit price. Zero MEV by structural design, not by good faith. Component Analysis For algorithmic trading analysis, slippage in Nexus consists of: 1. Impact Slippage: The deterministic price movement natively caused by passing the trade volume across the CPMM/CLMM curve. 2. Routing Slippage: The compounded impact resulting from bridging across distinct fragmented liquidity sources via Multi-Maker Routing. 3. *Note: Volatility Slippage (market moving between Request and Execution) is entirely mitigated by the aforementioned PSBT Slippage Guard.* #### Transparent Fee Architecture Nexus employs a competitive, transparent fee model separating purely independent Node Operators from general Protocol Treasuries. This creates natural market-driven yield optimization for liquidity providers. Institutional Nexus Nodes (Self-Custodial LP) Entities running bespoke Node and Institutional MPC strategies retain absolute control over their yield metrics. * Variable LP Fee: Independently defined by the Node operator based on their proprietary market-making algorithmic risk models. (e.g. Setting a high spread on low-liquidity long-tail assets). * Fixed Protocol Infrastructure Fee: A flat `0.1%` collected automatically via the transaction outputs to fund ongoing Nexus infrastructure and developmental maintenance. * Settlement: The LP Fees are settled *instantly* and *directly* back to the operator's private, self-custodied wallet on every atomic trade. Sourced Liquidity Pools (Custodial LP) For baseline liquidity aggregated globally under the managed Nexus Pool (previously DotSwap): * Dynamic Fee Share: A strict 4:1 ratio. `80%` of the total transaction fee distributes proportionally among the Liquidity Providers, while `20%` flows to the Protocol Infrastructure. * Competition: Because independent Institutional Nodes command their own fee markets, algorithmic Taker routines automatically route volume to the most capital-efficient nodes, driving a constant, natural compression on execution costs ecosystem-wide. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.on.nexus/trading-and-routing-strategies/economics.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.