Zilliqa Announcement
Kanalga Telegram’da o‘tish
Official Zilliqa Announcement Channel Official Zilliqa chat https://t.me/zilliqachat
Ko'proq ko'rsatish6 173
Obunachilar
-424 soatlar
-247 kunlar
-11330 kunlar
Ma'lumot yuklanmoqda...
O'xshash kanallar
![XDC Network Updates [XDC]](https://cdn.tlmtr.io/_next/image?url=https%3A%2F%2Fimg.telemetr.io%2Fc%2F1ctsHz%2F6138482090145070470%3Fty%3Dx&w=256&q=75)
Taglar buluti
Kirish va chiqish esdaliklari
---
---
---
---
---
---
Obunachilarni jalb qilish
Iyul '26
Iyul '26
+17
1 kanalda
Iyun '26
+12
0 kanalda
Get PRO
May '26
+20
0 kanalda
Get PRO
Aprel '26
+8
0 kanalda
Get PRO
Mart '26
+11
0 kanalda
Get PRO
Fevral '26
+17
4 kanalda
Get PRO
Yanvar '26
+13
0 kanalda
Get PRO
Dekabr '25
+20
2 kanalda
Get PRO
Noyabr '25
+26
0 kanalda
Get PRO
Oktabr '25
+24
0 kanalda
Get PRO
Sentabr '25
+17
0 kanalda
Get PRO
Avgust '25
+36
1 kanalda
Get PRO
Iyul '25
+33
1 kanalda
Get PRO
Iyun '25
+27
2 kanalda
Get PRO
May '25
+28
3 kanalda
Get PRO
Aprel '25
+29
1 kanalda
Get PRO
Mart '25
+22
1 kanalda
Get PRO
Fevral '25
+26
1 kanalda
Get PRO
Yanvar '25
+43
1 kanalda
Get PRO
Dekabr '24
+49
3 kanalda
Get PRO
Noyabr '24
+27
1 kanalda
Get PRO
Oktabr '24
+26
2 kanalda
Get PRO
Sentabr '24
+764
9 kanalda
Get PRO
Avgust '24
+28
2 kanalda
Get PRO
Iyul '24
+19
3 kanalda
Get PRO
Iyun '24
+49
4 kanalda
Get PRO
May '24
+62
3 kanalda
Get PRO
Aprel '24
+54
4 kanalda
Get PRO
Mart '24
+95
5 kanalda
Get PRO
Fevral '24
+41
8 kanalda
Get PRO
Yanvar '24
+49
8 kanalda
Get PRO
Dekabr '23
+77
7 kanalda
Get PRO
Noyabr '23
+28
2 kanalda
Get PRO
Oktabr '23
+23
1 kanalda
Get PRO
Sentabr '23
+20
0 kanalda
Get PRO
Avgust '23
+26
0 kanalda
Get PRO
Iyul '23
+45
0 kanalda
Get PRO
Iyun '23
+25
0 kanalda
Get PRO
May '23
+40
0 kanalda
Get PRO
Aprel '23
+93
0 kanalda
Get PRO
Mart '23
+46
0 kanalda
Get PRO
Fevral '23
+53
0 kanalda
Get PRO
Yanvar '23
+75
0 kanalda
Get PRO
Dekabr '22
+28
0 kanalda
Get PRO
Noyabr '22
+39
0 kanalda
Get PRO
Oktabr '22
+40
0 kanalda
Get PRO
Sentabr '22
+60
0 kanalda
Get PRO
Avgust '22
+67
0 kanalda
Get PRO
Iyul '22
+71
0 kanalda
Get PRO
Iyun '22
+56
0 kanalda
Get PRO
May '22
+87
0 kanalda
Get PRO
Aprel '22
+699
0 kanalda
Get PRO
Mart '22
+443
0 kanalda
Get PRO
Fevral '22
+43
0 kanalda
Get PRO
Yanvar '22
+97
0 kanalda
Get PRO
Dekabr '21
+132
0 kanalda
Get PRO
Noyabr '21
+119
0 kanalda
Get PRO
Oktabr '21
+235
0 kanalda
Get PRO
Sentabr '21
+258
0 kanalda
Get PRO
Avgust '21
+219
0 kanalda
Get PRO
Iyul '21
+209
0 kanalda
Get PRO
Iyun '21
+360
0 kanalda
Get PRO
May '21
+838
0 kanalda
Get PRO
Aprel '21
+804
0 kanalda
Get PRO
Mart '21
+895
0 kanalda
Get PRO
Fevral '21
+642
0 kanalda
Get PRO
Yanvar '21
+451
0 kanalda
Get PRO
Dekabr '20
+10 832
0 kanalda
| Sana | Obunachilarni jalb qilish | Esdaliklar | Kanallar | |
| 20 Iyul | +6 | |||
| 19 Iyul | +1 | |||
| 18 Iyul | 0 | |||
| 17 Iyul | +2 | |||
| 16 Iyul | 0 | |||
| 15 Iyul | +1 | |||
| 14 Iyul | +2 | |||
| 13 Iyul | +2 | |||
| 12 Iyul | +1 | |||
| 11 Iyul | 0 | |||
| 10 Iyul | 0 | |||
| 09 Iyul | 0 | |||
| 08 Iyul | 0 | |||
| 07 Iyul | 0 | |||
| 06 Iyul | +1 | |||
| 05 Iyul | 0 | |||
| 04 Iyul | 0 | |||
| 03 Iyul | 0 | |||
| 02 Iyul | +1 | |||
| 01 Iyul | 0 |
Kanal postlari
As our investigation has progressed, we would like to clarify one important point:
At this stage, we have found no evidence that the incident was caused by the exchange’s wallet management or operational processes. We appreciate the exchange’s cooperation in identifying the issue quickly and assisting throughout the investigation.
The investigation has instead identified a technical issue affecting transaction signing in a specific set of legacy ZIL1 wallets. We are continuing to verify the precise root cause before publishing a detailed technical report.
We will share a full post-mortem, including technical findings and any recommended actions, as soon as the investigation is complete.
Thank you for your patience while we work to ensure the information we share is accurate.
| 2 | We have been made aware of a security incident involving one of our exchange partners, in which ZIL was stolen from a cold wallet.
The incident is under active investigation, and we are working with the relevant parties to establish the root cause and full scope. As a precaution, all exchanges have been notified and asked to temporarily pause ZIL deposits and withdrawals to prevent the stolen funds from being moved or sold through centralised platforms.
We understand the community will have questions. We will share further updates as soon as we have verified information. Please rely only on official Zilliqa channels for updates. | 540 |
| 3 |  A question institutional teams ask: why not just run a compliance layer over an existing settlement chain?
On a chain built to settle first, settlement is the state transition; permission would have to be built into the definition of a valid transaction, not added after it. You cannot retrofit that.
The new post works through the architecture, and through the two-hander it depends on: LTIN issues the identity, Zilliqa runs the check beside it. https://blog.zilliqa.com/mediation-defined/ | 844 |
| 4 |  August 2022. A counterparty already on the sanctions list. The payment goes out in USDT - the issuer doesn't block on designation, so it confirms and settles like any other transfer. Send the same value in USDC and the token itself would have refused it; on a permissionless rail you don't get to choose what your counterparty holds.
Screening happens afterward: a disclosure filed, the transfer still standing. Enforcement that depends on which coin moved isn't enforcement.
The fix is a permission check before settlement - run beside the rail, not by it.
- Identity issued by LTIN
- checked by Zilliqa before a transaction settles
That is what this partnership is built for. | 740 |
| 5 |  A new chapter, not a new pitch.
LTIN and Zilliqa first started building together at LTIN's launch last October; today it becomes a partnership, which creates a new category. LTIN issues the verifiable identity; Zilliqa runs the neutral check that confirms permission before a transaction settles, beside it, on any chain.
Follow along. https://www.ltin.li/insights/ltin-and-zilliqa-deepen-partnership-to-build-trustworthy-global-digital-infrastructure-as-a-public-good | 1 227 |
| 6 |  The roadmap is live - and there's a blog post explaining the thinking behind it.
Short version: Institutional blockchain finance has always settled first, checked
compliance after. Zilliqa is built to run that check before - on any chain or
settlement rail. The roadmap sets out how we build that infrastructure from now
through 2027, phase by phase, each step tied to something we ship.
Read the blog: https://blog.zilliqa.com/compliance-before-settlement-the-zilliqa-roadmap/
Read the roadmap: https://zilliqa.com/roadmap
More to come later this year. For now - this is the direction, on the record.
Tell us what you think. | 1 398 |
| 7 |  Protofire has completed a major upgrade across the Zilliqa Safe stack.
What's new for users?
- Better protection against scams and address poisoning attacks
- Faster loading and fewer delays thanks to backend and performance upgrades
- Export your transaction history to CSV
- Batch multiple transactions together, including existing transaction batches
- Improved WalletConnect experience when switching networks
- Safe account limit increased from 10 to 40
- Cleaner signing flow with clearer transaction status
- Automatic execution option when enough signatures have been collected
Behind the scenes, the infrastructure has also been upgraded to improve reliability, scalability, and security across the platform.
This release lays the groundwork for upcoming features including:
Spaces - shared workspaces for teams and organisations
Nested Safes - manage Safes within Safes with a dedicated interface
Built on the trusted Safe protocol, Zilliqa Safe continues to improve with stronger security, better usability, and a smoother overall experience.
Try now: https://safe.zilliqa.com/home | 1 530 |
| 8 | Zilliqa mainnet will undergo a scheduled upgrade with the release of v0.21.0, introducing improvements to performance, security, and validator infrastructure.
Key upgrades:
• State pruning for better storage efficiency
• RANDAO support for improved randomness in consensus
• Deposit contract upgrade (deposit_v8)
• Flexible checkpoint versioning for smoother recovery and upgrades
Upgrade timeline (mainnet):
• Deposit_v8 activation - Block 25,902,000 (~May 5, 08:37 UTC)
• RANDAO activation - Block 25,905,600 (~May 5, 09:49 UTC)
Validators and node operators have already been notified and have upgraded ahead of these block heights. If any validator has not upgraded yet, please do so at earliest.
Community: No action is required. Funds remain SAFU.
More details: https://github.com/Zilliqa/zq2/releases/tag/v0.21.0 | 1 240 |
