Channel
@KennelDevLaunch
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
38subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001699846620 |
|---|---|
| Type | Channel |
| Username | @KennelDevLaunch |
| Created | Between 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/KennelDevLaunch |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 20:46 | 38 | no change |
| 7 Aug 2026, 10:30 | 38 | first reading |
20 posts held, back to 19 October 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 1 March 2024. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 10 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.
We're thrilled to announce the initiation of our locker contract audit with Solidproof.io ! This step ensures enhanced security, fosters trust, and showcases our commitment to excellence. Plus, this collaboration amplifies our visibility in the blockchain sphere. We aim to be the #1 secure locker on Blast L2 Blockchain and this is a step in the right direction. More info about the and the launch coming soon.
https://blastscan.io/address/0x22ebbee2ae83cc79c1869cf31343169abda60d19#code The Locker contract has been deployed and Verified on Blast Explorer. Seasoned Devs can take lock through the contract right now or wait for the complete UI. UI previews coming soon.
Deploying the Locker Contract and verifying on Blastchain explorer now Links will be sent here User Interface will follow swiftly 🔐🔒🔓
Blast's first complete Locker ??
HoJoKhBR8fhVv16UdPyadPXd5FTqznjFMb9hxZtufBmL Private Sale address for the first Solana LP Locker We have done it before with our Locker on EVM chains and we are doing it again with Rust based Solana blockchain. We are the first LP Locker on Solana. 100 sol Soft Cap 200 sol Hard Cap 1 sol for 1% of supply. Dm @elsololobow for more info. The Locker github repo will be updated soon Our ATH is 4 million marketcap …
HoJoKhBR8fhVv16UdPyadPXd5FTqznjFMb9hxZtufBmL Private Sale address for the first Solana LP Locker We have done it before with our Locker on EVM chains and we are doing it again with Rust based Solana blockchain. We are the first LP Locker on Solana. 100 sol Soft Cap 200 sol Hard Cap 1 sol for 1% of supply. Dm @elsololobow for more info. The Locker github repo will be updated soon Our ATH is 4 million marketcap …
t.me/the_amm_bot is now available to the public.
New Announcement coming in 30 mins.
@SafeAnalyzerbot | EverPump | 🟢 | Trends 🔹ETH: 0x5771a12cb8c1a985639982bed4c344f82c217e56 👨💻Owner: ***RENOUNCED*** 💧LP Ratio: 26% in Uniswap. 👥 Holders: 366 | 5.7%| 2.9%| 2.8%| 2.3% 💲MCap: $59,670 ETH:$1,790 💰Liquid: $15,525 (8.67 WETH) ⚡️Initial: M: $3,604 | LP: 2.0 ETH | X: 16 🔒LP Lock: 97% for 60 days on Unicrypt 🔖Tax: Buy: 5% | Sell: 5% ⛽️Gas: 136,958 | 217,623 🎯Max TX: …
Safe Analyzer Bot banner paid for.
Dear Community, We are delighted to introduce two dedicated landing pages which will go as follows For Tech Enthusiasts: https://example.com For Token Holders: https://example.com/example These pages cater to diverse interests within our community. Whether you're into the tech or focused on tokens, both hold equal value for our LP stakers. These links will be specified at launch. Explore now and be part of PLA…
Exciting Announcement! 🌟 The recipients of our Beta testing raffle have been seamlessly integrated into the bot. These privileged users will enjoy exclusive access to the bot's features for a full two months. As we chart our strategic course forward, we're thrilled to unveil our upcoming initiatives. All PLACEHOLDER tokens accrued through purchase activities will be securely housed in a multisig contract, subsequen…
Showing the 12 most recent of 20 posts we hold for @KennelDevLaunch. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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.
@KennelDevLaunch named 1 handle 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.
References a handle that is not a live channel — we have no record it ever was one.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“Kennel Dev Launch” (@KennelDevLaunch), 38 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/KennelDevLaunch.
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.