NILE

  • Name: NILE
  • URL: https://nile.build
  • Category: concentrated-liquidity ve(3,3) DEX / gauge marketplace / Linea liquidity-routing layer
  • Tags: ethereum-ecosystem
  • Summary: NILE is a Linea fork of the Ramses / Solidly emissions machine, not a new category. The useful read is where the fork keeps practical authority: timelocked upgrades, multisig-controlled fee policy, weekly emissions routing, and whatever wrapper or locker path becomes the default route into veNILE.
  • What it does:
    • Runs a concentrated-liquidity DEX on Linea with volatile and correlated pools
    • Lets users lock into veNILE ERC-721 positions that vote on gauge emissions for LP pairs
    • Pays veNILE voters through vote bribes and swap-fee capture tied to the pools they back
    • Uses rebases as explicit anti-dilution protection for vote-escrow holders
    • Maintains a timelocked proxy-upgrade structure rather than immediate immutability, with Discord/onchain visibility emphasized in docs
    • Inherits architecture and audit posture from RAMSES as an authorized fork rather than presenting itself as a wholly new primitive
  • Key claims:
    • The docs homepage says NILE is “The Next Generation of Concentrated Liquidity” and calls it a sister fork to RAMSES that inherits a proprietary concentrated-liquidity ve(3,3) implementation for Linea
    • The veNILE page says vote-escrow positions are ERC-721 veNFTs that can vote on gauge emissions, earn vote bribes and swap fees, transfer or merge positions, and receive dilution-protection rebases
    • The voting docs make emissions routing the central control surface: LP pairs receive weekly emissions in proportion to their share of total epoch votes
    • The swap-fee docs say standard volatile and correlated pools start at 0.25% and 0.01% respectively, while the native NILE/wETH pair starts at 2% specifically to further incentivize protocol-aligned native liquidity
    • That same fee page says fees are adjustable by the NILE multisig and can range materially higher under volatility, which means fee policy remains a governance / operator control surface rather than a fixed market rule
    • The dilution-protection docs say veNILE holders initially receive a 25% weekly anti-dilution rebase that increases by 1% each epoch until a 50% cap, showing that anti-dilution is not a side feature but a headline part of the tokenomics story
    • The proxy-contracts page explicitly argues that Solidly-style systems are too complex and vulnerability-prone to freeze immediately, and says upgrades must pass through a timelock with public notification hooks; that matters because NILE openly trades immutability for patchability and operator reassurance
    • The formal-audits page says NILE is an authorized fork of RAMSES and inherits RAMSES security work, including a yAudit review of the V2/BUSL-protected codebase, reinforcing that NILE should be read as a descendant implementation with localized governance and operational choices
  • Whitepaper: No canonical standalone whitepaper or litepaper surfaced in this pass. The strongest primary materials were the official docs on protocol overview, veNILE, voting, fees, rebases, proxy/timelock rationale, and inherited audits; see ../whitepapers/nile-primary-sources-2026-05-07.md.
  • Sources:

Internal linkages

  • Keep this note pointed upward: ramses, velodrome, and aerodrome.
  • Useful cut: NILE is a localized gauge-market fork with timelocked admin, not a new emissions primitive.

Control surface

  • Practical authority sits in fee-setting, upgrade timing, gauge emissions routing, and whichever locker or wrapper path becomes the default route into veNILE.

  • Read NILE as a regional fork with admin levers, not a category anchor.

  • Last reviewed: 2026-06-12 UTC