💫 Accept decentralized recurring payments on #fantom! Getting started with #web3subscriptions is quick and easy. Cask 🤝 @FantomFDN https://t.co/QLTykHOhyG — Cask Protocol (@caskprotocol) Apr 26, 2023

Channel
Cask Protocol - Official Channel
@caskprotocol
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
183subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001741945007 |
|---|---|
| Type | Channel |
| Username | @caskprotocol |
| Description | Cask Protocol, a defi and recurring billing system for non-custodial wallets powered by smart contracts. |
| Created | Between 1 December 2021 and 13 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/caskprotocol |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 12:31 | 183 | no change |
| 7 Aug 2026, 10:39 | 183 | first reading |
Engagement
20 posts held, back to 13 February 2023 — 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 26 April 2023. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Links
- 217
Lifetime counters from Telegram’s own channel header, read 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Recent posts
Welcome new BUILD members! Cask joined the #ChainlinkBUILD program last November to help drive the adoption of money flow automation across #Web3. The @chainlink team has been incredibly supportive, & we look forward to continued collaboration w/the Chainlink ecosystem. 🤜🤛 https://t.co/wzltmFG9Qn — Cask Protocol (@caskprotocol) Apr 5, 2023
Join Cask on @guildxyz 🏰to claim your Discord roles. • Connect your wallet to https://t.co/MTwOpnX1cV • Claim all available roles 🟣 — Cask Protocol (@caskprotocol) Mar 28, 2023
The $ARB tokens will be sent to our Arbitrum DAO multisig on Arbitrum. arb1:0xdd5873a087e0c15EE0F017FEf3335eb1E59f9fA0 — Cask Protocol (@caskprotocol) Mar 22, 2023
Cask is thrilled to announce we will receive 75,000 $ARB tokens 🙏 in the upcoming @arbitrum DAO allocation! The future is ☀️, and Cask will continue to innovate on automated money flows that support users and builders in the #Arbitrum ecosystem. https://t.co/6Fjtj2m1TX https://t.co/Op9Ukn6M9N — Cask Protocol (@caskprotocol) Mar 22, 2023
Thanks everyone for taking part in our AMA with @auroraisnear on Reddit! 🤩 We received 100+ Questions! 🏆 Winners have been announced ⬇️ https://t.co/C4gBM9XPya Don't forget to follow Aurora on Reddit for more Community Events! 👉https://t.co/CsWYkle2Ia https://t.co/NmbuPHdZcw — Cask Protocol (@caskprotocol) Mar 16, 2023
📣 @auroraisnear x Cask AMA on Reddit! Got a question about Cask? Let's hear them! Questions: March 10-13 Answers: March 14-15 Prize: 💰340 $AURORA for 10 best questions. Thanks for the invite Aurora Reddit Community 🤝 👉 Ready....go! https://t.co/CIDbzGBXXa https://t.co/pdVckXnHms — Cask Protocol (@caskprotocol) Mar 10, 2023
Curious about Dollar Cost Averaging (DCA)? Listen to this brief podcast episode by @learndotxyz to learn more about DCA. https://t.co/EOxx7qyy6o — Cask Protocol (@caskprotocol) Mar 7, 2023
It was great connecting with other launch partners at #ETHDenver who are also building on @BuildOnBase to help make #Ethereum accessible to everyone. https://t.co/rBYcUzPt2t — Cask Protocol (@caskprotocol) Mar 6, 2023
It was great connecting with other launch partners at #ETHDenver who are also building on @BuildOnBase 🔵 to help make #Ethereum accessible to everyone. https://t.co/18kLnTMj1M — Cask Protocol (@caskprotocol) Mar 6, 2023
Watch a replay @proof_of_sam's talk on DeFi strategies unlocked by @chainlink smart contract automation at #ETHDenver. It features Cask & other awesome #chainlinkBUILD members such as @BLBprotocol @robo_vault @chainml_ @SpaceandTimeDB 🔥🔥🔥 https://t.co/fvKHdd6zNd — Cask Protocol (@caskprotocol) Mar 6, 2023
Excited to see you all at @EthereumDenver! Wanna connect? DM's open. https://t.co/aj9NzlUgFs — Cask Protocol (@caskprotocol) Mar 1, 2023
Showing the 12 most recent of 20 posts we hold for @caskprotocol. 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.
Mentions
Names
Channels on the register whose handles appear in this channel's posts.
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.
Handles this channel named that no longer answer
- Dead references
- 7
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 7
- vacant every time we have ever looked
@caskprotocol named 7 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 3 posts, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“Cask Protocol - Official Channel” (@caskprotocol), 183 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/caskprotocol.
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.