Telegram RegisterThe public register of Telegram
Telegram profile photo for 1inch

Channel

1inch

@OneInchNetworkNews

Verified by Telegram

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry

17,439subscribers

-343 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001313539545
TypeChannel
Username@OneInchNetworkNews
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live26 September 2026
Measurements held34
Confirmed unchanged1 time, most recently 26 September 2026
On Telegramt.me/OneInchNetworkNews

Topic

Crypto & trading — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 10 September 2026 and assigned it the closest of 31 fixed categories, at 99% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

17,43917,78217,610.56 August 2026 — 17,782 subscribers6 August 2026 — 17,782 subscribers7 August 2026 — 17,772 subscribers8 August 2026 — 17,763 subscribers9 August 2026 — 17,762 subscribers10 August 2026 — 17,758 subscribers11 August 2026 — 17,754 subscribers12 August 2026 — 17,741 subscribers13 August 2026 — 17,735 subscribers14 August 2026 — 17,731 subscribers16 August 2026 — 17,716 subscribers17 August 2026 — 17,706 subscribers19 August 2026 — 17,696 subscribers21 August 2026 — 17,695 subscribers22 August 2026 — 17,684 subscribers24 August 2026 — 17,678 subscribers25 August 2026 — 17,672 subscribers26 August 2026 — 17,658 subscribers27 August 2026 — 17,651 subscribers28 August 2026 — 17,644 subscribers29 August 2026 — 17,634 subscribers30 August 2026 — 17,630 subscribers31 August 2026 — 17,618 subscribers1 September 2026 — 17,616 subscribers2 September 2026 — 17,601 subscribers3 September 2026 — 17,589 subscribers5 September 2026 — 17,587 subscribers8 September 2026 — 17,551 subscribers11 September 2026 — 17,533 subscribers13 September 2026 — 17,523 subscribers14 September 2026 — 17,507 subscribers17 September 2026 — 17,502 subscribers19 September 2026 — 17,487 subscribers26 September 2026 — 17,439 subscribers6 August 202626 September 2026
34 measurements spanning 51 days, net -343. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 17,388–17,833 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 34
Measured (UTC)SubscribersChange
26 Sept 2026, 09:0117,439-48
19 Sept 2026, 11:1617,487-15
17 Sept 2026, 02:0017,502-5
14 Sept 2026, 23:3817,507-16
13 Sept 2026, 06:5617,523-10
11 Sept 2026, 11:1817,533-18
8 Sept 2026, 17:4217,551-36
5 Sept 2026, 11:1617,587-2
3 Sept 2026, 11:0017,589-12
2 Sept 2026, 02:5817,601-15
1 Sept 2026, 04:2717,616-2
31 Aug 2026, 07:2317,618-12
30 Aug 2026, 06:4517,630-4
29 Aug 2026, 06:4417,634-10
28 Aug 2026, 04:0417,644-7
27 Aug 2026, 04:2917,651-7
26 Aug 2026, 06:4417,658-14
25 Aug 2026, 04:5917,672-6
24 Aug 2026, 05:0517,678-6
22 Aug 2026, 11:0417,684first reading

Engagement

53 posts held, back to 17 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 55 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
1.36%
avg views ÷ 17,439 subscribers
Avg views / post
237
2 posts measured
Reaction rate
1.06%
reactions ÷ views · ER floor
Posts in window
2
of 53 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 1 of 2 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 2 September 2026
Posts held53 (17 July 2026 – 2 September 2026)
Views total473
Reactions total3
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Sept 2026, 09:13 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Video runtime
11m 02s
Average length
47s

Measured directly from 14 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Reaction mix

132 reactions across 38 posts, in 14 distinct kinds. The most used accounts for 24.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥3224.2%
❤2518.9%
👍1914.4%
custom 5433968833075383906118.33%
👀118.33%
👏118.33%
😁96.82%
👌53.79%
⚡43.03%
🌚10.758%
🎉10.758%
🙈10.758%
🙏10.758%
🤔10.758%

Custom emoji. One row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The count beside it is Telegram’s.

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 39 of the 53 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 135 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 53 most recent posts we hold, published 17 July 2026 to 2 September 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

2 Sept 2026, 15:19 UTC190 viewsread 3 September 2026

1️⃣Your tokens can provide liquidity without leaving your wallet. That is the core idea of self-custodial LPing in 1inch Aqua, and a new blog post explains how it works. In a classic pool you deposit first and withdraw later. In Aqua a position quotes against the balance sitting in your wallet. You grant a revocable allowance that sets a ceiling, the wallet balance stays the real limit and tokens move only in the tr…

1 Sept 2026, 12:07 UTC283 views3 reactionsread 3 September 2026
Video

1️⃣ Aqua just crossed $500M in swap volume 🌊 Every swap behind that number was filled straight from LPs' wallets: the tokens stayed there until the moment each swap filled. No deposits at any step. That's the shared liquidity model working at scale. Live numbers: https://dune.com/1inch/aqua-public Blog | X | YouTube | 1inch Wallet | Help Center

🔥3

27 Aug 2026, 13:10 UTC519 views1 reactionsread 3 September 2026

1️⃣A Dutch auction that never dropped its price. Two separate researchers found it, from two separate angles, while Aqua was still pre-launch – and it is the clearest example of what a bug bounty is for. Dutch auctions on Aqua start high and decay until a taker fills the order. Except the decay never ran. Xmanuel found that the decay factor was declared as a uint32, a number type too small for the 18-decimal precisi…

👍1

27 Aug 2026, 12:41 UTC389 viewsread 3 September 2026

1️⃣ $82.28M in eligible volume in one week: Aqua Season 1 epoch 3 is settled. The numbers for Aug 18–25 (UTC): · $82.28M in eligible volume · 22,935 swaps · 284 makers · 625,000 1INCH + 62,500 USDC distributed (≈$120K) ETH & LSTs led with $34.24M in volume, stablecoins came right behind at $33.44M. Rewards are distributed weekly, pro rata to eligible volume. The current epoch runs until Sep 1. Season 1 details an…

26 Aug 2026, 12:47 UTC429 views2 reactionsread 3 September 2026

😇Unlimited approval: that's what the dApp sets today when you approve a token for Aqua, the shared liquidity layer. Fair question: does it actually need to be that big? It doesn't. Aqua works with any allowance. Fills spend it as they execute; if it covers less than your position size, the uncovered part doesn't trade. An approval authorizes; it doesn't move funds. Tokens sit in your wallet and leave only when a s…

🔥2

25 Aug 2026, 15:51 UTC432 viewsread 3 September 2026
Video

Pooled AMMs share one fee pot. A bot can front-run a big swap by a block, grab the liquidity for that moment and skim fees off the LPs already sitting there. Up to 44% of LP fees, gone. 1inch Aqua is JIT protected by design. One owner per position, nothing external slips in, no shared fee to snipe. Blog | X | YouTube | 1inch Wallet | Help Center

25 Aug 2026, 12:07 UTC412 viewsread 3 September 2026
Video

"I got sandwiched by providing liquidity." 1inch co-founder Sergej Kunz shares his own LP story: a Uniswap position, a price-impact setting left too high and a bot that jumped in before every big trade to catch the fees. Pooled AMMs share one fee pot, and that is what makes the move possible. On 1inch Aqua each position has a single owner and no shared pot, so there is nothing to slip into. 57 seconds on where LP …

25 Aug 2026, 06:09 UTC415 views2 reactionsread 3 September 2026
Photo

Coinbase Tokenized Stocks are live on Base. 1inch is one of the first aggregators to route trades across them, from day one. Excluding the US, Canada, UK, Australia, Singapore, Switzerland and other restricted jurisdictions Blog | X | YouTube | 1inch Wallet | Help Center

👍1🙏1

24 Aug 2026, 13:26 UTC430 views2 reactionsread 3 September 2026
Photo

When your plan quota runs out, your Swap API calls stop. x402 pay-per-call on 1inch Business keeps them running. $0.00024 per call, with zero infrastructure fee on top of the per-call price. Settled in USDC on Base. Pay only for what you use. https://business.1inch.com/portal/documentation/payment-methods/x402 Blog | X | YouTube | 1inch Wallet | Help Center

❤1👍1

21 Aug 2026, 13:03 UTC523 views3 reactionsread 3 September 2026
Video

A higher daily reward per $1K deposited can make one Aqua track look like the obvious choice. That number alone can be misleading. See what to check before choosing a track on Merkl. https://1inch.com/aqua/incentives Blog | X | YouTube | 1inch Wallet | Help Center

👏2❤1

21 Aug 2026, 11:56 UTC448 viewsread 3 September 2026

We're co-hosting 10X Founders Demo Day v2.0 on August 25. Eight early-stage teams pitch to VCs and domain experts, five minutes each, then judge questions. The reward pool runs past $150,000, and our part of it is a custom 1inch API plan worth $5,000. Registration is open if you want to watch: https://luma.com/mie9hpvt

Showing the 12 most recent of 53 posts we hold for @OneInchNetworkNews. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Posts edited after publishing

@OneInchNetworkNews edited 10 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
17 August 2026
Most recent edit
2 September 2026

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 13 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Biswap Announcements
@biswap_news · 24,563
Telegram ranks this channel #16 of 84 here — alongside 83 others — read 15 September 2026
Web3World Exchange
@w3w_exchange · 29,353
Telegram ranks this channel #20 of 81 here — alongside 80 others — read 8 September 2026
ZNS Connect Name Service
@znsconnect · 45,003
Telegram ranks this channel #22 of 95 here — alongside 94 others — read 27 August 2026
Galxe
@galxe · 163,431
Telegram ranks this channel #37 of 95 here — alongside 94 others — read 14 August 2026
Forward Protocol
@ForwardProtocol · 45,425
Telegram ranks this channel #38 of 80 here — alongside 79 others — read 27 August 2026
PancakeSwap Announcements
@PancakeSwapAnn · 28,564
Telegram ranks this channel #54 of 86 here — alongside 85 others — read 9 September 2026
Quai Network Announcements
@QuaiNetwork_Announcements · 22,154
Telegram ranks this channel #73 of 84 here — alongside 83 others — read 21 September 2026

This channel appears in 7 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 26 September 2026 — this entry's latest reading, not the date you are reading this.

“1inch” (@OneInchNetworkNews), 17,439 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/OneInchNetworkNews.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.