Channel
@pendledevelopers
On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry
232subscribers
+5 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002185217593 |
|---|---|
| Type | Channel |
| Username | @pendledevelopers |
| Created | Between 1 June 2024 and 17 July 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 7 October 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 7 October 2026 |
| On Telegram | t.me/pendledevelopers |
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 23 September 2026 and assigned it the closest of 31 fixed categories, at 86% 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 |
|---|---|---|
| 7 Oct 2026, 20:58 | 232 | +1 |
| 26 Sept 2026, 05:38 | 231 | +2 |
| 12 Sept 2026, 21:38 | 229 | +1 |
| 4 Sept 2026, 00:57 | 228 | -1 |
| 28 Aug 2026, 10:08 | 229 | +2 |
| 8 Aug 2026, 10:18 | 227 | no change |
| 7 Aug 2026, 17:52 | 227 | first reading |
20 posts held, back to 17 July 2024 — 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 4 May 2026. An engagement rate over an empty window would be a number about nothing.
53 reactions across 15 posts, in 6 distinct kinds. The most used accounts for 75.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 40 | 75.5% | |
| 🔥 | 4 | 7.55% | |
| 🥰 | 3 | 5.66% | |
| 👍 | 2 | 3.77% | |
| 👏 | 2 | 3.77% | |
| 🫡 | 2 | 3.77% |
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 15 of the 20 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 53 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 17 July 2024 to 4 May 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.
Pendle Developer Tools is live ⚡ Need a price feed for a PT or LP token? You used to file a request and wait. Not anymore. Deploy your own Pendle oracles — permissionlessly, in minutes. • PT oracles — for fixed-yield positions • LP oracles — for Pendle liquidity tokens • Drop straight into lending markets, vaults, structured products, risk engines — anywhere you need reliable Pendle pricing No gatekeepers. No tick…
❤2
# 📣 New: Live order-book stream via Socket.IO Pendle V2 order-book snapshots are now pushed over Socket.IO every 5 seconds for every whitelisted-pro, safe, non-expired market — no more polling the REST endpoint. ## How to use 1. Connect to https://api-v2.pendle.finance, namespace /pendle-v2. 2. Emit subscribe with room id market:<chainId>-<marketAddress>:order-book:precision-<0|1|2|3> (precision is decimal digits …
## Update: Limit Order Expiry & Incentives We are updating our expiry requirements to ensure your orders have sufficient time to be filled and to maintain consistency across our platforms. --- ### New Expiry Requirements * API: Minimum expiry of 5 minutes. * UI: Minimum expiry of 7 minutes (includes a buffer to prevent premature expiration during processing). ### Incentive Eligibility To qualify for incentives, a…
Contract upgrades to support sPendle We expect none of the upgrades to affect readers as they are mostly at incentive levels. Below are the details: - VotingController will no longer be used in the Pendle V2 system. - Gauge controller upgrade: - Reward data will no longer be updated via the voting controller. - Reward data will be updated manually on each chain. - Removed events: - ReceiveVoti…
Introducing Optional `receiver` Parameter in SDK Endpoints We have updated our SDK endpoints so that the receiver parameter is now optional. Validation of Invalid Receivers Begins Soon Starting 12 Dec 2025, we will begin enforcing validation to reject invalid receiver addresses. Examples of invalid receivers include: - The zero address - Pendle market contract addresses Please ensure your applications do not submi…
👍2❤1
Introducing Paid Plans for Higher API Rate Limits We are introducing paid plan for those who want a higher rate. Free users are not affected (rate limit remains 100 CU per minute, 200k CU quota per week). # How does API pricing work? Our pricing is simple and scalable: $10/week = 500 CU/min + 1,000,000 CU/week. You can purchase multiple units to scale your rate limits based on your application's requirements. # H…
❤5
New V6 Factories & Oracle Deployment We've deployed YieldContractFactoryV6, MarketFactoryV6, and updated oracles (PyLpOracle & Chainlink) with enhanced security. All new Pendle PT, YT, and Markets will use these V6 factories. For Developers: - V6 factories are fully backward compatible—no action needed for most integrations - Old oracles remain functional, but we recommend switching to the new oracle for V6 markets…
❤3👏1🥰1
New API: Scaled Order Generation We’ve released a new endpoint that allows you to generate scaled (laddered) limit order data automatically, making it easier to distribute orders across price levels. Check here for the details: https://api-v2.pendle.finance/core/docs#/Limit%20Orders/LimitOrdersController_generateScaledLimitOrderData
❤1🔥1
API Update: We’re changing the default behavior from using all supported aggregators to using a preset selection of aggregators. The update will take effect on 06 Nov 2025. When calling the SDK endpoint with enableAggregator=true without specifying aggregators: Before: All aggregators were used by default. Now: A preset set of aggregators will be used, which may change over time for optimization. If you want to u…
❤3
Reminder that we will remove SDK version 1 API this week! Do migrate to version 2 ASAP!
New Pendle SDK Feature: All-in-one convert API We're excited to announce the new all-in-one convert API for our hosted SDK, offering: ✅ One endpoint for all Pendle interactions with consistent response format Key Information: 1. Benefits: - Unified Interface: One /convert endpoint replaces 12+ individual endpoints - Smart Action Detection: Automatically determines the action (swap, add liquidity, mint PT/Y…
❤6👏1🔥1🥰1
New Tool Launch: Pendle Developer Q&A Bot We’re excited to announce the launch of our new Pendle Developer Q&A Bot, designed to answer your questions about: ✅ API ✅ Contract interactions Key Information: - Get instant answers to your dev, API, and smart contract interaction questions. - Reduce back-and-forth and speed up your development process. - Available 24/7 to support your integration needs. How to use? - S…
❤3🥰1
Showing the 12 most recent of 20 posts we hold for @pendledevelopers. 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 7 October 2026 — this entry's latest reading, not the date you are reading this.
“Pendle Developer Updates” (@pendledevelopers), 232 subscribers as measured 7 October 2026. Telegram Register, tgregister.com/channel/pendledevelopers.
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.