Five amendments on the table
The xrpld 3.3.0 update bundles five proposed changes to the ledger's protocol. Developers will have a chance to review and vote on each amendment once the software is live. The exact timeline for adoption depends on validator consensus, but the release itself is slated for next week.
Two revised features return
Two of the five amendments are not new. They're reworked versions of features that were yanked from earlier releases after security researchers found critical vulnerabilities. The original proposals were withdrawn to prevent any risk of exploitation. Now, after fixes, they're back for another round of consideration.
What the bugs could have done
The critical bugs in the original versions were serious. One could have allowed unauthorized transactions — meaning an attacker might have been able to move funds without proper authorization. The other could have enabled fee draining, where someone could siphon transaction fees away from the network's intended use. Both were caught before any real-world damage occurred.
What happens next
The xrpld 3.3.0 release is expected next week. Once it's out, validators will review the five amendments and decide whether to adopt them. The two revised features will need to pass the same voting process as any other amendment. No date has been set for that vote yet.
We'll translate to Turkish. Keep HTML structure. Meta description: "XRP Ledger's xrpld 3.3.0 release next week includes five proposed amendments, two of which are revised features previously withdrawn after critical bugs that could allow unauthorized transactions or fee draining." Translate. Let's do it step by step. Title: "XRP Ledger'ın xrpld 3.3.0 Sürümü Daha Önce Geri Çekilen İki Değişikliği Geri Getiriyor" - but "Değişiklik" might be "Amendments" - in crypto context, "amendments" are protocol changes. We can use "değişiklik" or "öneri" but "amendment" is often "değişiklik" or "düzenleme". Since it's a technical term, we can keep "amendment" as is? But the requirement says use appropriate Turkish terminology. In Turkish crypto community, they might use "değişiklik" or "öneri". I'll use "değişiklik" but maybe "protokol değişikliği" is clearer. However, the title is short. I'll go with: "XRP Ledger'ın xrpld 3.3.0 Sürümü, Daha Önce Geri Çekilen İki Değişikliği Geri Getiriyor" But we need to ensure proper nouns: XRP Ledger, xrpld. So: "XRP Ledger'ın xrpld 3.3.0 Sürümü Daha Önce Geri Çekilen İki Değişikliği Geri Getiriyor" (without comma maybe fine). Now content: We'll translate each paragraph. First paragraph: "The next version of the core XRP Ledger software, xrpld 3.3.0, is expected to ship next week. The release includes five proposed amendments, two of which are revised features that were previously pulled after researchers flagged critical bugs. Those bugs could have let attackers push through unauthorized transactions or drain fees from the network." Translation: "Çekirdek XRP Ledger yazılımının bir sonraki sürümü olan xrpld 3.3.0'ın önümüzdeki hafta yayınlanması bekleniyor. Sürüm, beş önerilen değişiklik içeriyor; bunlardan ikisi, araştırmacıların kritik hatalar tespit etmesinin ardından daha önce geri çekilen revize edilmiş özelliklerdir. Bu hatalar, saldırganların yetkisiz işlemler yapmasına veya ağdan ücretleri çekmesine olanak tanıyabilirdi." We need to preserve HTML:...
Second heading: "Five amendments on the table" -> "Masada Beş Değişiklik" or "Beş Değişiklik Masada" - I'll use "Masada Beş Değişiklik" but better: "Beş Değişiklik Masada" - Actually heading: "Five amendments on the table" -> "Masada Beş Değişiklik" is fine. Paragraph: "The xrpld 3.3.0 update bundles five proposed changes to the ledger's protocol. Developers will have a chance to review and vote on each amendment once the software is live. The exact timeline for adoption depends on validator consensus, but the release itself is slated for next week." Translation: "xrpld 3.3.0 güncellemesi, defterin protokolüne yönelik beş önerilen değişikliği bir araya getiriyor. Yazılım canlıya alındığında geliştiriciler her değişikliği inceleme ve oylama şansına sahip olacak. Benimseme için kesin zaman çizelgesi doğrulayıcı mutabakatına bağlı, ancak sürümün kendisi önümüzdeki hafta için planlanıyor." Third heading: "Two revised features return" -> "İki Revize Özellik Geri Dönüyor" or "Revize Edilmiş İki Özellik Geri Dönüyor" - I'll use "İki Revize Özellik Geri Dönüyor" Paragraph: "Two of the five amendments are not new. They're reworked versions of features that were yanked from earlier releases after security researchers found critical vulnerabilities. The original proposals were withdrawn to prevent any risk of exploitation. Now, after fixes, they're back for another round of consideration." Translation: "Beş değişiklikten ikisi yeni değil. Bunlar, güvenlik araştırmacılarının kritik güvenlik açıkları bulmasının ardından önceki sürümlerden çekilen özelliklerin yeniden işlenmiş sürümleridir. Orijinal öneriler, herhangi bir istismar riskini önlemek için geri çekilmişti. Şimdi, düzeltmelerden sonra, bir kez daha değerlendirilmek üzere geri döndüler." Fourth heading: "What the bugs could have done" -> "Hatalar Ne Yapabilirdi?" or "Hataların Yapabilecekleri" - I'll use "Hatalar Ne Yapabilirdi?" Paragraph: "The critical bugs in the original versions were serious. One could have allowed unauthorized transactions — meaning an attacker might have been able to move funds without proper authorization. The other could have enabled fee draining, where someone could siphon transaction fees away from the network's intended use. Both were caught before any real-world damage occurred." Translation: "Orijinal sürümlerdeki kritik hatalar ciddiydi. Biri yetkisiz işlemlere izin verebilirdi; yani bir saldırgan, uygun yetkilendirme olmadan fonları hareket ettirebilirdi. Diğeri, birinin işlem ücretlerini ağın amaçlanan k
