Cowrie Research

nile-primary-sources-2026-05-07

3 min read

NILE primary sources — 2026-05-07

Project

  • Name: NILE
  • URL: https://nile.build
  • Category: concentrated-liquidity ve(3,3) DEX / gauge marketplace / Linea liquidity-routing layer
  • Whitepaper status: No canonical standalone whitepaper or litepaper surfaced in this pass.

Primary sources reviewed

  1. Docs overview / “What is NILE?”: https://docs.thenile.exchange/introduction-to-nile/what-is-nile

    • Frames NILE as “The Next Generation of Concentrated Liquidity.”
    • Says NILE is a sister fork to RAMSES on Arbitrum and inherits a concentrated-liquidity ve(3,3) implementation for Linea.
    • Useful because it places NILE in the Ramses/Solidly descendant lineage directly rather than leaving the comparison implicit.

  2. veNILE (veNFT) page: https://docs.thenile.exchange/introduction-to-nile/ve-3-3-fundamentals/venile-venft

    • Says veNILE positions are ERC-721 vote-escrow NFTs.
    • Lists the key rights: gauge-emissions voting, vote-bribe and swap-fee earning, transfer/merge of positions, and dilution-protection rebases.
    • Confirms that governance rights are packaged as transferrable/mergeable NFT positions rather than plain balance-based staking.

  3. Voting page: https://docs.thenile.exchange/introduction-to-nile/dex-functionalities/voting

    • States clearly that the main purpose of veNILE is to direct emissions to LP pairs.
    • Says pair emissions are proportional to their percentage of epoch votes.
    • Gives a concrete example where 10% of votes would route 10% of weekly NILE emissions to a pair.

  4. Swap-fee structure page: https://docs.thenile.exchange/introduction-to-nile/dex-functionalities/swaps/swap-fee-structure

    • Says default fees are 0.25% for volatile pairs and 0.01% for correlated pairs.
    • Says the native NILE/wETH pair starts at a 2% swap fee to strengthen protocol-aligned native liquidity.
    • Says the multisig can adjust fees, and that volatility can push fees beyond ordinary ranges, which shows fee policy remains an operator/governance lever.

  5. Dilution-protection rebases page: https://docs.thenile.exchange/nile-tokenomics/dilution-protection-3-3-rebases

    • Says veNILE holders begin with a 25% weekly anti-dilution rebase.
    • Says that rebase rate increases by 1% each epoch until a 50% cap.
    • Makes anti-dilution a first-class part of the incentive story rather than a minor implementation detail.

  6. Formal audits page: https://docs.thenile.exchange/security-and-legal-considerations/formal-audits

    • Says NILE is an authorized fork of RAMSES and inherits the same security posture.
    • Points to a yAudit review of the RAMSES concentrated-liquidity / BUSL-protected codebase.
    • Useful because NILE’s security claims depend heavily on inherited Ramses work rather than on a separate NILE-native audit corpus.

  7. Why proxy contracts?: https://docs.thenile.exchange/security-and-legal-considerations/why-proxy-contracts

    • Explicitly argues Solidly-style codebases are too complex and vulnerability-prone for immediate immutability.
    • Says upgrades pass through a timelock and that notifications are broadcast publicly through Discord/onchain tooling.
    • Shows NILE’s preferred tradeoff: patchability and operational oversight over pure immutability.

  8. dApp and socials page: https://docs.thenile.exchange/resources/dapp-and-socials

    • Confirms the main site as https://nile.build and links official social surfaces.

Mechanism takeaways

  • NILE is a useful comparison class for the Ramses / Velodrome / Solidly-descendant family because it ports the gauge-voting flywheel into a Linea-focused concentrated-liquidity venue.
  • The key control surface is still emissions routing by vote-escrow holders, but the docs also make clear that fee parameters and upgrades remain materially operator-shaped through multisig and timelock structures.
  • Relative to classic ve(3,3) stories, NILE foregrounds anti-dilution more explicitly than many competitors: rebases are not background mechanics here, they are part of the product pitch.
  • Relative to Ramses, NILE appears more as a localized deployment and governance wrapper than a new mechanism. That is still useful analytically because it shows how the same base design gets re-instantiated on another chain with new local rents, operators, and native-pair incentives.

Why this stays in the active corpus

  • It strengthens the Solidly / concentrated-liquidity descendant map beyond the better-known Optimism and Arbitrum cases.
  • It helps compare where governance rent sits when a CLMM is paired with vote-escrow emissions, adjustable fees, and timelocked but upgradeable operator control.
  • It is a good intermediate case between generic CLMMs and the more mutated x(3,3) systems like Ramses and Shadow.

Graph View