Loading market data...

La versión 3.3.0 de xrpld de XRP Ledger trae de vuelta dos enmiendas previamente retiradas

La versión 3.3.0 de xrpld de XRP Ledger trae de vuelta dos enmiendas previamente retiradas

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.

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 to Spanish. We'll translate each paragraph. Let's do it step by step. Title: "La versión 3.3.0 de xrpld de XRP Ledger trae de vuelta dos enmiendas previamente retiradas" Content: 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: "La próxima versión del software principal de XRP Ledger, xrpld 3.3.0, se espera que se lance la próxima semana. La versión incluye cinco enmiendas propuestas, dos de las cuales son características revisadas que se retiraron anteriormente después de que los investigadores señalaran errores críticos. Esos errores podrían haber permitido a los atacantes realizar transacciones no autorizadas o drenar tarifas de la red." But we should be careful: "push through" might be "llevar a cabo" or "forzar". "drain fees" = "drenar tarifas" or "desviar comisiones". Use "tarifas" or "comisiones". Let's use "comisiones" for fees? Actually in crypto context, "fees" often translated as "comisiones" or "tarifas". We'll use "tarifas" as it's common. But "drenar tarifas" might sound odd. Could say "sustraer tarifas" or "vaciar las tarifas". Let's use "drenar las tarifas" or "desviar las tarifas". I'll use "drenar las tarifas de la red". Second 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: "La actualización xrpld 3.3.0 incluye cinco cambios propuestos al protocolo del libro mayor. Los desarrolladores tendrán la oportunidad de revisar y votar cada enmienda una vez que el software esté en vivo. El cronograma exacto para la adopción depende del consenso de los validadores, pero el lanzamiento en sí está previsto para la próxima semana." Third 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: "Dos de las cinco enmiendas no son nuevas. Son versiones reelaboradas de características que fueron retiradas de versiones anteriores después de que los investigadores de seguridad encontraran vulnerabilidades críticas. Las propuestas originales fueron retiradas para prevenir cualquier riesgo de explotación. Ahora, después de las correcciones, vuelven para otra ronda de consideración." Fourth 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: "Los errores críticos en las versiones originales eran graves. Uno podría haber permitido transacciones no autorizadas, lo que significa que un atacante podría haber movido fondos sin la autorización adecuada. El otro podría haber habilitado el drenaje de tarifas, donde alguien podría desviar las tarifas de transacción del uso previsto de la red. Ambos fueron detectados antes de que ocurriera daño en el mundo real." Fifth paragraph: "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." Translation: "El lanzamiento de xrpld 3.3.0 se espera para la próxima semana. Una vez que esté disponible, los validadores revisarán las cinco enmiendas y decidirán si las adoptan. Las dos características revisadas deberán pasar por el mismo proceso de votación que cualquier otra enmienda. Aún no se ha establecido una fecha para esa votación." 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." Translation: "El lanzamiento de xrpld 3.3.0 de XRP Ledger la próxima semana incluye cinco enmiendas propuestas, dos de las cuales son características revisadas retiradas anteriormente después de errores críticos que podrían permitir transacciones no autorizadas o drenaje de tarifas." Now we need to output as JSON. Ensure we preserve HTML structure exactly with tags. We'll put the translated content inside the
tags. Let's assemble. Note: We should keep the h2 tags as well. So final JSON: { "title": "La versión 3.3.0 de xrpld de XRP Ledger trae de vuelta dos enmiendas previamente retiradas", "content": "

La próxima versión del software principal de XRP Ledger, xrpld 3.3.0, se espera que se lance la próxima semana. La versión incluye cinco enmiendas propuestas, dos de las cuales son características revisadas que se retiraron anteriormente después de que los investigadores señalaran errores críticos. Esos errores podrían haber permitido a los atacantes realizar transacciones no autorizadas o drenar las tarifas de la red.

Cinco enmiendas sobre la mesa

La actualización xrpld 3.3.0 incluye cinco cambios propuestos al protocol