Product

Changelog

What shipped, release by release.

32 releases · since Oct 6, 2026

v0.11.0

Latest release

The price–oracle deviation detector is retired, and the API and its database hold up better under load.

Fixes

  • The Privacy policy now lists everything our technical logs hold, the method and a request identifier included, and says we keep a client's own creation and revocation dates and copy readings of its call counters; the Terms say the API is served on a key we issue.
  • The price–oracle deviation detector is retired, with every signal it published: it flagged a pool's lasting gap to the market rather than a change, and made up nine signals in ten.
Technical details (4)
  • yog-signals drops its SIGNALS_PRICE_DEVIATION_* settings, and the stale, no_decoder and undecodable reasons of yog_signals_skipped_total.
  • The ingestion alarm fails its Healthchecks.io check once the ingestion has been delayed (2 min without a new event) instead of stale (15 min), within 7 min of its last event: a shorter outage was never signalled. Under INGEST_SCOPE=pools, a lull longer than 2 min fails it too.
  • Postgres gets 256 MB of shared memory instead of Docker's 64 MB default: parallel reads of the enrichment daemon no longer fail when they start together.
  • The API no longer rebuilds its routes for every connection: a live stream costs about 20 KiB instead of 235, and a request on a fresh connection answers several times faster.

v0.10.0

The API now takes a key: apart from the service status and the announcements, every route answers only a client we issued a key to.

Features

  • Every API route but the service status (/api/ingestion, /api/network, /api/windows) and /api/announcements now requires an API key, sent as Authorization: Bearer — the live stream, a ticket drawn from one; a call without one, or with a key that opens nothing, gets a 401.
  • The developers page explorer takes your API key, kept in your browser's memory and cleared on reload, and opens the live stream with it.
  • The Terms and the Privacy policy cover API keys: what a key holder agrees to, and what we keep about a client.

Fixes

  • After a cut of its live connection, the signals feed marks where it resumed, instead of fetching the signals it may have missed.
Technical details (3)
  • The live stream opens with a single-use ticket, issued for a key by POST /api/auth/tickets and valid 30 s, sent as Authorization: Bearer; a call without a ticket is refused.
  • The API exposes Prometheus metrics, its calls counted by client and route.
  • After a cut of the gRPC stream, the indexer resubscribes live instead of replaying from its last slot: a replay could fall behind the chain for good. A cut now leaves a short unobserved slot range; yog_indexer_grpc_resume_marks_abandoned_total is removed.

v0.9.0

The live feed now carries the on-chain activity, not only the signals, and a page whose live connection is refused reopens it by itself.

Features

  • In advanced mode, the Overview and the DAMM v2 Live activity tab show the on-chain events as they arrive: liquidity changes, pool creations, position changes, fee and reward claims, reward and pool changes.

Fixes

  • A page whose live connection is refused, when the server is full or restarting, reopens it by itself and fills the gap, instead of staying frozen until it is reloaded.
Technical details (8)
  • The live stream moves to /api/live, for all protocols, and /api/live/protocols/{protocol}, for one; its topics are the signals and the eight on-chain event collections other than swaps. /api/signals/stream is removed: listen on /api/live?topics=signals instead.
  • The on-chain event collections and their live items embed the pool's token pair.
  • A page holds one connection to the live stream, whatever the number of feeds it shows.
  • An embedded token without metadata now says decimals: null instead of 0: a client must handle null.
  • The three swap lists announce only the windows they serve: 24h at the root and under a protocol, 24h and 7d under a pool. A window they refuse gets a 400 whose text names the ones they serve.
  • The oracle-deviation detector counts a DAMM v2 price that does not decode as undecodable, not no_decoder; a price below decimal precision can no longer raise a Critical signal at a spot price of 0.
  • A panic of the indexer's slot-range writer stops the indexer instead of going unnoticed.
  • A green deployment removes the images it left without a name.

v0.8.0

Internal improvements only.

Technical details (4)
  • Each gRPC ingestion session records the slots it received for good, with the chain's time at each end (observed_slot_ranges); the ranges nobody watched are their complement, read in unobserved_slot_ranges.
  • A database connection is kept for that writer: the indexer persists with 8 tasks instead of 9 on a pool of 10.
  • Tests now cover the event decoder's failure paths, the signal engine's cycle and settings, the alert pings, the token cursors, the transaction processing, the context's HTTP clients and the live signal stream.
  • pulldown-cmark, a build dependency of the gRPC code, moves to 0.13.6 (RUSTSEC-2026-0433).

v0.7.2

Compressing old data during a database backup no longer stops the dashboard from reading for several minutes.

Fixes

  • The Live indicator keeps answering when a compression of old data crosses a backup.
  • The TVL curve no longer shows four false drops between 27 and 31 October, the lowest to $31.93M: those hours are removed.
Technical details (1)
  • TimescaleDB's jobs give up on a lock after 3 s and are retried, instead of queueing every read of the chunk behind them for as long as the pg_dump lasts.

v0.7.1

An hour of TVL no longer reads up to 30 % too low because a price went unwritten for a few minutes.

Fixes

  • Motionless prices are rewritten in time, so an hourly TVL reading no longer loses the side of a pool whose token did not move.
Technical details (1)
  • The price worker asks tokens at a cadence set by their class: every round, one in three below 10 $ held, one in 105 for a token still unpriced an hour after we met it. A round asks far fewer tokens.

v0.7.0

The API now says what the dashboard used to decide on its own; the figures on screen stay the same.

Features

  • The TVL tile says when its figure was read whenever it has no change to show.

Fixes

  • Over 7D, the liquidity chart no longer draws a partial bar at the edge of what it covers.
Technical details (8)
  • GET /api/windows: every window's bounds, whether it is open, when it opens and whether it runs late. The measures carry open, opensAt and late too, and rotation-runs/series its splitSince.
  • swaps/totals, tvl/totals and pool-creations/totals gain a total across protocols, swaps/series a total per bar, swaps/totals the window before it (previous) and /api/protocols the pools seen.
  • GET …/liquidity-turnover/totals, at the root and under a protocol: the window's volume over the last TVL reading.
  • Every series says its interval: 6h is the default over 7d, 1d over 30d. tvl/totals answers over 1h with the last reading alone, and the measures say what their coverage counts (coverageUnit).
  • Each signal says what its value counts (valueUnit) and, on a flow imbalance, which token its swaps mostly take from the pool (leansToward).
  • The dashboard no longer decides anything about the data: when a figure is available, how figures combine and what a signal's value means are read from the API, so any client publishes the same figures.
  • A named list ranks its rows before it names the page's, so a list read cold stays fast.
  • The observation key's health counts the WARN and ERROR of the daemons, which log in JSON.

v0.6.0

The Overview and the DAMM v2 page show the last hour, in 5-minute bars.

Features

  • 1H in the Overview's period selector: the rolling hour through the last 5-minute tranche measured, in twelve 5-minute bars, with its volume, fees, swaps, active and born pools, top tokens and the change on the hour before. The TVL shows its last reading, without a change: it is a stock, not a flow.
  • Removed: every …/hourly and …/daily route. A series is now …/series?interval=, the same rows by bucket — 1h an hour, 1d the 24 hours ending at asOf — on the swaps (root, protocol, pool), the pool creations, the liquidity moves and the rotation runs; the TVL's readings are …/tvl/series?interval=1h.
  • 1H on the DAMM v2 page: every tab reads the last hour in 5-minute bars. The TVL, read once an hour, draws no curve over it and says so; the positions' life cycle now follows the chosen period, in one column.
  • The rotation runs' stats on the DAMM v2 page: the runs still in progress show over every period, and the share seen in the first hour is read over the runs whose first hour ended before the period did — greyed over 1H, where none did.
Technical details (4)
  • window=1h on swaps/totals (offset=1h), swaps/by-token, pool-creations/totals and rotation-runs/totals, refused (400) elsewhere; new …/swaps/series and …/pool-creations/series with interval=5m|1h|1d, 5m over window=1h only. Over the last hour, poolHours count pool tranches. Migration 047 grants analytic_pool_5min to yog_api.
  • Every measure is read in …/totals and …/series over window=1h|24h|7d|30d, interval=5m over 1h only: the swaps of a pool, the liquidity moves, the rotation runs, the position changes and both claims join the swaps and the pool creations; position-changes, position-fee-claims and reward-claims gain their series. The TVL (read once an hour) and the pools discovered (measured over a day, a week and a month) are the two exceptions. The same error gives the same 400 message on every route.
  • window=1h on the liquidity-moves and rotation-runs lists, under a protocol and under a pool: the moves and the runs started in the last hour through the last tranche written.
  • rotation-runs/totals: firstHourVolumeUsd gives way to a firstHour block — the runs whose first hour ended before the window did, their volume and its part in that hour — null while none did, always over window=1h.

v0.5.2

Volume and fees are no longer valued at a token's market price that our pools' trades contradict.

Fixes

  • A token whose market price is more than ten times the highest price our pools traded it at over 7 days no longer values volume, fees, liquidity moves or claims either: its swaps are valued by the other token of the pool, and in a move or a claim it counts 0 beside a valued token, or leaves it unvalued alone. Over the week before, it would have corrected about $28,000 of volume.
Technical details (1)
  • yog_market_believed is the one rule for a quote our pools contradict: token_stock_price holds a stock to it, and yog-analytic a flow when it writes it — the tranches, the moves of pools that did not swap, the rewards outside their pool. An anchor so contradicted falls to what its pool traded and its partner values the swaps; it witnesses no ceiling. yog_price_asof stays the raw quote, so history never moves with a ceiling. Migration 046.

v0.5.1

The TVL no longer believes a token's market price that our pools' trades contradict.

Fixes

  • The TVL of DAMM v2 read about $554 million instead of about $51 million from 06:55 UTC on 29 October: one token, quoted 177,000 times its price of the day before, counted its whole reserve in 14 pools at that price. A token now counts 0 in the TVL when its market price is more than ten times the highest price our pools traded it at over 7 days; a token none of our pools traded keeps its price. The hours measured under that price are removed from the series.
Technical details (1)
  • token_stock_price is the price a stock is valued at: the market price unless more than yog_market_over_pool_max() (10) times the token's ceiling, the highest price the trades of its pools implied over yog_pool_witness_window() (7 days), a trade paying less than yog_pool_witness_min_usd() ($1) for it witnessing nothing. Each tranche writes what its trade implied for each token (pool_a_usd, pool_b_usd), each yog-analytic cycle keeps the ceilings (analytic_token_pool_ceilings); pool_current_tvl, and so the TVL, its discovered part, a pool's state and tvl_drain, read it. Migration 045.

v0.5.0

DAMM v2 has two new tabs: Fees, where its fees go and what the LPs take back, and Pools & positions, the pools being born and the positions' life cycle. The dashboard says it is in beta.

Features

  • The Fees tab of DAMM v2: the period's fees by destination — the LPs, the protocol, the referral — with each one's amount and share, and the fees per bar stacked by destination, the bar under the pointer detailed under the chart.
  • Beside it, what the LPs take back: the fees and the rewards their positions claimed over the period, valued, with the addresses that claimed them. Measured from this release on.
  • The Pools & positions tab of DAMM v2: the pools born over the period, bar by bar, and the five whose first deposit is worth the most, with their pair, creator, the lock their birth puts on a position — permanent, vesting or none — and age.
  • In the advanced mode, the positions' life cycle on DAMM v2 over 24 hours and 7 days: positions opened, vesting and permanent locks, positions split and closed, and the distinct active LPs.
  • The dashboard says it is in beta: a badge under the name in the menu, and a banner on every page warning that the figures may be incomplete or wrong, with a link to report an error. "Got it" hides the banner for 30 days.
Technical details (7)
  • yog-analytic values each claim of a position's fees or rewards once, at its pool's price in the tranche as a liquidity move (one shared function, yog_pool_amounts_usd), a reward outside its pool at its market price; /api/protocols/{protocol}/position-fee-claims/totals and /reward-claims/totals serve their totals. Migration 042.
  • /api/tvl/totals and /api/protocols/{protocol}/tvl/totals serve the TVL's change over the window: the last reading, the one a window before it, the part the pools discovered in the window hold, and the change without it. The dashboard reads its TVL change there instead of pairing three routes itself; the API's README writes the line: a rule that combines several routes is served.
  • /api/protocols/{protocol}/rotation-runs/hourly and /daily serve each bar's volume split by the runs — volumeUsd, now every swap of the bar, inRunsUsd and outsideRunsUsd — and the Volume tab reads that one route instead of matching it with swaps/hourly.
  • /api/protocols/{protocol}/liquidity-moves and /api/pools/{pool}/liquidity-moves take ?kind=create|add|remove to keep one kind of move; the cursor carries it.
  • yog-analytic notes the lock each liquidity move's transaction puts on a position — permanent, vesting or none — served as lock on liquidity-moves, null for a move valued before it was measured. Migration 043.
  • /api/protocols/{protocol}/position-changes/totals serves the positions opened, locked, split and closed over the window, counted by yog-analytic per hour and filled since the first event (migration 044); liquidity-moves/totals carries the distinct owners of the window's moves.
  • The API's OpenAPI contract carries the version it ships in, 0.5.0, and follows each release from now on.

v0.4.0

Over 7 days, the bar charts show 28 bars of 6 hours instead of 7 bars of a day.

Features

  • Over 7 days, the bar charts show 28 bars of 6 hours each, ending at the last complete hour, instead of 7 bars of a day.
Technical details (3)
  • A covered hour without a swap or a pool creation counts 0 in a protocol's series and totals, an hour without a rotation run 0 in the runs' bars, and a pool's swaps count 0 for each hour it did not swap since it was first seen; a missing hour now only means it was not covered.
  • The database stops a query within 10 seconds once the program that asked for it is gone, instead of running it for nobody beside the one asked again.
  • The price series is stored in 1-day chunks, each compressed a day after it closes and rolled up by week, instead of 7-day chunks compressed a week after: about two days of prices stay uncompressed instead of one to two weeks (migration 041).

v0.3.1

The hourly sweep for the tokens without metadata no longer compares each one to the whole table.

Fixes

  • The hourly sweep for the mints without metadata reads them in a tenth of a second on a copy of production, instead of more than two minutes; while it ran, the database slowed down and some API requests failed.

v0.3.0

The API serves the fee parameters of DAMM v2 pools, refuses a query key a route does not take, and no longer fails on very large amounts.

Fixes

  • The Meteora and Raydium logos of the menu fit their box again.
Technical details (6)
  • The fee parameters of a DAMM v2 pool's creation and of an operator's fee update, on pool-creations and pool-changes: the base fee by its schedule (time, market cap or rate limiter, linear or exponential), the compounding share and the dynamic fee. Each state is named, an unchanged field included; fees is null only where the stored bytes do not decode, and the indexer counts those it receives (yog_indexer_fee_parameters_undecodable_total).
  • A page of signals filtered by protocol or by severity reads only what can fill it, compressed chunks included, through two new indexes (migration 040).
  • TimescaleDB 2.31.0.
  • Changed: a query key a route does not take is refused (400, naming the key) on every API route, instead of being ignored — /api/swaps/totals?protocol=… used to answer with every protocol.
  • A page of pool creations, liquidity changes or position changes no longer fails (500) when one of its amounts ends in sixteen zeros or more.
  • yog-signals stops within the grace every daemon has, and names a detector that outlives it.

v0.2.0

DAMM v2 has its own page and two tabs: its liquidity, and where its volume comes from — rotation runs, or the rest.

Features

  • A page for Meteora DAMM v2, in the menu: its TVL, volume, fees and active pools over the period you choose, the same figures as its row on the Overview, with the fees' effective rate and, in the advanced mode, the protocol's share.
  • Its first tab, Liquidity: the TVL hour by hour on a tight axis, the liquidity deposited when pools are created and added above it, removed below, per hour or per day, and in the advanced mode the largest moves of the period with their owner.
  • Each liquidity move is valued once, at its pool's price, never above what the pool traded: a deposit of a token the market overprices is worth what the pool would pay for it, and a token without a market price counts 0, as in the TVL. Liquidity is measured from this release on, so the 24-hour figures fill in over a day and the 7-day ones over a week.
  • Its second tab, Volume: each hour or day of volume split between rotation runs and the rest. A rotation run is a stretch of 5-minute slices in which a pool's SOL, USDC or USDT side (both its sides if it has none or two) changes hands at least once, no more than 30 minutes apart — most often a pool born within the minute that trades thousands of balanced swaps before its liquidity leaves. Under the chart, the period's split, or the hour's or the day's under the pointer; beside it, the runs of the period, how long they last and how much of their volume their first hour holds; below, the largest runs, named by their tokens. The published volume does not change.
  • Rotation runs are measured from this release on: a bar they do not cover whole keeps its volume, unsplit, in a neutral tint; the 24-hour figures fill in over a day and the 7-day ones over a week.
  • A green dot beside DAMM v2 in the menu while the ingestion is live, and its page in the sitemap.
Technical details (3)
  • yog-analytic writes each liquidity move into analytic_liquidity_moves and their sums per protocol and hour (migration 035), and each tranche's rotation into analytic_pool_5min, and the rotation runs drawn from it into analytic_rotation_runs and analytic_rotation_run_hours (migrations 036 and 039).
  • The API follows its route rules: the on-chain collections at /api and under /api/protocols/{protocol}, and all but pool-creations under /api/pools/{pool} (swaps, liquidity-changes, pool-creations, position-changes, position-fee-claims, protocol-fee-claims, reward-claims, reward-changes, pool-changes); the measures yog-analytic computes — swaps at /api, under a protocol and under a pool, pool-creations at /api and under a protocol, liquidity-moves and rotation-runs under a protocol (totals, hourly, daily), tvl and its hourly readings, pool-discoveries — and the pages of liquidity-moves and rotation-runs under a protocol and a pool; pools, tokens and their prices; the signals of one protocol or one pool; /api/announcements with ?status=. Migrations 037 and 038 open the pool facts to the API and index the business reads.
  • Changed: /api/protocols is now a page with a cursor, its entries under items. Removed, their readers moved: /api/protocols/activity and its series, /api/protocols/tvl and its hourly series, /api/tokens/activity (now /api/swaps/by-token), /api/announcements/active (now /api/announcements?status=open), and the pool filter of /api/signals (now /api/pools/{pool}/signals); /api/signals refuses a query key it does not take.

v0.1.16

The TVL now says what it counts: no pool drops out because one of its tokens has no price, and its change no longer takes a pool seen for the first time for a deposit.

Fixes

  • A pool with one token without a market price dropped out of the TVL whole, with the value of its other side. That side now counts, the token without a price counting 0, as Meteora does.
  • A dormant pool touched for the first time brought its whole stock into the TVL, and its change showed it as a deposit. The change now leaves out the pools discovered during the period, and says how much they hold; a pool born during the period still counts as a deposit.
  • The TVL's tooltip says what it counts: the pools observed since 1 October 2026, at Jupiter prices under 15 minutes old, a token without a price at 0 — and what it does not measure, the liquidity that can be traded.
  • The TVL series starts again: the hours measured under the former price rule are deleted. The TVL itself shows "—" until the first hour measured after this release has closed, about an hour, and its change stays hidden until the new series covers the period.
Technical details (1)
  • The tvl_drain detector keeps reading a pool's TVL only when both of its sides are priced (pool_current_tvl.tvl_complete_usd): a drain over half a pool would be overstated.

v0.1.15

Search engines can now find the Overview, and the indexer no longer skips transactions when its stream provider turns a reconnection down for a reason the request did not cause.

Features

  • The Overview is listed in the sitemap, in English and in French, so search engines can index it.

Fixes

  • When the stream provider refused a reconnection over an expired key, a quota or an incident on its side, the indexer resumed from the latest block, and the transactions in between were never indexed. It now asks again for the block where it stopped, and gives that point up only when the provider says the request itself is at fault.
Technical details (3)
  • Production can be read by a key that can do nothing else: the state of each service, the daemons' counters and a few counts from the database, as a user with no rights of its own and a sudo rule limited to three exact commands.
  • Every resume point given up is logged and counted (yog_indexer_grpc_resume_marks_abandoned_total), labelled by the gRPC code that refused it.
  • tokio 1.54.1: 1.54.0 was withdrawn from crates.io.

v0.1.14

The volume counts again only what changed hands: a nearly empty pool could publish hundreds of millions of dollars for a few cents.

Fixes

  • A token without a market price was valued at its pool's price after the last swap, which a single swap can push to any value when the pool is nearly empty: one pool published $801 million of volume for three swaps worth two cents, and the 24-hour volume read over a billion dollars. Each direction of a trade is now worth what changed hands on the side of the token that has a market price, usually SOL, fee included as Meteora counts it: a purchase, the SOL the buyer paid; a sale, the SOL the seller received plus the fee the pool took.
  • A fee taken in a token without a market price is now worth its share of the trade that paid it, no longer that token's average price over five minutes, which could overstate it after a crash.
  • The volume, fees and most traded tokens of the past days are computed again under these rules. For about three hours after this update, the Overview shows figures that stop at an earlier hour, announced by its band, and the swap flow signal waits while they catch up.
Technical details (1)
  • The analytic writer prices a token in its pool at the rate its five-minute tranche traded at, no longer at the pool's mid price; its five-minute aggregate, recreated, carries the fee of each direction; and it writes the active pools of every hour it freezes.

v0.1.13

Internal improvements only.

Technical details (2)
  • Backups had stopped: a dump over 8.39 GB was refused by the bucket at its 1,001st part. Parts are now 32 MiB, so a dump of up to 33.5 GB is stored.
  • TimescaleDB 2.30.2, Rust 1.99.1, Node 26, Yellowstone gRPC schema 14 and the dependencies' updates.

v0.1.12

The Overview now says which protocol its figures come from, over 24 hours or 7 days, with the most traded tokens and an advanced mode; a token sold off within the hour no longer inflates the volume; and the price service gets the memory it needs.

Features

  • The Overview is rebuilt: TVL, volume, fees and active pools, activity protocol by protocol (DAMM v2 observed, DLMM, Raydium and Orca to come), volume by hour or by day, the most traded tokens and the latest signals. A period selector switches the whole page between 24 hours and 7 days; 30 days opens once enough data is measured.
  • An advanced mode, off by default, puts more data on the same screen without making the page longer: swaps and their rate per second, turnover (the period's volume divided by the TVL), fees and active pools by protocol, and fees by hour or by day under the volume. The choice is remembered by a cookie, declared in the privacy policy.
  • A volume or fee figure that leaves out hours it could not value shows the share it does cover, such as "97%", rounded down so that a partial figure never reads 100%.
  • Every figure of the Overview stops at the last complete hour, the same for the whole page, up to about 70 minutes behind. A period or a change that would compare with hours not yet measured shows "—" and says why, rather than a smaller number; figures stopped over two hours back are announced by a band at the top of the page.

Fixes

  • A token sold off within an hour used to be valued at its market price from before the fall: one pool could publish $14.5 million of volume for less than a dollar actually received. Each token is now priced every five minutes, and never above what its own pool pays for it: in each pool, the token traded in the most pools keeps its market price, and the other is bounded by the pool's rate.
  • The hourly volume and fees now start about a week back: older hours could not be valued again under the new rule, and are dropped rather than mixed with it. For about three hours after this update, the 24-hour volume shows as unavailable while it is rebuilt.
  • The swap flow signal reads the same valuation, about fifteen minutes later than before.
  • The service that fetches token prices and names gets 64 MB of memory instead of 32: it needed about 35, so it lived on swap and was slowed down during its calls to the price providers.
Technical details (2)
  • The API serves the protocols' activity, TVL and their hourly and daily series over a window (/api/protocols/…), and the tokens by volume (/api/tokens/activity). /api/stats, which only the old Overview read, is removed.
  • The analytic writer prices each pool's two tokens once per five-minute tranche, keeps the market price beside the price it publishes, and values the swaps from it; no reader values a swap anymore.

v0.1.11

Shared links now show a preview, every API error answers in one format, deploying a new version no longer slows the site down, and the price gap signal no longer floods the feed with shallow pools.

Features

  • Shared links and search engines now get a title, a description and a preview image, in each page's language, and a sitemap lists the site's pages in both languages.

Fixes

  • A new version is built on GitHub when it is tagged, and the server only downloads it: it used to compile it itself, for 13 to 41 minutes, while still serving the site and the API, which slowed both down.
  • The signal comparing a pool's price with the market price only looks at pools holding at least $10,000: below that, a pool's price strays from the market by nature, and those pools made 98% of all signals, about 12,700 a day.
  • The API now answers all its errors in one format, RFC 9457 Problem Details: a query or path it cannot read (an unknown severity, a non-numeric limit), an unknown route (404) and a wrong method (405) used to get plain text or an empty body.
  • An empty pool or cursor parameter on /api/signals (?pool=) is now refused with a 400 naming the parameter: it used to be read as absent and return the unfiltered feed.
Technical details (1)
  • The signal engine reads fewer pools at each round: the price gap signal only those above its value floor, instead of every pool ever priced, and the swap flow signal only the active pools above its volume floor, plus those it cannot value, to count them. Its memory no longer follows every pool discovered.

v0.1.10

Internal improvements only.

Technical details (6)
  • The pool registry drops its index on the last time a pool was seen, 345 MB that no query read since the pool list went away: refreshing that time on every event no longer has to write into every index of the table.
  • The hourly volume and fees are summed from five-minute slices refreshed every five minutes, instead of re-reading every swap of the open hour every five minutes: that read grew through the hour, up to a minute and a half, close to the two minutes after which the database cancels a query.
  • New tokens get their names looking only at the pools discovered in the last hour, instead of re-reading every pool known every ten seconds; every pool is still swept once an hour, for the tokens learned late.
  • The signal engine gets 64 MB of memory instead of 32: it needed about 40, so it lived on swap, reading back what it had just been made to set aside.
  • Two transactions discovering the same new pool at the same moment no longer make one of them fail, or deadlock in the database: the pool is recorded on its first event instead of its next one, and a failure that remains is now counted instead of only logged.
  • An ordinary instruction sent to the DAMM v2 program with few or no arguments is no longer counted as an event the indexer failed to read: nothing was lost, but the failure counter, the one that would show a misread of the stream, was never at zero. A truncated event is still counted, and so is data too short to be any instruction.

v0.1.9

The dashboard drops its pool pages, which timed out in production, ahead of the pages built around protocols and tokens, and the DAMM v2 TVL no longer drops to nothing one hour in two.

Fixes

  • The pool list, the pool pages and the Watchlist are gone: their data timed out in production. Their old addresses answer 404.
  • The Overview no longer shows the Top pools block, which failed to load.
  • A signal card shows its pool's pair without linking to a pool page; hovering it shows the pool address.
  • The About page no longer promises to watch pools or query their history.
  • The DAMM v2 TVL no longer drops to nothing, or to a third, about one hour in two.
Technical details (2)
  • The API drops its eight /api/pools routes and every read only they used; the contract and the dashboard's schemas are regenerated.
  • The price worker asks Jupiter only for the tokens one of our pools moved, or that Jupiter priced, in the last 24 hours — about 20,000 instead of 95,000 — so a price round no longer outlasts the 15-minute freshness bound.

v0.1.8

The site's About, Support us, changelog and legal pages take the dashboard's look, and the site no longer scrolls sideways on small phones.

Features

  • The changelog shows one block per release, with an All / Features / Fixes filter. Changes that only concern the code are folded under the technical details.
  • The About page is rebuilt in five numbered sections. Its list of covered protocols follows the dashboard menu: DAMM v2 observed; DLMM, Raydium and Orca soon.
  • Support us lists three free ways to help (a star on GitHub, a share on X or LinkedIn, feedback) and a Solana donation address with a Copy button.
  • The privacy policy, legal notice and terms share one layout: tabs between the three, the update date, a table of contents and numbered sections. Their texts are unchanged, except as noted below.

Fixes

  • Support us no longer offers GitHub Sponsors: its button led to a GitHub profile, and no sponsorship exists. The privacy policy no longer mentions it either.
  • The About page now says how Yog-Scope works: a continuous stream from a Solana node rather than a WebSocket connection, one decoder per protocol, and tens of thousands of pools rather than hundreds.
  • On screens narrower than 375 px, the site's pages no longer scroll sideways.
  • Release dates in the changelog no longer show the previous day west of UTC.
Technical details (1)
  • The database gets more memory: its daily compression no longer slows the whole database down, indexing included.

v0.1.7

The dashboard frame no longer waits for its data, and the site's home page, header and footer take the dashboard's look.

Features

  • The dashboard menu marks the pages still to come as "Soon" instead of a lock, which read as a paid feature. Its new Preferences hold the language switch, and up to 720 px the menu becomes a drawer.
  • A live indicator in the Overview header tells how fresh our indexing is (Live, Delayed, Stale or Offline). A click opens the last event, the Solana slot and the RPC latency, which leave the menu.
  • The site's home page shows an illustrated preview of the dashboard and how Yog-Scope works, in five steps.
  • The site's header and footer are rebuilt, with an "Open the dashboard" button, the version and a FR | EN switch that stays on the same page. The site takes the dashboard's colours and the Geist typeface, and its logos are vector images.

Fixes

  • The dashboard no longer waits for any data before it shows. The announcements and each Overview block arrive on their own, and a block that fails shows its own error instead of an error page.
Technical details (1)
  • The site and the API are served by a front web server shared with other sites on the same machine. Nothing changes for visitors.

v0.1.6

Pages no longer fail on a token logo that is not a link or on a mistyped pool address, and the network status is split between the Solana network and our own indexing.

Features

  • The network status is split in two: /api/network gives the Solana network as our probe sees it (slot and latency), /api/ingestion gives how fresh our own indexing is. /api/network/status is gone. In the dashboard, the network panel loads each half on its own, so one that is slow or down no longer blanks the other.
  • The current state of a pool gives the dollar value of each of its two sides, under the same price-age limit as its TVL. Tokens embedded in a pool or a signal no longer carry a price, which had no age limit: the pool page's composition chart now uses the server's values, and is hidden when a side's price is missing or more than 15 minutes old; the signal card no longer shows a line of token prices.

Fixes

  • A token logo that is not an http or https link is now dropped, and the page shows the token's initial instead. A logo that was not a link at all used to make the whole page fail to load (pool list, pool page, signals) or the Overview's top-pools block show an error.
  • A pool page opened with a malformed or truncated address now shows "Pool not found". It used to fail with a server error, or show an error with a Retry button that could never work.
Technical details (1)
  • A security update of the TLS library used by the backend services (rustls 0.23.46).

v0.1.5

The Overview's figures load again: they now read the values computed once per hour instead of being recomputed at each request.

Features

  • A new Yog-Scope logo and new browser icons, on the site and in the dashboard.

Fixes

  • The Overview's 24h volume, fees and total TVL now read the hourly values introduced in v0.1.4, instead of revaluing a full day of swaps at each request, which had made them fail to load. A figure the hourly service has not caught up with shows as — rather than as a partial sum.
Technical details (2)
  • Valuing the TVL of every pool now reads each token's latest price from a table that keeps one row per token, instead of searching the whole price history twice per pool. It was the slowest step of the hourly service.
  • The price-deviation signal reads its prices from the same table, instead of searching the whole price history twice per pool. It was the slowest step of the signal service.

v0.1.4

Internal improvements only.

Technical details (2)
  • A new background service values each pool's swaps in dollars once per hour, keeps the result, and freezes each hour ten minutes after it closes. Nothing reads these figures yet: the Overview's 24h volume, fees and TVL, which are still recomputed from every swap at each request and currently fail to load, will move to them once they cover a full day.
  • The backup service now reads the application's data schema by schema, instead of through PostgreSQL's built-in read-all role, which reached beyond what a backup needs.

v0.1.3

The dashboard is now organised by protocol, and raw swaps are kept for a week so the database stays within its disk.

Features

  • The dashboard menu is organised by protocol: Overview, then Meteora DAMM v2, Meteora DLMM, Raydium and Orca, then Token. Only Overview is open for now; the other entries carry a lock until their page exists. The pool list, signals and watchlist pages are no longer in the menu.
  • A new look for the dashboard frame: one colour per role, and the Geist typeface.

Fixes

  • Raw swap events are kept for 7 days instead of 30, and compressed one day after their day ends instead of seven: since every DAMM v2 pool is observed, they were outgrowing the disk. The hourly swap history that charts and analytics read is unaffected and still kept in full; a pool's list of individual swaps now goes back 7 days.
Technical details (1)
  • Next.js is updated to 16.3.8, following five advisories published on 7 October. None of them applied to this site's configuration.

v0.1.2

More regular price sampling: Jupiter requests are spaced instead of sent in bursts, and a restart keeps the prices a round had already received.

Fixes

  • Requests to Jupiter are spaced under the configured rate limit (60 per minute by default) instead of sent in bursts, which Jupiter refused (HTTP 429) and which left tokens that have a price without one, round after round.
Technical details (2)
  • A token Jupiter answers without a price is asked again less and less often — up to every 15 minutes at the default 30-second cadence — instead of at every round; the next price it gets puts it back on every round. A request in which none of its 50 tokens gets a price is read as a failed answer, and changes no token's turn.
  • Stopping the enrichment service in the middle of a pricing round keeps the prices already received, instead of losing the whole round.

v0.1.1

Internal improvements only.

Technical details (1)
  • sharp, the image library behind the dashboard, is updated to 0.35.5 for a vulnerability in the librsvg it bundles (CVE-2026-96889). Nothing else changes.

v0.1.0

The first production release: a real-time observer of Meteora DAMM v2 on Solana, with a signal engine that surfaces risk across every observed pool.

Features

  • Real-time indexing of Meteora DAMM v2 events — swaps, liquidity, positions, fee updates and pool lifecycle — decoded from on-chain Anchor emissions, for an operator-selected set of pools; the other pools their transactions touch are discovered along the way.
  • Pool pages: composition, spot price decoded from the on-chain sqrt-price, realized-fees analytics with 30-day fee and effective-rate charts, and Swaps, Liquidity and Alerts tabs.
  • Pools list with a fee column and a fee-tier filter, and a watchlist of starred pools, kept in the browser.
  • Overview with global KPIs — total TVL, 24h volume and fees, pools discovered — a top-pools ranking and the latest signals.
  • Signal engine with three risk detectors: flow imbalance, price–oracle deviation, and TVL drain (rug-like liquidity exodus).
  • Live signal feed on /signals — streamed over SSE, with severity × detector filters and per-detector explanations — and a worst-severity indicator on the pools list, with a hover detail.
  • Token enrichment: metadata, USD prices and pool-account backfill, independent from the ingestion path. Jupiter rate-limits (429) are retried with backoff, and every provider call carries a timeout.
  • Operator announcements: a dismissible banner for maintenance, incidents, releases and beta notes, published without a deploy.
  • Dashboard: collapsible sidebar with a network-status panel (Solana slot, RPC latency), metric definitions behind info popovers, an English and French interface, and a privacy notice that lists every processing and transfer.
Technical details (1)
  • Hardened serving: the API bounds its memory, connections and heavy requests — past its limits it turns heavy requests and streams away instead of running out of memory — and the dashboard sends HSTS and a content security policy that blocks framing and limits where it connects.