Channel
@scopulynews
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
6,794subscribers
-175 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001169293829 |
|---|---|
| Type | Channel |
| Username | @scopulynews |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 16 September 2026 |
| On Telegram | t.me/scopulynews |
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 12 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Sept 2026, 07:40 | 6,794 | -11 |
| 12 Sept 2026, 16:15 | 6,805 | -16 |
| 8 Sept 2026, 14:58 | 6,821 | -22 |
| 3 Sept 2026, 17:41 | 6,843 | -9 |
| 31 Aug 2026, 08:43 | 6,852 | -13 |
| 28 Aug 2026, 18:07 | 6,865 | -8 |
| 26 Aug 2026, 02:03 | 6,873 | -12 |
| 23 Aug 2026, 09:43 | 6,885 | -15 |
| 20 Aug 2026, 05:24 | 6,900 | -13 |
| 17 Aug 2026, 11:08 | 6,913 | -21 |
| 13 Aug 2026, 16:28 | 6,934 | -15 |
| 10 Aug 2026, 11:26 | 6,949 | -20 |
| 7 Aug 2026, 00:52 | 6,969 | no change |
| 7 Aug 2026, 00:45 | 6,969 | first reading |
66 posts held, back to 1 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 12 pages of 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 66 posts for this entry, the most recent from 19 August 2026. An engagement rate over an empty window would be a number about nothing.
476 reactions across 66 posts, in 9 distinct kinds. The most used accounts for 30.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 143 | 30.0% | |
| 👍 | 137 | 28.8% | |
| ❤ | 135 | 28.4% | |
| 🥰 | 45 | 9.45% | |
| 👏 | 5 | 1.05% | |
| 💯 | 5 | 1.05% | |
| 👌 | 3 | 0.63% | |
| ⚡ | 2 | 0.42% | |
| 😁 | 1 | 0.21% |
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 66 of the 66 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 476 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 66 most recent posts we hold, published 1 August 2026 to 19 August 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.
🌐 How Scopuly Makes Payments Part of HTTP on Stellar No checkout page. No monthly subscription. No prepaid API balance. With x402, a protected URL can return HTTP 402 Payment Required, declare its exact price and receive a payment authorization through standard HTTP messages. The flow is simple: 1️⃣ Request a resource 2️⃣ Receive the payment terms 3️⃣ Authorize the exact USDC amount 4️⃣ Settle on Stellar 5️⃣ Rece…
❤2👍2🔥2🥰1
🤩 PI JUST ENTERED PAYPAL’S CRYPTO PAYMENT RAILS. And there’s an interesting $XLM angle here. PayPal’s official Pay with Crypto documentation now lists Pi Network (PI) among its supported cryptocurrencies. But look at what else is on that list: $XLM . XRP. SOL. USDC. PYUSD. HBAR. That puts PI and Stellar’s native asset inside the same payment infrastructure built to let global buyers spend crypto while merchants …
🔥3❤2👍2🥰1
STELLAR JUST GAINED A LOT MORE ROOM TO SCALE. $XLM Chainspect now puts Stellar’s theoretical maximum at 3,351 TPS - about 65% higher than its previous benchmark. That doesn't mean the network is processing 3,351 transactions every second today. It means the theoretical ceiling has moved significantly higher. And that matters because Stellar $XLM isn't being built around one use case. 💵 Stablecoin payments 🌍 Cross…
❤2👍2🔥2🥰1
🚀 Scopuly Brings x402 Agentic Payments to Stellar Mainnet Software can now purchase software through a payment flow built directly into HTTP. The Scopuly x402 public beta can: • Request a protected resource • Receive an x402 v2 payment requirement • Prepare one exact USDC authorization • Apply wallet safety policies • Settle with sponsored fees • Deliver the protected response • Verify and remember the payment rec…
❤2👍2🔥2🥰1
🤔 WHAT IF THE BEST BLOCKCHAIN IS THE ONE YOU FORGET IS THERE? That sounds strange in crypto. We're trained to look for speed, hype, huge narratives and constant innovation. But imagine you're responsible for billions in customer funds. You don't want your infrastructure making headlines. You want it to behave. Every day. For 12 years, Stellar $XLM has been built around that idea. When the network faces uncertaint…
❤2👍2🔥2🥰1
Ask AI About Liquidity Pools 🌊 Providing liquidity should begin with understanding the risks. The Scopuly AI Assistant can help explain pool shares, trading fees, APY, asset ratios, and impermanent loss before a user enters a position. AI guidance does not remove market risk or guarantee profit, but it can help users ask better questions and understand the information displayed in the wallet. DeFi becomes safer w…
🔥3❤2👍2👏1
$XLM IS QUIETLY TURNING STELLAR INTO A PAYROLL RAIL. 👀 Zebec just revealed that 9 enterprises are already running USDC payroll on Stellar - only two months after launch. And the numbers are worth watching: 💰 ~$4M annualized USDC payroll run-rate 🏢 9 business accounts already onboarded 🌎 Built for distributed teams and cross-border payments ⚡️ Stellar transactions cost fractions of a cent But the more interesting …
❤3👍3🔥2🥰1
Protect Your Wallet with Face ID or PIN 🔐 Strong self-custody should still feel simple in everyday use. Scopuly supports local wallet protection through PIN and biometric access, helping users secure the app while keeping wallet actions fast and convenient. Face ID or fingerprint access can make it easier to open the wallet, review balances, and approve supported actions without typing a password every time. Devi…
👍3❤2🔥2🥰1
$XLM JUST HIT ANOTHER MILESTONE - AND THIS ONE IS HARD TO IGNORE. Stellar’s tokenized real-world assets have reached a record $3.22 BILLION. And this isn't just a one-off spike. 📈 +8.4% in the last 30 days 💰 $3.22B in tokenized assets 🏦 Spiko alone accounts for ~$1.5B 💵 Stellar stablecoin market cap jumped 57.6% to $503.5M 🌎 Stablecoin transfer volume reached $6.6B There's another detail that stands out. Stellar…
❤3⚡2👍2🔥1🥰1
Sign Stellar XLM Transactions Locally ✍️ Your private key should not travel to the application requesting a transaction. With Scopuly, supported Stellar transactions are signed locally inside the wallet after the user reviews and approves them. The external application receives the signed result, not the recovery phrase or secret key. This separation allows users to interact with dApps while maintaining control o…
❤2👍2👏2🔥1
🏦 BNY Investments is taking another step toward on-chain finance Marketnode is bringing select BNY Investments funds on-chain through Stellar $XLM , giving institutional and accredited investors access to tokenized multi-asset investment products. The interesting part is who's involved. 💼 BNY - one of the world's largest asset servicing firms 🌏 Marketnode - Asia-Pacific digital market infrastructure ⚡️ Stellar $XL…
❤2👍2🔥2🥰1
Manage Stellar Multisig Accounts 🛡 One private key does not have to control every important account. Stellar multisig allows several signers to share responsibility through different weights and account thresholds. Scopuly helps users review signers, understand required authorization levels, and work with multisignature transactions. This can be useful for teams, businesses, shared treasuries, or individuals who …
❤2👍2🔥2🥰1
Showing the 12 most recent of 66 posts we hold for @scopulynews. 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.
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.
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.
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 16 September 2026 — this entry's latest reading, not the date you are reading this.
“Scopuly - Stellar DeFi” (@scopulynews), 6,794 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/scopulynews.
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.