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 need to translate all text, preserving HTML tags. Let's translate paragraph by 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." Finnish: "XRP Ledger -ydinohjelmiston seuraavan version, xrpld 3.3.0:n, odotetaan julkaistavan ensi viikolla. Julkaisu sisältää viisi ehdotettua lisäystä, joista kaksi on tarkistettuja ominaisuuksia, jotka vedettiin aiemmin pois, kun tutkijat havaitsivat kriittisiä bugeja. Nämä bugit olisivat voineet antaa hyökkääjille mahdollisuuden toteuttaa luvattomia tapahtumia tai tyhjentää verkoston maksuja." I need to be careful with "drain fees" – "tyhjentää maksuja" might not be precise. Better: "viedä maksuja" or "kavaltää maksuja"? Actually "fee draining" means siphoning off fees. Could say "tyhjentää verkoston maksuvaroja" or "viedä verkoston maksut". I'll use "viedä verkoston maksuja" but that might be ambiguous. Maybe "tyhjentää verkoston maksut" is fine. Or "imeä verkoston maksuja". I'll use "tyhjentää verkoston maksuja" to be clear. Also "push through unauthorized transactions" – "toteuttaa luvattomia tapahtumia" is fine. Second heading: "Five amendments on the table" -> "Viisi lisäystä pöydällä" but that's literal. Better: "Viisi lisäystä käsiteltävänä" or "Viisi lisäystä esillä". I'll use "Viisi lisäystä käsiteltävänä" but the original "on the table" means under consideration. Could also be "Viisi lisäystä harkinnassa". I'll go with "Viisi lisäystä käsiteltävänä". Then 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." Finnish: "xrpld 3.3.0 -päivitys sisältää viisi ehdotettua muutosta protokollaan. Kehittäjät voivat tarkastella ja äänestää jokaisesta lisäyksestä, kun ohjelmisto on käytössä. Tarkka aikataulu käyttöönotolle riippuu validaattorien yksimielisyydestä, mutta itse julkaisu on suunniteltu ensi viikolle." I used "protokollaan" for "to the ledger's protocol". "Validaattorien" is fine. Third heading: "Two revised features return" -> "Kaksi tarkistettua ominaisuutta palaa" 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." Finnish: "Kaksi viidestä lisäyksestä ei ole uusia. Ne ovat uudelleentyöstettyjä versioita ominaisuuksista, jotka poistettiin aiemmista julkaisuista, kun tietoturvatutkijat löysivät kriittisiä haavoittuvuuksia. Alkuperäiset ehdotukset vedettiin pois estääkseen hyväksikäytön riskin. Nyt korjausten jälkeen ne ovat palanneet uudelleen harkittavaksi." I used "uudelleentyöstettyjä" for "reworked". "Poistettiin" for "yanked". "Vedettiin pois" for "withdrawn". Good. Fourth heading: "What the bugs could have done" -> "Mitä bugit olisivat voineet tehdä" 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." Finnish: "Alkuperäisten versioiden kriittiset bugit olivat vakavia
