Channel
@malda_xyz
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
901subscribers
-5 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002431585044 |
|---|---|
| Type | Channel |
| Username | @malda_xyz |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/malda_xyz |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 14:05 | 901 | -5 |
| 7 Aug 2026, 10:20 | 906 | no change |
| 7 Aug 2026, 01:31 | 906 | first reading |
20 posts held, back to 7 November 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 20 posts for this entry, the most recent from 20 February 2026. An engagement rate over an empty window would be a number about nothing.
93 reactions across 19 posts, in 8 distinct kinds. The most used accounts for 40.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 38 | 40.9% | |
| 🔥 | 29 | 31.2% | |
| 👍 | 8 | 8.60% | |
| 👎 | 8 | 8.60% | |
| ❤🔥 | 5 | 5.38% | |
| 😁 | 3 | 3.23% | |
| 🆒 | 1 | 1.08% | |
| 👏 | 1 | 1.08% |
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 19 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 93reactions 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 7 November 2025 to 20 February 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 can you add an extra layer of security on top of audits and firewall integrations? Phylax introduces preventative security measures with assertions for Malda directly to Linea’s sequencer. How does these assertions work and why are they forced on the Linea chain? Since the host chain for Malda sequencer is Linea, every txn has to go through the sequencer and Linea chain. With Phylax we can set rules such as 1+…
❤4
We picked the top bridges based on cost and speed. Cheapest: CCTP or Wormhole, with fees ranging from 0.01% to 0.14%. Fastest: Across, with sub-second execution. You use these bridges countless times to chase the best APY possible, but what if you didn’t have to? With Malda, you can supply from any supported chain and earn global APY, then borrow on any supported chain in seconds, paying only the borrow interest r…
❤3😁3
Get to know what drives the Department of Trustless Interop…
❤2
Crosschain lending can be complex, and we know the architecture raises questions. To clear the air, we have released The Healthy Anatomy for Crosschain article! In this article, you will find answers to: - What are Host & Extension Chains? - Why do we use this specific structure? - How do the Host & Extension Chains interact? - Why did we choose Linea as the Host Chain? - Why we aren't dependent on the success of …
❤4
Security Stack Update: Integrating Phylax Systems As we prepare for mainnet, our priority is building a security architecture that is proactive and institution-grade. Today, we are proud to announce our integration with Phylax Systems. Phylax operates as a Credible Layer that enforces strict security assertions directly on the Linea Sequencer. What does this mean for our security? To understand Phylax, you have …
🔥4❤1
As we move forward, we want to update you regarding our integration with the new Linea v4 Architecture. In December, Linea deployed its v4 update. While this improves the chain, it introduced some breaking changes in our proof system that required us to make some updates to our codebase. For Malda, this required a specific update to our cross-chain infrastructure to remain fully compatible since keeping our host ch…
👍6
Following the recent updates to the X (Twitter) API policy, we are currently re-evaluating the mechanics for the next phase of Malda Mentions. This change does not affect the Malda infrastructure. Our internal API access remains fully operational. This strictly impacts the third-party tracking tools used for the social campaign. We are using this opportunity to refine the campaign's structure. Our objective remains…
❤3
Don't miss the claim window for the Voluntary Recovery Fund if you are one of the affected users on the May 30th incident. You need to make your claim by December 31st!
🔥5
We are in the final phase of completing Malda’s security measures The remaining steps include sequencer resilience testing, a bug bounty, and final deployment checks. Currently, we are focused on Sequencer resilience testing while preparing the bug bounty setup simultaneously. We'd like to provide more details on the Sequencer Resilience specifically, as this is the most critical task. The sequencer is the backbon…
👎5❤3
The answer to the question on everyone’s minds: Are we well-positioned? We understand the eagerness for mainnet deployment. Please understand that our approach is Product & Security focused, not just timing the market. We view security as the foundation of a lending protocol, and it requires absolute precision. This patience is an investment in our future relevance. The market is primed to focus on ZK and interoper…
🔥2❤1
Are crosschain interactions trustless? Why do we need ZK? The answer is no; crosschain interactions are not trustless, as they depend on multisignatures, nodes, and validators. That's why we need ZK tech. To learn more about how we can achieve trustless interop. with ZK, check the Article below: https://x.com/malda_xyz/status/1998776909174333583?s=20
❤1
Reminder to Claim The Voluntary Recovery Fund! The affected users of May 30th 2025 incident can claim their voluntary recovery fund allocation until 31st of December. Make sure to claim until that date. Claim Site: https://recovery.malda.xyz/ Asset: Distributions are made in USDC, based on the USD value of your position at the time of the incident. Deadline: The claim portal will remain open until December 31, 20…
❤5👍1
Showing the 12 most recent of 20 posts we hold for @malda_xyz. 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.
Citation-graph rank — 1,174,945 of 1,548,671entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“Malda” (@malda_xyz), 901 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/malda_xyz.
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.