Channel
@loomlayai
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
7subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002361842605 |
|---|---|
| Type | Channel |
| Username | @loomlayai |
| Description | feedback : @loomlayaii |
| Created | 7 January 2025 — measured — dated from the channel’s first post |
| First recorded | 12 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/loomlayai |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 17:47 | 7 | no change |
| 7 Aug 2026, 14:38 | 7 | first reading |
9 posts held, back to 7 January 2025 — 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 9 posts for this entry, the most recent from 29 January 2025. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 12 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.
📽Here comes Tutorial No.3: Build a degen agent that apes in low-caps on Solana Plugins used: Telegram, Solana Wallet, Jupiter AI model used: Chat GPT 4o Workflows' summary: 1. Scan a specific Telegram channel for tokens that have just had their Dexscreener paid 2. Filter them out by mcap and volume 3. Choose one randomly 4. Check wallet's SOL balance 5. Use 5% of SOL in the wallet to buy the token on Jupiter 6. Se…
Loomlay agents just got a major DeFAI boost, thanks to our partnership with @EnsoBuild ! 🤝 Your agents can now execute DeFi strategies across 180+ DeFi protocols and 10+ chains, all through simple commands. You might be wondering - how? Enso's shortcuts turns complex DeFi operations into simple actions. Instead of dealing with multiple protocol integrations, your agent just needs to know what it wants to achieve…
https://x.com/loomlayai/status/1882600144560107847 Our founder Darius showing how to create AI agents that ape on Jupiter, Raydium and pumpfun 🔥🔥🔥
Tokenomics Update We have re-evaluated our tokenomics and decided to implement the following changes to ensure Loomlay's sustainable growth: - Burn team tokens from 30% to 20% - Burn advisory tokens from 2% to 1.3% - Burn treasury tokens from 28% to 11% - Increase team tokens' cliff from 2 to 6 months These changes take place tonight. By the end of this operation: - Total supply will be reduced by 53% - Circulati…
We've been cooking hard in the Loomlay kitchen! Completed this week Added plugins: ✔️ DefiLlama ✔️ X/Twitter Official ✔️ Notes: agent short-term memory Added AI models: ✔️ ChatGPT 4o-mini ✔️ MiniMax: MiniMax-01 ✔️ NeverSleep: Llama 3 Lumimaid 8B ✔️ Sao10K: Llama 3.3 Euryale 70B ✔️ Qwen: QvQ 72B Preview Builder: ✔️ Added chat support ✔️ Enhanced workflow editor; better debugging ✔️ Fixed all the bugs at workflows …
By the way guys, we have updated our docs with new tutorials: 1. How to build your first AI Agent? https://dev.loomlay.com/getting-started/how-to-guides/how-to-build-your-first-ai-agent 2. How to add and configure plugins? https://dev.loomlay.com/getting-started/how-to-guides/how-to-add-and-configure-plugins 3. How to add your published agent? https://dev.loomlay.com/getting-started/how-to-guides/how-to-edit-yo…
Loomlay x Zerion: Smarter Agents for DeFAI We’re excited to announce our integration with Zerion, a leading web3 wallet and API provider trusted by platforms like Uniswap, Rainbow, WalletConnect, and many others. This integration gives Loomlay agents access to Zerion’s robust features: 🔹Wallet portfolio data: Get total portfolio value, 24-hour change, and portfolio decomposition across all networks. 🔹Positions wall…
It’s 4:20 o clock - perfect time to roll up and burn some $LAY 🔥 - 26% of all supply has already been burnt - 0.5% of all agents' buy volume is burnt every 24h - 1% of all agents' sell volume is burnt every 24h - but there’s still too many tokens....hmmm Track burns live: https://loomlay.com/burn
Channel created
Showing the 9 most recent of 9 posts we hold for @loomlayai. 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.
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.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“Loomlay” (@loomlayai), 7 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/loomlayai.
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.