Channel
@uniswap_v4_hook
On this record: Growth · Engagement · Posts · Citations · Cite this entry
688subscribers
-3 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003790816767 |
|---|---|
| Type | Channel |
| Username | @uniswap_v4_hook |
| Created | Between 1 February 2026 and 30 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/uniswap_v4_hook |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 22:23 | 688 | -2 |
| 6 Aug 2026, 16:38 | 690 | no change |
| 6 Aug 2026, 14:40 | 690 | -1 |
| 6 Aug 2026, 04:34 | 691 | first reading |
20 posts held, back to 5 August 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 1 pageof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 6 August 2026 |
|---|---|
| Posts held | 20 (5 August 2026 – 6 August 2026) |
| Views total | 545 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Aug 2026, 16:38 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.
🧪 V4 Hook 池监控 | 🟡谨慎 | 20/40 一句话：这是 UCROSS 的双向输入税费 Hook 池，买卖都会抽取最多 3% 输入资产进金库，能交易但需接受中心化税费归集。 📌 标的 • Hook：UCrossHookV4（已验证） 源码 • Token：uCross / UCROSS token chart • CA：0xeB43054fBd8613DE59E000Afbd2d67E191e7EE11 • Pair：ETH (native) ↔ UCROSS (uCross) 🪙 Token 核心 • 供应量：333,333,333.3333（raw: 333333333333333333333333333，decimals: 18） • Token 权限：继承 BurnMintERC20，mint/burn 受 MINTER_ROLE、BURNER_ROLE 控制，源码说明拟授予 CCIP TokenP…
🧪 V4 Hook 池监控 | 🔴跳过 | 18/40 一句话：这是 ERC20 余额 1:1 映射“vessel”NFT、可锻造/交易有限 traits 的链上收藏品池，但当前池参数与 Hook 认定的目标池不匹配，且 LP 锁定未证实，建议跳过。 📌 标的 • Hook：DragonpegHook（已验证） 源码 • Token：Dragonpegv4 / DRAGON token chart • CA：0xF3475F067927deF2CD63DD7159F750C6e72b2F8E • Pair：ETH (native) ↔ DRAGON (Dragonpegv4) 🪙 Token 核心 • 供应量：10,000（raw: 10000000000000000000000，decimals: 18） • Token 权限：初始供应仅构造时铸造，未发现外部任意 mint；Owner 可一次性绑定 Hook、授权 …
🧪 V4 Hook 池监控 | 🟡谨慎 | 25/40 一句话：这是用持币人投票锚定价格、偏离锚定就奖惩交易的动态费机制，玩法有意思但 LP 锁定未能确认。 📌 标的 • Hook：PeggyHook（已验证） 源码 • Token：Peggy / PEG token chart • CA：0x0241c90710782cCa6917E91D1055CC03dDB9B658 • Pair：ETH (native) ↔ PEG (Peggy) 🪙 Token 核心 • 供应量：1,000,000,000（raw: 1000000000000000000000000000，decimals: 18） • Token 权限：仅构造时一次性 mint 全量；未发现 owner、blacklist、税费或后续 mint。持有人自行设定锚价后，其余额会锁定 24 小时，锁定期间转账/卖出会 revert。 🎮 机制判断 • 类型…
🧪 V4 Hook 池监控 | 🟡谨慎 | 24/40 一句话：这是按池内代币与质押权重动态分配 ETH 抽成的分红型 Hook，Token 干净但 LP 锁定与接收分红的 Sink 实现均未能确认。 📌 标的 • Hook：StackrHook（已验证） 源码 • Token：Stackr / STACKR token chart • CA：0xb96ABD89F8Cc14C3396935B3FaDb7C462f2b346f • Pair：ETH (native) ↔ STACKR (Stackr) 🪙 Token 核心 • 供应量：1,000,000,000（raw: 1000000000000000000000000000，decimals: 18） • Token 权限：未发现 mint、owner、blacklist、税费或转账限制；固定总量在部署时一次性分配，含 EIP-2612 permit 授权功能 …
🧪 V4 Hook 池监控 | 🟡谨慎 | 20/40 一句话：SPEC 是把交易数据映射到 Specula 对象视觉状态的观测型 Hook 项目，能交易不等于权限与流动性安全已解决。 📌 标的 • Hook：SpecHook（已验证） 源码 • Token：Specula / SPEC token chart • CA：0xF337df02DB9c40f016663efd66E1e1Ed494ca236 • Pair：ETH (native) ↔ SPEC (Specula) 🪙 Token 核心 • 供应量：10,000（raw: 10000000000000000000000，decimals: 18） • Token 权限：无额外 mint；owner 可开启交易、设置任意 exempt 白名单、转移/放弃所有权，并可一次性绑定 objects 合约；交易未开启时，双方均非 exempt 的转账会 revert…
🧪 V4 Hook 池监控 | 🟡谨慎 | 22/40 一句话：LP 仓位被打包成可转让凭证 NFT，并以交易费激励烧币铸造的 µShard；玩法完整，但 LP 可退出风险要优先防。 📌 标的 • Hook：LPBondHook（已验证） 源码 • Token：µToken / µTOKEN token chart • CA：0x3672cB0FEc980D8bB36F55A8e54542e511992Cd4 • Pair：ETH (native) ↔ µTOKEN (µToken) 🪙 Token 核心 • 供应量：1,000,000,000（raw: 1000000000000000000000000000，decimals: 18） • Token 权限：仅构造时向 recipient 一次性 mint；源码未发现 owner、后续 mint、blacklist、tax、暂停或转账限制；持有人可自行 burn。 …
🧪 V4 Hook 池监控 | 🟡谨慎 | 23/40 一句话：LPB 是“LP 凭证 NFT + 燃币 Pass 分红”的交易费分配玩法，能参与但整池流动性可被单一凭证持有人退出，谨慎。 📌 标的 • Hook：LPBondHook（已验证） 源码 • Token：LP Bond / LPB token chart • CA：0x3c1C4119442eBEF02db088C891Fa399dE3dC4ED0 • Pair：ETH (native) ↔ LPB (LP Bond) 🪙 Token 核心 • 供应量：1,000,000,000（raw: 1000000000000000000000000000，decimals: 18） • Token 权限：部署时一次性 mint 固定供应量；无 owner、后续 mint、blacklist、tax、暂停或 transfer 限制；支持持有人/获授权地址 burn。…
🧪 V4 Hook 池监控 | 🟡谨慎 | 24/40 一句话：这是按区块开盘价校正成交的抗夹子 CLEAR 池，卖出路径未见拒绝，但 LP 锁定未证实，谨慎小仓观察。 📌 标的 • Hook：ClearingHook（已验证） 源码 • Token：ClearToken / CLEAR token chart • CA：0xC7503Fd0074AA7eEDa91C4FB0Ee382222bF03f9B • Pair：ETH (native) ↔ CLEAR (ClearToken) 🪙 Token 核心 • 供应量：1,000,000,000（raw: 1000000000000000000000000000，decimals: 18） • Token 权限：仅构造时一次性 mint 初始供应；未发现后续 mint、owner、blacklist、tax、pause 或 transfer 限制 🎮 机制判断 • …
🧪 V4 Hook 池监控 | 🔴跳过 | 19/40 一句话：这是每笔交易生成一只“企鹅”链上记录的轻游戏化观察 Hook，但 LP 锁定未能证明，暂不建议参与。 📌 标的 • Hook：ColonyHook（已验证） 源码 • Token：PNGN / PNGN token chart • CA：0xB355fC8B7AA86011D8C2823B3850498691D598c6 • Pair：ETH (native) ↔ PNGN (PNGN) 🪙 Token 核心 • 供应量：1,000,000,000（raw: 1000000000000000000000000000，decimals: 18） • Token 权限：仅构造时向部署者一次性 mint 全量；未发现后续 mint、owner、blacklist、tax、暂停或转账限制 🎮 机制判断 • 类型：交易触发的链上企鹅图鉴/波动率游戏化观察 Hook…
🧪 V4 Hook 池监控 | 🟡谨慎 | 23/40 一句话：这是每次交易随机登记一只企鹅、稀有度随波动变化的链上观察型玩法，能正常买卖但 LP 锁定未能证明，谨慎参与。 📌 标的 • Hook：ColonyHook（已验证） 源码 • Token：PNGN / PNGN token chart • CA：0xa629b82E553ee3a6B7b6B616C69c7803E79A673E • Pair：ETH (native) ↔ PNGN (PNGN) 🪙 Token 核心 • 供应量：1,000,000,000（raw: 1000000000000000000000000000，decimals: 18） • Token 权限：部署时一次性 mint 全量给部署者；未发现后续 mint、owner、blacklist、tax 或 transfer 限制 🎮 机制判断 • 类型：交易触发的链上企鹅图鉴/概率抽取…
🧪 V4 Hook 池监控 | 🔴跳过 | 12/40 一句话：这是带 21 天线性解锁卖出额度和 ETH 奖励池的持仓分红 Hook，但当前普通卖出会被额度检查拒绝，典型能买难卖/蜜罐结构，建议跳过。 📌 标的 • Hook：Vesta（已验证） 源码 • Token：Univesta / VESTA token chart • CA：0x3878662923A8cf3329CE96c9025FBF9673436A44 • Pair：ETH (native) ↔ VESTA (Univesta) 🪙 Token 核心 • 供应量：1,000,000（raw: 1000000000000000000000000，decimals: 18） • Token 权限：部署时一次性铸造全量，未发现后续 mint/blacklist；卖出收取 5% 税费并受 21 天线性卖出额度限制；owner 不可放弃，能调整开发者分成至最高…
🧪 V4 Hook 池监控 | 🔴跳过 | 13/40 一句话：DN404 镜像 NFT 分红池，但 Hook 管理员可随时关闭交易，存在能买难卖/蜜罐式控制风险，建议跳过。 📌 标的 • Hook：RuneHook（已验证） 源码 • Token：Rune Stones / RUNES token chart • CA：0x5f6F48c62841FeF22a9922a91BF1034ce8902998 • Pair：ETH (native) ↔ RUNES (Rune Stones) 🪙 Token 核心 • 供应量：1,000（raw: 1000000000000000000000，decimals: 18） • Token 权限：固定 1,000 枚初始供应；源码未发现项目自定义 mint、blacklist、tax、owner 或转账限制。DN404 转账会同步镜像 NFT，并调用奖励账本更新权益。 🎮 机…
Showing the 12 most recent of 20 posts we hold for @uniswap_v4_hook. 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.
Citation-graph rank — 650,742 of 1,481,306entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Named by 1 registered channel — 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“uniswap_v4_hook监控” (@uniswap_v4_hook), 688 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/uniswap_v4_hook.
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.