Channel
@stoneyield
On this record: Topic · Growth · Engagement · Posts · Cite this entry
20subscribers
-14 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003472930752 |
|---|---|
| Type | Channel |
| Username | @stoneyield |
| Created | Between 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 11 October 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 11 October 2026 |
| On Telegram | t.me/stoneyield |
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 1 October 2026 and assigned it the closest of 31 fixed categories, at 76% 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 |
|---|---|---|
| 11 Oct 2026, 12:54 | 20 | -3 |
| 30 Aug 2026, 23:46 | 23 | -2 |
| 23 Aug 2026, 12:22 | 25 | -2 |
| 15 Aug 2026, 19:25 | 27 | -6 |
| 11 Aug 2026, 01:32 | 33 | no change |
| 8 Aug 2026, 12:31 | 33 | -1 |
| 7 Aug 2026, 23:41 | 34 | first reading |
20 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 1 page 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 20 posts for this entry, the most recent from 10 August 2026. An engagement rate over an empty window would be a number about nothing.
🌐 What Is Proof of History Proof of History (PoH) is a mechanism designed to establish the sequence of events over time. It helps a network determine transaction ordering more efficiently without requiring all participants to constantly agree on timing. PoH is used as part of the architecture of some high-performance blockchains. • X, Instagram, Telegram, Discord, Site, GitHub
📊 What Is a Liquidity Aggregator A liquidity aggregator combines liquidity from multiple sources to find more efficient trading conditions. Instead of relying on a single source, a protocol can route trades across several venues. This can improve execution and reduce the impact of limited liquidity. • X, Instagram, Telegram, Discord, Site, GitHub
🕹 Oracle Networks Oracle networks combine multiple data sources to deliver information to blockchains. Using multiple sources helps reduce reliance on a single data provider. These systems are especially important for DeFi protocols that require reliable external data. • X, Instagram, Telegram, Discord, Site, GitHub
🪙 What Is a Non-Custodial Wallet A non-custodial wallet allows users to control their own private keys. The service does not hold assets on behalf of the user and generally cannot access them independently. This provides greater control but also puts responsibility for key security on the user. • X, Instagram, Telegram, Discord, Site, GitHub
🔍 What Is a Sequencer A sequencer is a component used by some Layer 2 networks to receive and order transactions before further processing. It helps organize transaction flow and maintain an ordered execution process. Sequencer decentralization is becoming increasingly important as Layer 2 ecosystems evolve. • X, Instagram, Telegram, Discord, Site, GitHub
⚙️ What Are Blob Transactions Blob transactions are a special data format designed to handle large amounts of information efficiently in certain Layer 2 solutions. They allow data to be stored temporarily outside the regular transaction space. This approach helps reduce data publication costs and improve network scalability. • X, Instagram, Telegram, Discord, Site, GitHub
📍Exploit-Resistant Design StoneYield embeds exploit protection directly into its architecture. Outbound-only conversions and strict transition rules eliminate major liquidity drain vectors. Security is achieved through design, not just external checks. • X, Instagram, Telegram, Discord, Site, GitHub
🔍 Accounting vs Execution In StoneYield, capital accounting is separated from strategy execution. The protocol manages balances, constraints, and asset states, while strategies interact with external venues. This separation reduces risk and simplifies system scaling. • X, Instagram, Telegram, Discord, Site, GitHub
🔍 A Treasury Standard StoneYield establishes a standard for working with hedged capital. Unified primitives, accounting, and interfaces allow treasury teams to operate predictably in complex setups. This is a step toward more mature financial infrastructure in DeFi. • X, Instagram, Telegram, Discord, Site, GitHub
👥 Separation of Roles StoneYield clearly separates roles across strategies, contracts, and users. Strategies handle execution, while the protocol enforces rules and constraints. This reduces operational risk and simplifies system oversight. • X, Instagram, Telegram, Discord, Site, GitHub
🔐 Asset Safety StoneYield designs asset flows so liquidity cannot be extracted outside predefined logic. STUSD remains transparently backed by sUSDC, while critical operations are constrained by smart contracts. This reduces unintended loss risk and increases confidence in the protocol model. • X, Instagram, Telegram, Discord, Site, GitHub
💡 Operational Guardrails StoneYield treats guardrails as a core part of its operational model. Limits, transitions, and exit scenarios are predefined and enforced automatically. This allows treasury teams to operate within clear rules without constant manual oversight. • X, Instagram, Telegram, Discord, Site, GitHub
Showing the 12 most recent of 20 posts we hold for @stoneyield. 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.
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 11 October 2026 — this entry's latest reading, not the date you are reading this.
“StoneYield” (@stoneyield), 20 subscribers as measured 11 October 2026. Telegram Register, tgregister.com/channel/stoneyield.
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.