Market reality · 1 Nov 2026

ENA on Ethereum: how much real on-chain market is there?

Exchange listings, dashboards and token pages show a volume number. This page asks what stands behind it for ENA (Ethena) on Ethereum: how much can actually be sold or bought before the price moves, how much of the trading looks independent, who provides the liquidity, and how much of it we can verify. Everything comes from public chain data and every number can be re-derived.

Ethereum mainnet · trading window 2026-10-25 00:00 → 2026-11-01 00:00 UTC (blocks 26,265,959–26,316,188) · pool state at block 26,318,400 (01 Nov 2026, 07:23 UTC) · token units only (prices in the pools' own quote tokens); no USD, no third-party prices · methodology market-reality/0.1

Why ENA

ENA is a large token with a known team (Ethena Labs), real activity and liquidity spread over several venues on Ethereum: Uniswap v3 and v4, PancakeSwap v3, smaller concentrated-liquidity forks and one venue we do not decode. Our pipeline already collects its main pools, so this page can show both what we verify today and what is still missing. We have no relationship with Ethena Labs.

This week was not ordinary. On 29–30 Oct an address that had received ENA from the wallet labelled “Binance 14” sold it into Uniswap pools (documented block by block in our 29 Oct research page). Those two days carry 94% of the week's ENA volume, so where it matters we also give the numbers for the other five days.

Every section answers five questions: what was observed, where the evidence is, how it was computed, how far it can be trusted, and how to check it yourself.

1. Pool map

Observed

268 pools hold ENA on Ethereum; 66 had swaps in the window. Our verified pipeline already collects 36.8% of the 7-day ENA volume — 94.3% on the five days without the 29–30 Oct sales. The gap is one pool: ENA/WETH 1%, which carried 58.4% of the week's volume, almost all of it on 29–30 Oct, was not pinned in our pipeline during the window, and was added on 1 Nov 2026 as a result of this analysis. With the pools decoded for this report, 99.5% is read from the pools' own Swap events.

Evidence

Pool creation logs on Ethereum that name ENA in an indexed field (Uniswap v2/v3 factories and forks, Uniswap v4 Initialize), blocks 19,000,000–26,318,400; the DexScreener pair list was used only to cross-check that no listed pool was missing. Swaps: the pools' Swap logs in 2026-10-25 00:00 → 2026-11-01 00:00 UTC (blocks 26,265,959–26,316,188); our ClickHouse rows for the verified pools.

Method

Volume = sum of |ENA amount| per Swap event, in ENA units (no USD). Not-supported pools: ENA Transfer logs into + out of the pool.

Trust

Verified pools: our pipeline's 8,015 stored swaps are identical (transaction, log index, both amounts) to the chain's Swap logs in 8,015 of 8,015 cases. Pool-reported: standard event layouts decoded here, not yet receipt-reconciled by the pipeline. Two pools listed by DexScreener (Metric, Supernova) have no creation event that names ENA and were added from that list; pools of that kind that nobody lists, and Curve/Balancer-style vaults, can be missed.

Check it

eth_getLogs with topics[0] = the pool's Swap topic for any pool below; recipe at the end of this section.

202 more pools exist but had no swaps in the window — most are Uniswap v4 pools pairing ENA with tokens that have no other market. Trust labels: verified = collected and receipt-checked by our pipeline; pool-reported = read from the pool's own Swap events for this report (standard layouts), not yet part of the verified pipeline; not supported = an event layout we do not decode, measured here only by ENA Transfer logs.

curl -s https://gateway.tenderly.co/public/mainnet -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_getLogs","params":[{
  "address":"0xc3db44adc1fcdfd5671f555236eae49f4a8eea18",
  "topics":["0xc42079f94a6350d7e6235f29174924f928cc2ac818eb64fed8004e115fbcca67"],
  "fromBlock":"0x190c967","toBlock":"0x1918d9c"}]}' |
python3 -c 'import json,sys; L=json.load(sys.stdin)["result"]; s=lambda h:int(h,16)-(1<<256)*(int(h,16)>=1<<255)
print(len(L), "swaps,", round(sum(abs(s(l["data"][2:66])) for l in L)/1e18), "ENA")'   # amount0 = ENA (token0)
# printed on 01 Nov 2026: 6113 swaps, 309680651 ENA

2. Liquidity depth

Observed

Selling 516,045 ENA moves the exit pools −2%; 1.28 M moves them −5%, 2.52 M −10%. Buying side: 521,916 / 1.31 M / 2.51 M ENA for +2 / +5 / +10%. One pool, ENA/WETH 0.3%, holds 96% of the −2% depth.

Evidence

Pool state at block 26,318,400 (01 Nov 2026, 07:23 UTC): slot0, liquidity, tickBitmap and ticks (v3-style pools), the same through Uniswap's StateView contract for v4 pools, getReserves for v2 pools. Only pools quoted in ETH/WETH, USDC or USDT count as exit depth.

Method

Concentrated liquidity is walked tick by tick: between two initialized ticks the pool behaves like x·y = L² (amount of token0 = L·(1/√P_low − 1/√P_high)), and crossing a tick adds or removes its liquidityNet. The LP fee is added to the input. Routing assumption: the order is split so that every exit pool ends at the same relative price move (what arbitrage would enforce); real routers split less well, so a single-pool sale moves the price more.

Trust

Independent check: Uniswap's QuoterV2 contract simulated the same sales against the live pool code at the same block — see the table below. Depth is a snapshot: liquidity providers can add or withdraw at any time. sENA pools (4.14 M ENA at −2%) are shown but not counted, since sENA is a staking receipt of ENA itself.

Check it

Run check_depth.py (below): it reads the same state from any Ethereum node and asks QuoterV2.

Independent check with Uniswap's QuoterV2

QuoterV2 (0x61ff…b21e) runs the pool's own swap code in a simulated call. We asked it to sell exactly the amount our tick walk computed, in ENA/WETH 0.3%, at block 26,318,400:

Uniswap v4 check (ENA/ETH 0.3%, V4Quoter 0x52f0…1203): selling 9,826 ENA returns 0.804076 ETH; our walk gives 0.804076 ETH. v4 pools add a protocol fee (here 0.05%) to the LP fee; without it the two differed by 0.05%.

"""Standalone check (no dependencies): how much ENA moves the Uniswap v3 ENA/WETH 0.3 % pool price by -2 / -5 / -10 %.

Reads slot0, liquidity, the tick bitmap and every initialized tick within ±1,300 ticks at one block, walks the price
down tick by tick (constant-liquidity math between ticks), then asks Uniswap's QuoterV2 to simulate the -2 % sale.
Usage: python3 check_depth.py [block]
"""
import json
import sys
import urllib.request

RPC = "https://gateway.tenderly.co/public/mainnet"       # any Ethereum node that serves state at the block
POOL = "0xc3db44adc1fcdfd5671f555236eae49f4a8eea18"      # ENA (token0, 18 dec) / WETH (token1, 18 dec), fee 0.3 %, spacing 60
QUOTER = "0x61ffe014ba17989e743c5f6cb21bf9697530b21e"    # Uniswap QuoterV2
ENA, WETH = "57e114b691db790c35207b2e685d4a43181e6061", "c02aaa39b223fe8d0a0e5c4f27ead9083c756cc2"
BLOCK = hex(int(sys.argv[1]) if len(sys.argv) > 1 else 26318400)
op = urllib.request.build_opener(urllib.request.ProxyHandler({}))


def call(to, data):
    body = json.dumps({"jsonrpc": "2.0", "id": 1, "method": "eth_call", "params": [{"to": to, "data": data}, BLOCK]}).encode()
    req = urllib.request.Request(RPC, body, {"Content-Type": "application/json", "User-Agent": "check"})
    return json.load(op.open(req, timeout=60))["result"]


def word(h, i, signed=False):
    v = int(h[2 + 64 * i:2 + 64 * (i + 1)], 16)
    return v - (1 << 256) if signed and v >= 1 << 255 else v


def enc(v):
    return format(v % (1 << 256), "064x")


slot0 = call(POOL, "0x3850c7bd")
s, tick = word(slot0, 0) / 2 ** 96, word(slot0, 1, True)
L = word(call(POOL, "0x1a686502"), 0)
ticks = {}
for w in range(((tick - 1300) // 60) >> 8, (((tick + 1300) // 60) >> 8) + 1):
    bm = word(call(POOL, "0x5339c296" + enc(w)), 0)                     # tickBitmap(int16)
    for bit in range(256):
        t = (w * 256 + bit) * 60
        if bm >> bit & 1 and t <= tick and tick - t <= 1300:
            ticks[t] = word(call(POOL, "0xf30dba93" + enc(t)), 1, True)  # ticks(int24) -> liquidityNet
for level in (0.02, 0.05, 0.10):
    target, cur, liq, ena_in, weth_out = s * (1 - level) ** 0.5, s, L, 0.0, 0.0
    for t in sorted(ticks, reverse=True):                               # cross initialized ticks downwards
        st = 1.0001 ** (t / 2)
        if st <= target:
            break
        ena_in += liq * (1 / st - 1 / cur); weth_out += liq * (cur - st); cur = st; liq -= ticks[t]
    ena_in += liq * (1 / target - 1 / cur); weth_out += liq * (cur - target)
    gross = ena_in / 0.997                                              # the 0.3 % LP fee is charged on the input
    print(f"-{level:.0%}: sell {gross / 1e18:,.0f} ENA -> {weth_out / 1e18:,.4f} WETH")
    if level == 0.02:
        q = call(QUOTER, "0xc6a5026a" + enc(int(ENA, 16)) + enc(int(WETH, 16)) + enc(int(gross)) + enc(3000) + enc(0))
        moved = (word(q, 1) / 2 ** 96) ** 2 / s ** 2 - 1
        print(f"   QuoterV2: {word(q, 0) / 1e18:,.4f} WETH out, pool price after {moved:+.3%}")

-2%: sell 493,764 ENA -> 40.3288 WETH
   QuoterV2: 40.3288 WETH out, pool price after -2.000%
-5%: sell 1,234,629 ENA -> 99.3157 WETH
-10%: sell 2,444,481 ENA -> 191.6334 WETH

3. Organic vs. inflated activity

Observed

1,948 distinct traders made 14,975 swaps (850.86 M ENA gross). The top 10 addresses account for 67.8% of the volume, the largest alone for 25.6%. Our organic estimate is 73.2% of gross volume (60.6% if bot-like cadence is also removed). The week is two different markets: on 29–30 Oct, 94% of the week's volume traded in two days; on the other five days, 49.88 M ENA traded, 97% passed the exclusion rules, but only 14% came from addresses without a bot-like cadence and the top 10 addresses made 91% of it.

Evidence

Every Swap log of the decoded pools in the window and the receipt of each of its 10,823 transactions (sender, called contract, ENA Transfer logs).

Method

Trader = the address whose ENA balance went down (sale) or up (purchase) in that transaction's ENA Transfer logs, never a pool, router or settlement contract; if none qualifies, the transaction sender (tx.from). This is the same rule as our live trader attribution. We do not use the Swap event's sender/recipient, which are usually routers (604 distinct recipients vs 2,342 distinct transaction senders). 87% of swaps were attributed from Transfer logs.

Trust

Patterns are measured, not intent: a wash-like round trip can be a market maker rebalancing, a sandwich-shaped sequence can be coincidence. We exclude only clear shapes, so the organic share is an upper bound: genuinely independent demand can only be lower.

Check it

Swap logs + receipts from any node; the rules are fixed numbers listed below (methodology market-reality/0.1).

Rules (all conservative: a swap is excluded only when the shape is clear)

• Same-transaction round trip (excluded, 225.74 M ENA): one transaction swaps ENA in two or more pools in opposite directions and its net ENA is within 1% of the gross — arbitrage between ENA pools or a route that passes through ENA. 710 transactions.
• Same-block sandwich (excluded, 569,838 ENA): in one block and pool, the same actor (the contract it calls, or its sender) trades before and after another trader's swap in the same direction, the back leg within 20% of the front leg's size. Only the two outer legs are excluded; the trade in the middle is real demand. 14 found.
• Wash-like round trip (excluded, 2.13 M ENA): one trader buys and sells with no more than 25 blocks (~5 minutes) between consecutive swaps, and the run's net ENA is within 2% of its gross. 24 runs by 21 traders.
• Bot-like cadence (flagged, removed only in the strict estimate, 217.03 M ENA by 23 traders): ≥ 50 swaps in 7 days, or ≥ 20 swaps at a regular rhythm (coefficient of variation of the block gaps < 0.5). Arbitrage and market-making bots keep pools in line with other markets, so they are not counted as fake.

Top 10 trader addresses

The largest address, 0x7f9d…15e3, is the ENA seller described in our 29 Oct research page: 217.50 M ENA sold in 20 swaps within about two hours on 29–30 Oct. It counts as organic here — it is a real seller, not a pattern. Most same-transaction round trips (225.74 M ENA, 27% of the week) are contracts that bought ENA in one pool and sold it in another in the same transaction while those sales pushed the pool prices apart; they move prices back into line but add volume without any net demand.

4. Liquidity providers

Observed

252 owners provide the ENA liquidity within ±2% of the price; the largest holds 46.2%, the top 5 71.3%, the top 10 82.1%. 68% of that band sits in positions first funded more than 30 days ago. In the window, 283 deposits added ≈ 125.42 M ENA-equivalent and 158 withdrawals removed ≈ 128.66 M. Almost all of that moved through ENA/WETH 1% on 29–30 Oct: deposits there were mostly WETH (9,823 WETH, 507,747 ENA) and withdrawals mostly ENA (29.79 M ENA, 7,748 WETH) — consistent with liquidity placed below the price that bought the sold ENA. In the main pool, ENA/WETH 0.3%, ≈ 5.65 M ENA-equivalent was added and ≈ 4.61 M withdrawn over the week (137 deposits, 50 withdrawals); positions first funded during the week hold 14% of today's ±2% band.

Evidence

Every Mint/Burn log of the v3-style ENA pools since before the token existed (to block 26,318,400 (01 Nov 2026, 07:23 UTC)); Uniswap v4 ModifyLiquidity logs of the ENA pools; positions(tokenId) and ownerOf(tokenId) on the position managers at the snapshot.

Method

Positions are rebuilt from the pools' own events (owner, tick range, liquidity). For positions held through the v3 PositionManager, the NFT id is read from the IncreaseLiquidity log next to each Mint; its current liquidity and holder come from the PositionManager. Each position's share = the ENA it would absorb or release while the price moves within ±2% (the same walk as the depth section). ENA-equivalent amounts convert the quote side at the pool's own snapshot price.

Trust

Reconstruction check: summing the rebuilt in-range positions reproduces the pool's on-chain liquidity() exactly for 258 of 258 pools (all 47 of 47 with liquidity). Position NFTs: 194 of 194 PositionManager ranges match the NFTs found.

Check it

cast call 0xc36442b4a4522e871399cd717abdd847ab11fe88 "positions(uint256)" <tokenId> --block 26318400 and ownerOf for any position.

Largest withdrawals in the window

Liquidity pull risk, in plain terms: if the largest provider withdrew, the ±2% band would shrink by 46%; if the top five did, by 71%.

5. Hook and pool risk (Uniswap v4)

Observed

222 Uniswap v4 pools pair ENA with another token; 48 of them had swaps in the window (4.3% of the volume). 20 pools use a hook with permission bits set, 16 of them with a swap ReturnDelta bit. None of the hooked pools had a swap in the window: all v4 trading in ENA went through hookless pools (hook address 0x0, no permission bits).

Evidence

The pools' Initialize logs on the PoolManager (0x0000…8a90), which carry the full PoolKey (currencies, fee, tick spacing, hook address); every key was re-hashed to its PoolId.

Method

In Uniswap v4 a hook's permissions are fixed by its address: the lowest 14 bits of the hook address say which callbacks the PoolManager will call. We read those bits; we do not audit the hook's code.

Trust

Exact for the permission set (the PoolManager enforces it). What an enabled hook actually does needs a code review. Many of these pools pair ENA with tokens that have no other market (Pendle SY/PT wrappers, launch tokens); they hold no or little liquidity.

Check it

int(hook_address, 16) & 0x3fff — each set bit is one permission in the table below.

The two …ReturnDelta swap bits matter most for data quality: with them, the Swap event no longer equals what the trader paid or received, so volume read from events can be wrong. None of the ENA pools that traded this week has a hook at all.

6. Anomaly timeline (our existing findings)

What our monitoring flagged for ENA on Ethereum since collection started (2026-10-24 to 2026-11-01). Each finding has an Evidence Card in the app with its baseline, query and ingestion runs.

How to read this: the 29 Oct volume spike and 30 Oct activity spike are the sales described above. The liquidity finding for ENA/sENA 0.05% is one step change on 24 Oct (active liquidity about 9× higher) that the detector reports again on later days against the same baseline; it is a rise, not a withdrawal. The volume declines on 24 and 31 Oct are quiet hours against a busier baseline. Re-detections of the same finding on later runs are collapsed here (19 stored rows, 10 shown).

7. Market reality summary

Not a score and not a valuation: each line is a measured number with its caveat.

What this does and does not say

• It describes on-chain DEX markets on Ethereum only. Centralized exchanges, other chains and OTC trading are outside this view, and for a large token they can be bigger than everything here.
• Depth is a snapshot of one block. Concentrated liquidity can be added or removed in a single transaction.
• “Organic”, “wash-like”, “sandwich” and “bot-like” are pattern labels from fixed rules, not findings about intent or wrongdoing. A different threshold gives a different number; the rules and thresholds are on this page.
• An address is not a person: one trader can use several addresses, and a contract (vault, smart wallet, settlement) can stand for many users.
• Pool discovery relies on creation events that name the token. Pools created by unusual factories, or vaults that do not index token addresses, can be missing; the venue we cannot decode is shown with an upper-bound estimate.
• Amounts are token units; quote-side amounts are in the pool's own quote token (WETH, USDC, USDT). We do not convert to USD.
• WATAM is independent and not affiliated with Ethena Labs, Uniswap, PancakeSwap or any venue named here. This is not investment advice and not a price or value assessment.

Inputs, cache and scripts: commercial-audit/research-data/market-reality/ (collect.py → analyze.py → build_page.py). Data read on 01 Nov 2026 from public Ethereum nodes (Tenderly public gateway, Pocket, dRPC, BlockPI) and our ClickHouse store.