From c3194d9b0830a83c259b01bdfc6b2c64a010728d Mon Sep 17 00:00:00 2001 From: mDuo13 Date: Thu, 28 Mar 2024 15:29:50 -0700 Subject: [PATCH] =?UTF-8?q?Blog:=20migrate=20metadata=20for=202014?= =?UTF-8?q?=E2=80=932019?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Also, adjust some formatting for Redocly (admonitions, indented code blocks, authorship lines) --- .../biweekly-release-notes-14-august-2014.md | 10 ++++ ...iweekly-release-notes-17-september-2014.md | 10 ++++ ...biweekly-release-notes-3-september-2014.md | 10 ++++ .../biweekly-release-notes-31-july-2014.md | 10 ++++ blog/2014/curves-with-a-twist.md | 10 ++++ blog/2014/dev-portal-adds-rippled-apis.md | 13 ++++- ...ateway-advisory-on-partial-payment-flag.md | 10 ++++ .../2014/how-ripple-labs-supports-gateways.md | 14 ++++- blog/2014/introducing-offer-autobridging.md | 13 ++++- blog/2014/introducing-ripple-names.md | 10 ++++ blog/2014/release-notes-14-october-2014.md | 10 ++++ blog/2014/release-notes-19-november-2014.md | 10 ++++ blog/2014/release-notes-29-october-2014.md | 10 ++++ blog/2014/release-notes-3-december-2014.md | 10 ++++ ...bs-bounty-program-moves-to-bountysource.md | 13 ++++- blog/2014/ripplerest-1.3-release.md | 10 ++++ ...urn-your-exchange-into-a-ripple-gateway.md | 8 +++ blog/2014/use-of-cpp14-in-rippled.md | 13 ++++- ...ar-forking-issue-does-not-affect-ripple.md | 11 ++++ blog/2014/xrp-giveaway-for-developers.md | 12 ++++- ...ating-balance-changes-for-a-transaction.md | 11 ++++ blog/2015/correction-to-ripple-white-paper.md | 10 ++++ ...-you-have-what-it-takes-to-be-a-gateway.md | 8 +++ blog/2015/gatewayd-no-longer-available.md | 10 ++++ blog/2015/introducing-the-data-api.md | 10 ++++ ...-update-payment-volume-and-issued-value.md | 10 ++++ blog/2015/validator-registry.md | 10 ++++ blog/2016/data-api-v2.2.md | 10 ++++ blog/2016/flow-available.md | 10 ++++ blog/2016/flow-reminder.md | 10 ++++ blog/2016/flow-voting.md | 10 ++++ blog/2016/flowv2-vetoed.md | 18 ++++--- blog/2016/flowv2-voting.md | 10 ++++ blog/2016/introducing-rippleapi.md | 10 ++++ blog/2016/multisign-available.md | 10 ++++ blog/2016/multisign-reminder.md | 12 ++++- blog/2016/rippled-0.30.1.md | 10 ++++ blog/2016/rippled-0.31.2-updates.md | 10 ++++ blog/2016/rippled-0.32.0.md | 10 ++++ blog/2016/rippled-0.32.1.md | 10 ++++ blog/2016/rippled-0.33.0-hf1.md | 10 ++++ blog/2016/rippled-0.33.0.md | 10 ++++ blog/2016/rippled-0.40.0.md | 10 ++++ blog/2016/testnet-ledger-reset.md | 12 ++++- blog/2016/trustsetauth-available.md | 10 ++++ blog/2016/trustsetauth-reminder.md | 13 ++++- blog/2016/trustsetauth-voting.md | 10 ++++ blog/2017/data-api-load-balancing-test.md | 10 ++++ blog/2017/decent-strategy-update.md | 10 ++++ blog/2017/escrow-paychan-fix1368-reminder.md | 10 ++++ .../2017/explanation-of-ripples-xrp-escrow.md | 10 ++++ blog/2017/high-scalability-xrp-ledger.md | 10 ++++ blog/2017/invariant-checking.md | 13 ++++- blog/2017/response-to-china-cert-report.md | 10 ++++ ...an-sustain-1000-transactions-per-second.md | 10 ++++ blog/2017/rippled-0.40.1.md | 10 ++++ blog/2017/rippled-0.50.0.md | 10 ++++ blog/2017/rippled-0.50.2.md | 11 ++++ blog/2017/rippled-0.50.3.md | 10 ++++ blog/2017/rippled-0.60.0.md | 10 ++++ blog/2017/rippled-0.60.1.md | 10 ++++ blog/2017/rippled-0.60.2-2-rpm.md | 10 ++++ blog/2017/rippled-0.60.2.md | 10 ++++ blog/2017/rippled-0.60.3.md | 10 ++++ blog/2017/rippled-0.70.0.md | 10 ++++ blog/2017/rippled-0.70.1.md | 16 +++++- blog/2017/rippled-0.70.2.md | 10 ++++ blog/2017/rippled-0.80.0.md | 10 ++++ blog/2017/rippled-0.80.2.md | 10 ++++ blog/2017/ticksize-3days.md | 10 ++++ blog/2017/ticksize-7days.md | 10 ++++ blog/2017/ticksize-available.md | 10 ++++ blog/2017/ticksize-voting.md | 10 ++++ blog/2017/trust-line-quality-sendmax.md | 12 ++++- blog/2018/data-api-validations-changes.md | 10 ++++ blog/2018/depositauth-fix1513-available.md | 10 ++++ blog/2018/depositpreauth-fix1515-enabled.md | 10 ++++ blog/2018/fix1543-fix1571-fix1623-voting.md | 10 ++++ blog/2018/fix1571-enabled.md | 10 ++++ blog/2018/introducing-history-sharding.md | 10 ++++ blog/2018/ripple-lib-1.0.0.md | 12 ++++- blog/2018/rippled-0.81.0.md | 10 ++++ blog/2018/rippled-0.90.0.md | 10 ++++ blog/2018/rippled-0.90.1.md | 10 ++++ blog/2018/rippled-1.0.0.md | 10 ++++ blog/2018/rippled-1.0.1.md | 10 ++++ blog/2018/rippled-1.1.0.md | 10 ++++ blog/2018/rippled-1.1.1.md | 20 +++++-- blog/2018/rippled-1.1.2.md | 10 ++++ blog/2018/rippled-boost166-warning.md | 11 ++++ .../2018/rippled-validator-key-replacement.md | 54 +++++++++++-------- ...rections-to-data-api-xrp-charts-metrics.md | 6 ++- blog/2019/discover-xrp-ledger-explorer.md | 10 ++++ blog/2019/fix1578-enabled.md | 10 ++++ blog/2019/fix1578-expected.md | 10 ++++ blog/2019/fixmasterkeyasregularkey-1day.md | 10 ++++ blog/2019/fixmasterkeyasregularkey-enabled.md | 12 ++++- .../2019/fixmasterkeyasregularkey-expected.md | 10 ++++ blog/2019/fixtakerdryofferremoval-enabled.md | 12 ++++- blog/2019/interledger-checkin.md | 10 ++++ blog/2019/labeling-the-internet-of-value.md | 9 +++- blog/2019/multisignreserve-enabled.md | 10 ++++ blog/2019/multisignreserve-expected.md | 10 ++++ blog/2019/rippled-1.2.0.md | 10 ++++ blog/2019/rippled-1.2.1.md | 10 ++++ blog/2019/rippled-1.2.2.md | 10 ++++ blog/2019/rippled-1.2.3.md | 10 ++++ blog/2019/rippled-1.2.4.md | 10 ++++ blog/2019/rippled-1.3.1.md | 10 ++++ blog/2019/rippled-1.4.0.md | 10 ++++ blog/2019/secure-development-practices.md | 14 ++++- ...atement-on-the-biased-nonce-sense-paper.md | 10 ++++ blog/2019/testnet-reset.md | 16 +++++- blog/2019/websocket-tool-update.md | 10 ++++ blog/2019/welcome-to-xrpl-org.md | 10 ++++ blog/2019/xrpl-devnet-launch.md | 10 ++++ .../2020/requirefullycanonicalsig-expected.md | 1 - blog/2020/rippled-1.4.0-upgrade-advisory.md | 1 - blog/2020/rippled-1.5.0.md | 2 +- blog/2020/running-an-xrp-ledger-validator.md | 2 +- blog/2021/introducing-xrpl-js.md | 2 +- .../introducing-xrpl-py-for-pythonistas.md | 2 +- ...tions-pt-1-proposal-validation-relaying.md | 3 +- blog/2021/xrpl-node-configurator.md | 2 +- blog/2022/introducing-xrpl-py-2.0.0beta.md | 8 +-- 125 files changed, 1215 insertions(+), 77 deletions(-) diff --git a/blog/2014/biweekly-release-notes-14-august-2014.md b/blog/2014/biweekly-release-notes-14-august-2014.md index b78d8b106a..94b18df9c4 100644 --- a/blog/2014/biweekly-release-notes-14-august-2014.md +++ b/blog/2014/biweekly-release-notes-14-august-2014.md @@ -1,3 +1,13 @@ +--- +date: 2014-08-14 +category: 2014 +labels: + - Release Notes +theme: + markdown: + editPage: + hide: true +--- # Biweekly Release Notes (14 August 2014) _Release notes are part of a larger overhaul of our developer resources, which we are continually adding to. Curated release notes will be posted on this blog and will include updates from every active project. Specifically we will post and link to any new release notes, open bounties, and upcoming features. We hope you find these useful! Please let us know if you have feedback in the comments._ diff --git a/blog/2014/biweekly-release-notes-17-september-2014.md b/blog/2014/biweekly-release-notes-17-september-2014.md index b454942716..8c29540065 100644 --- a/blog/2014/biweekly-release-notes-17-september-2014.md +++ b/blog/2014/biweekly-release-notes-17-september-2014.md @@ -1,3 +1,13 @@ +--- +date: 2014-07-17 +category: 2014 +labels: + - Release Notes +theme: + markdown: + editPage: + hide: true +--- # Biweekly release notes (17 September 2014) *Curated release notes will be posted on this blog and will include updates from every active project. Specifically we will post and link to any new release notes, open bounties, and upcoming features.* diff --git a/blog/2014/biweekly-release-notes-3-september-2014.md b/blog/2014/biweekly-release-notes-3-september-2014.md index 53cc95f39b..8b0e385cfa 100644 --- a/blog/2014/biweekly-release-notes-3-september-2014.md +++ b/blog/2014/biweekly-release-notes-3-september-2014.md @@ -1,3 +1,13 @@ +--- +date: 2014-07-03 +category: 2014 +labels: + - Release Notes +theme: + markdown: + editPage: + hide: true +--- # Biweekly Release Notes (3 September 2014) *A few days tardy, but better late than never...* *Curated release notes will be posted on this blog and will include updates from every active project. Specifically we will post and link to any new release notes, open bounties, and upcoming features.* *We hope you find these useful! Please let us know if you have feedback in the comments.* diff --git a/blog/2014/biweekly-release-notes-31-july-2014.md b/blog/2014/biweekly-release-notes-31-july-2014.md index 745cab4659..7992ef0dd9 100644 --- a/blog/2014/biweekly-release-notes-31-july-2014.md +++ b/blog/2014/biweekly-release-notes-31-july-2014.md @@ -1,3 +1,13 @@ +--- +date: 2014-07-31 +category: 2014 +labels: + - Release Notes +theme: + markdown: + editPage: + hide: true +--- # Biweekly release notes (31 July 2014) Starting today, Ripple Labs will release curated release notes on a bi-weekly basis to ensure better communication with the developer community about ongoing projects. diff --git a/blog/2014/curves-with-a-twist.md b/blog/2014/curves-with-a-twist.md index 1016f16fe5..11c7a97ec7 100644 --- a/blog/2014/curves-with-a-twist.md +++ b/blog/2014/curves-with-a-twist.md @@ -1,3 +1,13 @@ +--- +date: 2014-06-26 +category: 2014 +labels: + - Features +theme: + markdown: + editPage: + hide: true +--- # Curves with a Twist Ripple Labs is considering the addition of a new elliptic curve implementation to the Ripple protocol to complement the existing cryptographic system. The addition of a Schnorr-based cryptosystem will produce more optimal and secure design schemes and provides a platform for robust and sophisticated functionality while preserving existing network structure and efficiency. diff --git a/blog/2014/dev-portal-adds-rippled-apis.md b/blog/2014/dev-portal-adds-rippled-apis.md index e33b6faaad..b2a87968ad 100644 --- a/blog/2014/dev-portal-adds-rippled-apis.md +++ b/blog/2014/dev-portal-adds-rippled-apis.md @@ -1,7 +1,16 @@ +--- +category: 2014 +date: 2014-08-01 +labels: + - Development +theme: + markdown: + editPage: + hide: true +author: Rome Reginelli +--- # Dev Portal Adds rippled APIs -_By Rome Reginelli, technical writer_ - Today, the [Ripple Dev Portal](https://developers.ripple.com/) gets a big boost of content and usability. The new additions to our development portal include thorough and tested documentation of all the public API methods for our core server software, ‘rippled’, alongside a host of improvements in styling and formatting, as well as new introductory material to give you direction in navigating the sea of Ripple technology. This update brings very crucial content into the fold of documentation that's thorough, complete, and software-tested. Today, you can access [full specs and usage information for all 20+ public methods in the rippled WebSocket API](https://developers.ripple.com/rippled-api.html). diff --git a/blog/2014/gateway-advisory-on-partial-payment-flag.md b/blog/2014/gateway-advisory-on-partial-payment-flag.md index 50f1c4e77e..20ddd9e073 100644 --- a/blog/2014/gateway-advisory-on-partial-payment-flag.md +++ b/blog/2014/gateway-advisory-on-partial-payment-flag.md @@ -1,3 +1,13 @@ +--- +date: 2014-10-22 +category: 2014 +labels: + - Advisories +theme: + markdown: + editPage: + hide: true +--- # Gateway Advisory On Partial Payment Flag Ripple Labs has issued a Gateway Bulletin on the Partial Payment flag which describes the flag and best practices around balancing activity on and off the ledger. The tfPartialPayment flag is set by the sender to specify a payment where the beneficiary can receive less than the specified amount. diff --git a/blog/2014/how-ripple-labs-supports-gateways.md b/blog/2014/how-ripple-labs-supports-gateways.md index 543453fbd7..977eb13f67 100644 --- a/blog/2014/how-ripple-labs-supports-gateways.md +++ b/blog/2014/how-ripple-labs-supports-gateways.md @@ -1,9 +1,19 @@ +--- +category: 2014 +date: 2014-09-22 +theme: + markdown: + editPage: + hide: true +--- # How Ripple Labs supports gateways -
This program is no longer active.
- _To help accelerate the creation of strong, reliable, and compliant gateways, Ripple Labs will be providing XRP incentives and extended technical support for gateways that meet criteria considered to be critical for the success of a gateway._ +{% admonition type="danger" %} +This program is no longer active. +{% /admonition %} + Ripple Labs wants every gateway to achieve a gold standard in business planning, technical reliability and stability, regulatory compliance, and liquidity. The Ripple protocol enables the federation and interoperability of many independent payment systems. As such, we’re actively developing the specifications for [Gateway Services APIs](https://ripple.com/wiki/Gateway_Services) and are eager to help gateways with implementation. In the meantime, here are some of the steps and assistance provided by Ripple Labs to help get your gateway to that point. diff --git a/blog/2014/introducing-offer-autobridging.md b/blog/2014/introducing-offer-autobridging.md index cd332b03e3..c8d3588456 100644 --- a/blog/2014/introducing-offer-autobridging.md +++ b/blog/2014/introducing-offer-autobridging.md @@ -1,7 +1,16 @@ +--- +date: 2014-07-02 +category: 2014 +labels: + - Features +theme: + markdown: + editPage: + hide: true +author: Nikolaos D. Bougalis +--- # Introducing: Offer Autobridging -_By Nikolaos D. Bougalis_ - Ripple’s powerful system allows payments between any source and destination currency to be made easily. Pathfinding considers multiple conversions between currencies to find the best rate for a payment. The new **autobridging** feature improves offer placement in a similar fashion to pathfinding: when consuming existing offers, a newly placed offer will have the liquidity available in not only the direct order book (source to destination currency) but also in the corresponding books in which XRP is the destination and source respectively. diff --git a/blog/2014/introducing-ripple-names.md b/blog/2014/introducing-ripple-names.md index 19ea06fdaf..6865404116 100644 --- a/blog/2014/introducing-ripple-names.md +++ b/blog/2014/introducing-ripple-names.md @@ -1,3 +1,13 @@ +--- +date: 2014-04-28 +category: 2014 +labels: + - Features +theme: + markdown: + editPage: + hide: true +--- # Introducing Ripple Names Ripple names work in conjunction with Ripple addresses as a destination to receive funds, as an identifier for the sender, and as a handle to set trustlines. diff --git a/blog/2014/release-notes-14-october-2014.md b/blog/2014/release-notes-14-october-2014.md index 21c63713fc..e778fef553 100644 --- a/blog/2014/release-notes-14-october-2014.md +++ b/blog/2014/release-notes-14-october-2014.md @@ -1,3 +1,13 @@ +--- +date: 2014-10-14 +category: 2014 +labels: + - Release Notes +theme: + markdown: + editPage: + hide: true +--- # Release Notes (14 October 2014) *Curated release notes will be posted on this blog and will include updates from every active project. Specifically we will post and link to any new release notes, open bounties, and upcoming features.* diff --git a/blog/2014/release-notes-19-november-2014.md b/blog/2014/release-notes-19-november-2014.md index 5187bafc34..aeefe65443 100644 --- a/blog/2014/release-notes-19-november-2014.md +++ b/blog/2014/release-notes-19-november-2014.md @@ -1,3 +1,13 @@ +--- +category: 2014 +date: 2014-11-19 +labels: + - Release Notes +theme: + markdown: + editPage: + hide: true +--- # Release Notes (19 November 2014) *Curated release notes will be posted on this blog and will include updates from every active project. Specifically we will post and link to any new release notes, open bounties, and upcoming features.* diff --git a/blog/2014/release-notes-29-october-2014.md b/blog/2014/release-notes-29-october-2014.md index 7beeff81b5..238e7ee0e3 100644 --- a/blog/2014/release-notes-29-october-2014.md +++ b/blog/2014/release-notes-29-october-2014.md @@ -1,3 +1,13 @@ +--- +category: 2014 +date: 2014-10-29 +labels: + - Release Notes +theme: + markdown: + editPage: + hide: true +--- # Release Notes (29 October 2014) *Curated release notes will be posted on this blog and will include updates from every active project. Specifically we will post and link to any new release notes, open bounties, and upcoming features.* diff --git a/blog/2014/release-notes-3-december-2014.md b/blog/2014/release-notes-3-december-2014.md index 04059e4ad1..8d12287bb0 100644 --- a/blog/2014/release-notes-3-december-2014.md +++ b/blog/2014/release-notes-3-december-2014.md @@ -1,3 +1,13 @@ +--- +date: 2014-12-03 +category: 2014 +labels: + - Release Notes +theme: + markdown: + editPage: + hide: true +--- # Release Notes (3 December 2014) *Curated release notes will be posted on this blog and will include updates from every active project. Specifically we will post and link to any new release notes, open bounties, and upcoming features.* diff --git a/blog/2014/ripple-labs-bounty-program-moves-to-bountysource.md b/blog/2014/ripple-labs-bounty-program-moves-to-bountysource.md index 6ccaab17df..3de60c019c 100644 --- a/blog/2014/ripple-labs-bounty-program-moves-to-bountysource.md +++ b/blog/2014/ripple-labs-bounty-program-moves-to-bountysource.md @@ -1,7 +1,16 @@ +--- +category: 2014 +date: 2014-07-07 +labels: + - Advisories +theme: + markdown: + editPage: + hide: true +author: Daniel Radding +--- # Ripple Labs Bounty Program Moves To Bountysource -_Posted by Daniel Radding_ - The Ripple Labs Bounty Program is moving to its [new home at Bountysource](https://www.bountysource.com/teams/ripple/bounties), a vibrant and robust bounty marketplace that will make paid contributions to the Ripple source code more effective and efficient. One of the major benefits of Bountysource is its seamless GitHub integration. You can view Ripple GitHub projects on our team page. Bountysource automatically pulls open issues from these projects. Issues from JIRA can be manually added with a deeplink. diff --git a/blog/2014/ripplerest-1.3-release.md b/blog/2014/ripplerest-1.3-release.md index d2ee2cb094..a5db79eb9d 100644 --- a/blog/2014/ripplerest-1.3-release.md +++ b/blog/2014/ripplerest-1.3-release.md @@ -1,3 +1,13 @@ +--- +category: 2014 +date: 2014-11-04 +labels: + - Release Notes +theme: + markdown: + editPage: + hide: true +--- # ripple-rest 1.3 release Last Friday we did a master release of ripple-rest version 1.3.0. We’ve done a few changes externally but the substantial additions in 1.3.0 have been stability and verbose error handling. If you’ve been following the commits on [github](https://github.com/ripple/ripple-rest), we’ve also vastly improved test coverage and introduced simplicity by removing the need for Postgres. diff --git a/blog/2014/turn-your-exchange-into-a-ripple-gateway.md b/blog/2014/turn-your-exchange-into-a-ripple-gateway.md index 42c89dd14f..e20e21601f 100644 --- a/blog/2014/turn-your-exchange-into-a-ripple-gateway.md +++ b/blog/2014/turn-your-exchange-into-a-ripple-gateway.md @@ -1,3 +1,11 @@ +--- +category: 2014 +date: 2014-12-18 +theme: + markdown: + editPage: + hide: true +--- # Turn your exchange into a Ripple Gateway Throughout 2014 we've talked to businesses all over the world, both big and small, who are interested in tapping into Ripple's increasing liquidity and settlement capabilities. For exchanges dealing in bitcoins and other assets, the value proposition is clear - deeper orderbooks and the ability for customers to hop between different assets instantly is a major boon to their service. The natural follow-up question is how to get started. diff --git a/blog/2014/use-of-cpp14-in-rippled.md b/blog/2014/use-of-cpp14-in-rippled.md index f8c7989397..2e07b519ab 100644 --- a/blog/2014/use-of-cpp14-in-rippled.md +++ b/blog/2014/use-of-cpp14-in-rippled.md @@ -1,7 +1,16 @@ +--- +date: 2014-08-19 +category: 2014 +labels: + - Development +theme: + markdown: + editPage: + hide: true +author: Howard Hinnant +--- # Use of C++14 in rippled -_Posted by Howard Hinnant_ - C++ is a language under constant development, resulting in alternating minor and major releases. The last major release of C++ was C++11. [A minor release](https://isocpp.org/blog/2014/08/we-have-cpp14) has just been approved by all participating national bodies (zero negative votes). This will be C++14. C++17 is the next planned major release and is currently under development by the committee. Rippled has already adopted a number of useful C++14 features. We’ve done this through the development environment where native support is available, or by emulating the features through providing compatible implementations using our beast cxx14 compatibility library ( [https://github.com/ripple/rippled/tree/develop/src/beast/beast/cxx14](https://github.com/ripple/rippled/tree/0.26.2/src/beast/beast/cxx14)). diff --git a/blog/2014/why-the-stellar-forking-issue-does-not-affect-ripple.md b/blog/2014/why-the-stellar-forking-issue-does-not-affect-ripple.md index cb0b5ef30f..58e9565f1b 100644 --- a/blog/2014/why-the-stellar-forking-issue-does-not-affect-ripple.md +++ b/blog/2014/why-the-stellar-forking-issue-does-not-affect-ripple.md @@ -1,3 +1,14 @@ +--- +date: 2014-12-07 +category: 2014 +labels: + - Advisories + - Security +theme: + markdown: + editPage: + hide: true +--- # Why the Stellar Forking Issue Does Not Affect Ripple The Stellar Development Foundation (SDF) which maintains Stellar, a network built on a modified version of the Ripple code base, recently published a post claiming flaws in the Ripple consensus algorithm. We take any reports about possible security issues very seriously and after reviewing the information conclude that there is no threat to the continued operation of the Ripple network. We'd like to share our thoughts. diff --git a/blog/2014/xrp-giveaway-for-developers.md b/blog/2014/xrp-giveaway-for-developers.md index 9bc72f958b..ccb6d22554 100644 --- a/blog/2014/xrp-giveaway-for-developers.md +++ b/blog/2014/xrp-giveaway-for-developers.md @@ -1,3 +1,13 @@ +--- +date: 2014-07-28 +category: 2014 +labels: + - Development +theme: + markdown: + editPage: + hide: true +--- # XRP Giveaway for Developers Ripple Labs has partnered with [Assembla](https://www.assembla.com/home) to send qualified developers 1,000 XRP to their Ripple Trade account. To apply for this giveaway please fill out and submit [the application form](https://www.assembla.com/ripple). If you’re interested in developing on Ripple please check out the [Primer](https://ripple.com/ripple_primer.pdf) for a high level overview. From there you can dive into different layers of the Ripple ecosystem. @@ -24,8 +34,6 @@ A simple request-response communication via HTTP. For more information, click [h ## Middleware -### - ### Ripple Rest API Use the [official REST API](https://github.com/ripple/ripple-rest) to easily interact with Ripple. Check balances, send payments, set trustlines, and more. Additionally, check out the [community made libraries](https://github.com/ripplelabsbounties) for Ripple Rest. diff --git a/blog/2015/calculating-balance-changes-for-a-transaction.md b/blog/2015/calculating-balance-changes-for-a-transaction.md index 3882a17990..6d8791b151 100644 --- a/blog/2015/calculating-balance-changes-for-a-transaction.md +++ b/blog/2015/calculating-balance-changes-for-a-transaction.md @@ -1,3 +1,14 @@ +--- +date: 2015-02-19 +category: 2015 +labels: + - Development + - Features +theme: + markdown: + editPage: + hide: true +--- # Calculating Balance Changes for a Transaction ## Introduction diff --git a/blog/2015/correction-to-ripple-white-paper.md b/blog/2015/correction-to-ripple-white-paper.md index fe16c25a06..5927987979 100644 --- a/blog/2015/correction-to-ripple-white-paper.md +++ b/blog/2015/correction-to-ripple-white-paper.md @@ -1,3 +1,13 @@ +--- +date: 2015-09-02 +category: 2015 +labels: + - Advisories +theme: + markdown: + editPage: + hide: true +--- # Correction to Ripple White Paper We've recently been made aware of a [paper](http://www.ghassankarame.com/ripple.pdf) discussing the possibility of forks in the Ripple system. We agree with the authors' conclusion that a fork is not possible given that the UNL overlap is greater than 40%. Unfortunately, this is different than the 20% figure stated in our [2014 white paper](https://ripple.com/consensus-whitepaper/). We apologize for the oversight and are issuing a corrected version. diff --git a/blog/2015/do-you-have-what-it-takes-to-be-a-gateway.md b/blog/2015/do-you-have-what-it-takes-to-be-a-gateway.md index 7f62c6de39..97113a71d7 100644 --- a/blog/2015/do-you-have-what-it-takes-to-be-a-gateway.md +++ b/blog/2015/do-you-have-what-it-takes-to-be-a-gateway.md @@ -1,3 +1,11 @@ +--- +category: 2015 +date: 2015-03-18 +theme: + markdown: + editPage: + hide: true +--- # Do You Have What It Takes to Be a Gateway? We're proud to announce the first release of [our new Gateway Guide](https://developers.ripple.com/become-an-xrp-ledger-gateway.html), a comprehensive manual to operating a gateway in the Ripple network. Whether you're trying to understand [how a gateway makes revenue](https://developers.ripple.com/become-an-xrp-ledger-gateway.html#fees-and-revenue-sources), or how to use the [authorized accounts](https://developers.ripple.com/become-an-xrp-ledger-gateway.html#authorized-trust-lines) feature, or even just [what a warm wallet is](https://developers.ripple.com/issuing-and-operational-addresses.html), the gateway guide has you covered. diff --git a/blog/2015/gatewayd-no-longer-available.md b/blog/2015/gatewayd-no-longer-available.md index a2256cc096..0945f0587f 100644 --- a/blog/2015/gatewayd-no-longer-available.md +++ b/blog/2015/gatewayd-no-longer-available.md @@ -1,3 +1,13 @@ +--- +date: 2015-07-01 +labels: + - Advisories +category: 2015 +theme: + markdown: + editPage: + hide: true +--- # Gatewayd No Longer Available In the interest of focusing our resources on other projects, starting today, Gatewayd will no longer be available on Github. diff --git a/blog/2015/introducing-the-data-api.md b/blog/2015/introducing-the-data-api.md index 8e0b23c090..02efa1427d 100644 --- a/blog/2015/introducing-the-data-api.md +++ b/blog/2015/introducing-the-data-api.md @@ -1,3 +1,13 @@ +--- +date: 2015-08-05 +category: 2015 +labels: + - Features +theme: + markdown: + editPage: + hide: true +--- # Introducing the Data API Ripple Labs data is moving under one roof, the Data API – a version two of the Historical Database API – and one infrastructure, Hadoop. We are building a much more robust and reliable way to import, parse, and house data that is not taxing on the Ripple network. Housing all of our endpoints together will allow us to scale much faster and with more confidence as the ledger and our data needs grow. diff --git a/blog/2015/ripple-charts-update-payment-volume-and-issued-value.md b/blog/2015/ripple-charts-update-payment-volume-and-issued-value.md index 05babbb4c2..349fd5bc3a 100644 --- a/blog/2015/ripple-charts-update-payment-volume-and-issued-value.md +++ b/blog/2015/ripple-charts-update-payment-volume-and-issued-value.md @@ -1,3 +1,13 @@ +--- +date: 2015-06-10 +labels: + - Advisories +category: 2015 +theme: + markdown: + editPage: + hide: true +--- # Ripple Charts Update: Payment Volume and Issued Value Starting today, we are rolling out a small update to Ripple Charts that may seem minor but hopefully will have a big impact in the way we look at Ripple in the future. diff --git a/blog/2015/validator-registry.md b/blog/2015/validator-registry.md index a547b306d9..757bc7fefb 100644 --- a/blog/2015/validator-registry.md +++ b/blog/2015/validator-registry.md @@ -1,3 +1,13 @@ +--- +date: 2015-08-18 +category: 2015 +labels: + - Features +theme: + markdown: + editPage: + hide: true +--- # Validator Registry At Ripple Labs, our goal is to expand the size and diversity of the Ripple consensus network by enabling people to easily run rippled validators and understand how those validators perform. We aim to create a network where validating participants are well known and respected by gathering and publicizing identity information of validators in addition to performance statistics. diff --git a/blog/2016/data-api-v2.2.md b/blog/2016/data-api-v2.2.md index 69b6f902d2..895f7b466b 100644 --- a/blog/2016/data-api-v2.2.md +++ b/blog/2016/data-api-v2.2.md @@ -1,3 +1,13 @@ +--- +date: 2016-06-15 +category: 2016 +labels: + - Release Notes +theme: + markdown: + editPage: + hide: true +--- # Data API v2.2 Released The Data team is proud to announce the release of the [Ripple Data API v2.2](https://github.com/ripple/rippled-historical-database/releases/tag/v2.2.0)! This release includes lots of new features, including a total of 15 new methods, improvements in data quality, and documentation. diff --git a/blog/2016/flow-available.md b/blog/2016/flow-available.md index cac441827f..dad4123b85 100644 --- a/blog/2016/flow-available.md +++ b/blog/2016/flow-available.md @@ -1,3 +1,13 @@ +--- +date: 2016-10-24 +labels: + - Amendments +category: 2016 +theme: + markdown: + editPage: + hide: true +--- # The Flow Amendment is Now Available The Flow Amendment became available on the Ripple Consensus Ledger in ledger 24,970,753 [(2016-10-21T19:47:22Z)](https://xrpcharts.ripple.com/#/transactions/C06CE3CABA3907389E4DD296C5F31C73B1548CC20BD7B83416C78CD7D4CD38FC). diff --git a/blog/2016/flow-reminder.md b/blog/2016/flow-reminder.md index 0e93324434..e6bd7fe8f4 100644 --- a/blog/2016/flow-reminder.md +++ b/blog/2016/flow-reminder.md @@ -1,3 +1,13 @@ +--- +date: 2016-10-17 +labels: + - Amendments +category: 2016 +theme: + markdown: + editPage: + hide: true +--- # The Flow Amendment Will Soon Be Available A majority of `rippled` validators voted to enable the [Flow Amendment](https://ripple.com/build/amendments/#flow), which is scheduled to become active on the protocol on Thursday, 2016-10-20. This amendment replaces the payment processing engine with a more robust and efficient rewrite called the Flow engine. The new payments engine adds no new features, but improves efficiency and robustness in payment handling. diff --git a/blog/2016/flow-voting.md b/blog/2016/flow-voting.md index a38df5a47a..355fd0bd27 100644 --- a/blog/2016/flow-voting.md +++ b/blog/2016/flow-voting.md @@ -1,3 +1,13 @@ +--- +date: 2016-10-07 +labels: + - Amendments +category: 2016 +theme: + markdown: + editPage: + hide: true +--- # The Flow Amendment is Open for Voting Originally introduced in `rippled` [version 0.32.1](https://developers.ripple.com/blog/2016/rippled-0.32.1.html), but later [vetoed](https://developers.ripple.com/blog/2016/flowv2-vetoed.html) after a flaw was discovered in the code while testing, the new [Flow Amendment](https://ripple.com/build/amendments/#flow) is now open for voting. This amendment replaces the payment processing engine with a more robust and efficient rewrite called the Flow engine. The new payments engine adds no new features, but improves efficiency and robustness in payment handling. diff --git a/blog/2016/flowv2-vetoed.md b/blog/2016/flowv2-vetoed.md index 55458008f3..f0e30c0651 100644 --- a/blog/2016/flowv2-vetoed.md +++ b/blog/2016/flowv2-vetoed.md @@ -1,12 +1,16 @@ +--- +date: 2016-08-18 +labels: + - Amendments +category: 2016 +theme: + markdown: + editPage: + hide: true +--- # The FlowV2 Amendment Was Vetoed -## Background - -[Originally](https://developers.ripple.com/blog/2016/rippled-0.32.1.html), the [FlowV2 amendment](https://ripple.com/build/amendments/#flowv2) was planned to replace `rippled`’s payment processing engine with a more robust and efficient implementation. It was previously expected to become active on Wednesday, 2016-08-24. - -## FlowV2 Was Vetoed - -The `rippled` team found a flaw in FlowV2 while testing. As a result, the Ripple network has [vetoed](https://ripple.com/build/amendments/#amendment-voting) the new payment engine amendment. +The `rippled` team found a flaw in FlowV2 while testing. As a result, the Ripple network has [vetoed](https://ripple.com/build/amendments/#amendment-voting) the new payment engine amendment. [Originally](https://developers.ripple.com/blog/2016/rippled-0.32.1.html), the [FlowV2 amendment](https://ripple.com/build/amendments/#flowv2) was planned to replace `rippled`’s payment processing engine with a more robust and efficient implementation. It was previously expected to become active on Wednesday, 2016-08-24. A corrected version of the payment processing engine has been created and is now undergoing further testing. It is scheduled to be included in a future version of `rippled` as an amendment called [Flow](https://github.com/seelabs/rippled/blob/6466629f935821583eeddadbd06fabd9ea0875d0/src/ripple/app/main/Amendments.cpp#L50-L51). diff --git a/blog/2016/flowv2-voting.md b/blog/2016/flowv2-voting.md index 284cbc90e6..d154ac15db 100644 --- a/blog/2016/flowv2-voting.md +++ b/blog/2016/flowv2-voting.md @@ -1,3 +1,13 @@ +--- +date: 2016-08-10 +labels: + - Amendments +category: 2016 +theme: + markdown: + editPage: + hide: true +--- # The FlowV2 Amendment is Open for Voting The [FlowV2 Amendment](https://ripple.com/build/amendments/#flowv2) is now open for voting. This amendment replaces the payment processing engine with a more robust and efficient rewrite called the FlowV2 engine. The new version of the payment processing engine is intended to follow the same rules as the old engine. However, the new engine occasionally produces different results due to floating point rounding. diff --git a/blog/2016/introducing-rippleapi.md b/blog/2016/introducing-rippleapi.md index 020f997c29..f7fd2018aa 100644 --- a/blog/2016/introducing-rippleapi.md +++ b/blog/2016/introducing-rippleapi.md @@ -1,3 +1,13 @@ +--- +date: 2016-06-12 +category: 2016 +labels: + - Release Notes +theme: + markdown: + editPage: + hide: true +--- # Introducing RippleAPI Ripple is proud to announce an improved, unified interface to the Ripple Consensus Ledger: the new **RippleAPI**! RippleAPI merges ripple-lib and Ripple-REST into a single high-level interface for JavaScript that is fully-documented, fully-tested, schema-validated, stateless, and easier to use. diff --git a/blog/2016/multisign-available.md b/blog/2016/multisign-available.md index bea7ea1b8d..3227a06e9a 100644 --- a/blog/2016/multisign-available.md +++ b/blog/2016/multisign-available.md @@ -1,3 +1,13 @@ +--- +date: 2016-06-27 +labels: + - Amendments +category: 2016 +theme: + markdown: + editPage: + hide: true +--- # Multi-Signing Now Available # As [predicted previously](https://developers.ripple.com/blog/2016/multisign-reminder.html), multi-signing became available on the Ripple Consensus Ledger this afternoon in Pacific time ([2016-06-27T11:34:41Z](https://xrpcharts.ripple.com/#/transactions/168F8B15F643395E59B9977FC99D6310E8708111C85659A9BAF8B9222EEAC5A7), to be exact). diff --git a/blog/2016/multisign-reminder.md b/blog/2016/multisign-reminder.md index b5263b4f7a..d49fe663fc 100644 --- a/blog/2016/multisign-reminder.md +++ b/blog/2016/multisign-reminder.md @@ -1,4 +1,14 @@ -# Multi-Signing Will Soon Be Available # +--- +date: 2016-06-21 +labels: + - Amendments +category: 2016 +theme: + markdown: + editPage: + hide: true +--- +# Multi-Signing Will Soon Be Available The multi-signing amendment is currently supported by the majority of voting validators on Ripple, and is scheduled to become active on the protocol on Monday, **2016-06-27**. For more information, please see the multi-signing documentation in the Ripple Developer Portal: diff --git a/blog/2016/rippled-0.30.1.md b/blog/2016/rippled-0.30.1.md index 678492c4c9..4d0f026df7 100644 --- a/blog/2016/rippled-0.30.1.md +++ b/blog/2016/rippled-0.30.1.md @@ -1,3 +1,13 @@ +--- +date: 2016-02-10 +labels: + - Release Notes +category: 2016 +theme: + markdown: + editPage: + hide: true +--- # rippled 0.30.1 Released The latest version of `rippled`, the core server of the Ripple Consensus Ledger, is here! Version 0.30.1 contains lots of small features and improvements, including updates to account\_offers, server\_info, peer subscriptions, and more. It also adds several optimizations to the consensus process that have already led to a dramatic increase in the number of ledgers validated per day! Learn more: diff --git a/blog/2016/rippled-0.31.2-updates.md b/blog/2016/rippled-0.31.2-updates.md index a003cf6b83..12dc07f793 100644 --- a/blog/2016/rippled-0.31.2-updates.md +++ b/blog/2016/rippled-0.31.2-updates.md @@ -1,3 +1,13 @@ +--- +date: 2016-06-10 +labels: + - Release Notes +category: 2016 +theme: + markdown: + editPage: + hide: true +--- # rippled 0.31.2 and Other Updates The `rippled` team is proud to announce a bundle of related news items: diff --git a/blog/2016/rippled-0.32.0.md b/blog/2016/rippled-0.32.0.md index 753941a4d5..c4e2f95c17 100644 --- a/blog/2016/rippled-0.32.0.md +++ b/blog/2016/rippled-0.32.0.md @@ -1,3 +1,13 @@ +--- +date: 2016-06-27 +labels: + - Release Notes +category: 2016 +theme: + markdown: + editPage: + hide: true +--- # rippled version 0.32.0 has been released # Ripple is proud to announce the release of `rippled` version 0.32.0. This release introduces several enhancements that improve the reliability and scalability of the Ripple Consensus Ledger. Ripple recommends that all server operators upgrade to the new version. diff --git a/blog/2016/rippled-0.32.1.md b/blog/2016/rippled-0.32.1.md index a94fcef3b7..3be22112e6 100644 --- a/blog/2016/rippled-0.32.1.md +++ b/blog/2016/rippled-0.32.1.md @@ -1,3 +1,13 @@ +--- +date: 2016-07-29 +labels: + - Release Notes +category: 2016 +theme: + markdown: + editPage: + hide: true +--- # rippled version 0.32.1 Ripple is proud to announce the release of `rippled` version 0.32.1, which introduces several enhancements that improve the reliability and scalability of the Ripple Consensus Ledger. Ripple recommends that all server operators upgrade to version 0.32.1 by Wednesday, 2016-08-24, for the best performance. diff --git a/blog/2016/rippled-0.33.0-hf1.md b/blog/2016/rippled-0.33.0-hf1.md index 51d6481cb7..22a5b2ba7c 100644 --- a/blog/2016/rippled-0.33.0-hf1.md +++ b/blog/2016/rippled-0.33.0-hf1.md @@ -1,3 +1,13 @@ +--- +date: 2016-10-16 +labels: + - Release Notes +category: 2016 +theme: + markdown: + editPage: + hide: true +--- # rippled version 0.33.0-hf1 Ripple has released `rippled` version 0.33.0-hf1, which fixes a JSON parsing issue in all `rippled` servers. Ripple recommends upgrading to 0.33.0-hf1 only if server operators are experiencing a `jsonInvalid` error response to client requests. There are no new or updated features in the 0.33.0-hf1 release. diff --git a/blog/2016/rippled-0.33.0.md b/blog/2016/rippled-0.33.0.md index 6c1861032e..9268066b22 100644 --- a/blog/2016/rippled-0.33.0.md +++ b/blog/2016/rippled-0.33.0.md @@ -1,3 +1,13 @@ +--- +date: 2016-09-29 +labels: + - Release Notes +category: 2016 +theme: + markdown: + editPage: + hide: true +--- # rippled version 0.33.0 Ripple has released `rippled` version 0.33.0, which introduces several new enhancements that improve the reliability and scalability of the Ripple Consensus Ledger (RCL). Ripple recommends that all server operators upgrade to version 0.33.0 by Wednesday, 2016-10-20, for service continuity. diff --git a/blog/2016/rippled-0.40.0.md b/blog/2016/rippled-0.40.0.md index 3293ec9505..29b5ed6cee 100644 --- a/blog/2016/rippled-0.40.0.md +++ b/blog/2016/rippled-0.40.0.md @@ -1,3 +1,13 @@ +--- +date: 2016-12-20 +labels: + - Release Notes +category: 2016 +theme: + markdown: + editPage: + hide: true +--- # rippled version 0.40.0 Ripple has released `rippled` version 0.40.0, which introduces several enhancements that improve the reliability and scalability of the Ripple Consensus Ledger (RCL). Ripple recommends that all server operators upgrade to version 0.40.0 by Tuesday, 2017-01-17, for service continuity. diff --git a/blog/2016/testnet-ledger-reset.md b/blog/2016/testnet-ledger-reset.md index fa65cd8aae..c9bdde1a48 100644 --- a/blog/2016/testnet-ledger-reset.md +++ b/blog/2016/testnet-ledger-reset.md @@ -1,7 +1,15 @@ +--- +date: 2016-09-01 +category: 2016 +labels: + - Advisories +theme: + markdown: + editPage: + hide: true +--- # Ripple Test Network Ledger Will Be Reset -## Summary - On 2016-09-02, Ripple will be resetting the [test network](https://xrpl.org/xrp-test-net-faucet.html) ledger and balances. This means that all test net order books will be deleted and all account balances will be depleted. This will have absolutely no effect on the live, production Ripple Consensus Ledger (RCL). diff --git a/blog/2016/trustsetauth-available.md b/blog/2016/trustsetauth-available.md index 0dec356b2b..ba3a249a9f 100644 --- a/blog/2016/trustsetauth-available.md +++ b/blog/2016/trustsetauth-available.md @@ -1,3 +1,13 @@ +--- +date: 2016-07-19 +category: 2016 +labels: + - Amendments +theme: + markdown: + editPage: + hide: true +--- # TrustSetAuth is Now Available As [predicted previously](https://developers.ripple.com/blog/2016/trustsetauth-reminder.html), TrustSetAuth became available on the Ripple Consensus Ledger this afternoon (PDT) in ledger 22,721,281 ([2016-07-19T15:10](https://xrpcharts.ripple.com/#/transactions/0E589DE43C38AED63B64FF3DA87D349A038F1821212D370E403EB304C76D70DF)). diff --git a/blog/2016/trustsetauth-reminder.md b/blog/2016/trustsetauth-reminder.md index afb7fd48d3..e37dc23dbc 100644 --- a/blog/2016/trustsetauth-reminder.md +++ b/blog/2016/trustsetauth-reminder.md @@ -1,5 +1,14 @@ -TrustSetAuth Will Soon Be Available -=================================== +--- +date: 2016-07-12 +category: 2016 +labels: + - Amendments +theme: + markdown: + editPage: + hide: true +--- +# TrustSetAuth Will Soon Be Available This notice is for all validator operators, and may be useful for gateways that utilize the Authorized Accounts feature. diff --git a/blog/2016/trustsetauth-voting.md b/blog/2016/trustsetauth-voting.md index b7dda5c854..dec546f315 100644 --- a/blog/2016/trustsetauth-voting.md +++ b/blog/2016/trustsetauth-voting.md @@ -1,3 +1,13 @@ +--- +date: 2016-07-05 +category: 2016 +labels: + - Amendments +theme: + markdown: + editPage: + hide: true +--- # The TrustSetAuth Amendment Is Open For Voting # This notice is for all validator operators, and may be relevant to gateways that utilize the Authorized Account feature. diff --git a/blog/2017/data-api-load-balancing-test.md b/blog/2017/data-api-load-balancing-test.md index 05a9f0ceac..e94ac808a2 100644 --- a/blog/2017/data-api-load-balancing-test.md +++ b/blog/2017/data-api-load-balancing-test.md @@ -1,3 +1,13 @@ +--- +date: 2017-01-18 +category: 2017 +labels: + - Advisories +theme: + markdown: + editPage: + hide: true +--- # Load Testing Data API The Ripple Data team will be running load balancing tests on Ripple Data API starting Wednesday, 2017-01-18, at 2pm PST, which will last approximately 15 minutes. The Ripple Data API is an open and free resource that provides access to information about changes in the Ripple Consensus Ledger, including transaction history and processed analytical data. diff --git a/blog/2017/decent-strategy-update.md b/blog/2017/decent-strategy-update.md index feeb6142f7..6edb58963b 100644 --- a/blog/2017/decent-strategy-update.md +++ b/blog/2017/decent-strategy-update.md @@ -1,3 +1,13 @@ +--- +date: 2017-10-17 +category: 2017 +labels: + - Features +theme: + markdown: + editPage: + hide: true +--- # Decentralization Strategy Update As Ripple progresses towards further decentralizing the XRP Ledger, we want to make server operators and members of the XRP Ledger community aware of a few upcoming changes to help ensure the reliability and stability of the network as it transitions to a distributed architecture with fully decentralized validators. diff --git a/blog/2017/escrow-paychan-fix1368-reminder.md b/blog/2017/escrow-paychan-fix1368-reminder.md index a6da98d690..346efdc033 100644 --- a/blog/2017/escrow-paychan-fix1368-reminder.md +++ b/blog/2017/escrow-paychan-fix1368-reminder.md @@ -1,3 +1,13 @@ +--- +date: 2017-03-27 +category: 2017 +labels: + - Amendments +theme: + markdown: + editPage: + hide: true +--- # Escrow, PayChan, and fix1368 Will Be Available in 3 Days A majority of `rippled` validators voted to enable the [Escrow](https://ripple.com/build/amendments/#escrow), [PayChan](https://ripple.com/build/amendments/#paychan), and [fix1368](https://ripple.com/build/amendments/#fix1368) Amendments, which are scheduled to become enabled on the network on Thursday, 2017-03-30. diff --git a/blog/2017/explanation-of-ripples-xrp-escrow.md b/blog/2017/explanation-of-ripples-xrp-escrow.md index cd7d354e70..acb4ce006b 100644 --- a/blog/2017/explanation-of-ripples-xrp-escrow.md +++ b/blog/2017/explanation-of-ripples-xrp-escrow.md @@ -1,3 +1,13 @@ +--- +date: 2017-12-15 +category: 2017 +labels: + - Features +theme: + markdown: + editPage: + hide: true +--- # An Explanation of Ripple’s XRP Escrow To provide additional predictability to the XRP supply, Ripple has locked 55 billion XRP (55% of the total possible supply) into a series of escrows. These escrows are on the ledger itself and the ledger mechanics, enforced by consensus, control the release of the XRP. diff --git a/blog/2017/high-scalability-xrp-ledger.md b/blog/2017/high-scalability-xrp-ledger.md index 1f193871c6..67e92d2482 100644 --- a/blog/2017/high-scalability-xrp-ledger.md +++ b/blog/2017/high-scalability-xrp-ledger.md @@ -1,3 +1,13 @@ +--- +labels: + - Features +category: 2017 +date: 2017-10-02 +theme: + markdown: + editPage: + hide: true +--- # The Most (Demonstrably) Scalable Blockchain Blockchain technology is set to fundamentally transform the way the world moves value, but to do so, it must first meet a number of challenges. diff --git a/blog/2017/invariant-checking.md b/blog/2017/invariant-checking.md index 42930a5c7f..b6d3b8b991 100644 --- a/blog/2017/invariant-checking.md +++ b/blog/2017/invariant-checking.md @@ -1,7 +1,16 @@ +--- +category: 2017 +labels: + - Features +date: 2017-07-19 +theme: + markdown: + editPage: + hide: true +author: Nik Bougalis +--- # Protecting the Ledger: Invariant Checking -_By Nik Bougalis, Engineering Manager_ - At Ripple, we have been developing next-generation financial infrastructure with an eye towards making value move as fast and as efficiently as information does today. But we are also keenly aware of the need for value to also move securely and reliably, so we place heavy emphasis on writing solid, secure and robust code. Our singular focus on code quality is the reason that the Ripple network experienced no service outages through 2016 or, so far, in 2017. diff --git a/blog/2017/response-to-china-cert-report.md b/blog/2017/response-to-china-cert-report.md index 387ef3af62..bf8802765e 100644 --- a/blog/2017/response-to-china-cert-report.md +++ b/blog/2017/response-to-china-cert-report.md @@ -1,3 +1,13 @@ +--- +category: 2017 +labels: + - Security +date: 2017-01-12 +theme: + markdown: + editPage: + hide: true +--- # Response to China CERT Report As a leader in open-source, distributed financial technology, Ripple recognizes the importance of security researchers and we always encourage responsible disclosure of potential security vulnerabilities via our [bug bounty program](https://ripple.com/bug-bounty/). Ripple also employs regular external security audits and, as a matter of practice, the maintainers of the Ripple Consensus Ledger (RCL) technology (`rippled`) routinely use static and dynamic analysis tools on the C++ codebase (most recently version 0.50.0-b1). diff --git a/blog/2017/ripple-consensus-ledger-can-sustain-1000-transactions-per-second.md b/blog/2017/ripple-consensus-ledger-can-sustain-1000-transactions-per-second.md index 486d8ba248..3875662edb 100644 --- a/blog/2017/ripple-consensus-ledger-can-sustain-1000-transactions-per-second.md +++ b/blog/2017/ripple-consensus-ledger-can-sustain-1000-transactions-per-second.md @@ -1,3 +1,13 @@ +--- +category: 2017 +labels: + - Features +date: 2017-02-28 +theme: + markdown: + editPage: + hide: true +--- # Ripple Consensus Ledger Can Sustain 1000 Transactions per Second 2016 was an [important year for Ripple](https://ripple.com/insights/ripple-2016-year-review/). Banks were added to our [growing network](http://www.ibtimes.co.uk/seven-banks-kick-off-ripples-blockchain-network-including-santander-ubs-unicredit-90-more-1566894), we completed a successful [Series B investment round](https://ripple.com/insights/ripple-raises-55-million-in-series-b-funding/) and formed the [Global Payments Steering Group](https://ripple.com/insights/announcing-ripples-global-payments-steering-group/). Underlying all those milestones was the Ripple Consensus Ledger (RCL), which runs 24 hours a day, 7 days a week and recently celebrated its 4th birthday on February 17, 2017. In 2016 alone, RCL closed over 8 million ledgers, processing more than 225 million transactions and handling more than $1 Billion dollars in payment volume throughout the year. diff --git a/blog/2017/rippled-0.40.1.md b/blog/2017/rippled-0.40.1.md index b1cc49af7f..635e029490 100644 --- a/blog/2017/rippled-0.40.1.md +++ b/blog/2017/rippled-0.40.1.md @@ -1,3 +1,13 @@ +--- +date: 2017-01-11 +category: 2017 +labels: + - Release Notes +theme: + markdown: + editPage: + hide: true +--- # rippled version 0.40.1 The `rippled` team has released version 0.40.1, which increases SQLite database limits in all `rippled` full-history servers. Ripple recommends upgrading to 0.40.1 only if server operators are running `rippled` servers with full-history of the ledger. There are no new or updated features in the 0.40.1 release. diff --git a/blog/2017/rippled-0.50.0.md b/blog/2017/rippled-0.50.0.md index aff59ff670..dc7e0aba44 100644 --- a/blog/2017/rippled-0.50.0.md +++ b/blog/2017/rippled-0.50.0.md @@ -1,3 +1,13 @@ +--- +date: 2017-01-27 +category: 2017 +labels: + - Release Notes +theme: + markdown: + editPage: + hide: true +--- # rippled version 0.50.0 Ripple has released `rippled` version 0.50.0, which introduces several enhancements that improve the reliability and scalability of the Ripple Consensus Ledger (RCL). Ripple recommends that all server operators upgrade to version 0.50.0 by Tuesday, 2017-02-21, for service continuity. diff --git a/blog/2017/rippled-0.50.2.md b/blog/2017/rippled-0.50.2.md index 4792c860f2..4459c3c209 100644 --- a/blog/2017/rippled-0.50.2.md +++ b/blog/2017/rippled-0.50.2.md @@ -1,3 +1,14 @@ +--- +date: 2017-01-30 +category: 2017 +labels: + - Release Notes +theme: + markdown: + editPage: + hide: true +--- + # rippled version 0.50.2 The `rippled` team has released 0.50.2, which adjusts the default TLS cipher list and corrects a flaw that would not allow an SSL handshake to properly complete if the port was configured using the wss keyword. Ripple recommends upgrading to 0.50.2 only if server operators are running `rippled` servers that accept client connections over TLS. There are no new or updated features in the 0.50.2 release. diff --git a/blog/2017/rippled-0.50.3.md b/blog/2017/rippled-0.50.3.md index 386d03b227..e3d9ea06a4 100644 --- a/blog/2017/rippled-0.50.3.md +++ b/blog/2017/rippled-0.50.3.md @@ -1,3 +1,13 @@ +--- +date: 2017-03-14 +category: 2017 +labels: + - Release Notes +theme: + markdown: + editPage: + hide: true +--- # rippled version 0.50.3 The `rippled` team has released version 0.50.3, which patches a reported exploit that would allow a combination of trust lines and order books in a payment path to bypass the blocking effect of the `NoRipple` flag. Ripple recommends that all `rippled` server operators immediately upgrade to version 0.50.3, which contains a patch that fixes the exploit. There are no new or updated features in the 0.50.3 release. diff --git a/blog/2017/rippled-0.60.0.md b/blog/2017/rippled-0.60.0.md index 209d341283..291f8ef245 100644 --- a/blog/2017/rippled-0.60.0.md +++ b/blog/2017/rippled-0.60.0.md @@ -1,3 +1,13 @@ +--- +date: 2017-03-17 +category: 2017 +labels: + - Release Notes +theme: + markdown: + editPage: + hide: true +--- # rippled Version 0.60.0 Ripple has released `rippled` version 0.60.0, which introduces several enhancements that improve the reliability and scalability of the Ripple Consensus Ledger (RCL), including [Interledger Protocol](https://interledger.org/overview.html) compatibility for ledger interoperability. Ripple recommends that all server operators upgrade to version 0.60.0 by Thursday, 2017-03-30, for service continuity. diff --git a/blog/2017/rippled-0.60.1.md b/blog/2017/rippled-0.60.1.md index ab36d8c133..163ffcd1e3 100644 --- a/blog/2017/rippled-0.60.1.md +++ b/blog/2017/rippled-0.60.1.md @@ -1,3 +1,13 @@ +--- +date: 2017-03-29 +category: 2017 +labels: + - Release Notes +theme: + markdown: + editPage: + hide: true +--- # rippled version 0.60.1 The `rippled` team has released `rippled` version 0.60.1, which corrects a technical flaw that resulted from using 32-bit space identifiers instead of the protocol-defined 16-bit values for Escrow and Payment Channel ledger entries. `rippled` version 0.60.1 also fixes a problem where the websocket timeout timer would not be cancelled when certain errors occurred during subscription streams. **Ripple strongly recommends upgrading to `rippled` version 0.60.1 immediately.** diff --git a/blog/2017/rippled-0.60.2-2-rpm.md b/blog/2017/rippled-0.60.2-2-rpm.md index 63db5e6c52..63f47fb1e9 100644 --- a/blog/2017/rippled-0.60.2-2-rpm.md +++ b/blog/2017/rippled-0.60.2-2-rpm.md @@ -1,3 +1,13 @@ +--- +date: 2017-05-03 +category: 2017 +labels: + - Advisories +theme: + markdown: + editPage: + hide: true +--- # rippled RPM version 0.60.2-2 Ripple has released a new `rippled` 0.60.2-2 RPM that contains an update to the [validator-keys](https://github.com/ripple/validator-keys-tool/blob/master/doc/validator-keys-tool-guide.md#validator-keys) key generation and management tool. The latest version of validator-keys allows validator operators to [sign data with their validator key](https://github.com/ripple/validator-keys-tool/blob/master/doc/validator-keys-tool-guide.md#signing). diff --git a/blog/2017/rippled-0.60.2.md b/blog/2017/rippled-0.60.2.md index 55bae13251..f3f6f4ac26 100644 --- a/blog/2017/rippled-0.60.2.md +++ b/blog/2017/rippled-0.60.2.md @@ -1,3 +1,13 @@ +--- +date: 2017-03-30 +category: 2017 +labels: + - Release Notes +theme: + markdown: + editPage: + hide: true +--- # rippled version 0.60.2 The `rippled` team has released `rippled` version 0.60.2, which further strengthens handling of cases associated with a [previously patched exploit](https://developers.ripple.com/blog/2017/rippled-0.50.3.html), in which `NoRipple` flags were being bypassed by using offers. Ripple requires upgrading to `rippled` version 0.60.2 immediately. There are no new features in the 0.60.2 release. **Note**: This does not affect XRP transactions. diff --git a/blog/2017/rippled-0.60.3.md b/blog/2017/rippled-0.60.3.md index bb9d13476a..e5f596b3f6 100644 --- a/blog/2017/rippled-0.60.3.md +++ b/blog/2017/rippled-0.60.3.md @@ -1,3 +1,13 @@ +--- +date: 2017-05-11 +category: 2017 +labels: + - Release Notes +theme: + markdown: + editPage: + hide: true +--- # rippled version 0.60.3 The `rippled` team has released `rippled` version 0.60.3, which helps to increase the stability of the overlay network under increased load. Ripple recommends server operators upgrade to `rippled` version 0.60.3 immediately. There are no new features in the 0.60.3 release. diff --git a/blog/2017/rippled-0.70.0.md b/blog/2017/rippled-0.70.0.md index 065e04c2da..059ab47c89 100644 --- a/blog/2017/rippled-0.70.0.md +++ b/blog/2017/rippled-0.70.0.md @@ -1,3 +1,13 @@ +--- +date: 2017-06-15 +category: 2017 +labels: + - Release Notes +theme: + markdown: + editPage: + hide: true +--- # rippled Version 0.70.0 Ripple has released `rippled` version 0.70.0, which introduces several enhancements that improve the reliability, scalability and security of the Ripple Consensus Ledger. Ripple recommends that all `rippled` server operators upgrade to version 0.70.0 by Thursday, 2017-06-29, for service continuity. diff --git a/blog/2017/rippled-0.70.1.md b/blog/2017/rippled-0.70.1.md index e2e48f9ea8..37250eefd2 100644 --- a/blog/2017/rippled-0.70.1.md +++ b/blog/2017/rippled-0.70.1.md @@ -1,11 +1,23 @@ +--- +date: 2017-07-10 +category: 2017 +labels: + - Release Notes +theme: + markdown: + editPage: + hide: true +--- # rippled version 0.70.1 -**UPDATE 7-12-2017:** This announcement now contains corrected SHA-256 values for the `RPM` and source `RPM`. - The `rippled` team has released `rippled` version 0.70.1, which corrects a technical flaw in the newly [refactored](https://github.com/ripple/rippled/commit/00c60d408a887d8a986db81afbb5ead121e8310c#diff-dab2766c14d0ef8e760dc5e353fa7b9dR1389) consensus code that could, in rare cases, cause a node to get stuck in consensus due to stale votes from a peer. **Ripple requires upgrading to `rippled` version 0.70.1 immediately.** There are no new features in the 0.70.1 release. +{% admonition type="danger" name="UPDATE 7-12-2017" %} +This announcement now contains corrected SHA-256 values for the RPM and source RPM. +{% /admonition %} + ## Action Required **If you operate a `rippled` server, then you should upgrade to 0.70.1 immediately.** diff --git a/blog/2017/rippled-0.70.2.md b/blog/2017/rippled-0.70.2.md index a6ea20a128..f85d99f9ba 100644 --- a/blog/2017/rippled-0.70.2.md +++ b/blog/2017/rippled-0.70.2.md @@ -1,3 +1,13 @@ +--- +date: 2017-09-21 +category: 2017 +labels: + - Release Notes +theme: + markdown: + editPage: + hide: true +--- # rippled version 0.70.2 The `rippled` team has released `rippled` version 0.70.2, which corrects an emergent behavior that resulted in high transaction costs and fewer transactions in validated ledgers over the past few days. The problematic behavior involved large numbers of transactions being stuck in different `rippled` instances' open ledgers without being consistently relayed to validators. The large number of "stuck" transactions filled the transaction queue and caused a dramatic increase in the open ledger cost. diff --git a/blog/2017/rippled-0.80.0.md b/blog/2017/rippled-0.80.0.md index fd869fc38c..81db903451 100644 --- a/blog/2017/rippled-0.80.0.md +++ b/blog/2017/rippled-0.80.0.md @@ -1,3 +1,13 @@ +--- +date: 2017-10-23 +category: 2017 +labels: + - Release Notes +theme: + markdown: + editPage: + hide: true +--- # rippled Version 0.80.0 Ripple has released `rippled` version 0.80.0, which introduces several enhancements that improve the reliability, scalability and security of the XRP Ledger. Ripple recommends that all `rippled` server operators upgrade to version 0.80.0 by Tuesday, 2017-11-07, for service continuity. diff --git a/blog/2017/rippled-0.80.2.md b/blog/2017/rippled-0.80.2.md index f14601d23f..bd0b09ceaf 100644 --- a/blog/2017/rippled-0.80.2.md +++ b/blog/2017/rippled-0.80.2.md @@ -1,3 +1,13 @@ +--- +date: 2017-12-15 +category: 2017 +labels: + - Release Notes +theme: + markdown: + editPage: + hide: true +--- # rippled Version 0.80.2 Ripple has released `rippled` version 0.80.2, which improves the transaction dispatch logic of `rippled`, allows for more transactions to be in flight at any one time and reduces the overall resource usage of `rippled`. The improved transaction dispatch logic ensures that a transaction is dispatched at most once every 10 seconds, even if it received from multiple peers during that interval. diff --git a/blog/2017/ticksize-3days.md b/blog/2017/ticksize-3days.md index 8e8e5e0f1c..12db85b4f8 100644 --- a/blog/2017/ticksize-3days.md +++ b/blog/2017/ticksize-3days.md @@ -1,3 +1,13 @@ +--- +date: 2017-02-18 +category: 2017 +labels: + - Amendments +theme: + markdown: + editPage: + hide: true +--- # TickSize Will Be Available in 3 Days This notice is for all validator operators, and may be useful for gateways that intend to use tick sizes. diff --git a/blog/2017/ticksize-7days.md b/blog/2017/ticksize-7days.md index 7baa92a716..0b22ab3edd 100644 --- a/blog/2017/ticksize-7days.md +++ b/blog/2017/ticksize-7days.md @@ -1,3 +1,13 @@ +--- +date: 2017-02-14 +category: 2017 +labels: + - Amendments +theme: + markdown: + editPage: + hide: true +--- # TickSize Will Be Available in 7 Days This notice is for all validator operators, and may be useful for gateways that intend to use tick sizes. diff --git a/blog/2017/ticksize-available.md b/blog/2017/ticksize-available.md index 9e8da82f01..0b8678f801 100644 --- a/blog/2017/ticksize-available.md +++ b/blog/2017/ticksize-available.md @@ -1,3 +1,13 @@ +--- +date: 2017-02-22 +category: 2017 +labels: + - Amendments +theme: + markdown: + editPage: + hide: true +--- # TickSize is Now Available As [predicted previously](https://developers.ripple.com/blog/2017/ticksize-3days.html), the TickSize amendment became available on the Ripple Consensus Ledger yesterday afternoon (PST) in ledger 27841793 ([2017-02-21T23:02:52Z](https://xrpcharts.ripple.com/#/transactions/A12430E470BE5C846759EAE3C442FF03374D5D73ECE5815CF4906894B769565E)). diff --git a/blog/2017/ticksize-voting.md b/blog/2017/ticksize-voting.md index d32c09a0c1..32d1b763ce 100644 --- a/blog/2017/ticksize-voting.md +++ b/blog/2017/ticksize-voting.md @@ -1,3 +1,13 @@ +--- +date: 2017-02-10 +category: 2017 +labels: + - Amendments +theme: + markdown: + editPage: + hide: true +--- # TickSize Amendment Open for Voting Previously [introduced](https://developers.ripple.com/blog/2017/rippled-0.50.0.html) in `rippled` version 0.50.0, the [TickSize amendment](https://ripple.com/build/amendments/#ticksize) to the Ripple Consensus Ledger is now open for voting. The amendment changes the way offers are ranked in the RCL's order books, so that currency issuers can configure how many significant digits are taken into account when ranking offers by exchange rate. diff --git a/blog/2017/trust-line-quality-sendmax.md b/blog/2017/trust-line-quality-sendmax.md index d1f889b18f..031bf4767a 100644 --- a/blog/2017/trust-line-quality-sendmax.md +++ b/blog/2017/trust-line-quality-sendmax.md @@ -1,7 +1,15 @@ +--- +date: 2017-03-16 +category: 2017 +labels: + - Security +theme: + markdown: + editPage: + hide: true +--- # Gateway Bulletin: Setting Trust Line Quality with SendMax -## Summary - When you build an automated system to send payments into the Ripple Consensus Ledger (RCL) for your customers, you must make sure that it constructs payments carefully. Malicious actors are constantly trying to find flaws in a system implementation that pays them more money than it should. Once such flaw was [revealed](https://forum.ripple.com/viewtopic.php?f=1&t=18210) _(dead link)_ recently, related to setting [trust line quality](https://web.archive.org/web/20150422102043/https://wiki.ripple.com/Trust_line_quality), which affects gateways that use a `SendMax` value greater than the amount they deliver. This setup could result in a destination account receiving slightly higher (typically less than 1% higher) than the expected amount from the gateway's account. diff --git a/blog/2018/data-api-validations-changes.md b/blog/2018/data-api-validations-changes.md index b2bd3fe5f5..22957a71f9 100644 --- a/blog/2018/data-api-validations-changes.md +++ b/blog/2018/data-api-validations-changes.md @@ -1,3 +1,13 @@ +--- +date: 2018-10-23 +category: 2018 +labels: + - Advisories +theme: + markdown: + editPage: + hide: true +--- # Updates Coming to Data API The [Data API](https://developers.ripple.com/data-api.html), which provides data to [XRP Charts](https://xrpcharts.ripple.com/) and third-party tools, is scheduled to update to **version 2.4.0** in approximately two weeks, on **2018-11-07**. This version improves the way the Data API imports and summarizes data on XRP Ledger validators. diff --git a/blog/2018/depositauth-fix1513-available.md b/blog/2018/depositauth-fix1513-available.md index 183357e5d8..eb0f4cb9db 100644 --- a/blog/2018/depositauth-fix1513-available.md +++ b/blog/2018/depositauth-fix1513-available.md @@ -1,3 +1,13 @@ +--- +date: 2018-04-09 +category: 2018 +labels: + - Amendments +theme: + markdown: + editPage: + hide: true +--- # The DepositAuth & fix1513 Amendments are Now Available The [DepositAuth](https://ripple.com/build/deposit-authorization/) & fix1513 Amendments became available on the XRP Ledger in ledger sequence number 37,753,345 [(2018-04-06T01:44:42Z)](https://xrpcharts.ripple.com/#/transactions/902C51270B918B40CD23A622E18D48B4ABB86F0FF4E84D72D9E1907BF3BD4B25). diff --git a/blog/2018/depositpreauth-fix1515-enabled.md b/blog/2018/depositpreauth-fix1515-enabled.md index cb6bcdfa5d..97eb8ad981 100644 --- a/blog/2018/depositpreauth-fix1515-enabled.md +++ b/blog/2018/depositpreauth-fix1515-enabled.md @@ -1,3 +1,13 @@ +--- +date: 2018-10-09 +category: 2018 +labels: + - Amendments +theme: + markdown: + editPage: + hide: true +--- # DepositPreauth is Now Available The [DepositPreauth](https://xrpcharts.ripple.com/#/transactions/AD27403CB840AE67CADDB084BC54249D7BD1B403885819B39CCF723DC671F927) and [fix1515](https://xrpcharts.ripple.com/#/transactions/6DF60D9EC8AF3C39B173840F4D1C57F8A8AB51E7C6571483B4A5F1AA0A9AAEBF) amendments, [added in `rippled` v1.1.0](https://developers.ripple.com/blog/2018/rippled-1.1.0.html), became enabled on the XRP Ledger today, 2018-10-09. diff --git a/blog/2018/fix1543-fix1571-fix1623-voting.md b/blog/2018/fix1543-fix1571-fix1623-voting.md index 91a7748087..ec6ca17698 100644 --- a/blog/2018/fix1543-fix1571-fix1623-voting.md +++ b/blog/2018/fix1543-fix1571-fix1623-voting.md @@ -1,3 +1,13 @@ +--- +date: 2018-06-08 +category: 2018 +labels: + - Amendments +theme: + markdown: + editPage: + hide: true +--- # fix1543, fix1571 & fix1623 Amendments Open for Voting Previously [introduced in `rippled` version 1.0.0](https://developers.ripple.com/blog/2018/rippled-1.0.0.html), the [fix1543](https://developers.ripple.com/known-amendments.html#fix1543), [fix1571](https://developers.ripple.com/known-amendments.html#fix1571) and [fix1623](https://developers.ripple.com/known-amendments.html#fix1623) amendments are now open for voting. diff --git a/blog/2018/fix1571-enabled.md b/blog/2018/fix1571-enabled.md index 0a07d476a3..19af489a42 100644 --- a/blog/2018/fix1571-enabled.md +++ b/blog/2018/fix1571-enabled.md @@ -1,3 +1,13 @@ +--- +date: 2018-06-20 +category: 2018 +labels: + - Amendments +theme: + markdown: + editPage: + hide: true +--- # fix1571 is Now Available As previously announced, the fix1571 amendment [became enabled on the XRP Ledger](https://xrpcharts.ripple.com/#/transactions/920AA493E57D991414B614FB3C1D1E2F863211B48129D09BC8CB74C9813C38FC) on 2018-06-19. Furthermore, the fix1623 amendment is expected to become enabled on 2018-06-20, followed by the fix1543 amendment on 2018-06-21. diff --git a/blog/2018/introducing-history-sharding.md b/blog/2018/introducing-history-sharding.md index b9aa67e559..5e42dca205 100644 --- a/blog/2018/introducing-history-sharding.md +++ b/blog/2018/introducing-history-sharding.md @@ -1,3 +1,13 @@ +--- +date: 2018-11-07 +category: 2018 +labels: + - Features +theme: + markdown: + editPage: + hide: true +--- # Introducing History Sharding As `rippled` servers operate, they continually witness data appended onto an ever-growing blockchain. This data becomes the history that the network agrees upon and that constitutes everything about the XRP Ledger. diff --git a/blog/2018/ripple-lib-1.0.0.md b/blog/2018/ripple-lib-1.0.0.md index d0133325ce..79cb5c8e65 100644 --- a/blog/2018/ripple-lib-1.0.0.md +++ b/blog/2018/ripple-lib-1.0.0.md @@ -1,4 +1,14 @@ -# ripple-lib version 1.0.0 +--- +date: 2018-09-10 +category: 2018 +labels: + - Release Notes +theme: + markdown: + editPage: + hide: true +--- +# ripple-lib version 1.0.0 We are pleased to announce the release of **[ripple-lib version 1.0.0](https://github.com/ripple/ripple-lib/releases/tag/1.0.0)**! diff --git a/blog/2018/rippled-0.81.0.md b/blog/2018/rippled-0.81.0.md index 66ad941f1e..8804619c07 100644 --- a/blog/2018/rippled-0.81.0.md +++ b/blog/2018/rippled-0.81.0.md @@ -1,3 +1,13 @@ +--- +date: 2018-01-08 +category: 2018 +labels: + - Release Notes +theme: + markdown: + editPage: + hide: true +--- # rippled Version 0.81.0 Ripple has released `rippled` version 0.81.0, which introduces changes that improve the scalability of the XRP Ledger and transitions the recommended validator configuration to a new hosted site, as described in [Ripple's Decentralization Strategy Update](https://developers.ripple.com/blog/2017/decent-strategy-update.html) post. diff --git a/blog/2018/rippled-0.90.0.md b/blog/2018/rippled-0.90.0.md index db6f993ec2..2f9a735172 100644 --- a/blog/2018/rippled-0.90.0.md +++ b/blog/2018/rippled-0.90.0.md @@ -1,3 +1,13 @@ +--- +date: 2018-02-21 +category: 2018 +labels: + - Release Notes +theme: + markdown: + editPage: + hide: true +--- # rippled Version 0.90.0 Ripple has released `rippled` version 0.90.0, which introduces several enhancements that improve the reliability, scalability and security of the XRP Ledger. Ripple recommends that all server operators upgrade to version 0.90.0 by Thursday, 2018-03-15, for service continuity. diff --git a/blog/2018/rippled-0.90.1.md b/blog/2018/rippled-0.90.1.md index c8653f2681..e6f0ef96b5 100644 --- a/blog/2018/rippled-0.90.1.md +++ b/blog/2018/rippled-0.90.1.md @@ -1,3 +1,13 @@ +--- +date: 2018-03-22 +category: 2018 +labels: + - Release Notes +theme: + markdown: + editPage: + hide: true +--- # rippled version 0.90.1 Ripple has released `rippled` version 0.90.1, which includes fixes for issues reported by external security researchers. These issues, when exploited, could cause a `rippled` instance to restart or, in some circumstances, stop executing. diff --git a/blog/2018/rippled-1.0.0.md b/blog/2018/rippled-1.0.0.md index 7257876db1..b3891445cf 100644 --- a/blog/2018/rippled-1.0.0.md +++ b/blog/2018/rippled-1.0.0.md @@ -1,3 +1,13 @@ +--- +date: 2018-05-31 +category: 2018 +labels: + - Release Notes +theme: + markdown: + editPage: + hide: true +--- # rippled Version 1.0.0 Today, after almost 6 years of hard work, Ripple is very pleased to announce the release of `rippled` version 1.0.0. diff --git a/blog/2018/rippled-1.0.1.md b/blog/2018/rippled-1.0.1.md index 4262d2d829..e0dff4140b 100644 --- a/blog/2018/rippled-1.0.1.md +++ b/blog/2018/rippled-1.0.1.md @@ -1,3 +1,13 @@ +--- +date: 2018-06-14 +category: 2018 +labels: + - Release Notes +theme: + markdown: + editPage: + hide: true +--- # rippled Version 1.0.1 Ripple has released `rippled` version 1.0.1, which includes fixes for issues identified by Ripple engineers and reported by external security researchers. These issues, when exploited, could cause a `rippled` instance to restart or, in some circumstances, stop executing. diff --git a/blog/2018/rippled-1.1.0.md b/blog/2018/rippled-1.1.0.md index 05eef0ed58..c7e37659d4 100644 --- a/blog/2018/rippled-1.1.0.md +++ b/blog/2018/rippled-1.1.0.md @@ -1,3 +1,13 @@ +--- +date: 2018-09-17 +category: 2018 +labels: + - Release Notes +theme: + markdown: + editPage: + hide: true +--- # Introducing XRP Ledger (rippled) version 1.1.0 Ripple is pleased to announce the release of **XRP Ledger (`rippled`) version 1.1.0.** diff --git a/blog/2018/rippled-1.1.1.md b/blog/2018/rippled-1.1.1.md index a394966dde..8e9a77123c 100644 --- a/blog/2018/rippled-1.1.1.md +++ b/blog/2018/rippled-1.1.1.md @@ -1,3 +1,13 @@ +--- +date: 2018-10-23 +category: 2018 +labels: + - Release Notes +theme: + markdown: + editPage: + hide: true +--- # rippled Version 1.1.1 Ripple has released `rippled` version 1.1.1, which improves handling of validator list sites. These changes improve retrieval of Ripple's recommended UNL for servers in restrictive network environments, and prevent incorrect behavior in cases where a server is unable to fetch a validator list update before the previous list expires. @@ -22,11 +32,13 @@ For other platforms, please compile v1.1.1 from source. See the [`rippled` sourc The first log entry should be the change setting the version: - commit 72e6005f562a8f0818bc94803d222ac9345e1e40 - Author: seelabs - Date: Fri Oct 19 13:12:40 2018 -0400 +```text +commit 72e6005f562a8f0818bc94803d222ac9345e1e40 +Author: seelabs +Date: Fri Oct 19 13:12:40 2018 -0400 - Set version to 1.1.1 + Set version to 1.1.1 +``` ## Network Update diff --git a/blog/2018/rippled-1.1.2.md b/blog/2018/rippled-1.1.2.md index 071712d594..500c56e3ef 100644 --- a/blog/2018/rippled-1.1.2.md +++ b/blog/2018/rippled-1.1.2.md @@ -1,3 +1,13 @@ +--- +date: 2018-11-07 +category: 2018 +labels: + - Release Notes +theme: + markdown: + editPage: + hide: true +--- # Introducing XRP Ledger (rippled) version 1.1.2 Ripple is proud to announce the release of **XRP Ledger** (`rippled`) version 1.1.2. diff --git a/blog/2018/rippled-boost166-warning.md b/blog/2018/rippled-boost166-warning.md index 95d0ac4e2a..54a244e6a0 100644 --- a/blog/2018/rippled-boost166-warning.md +++ b/blog/2018/rippled-boost166-warning.md @@ -1,3 +1,14 @@ +--- +date: 2018-01-12 +category: 2018 +labels: + - Advisories + - Development +theme: + markdown: + editPage: + hide: true +--- # Boost 1.66 Not Supported for rippled 0.81.0 A warning to developers: `rippled` versions 0.81.0 and earlier do not compile with the recently-released Boost library version 1.66.0. To compile `rippled` yourself, Ripple recommends using **Boost version 1.65.1**. The minimum supported version of Boost is 1.58.0, which is included in the official repositories of Ubuntu 16.04 Xenial. diff --git a/blog/2018/rippled-validator-key-replacement.md b/blog/2018/rippled-validator-key-replacement.md index 95f83140bd..7144f47555 100644 --- a/blog/2018/rippled-validator-key-replacement.md +++ b/blog/2018/rippled-validator-key-replacement.md @@ -1,6 +1,15 @@ +--- +date: 2018-01-17 +category: 2018 +labels: + - Advisories +theme: + markdown: + editPage: + hide: true +--- # rippled Validator Key Replacement - On Wednesday, January 18, 2018, as described in the [0.81.0 release notes](https://github.com/ripple/rippled/blob/develop/RELEASENOTES.md), the current validator keys on all five Ripple-operated `rippled` validator servers will be replaced. **If you have been using the previous recommended default configuration** and do not reconfigure your `rippled` server to the new recommended default configuration before that time, then your `rippled` server will stop seeing validated ledgers. Ripple strongly recommends upgrading to `rippled` version 0.81.0 immediately. @@ -19,28 +28,31 @@ Ripple recommends that you: * After starting your `rippled` server, confirm that it is configured to use the new defaults by executing: - /opt/ripple/bin/rippled validators + ```sh + /opt/ripple/bin/rippled validators + ``` The result should include the following: - "local_static_keys" : [], - "publisher_lists" : [ - { - "available" : true, - "expiration" : "2018-Jan-23 00:00:00", - "list" : [ - "nHB1FqfBpNg7UTpiqEUkKcAiWqC2PFuoGY7FPWtCcXAxSkhpqDkm", - "nHUpwrafS45zmi6eT72XS5ijpkW5JwfL5mLdPhEibrqUvtRcMAjU", - "nHUBGitjsiaiMJBWKYsJBHU2shmYt9m29hRqoh8AS5bSAjXoHmdd", - "nHUXh1ELizQ5QLLqtNaVEbbbfMdq3wMkh14aJo5xi83xzzaatWWP", - "nHUgoJvpqXZMZwxh8ZoFseFJEVF8ryup9r2mFYchX7ftMdNn3jLT" - ], - "pubkey_publisher" : "ED2677ABFFD1B33AC6FBC3062B71F1E8397C1505E1C42C64D11AD1B28FF73F4734", - "seq" : 2, - "version" : 1 - } - ], - + ```json + "local_static_keys" : [], + "publisher_lists" : [ + { + "available" : true, + "expiration" : "2018-Jan-23 00:00:00", + "list" : [ + "nHB1FqfBpNg7UTpiqEUkKcAiWqC2PFuoGY7FPWtCcXAxSkhpqDkm", + "nHUpwrafS45zmi6eT72XS5ijpkW5JwfL5mLdPhEibrqUvtRcMAjU", + "nHUBGitjsiaiMJBWKYsJBHU2shmYt9m29hRqoh8AS5bSAjXoHmdd", + "nHUXh1ELizQ5QLLqtNaVEbbbfMdq3wMkh14aJo5xi83xzzaatWWP", + "nHUgoJvpqXZMZwxh8ZoFseFJEVF8ryup9r2mFYchX7ftMdNn3jLT" + ], + "pubkey_publisher" : "ED2677ABFFD1B33AC6FBC3062B71F1E8397C1505E1C42C64D11AD1B28FF73F4734", + "seq" : 2, + "version" : 1 + } + ], + ``` ## Impact of Not Upgrading @@ -59,7 +71,7 @@ For other platforms, please [compile version 0.81.0 from source](https://github. The first log entry should be the change setting the version: -``` +```text commit 4e8c8deeaac83d18eb62c95b7425d96e11847a41 Author: Nikolaos D. Bougalis Date: Wed Jan 3 14:43:42 2018 -0800 diff --git a/blog/2019/corrections-to-data-api-xrp-charts-metrics.md b/blog/2019/corrections-to-data-api-xrp-charts-metrics.md index 5679b24e4c..e249b5aa02 100644 --- a/blog/2019/corrections-to-data-api-xrp-charts-metrics.md +++ b/blog/2019/corrections-to-data-api-xrp-charts-metrics.md @@ -1,5 +1,9 @@ --- -category: 2020 +labels: + - Advisories + - Data API +category: 2019 +date: 2019-04-04 theme: markdown: editPage: diff --git a/blog/2019/discover-xrp-ledger-explorer.md b/blog/2019/discover-xrp-ledger-explorer.md index 22356b955c..86bdc50999 100644 --- a/blog/2019/discover-xrp-ledger-explorer.md +++ b/blog/2019/discover-xrp-ledger-explorer.md @@ -1,3 +1,13 @@ +--- +labels: + - Features +category: 2019 +date: 2019-07-03 +theme: + markdown: + editPage: + hide: true +--- # Discover the XRP Ledger with Explorer! Today, a new XRP Ledger explorer is available for both test net and production at [explorer.xrpl.org](https://explorer.xrpl.org/). diff --git a/blog/2019/fix1578-enabled.md b/blog/2019/fix1578-enabled.md index ba66cb867e..e932336ae4 100644 --- a/blog/2019/fix1578-enabled.md +++ b/blog/2019/fix1578-enabled.md @@ -1,3 +1,13 @@ +--- +labels: + - Amendments +category: 2019 +date: 2019-03-23 +theme: + markdown: + editPage: + hide: true +--- # fix1578 is Now Available [As previously announced](https://developers.ripple.com/blog/2019/fix1578-expected.html), the fix1578 amendment [became enabled on the XRP Ledger](https://xrpcharts.ripple.com/#/transactions/7A80C87F59BCE6973CBDCA91E4DBDB0FC5461D3599A8BC8EAD02FA590A50005D) on 2019-03-23. diff --git a/blog/2019/fix1578-expected.md b/blog/2019/fix1578-expected.md index 70023c3650..7cac11e78d 100644 --- a/blog/2019/fix1578-expected.md +++ b/blog/2019/fix1578-expected.md @@ -1,3 +1,13 @@ +--- +labels: + - Amendments +category: 2019 +date: 2019-03-19 +theme: + markdown: + editPage: + hide: true +--- # The fix1578 and fixTakerDryOfferRemoval Amendments are Expected The fix1578 amendment to the XRP Ledger, introduced in [`rippled` v1.2.0](https://github.com/ripple/rippled/releases/tag/1.2.0), has [gained support from a majority of trusted validators](https://xrpcharts.ripple.com/#/transactions/147C93F2D60CB7A3FEC16957B6BD64A6D5C4411DD00D82B51189B5DE9A6FC438). Currently, it is expected to become enabled on 2019-03-23. diff --git a/blog/2019/fixmasterkeyasregularkey-1day.md b/blog/2019/fixmasterkeyasregularkey-1day.md index 0719431a27..67cbc14fe0 100644 --- a/blog/2019/fixmasterkeyasregularkey-1day.md +++ b/blog/2019/fixmasterkeyasregularkey-1day.md @@ -1,3 +1,13 @@ +--- +labels: + - Amendments +date: 2019-09-30 +category: 2019 +theme: + markdown: + editPage: + hide: true +--- # fixMasterKeyAsRegularKey is Expected Tomorrow The fixMasterKeyAsRegularKey amendment to the XRP Ledger, introduced in [`rippled` v1.3.1](https://github.com/ripple/rippled/releases/tag/1.3.1), is expected to become enabled shortly past midnight UTC on 2019-10-02. Operators of `rippled` servers **must** upgrade to v1.3.1 (or higher) by that time. diff --git a/blog/2019/fixmasterkeyasregularkey-enabled.md b/blog/2019/fixmasterkeyasregularkey-enabled.md index 64ebc1b5d4..f94cb775b8 100644 --- a/blog/2019/fixmasterkeyasregularkey-enabled.md +++ b/blog/2019/fixmasterkeyasregularkey-enabled.md @@ -1,3 +1,13 @@ +--- +labels: + - Amendments +date: 2019-10-02 +category: 2019 +theme: + markdown: + editPage: + hide: true +--- # fixMasterKeyAsRegularKey is Now Available [As previously announced](https://xrpl.org/blog/2019/fixmasterkeyasregularkey-expected.html), the fixMasterKeyAsRegularKey amendment [became enabled on the XRP Ledger](https://xrpcharts.ripple.com/#/transactions/61096F8B5AFDD8F5BAF7FC7221BA4D1849C4E21B1BA79733E44B12FC8DA6EA20) on 2019-10-02. @@ -34,4 +44,4 @@ Other resources: * [The XRP Ledger Dev Blog](https://xrpl.org/blog/) * Ripple Technical Services: -* [XRP Chat Forum](http://www.xrpchat.com/) \ No newline at end of file +* [XRP Chat Forum](http://www.xrpchat.com/) diff --git a/blog/2019/fixmasterkeyasregularkey-expected.md b/blog/2019/fixmasterkeyasregularkey-expected.md index e110321929..0d331282be 100644 --- a/blog/2019/fixmasterkeyasregularkey-expected.md +++ b/blog/2019/fixmasterkeyasregularkey-expected.md @@ -1,3 +1,13 @@ +--- +labels: + - Amendments +date: 2019-09-18 +category: 2019 +theme: + markdown: + editPage: + hide: true +--- # The fixMasterKeyAsRegularKey Amendment is Expected 2019-10-02 The fixMasterKeyAsRegularKey amendment to the XRP Ledger, introduced in [`rippled` v1.3.1](https://github.com/ripple/rippled/releases/tag/1.3.1), has [gained support from a majority of trusted validators](https://xrpcharts.ripple.com/#/transactions/EE38E5927605FAB1BD8CFE44C9BE5118B4FD558F846E3DA717C23DA2ADB65991). Currently, it is expected to become enabled on 2019-10-02. As long as the fixMasterKeyAsRegularKey amendment continues to have the support of at least 80% of trusted validators continuously, it will become enabled on the scheduled date. diff --git a/blog/2019/fixtakerdryofferremoval-enabled.md b/blog/2019/fixtakerdryofferremoval-enabled.md index 62e4c6353e..1046e0c163 100644 --- a/blog/2019/fixtakerdryofferremoval-enabled.md +++ b/blog/2019/fixtakerdryofferremoval-enabled.md @@ -1,6 +1,16 @@ +--- +labels: + - Amendments +category: 2019 +date: 2019-04-02 +theme: + markdown: + editPage: + hide: true +--- # fixTakerDryOfferRemoval is Now Available -[As previously announced](https://developers.ripple.com/blog/2019/fix1578-expected.html), the fixTakerDryOfferRemoval amendment [became enabled on the XRP Ledger](https://xrpcharts.ripple.com/#/transactions/C42335E95F1BD2009A2C090EA57BD7FB026AD285B4B85BE15F669BA4F70D11AF) on 2019-04-02. +[As previously announced](./fix1578-expected.md), the fixTakerDryOfferRemoval amendment [became enabled on the XRP Ledger](https://xrpcharts.ripple.com/#/transactions/C42335E95F1BD2009A2C090EA57BD7FB026AD285B4B85BE15F669BA4F70D11AF) on 2019-04-02. ## Action Required diff --git a/blog/2019/interledger-checkin.md b/blog/2019/interledger-checkin.md index 24ed10fd94..4bac945533 100644 --- a/blog/2019/interledger-checkin.md +++ b/blog/2019/interledger-checkin.md @@ -1,3 +1,13 @@ +--- +labels: + - Features +category: 2019 +date: 2019-04-03 +theme: + markdown: + editPage: + hide: true +--- # Interledger Check-in Here at Ripple, we've been eagerly following and contributing to the progress of [Interledger](https://interledger.org), a neutral standard for connecting all money systems into an Internet-like network of networks. Since finalizing the core protocol suite in late 2017, contributors from a variety of companies and backgrounds have been working hard on growing the ecosystem with implementations and infrastructure. Progress has been rapid and wild, so we thought we'd help make sense of it by checking in to see where Interledger stands today. diff --git a/blog/2019/labeling-the-internet-of-value.md b/blog/2019/labeling-the-internet-of-value.md index 3247867f9a..34269a3ba8 100644 --- a/blog/2019/labeling-the-internet-of-value.md +++ b/blog/2019/labeling-the-internet-of-value.md @@ -1,7 +1,12 @@ +--- +labels: + - Features +category: 2019 +date: 2019-07-12 +author: Rome Reginelli +--- # Labeling the Internet of Value -_By Rome Reginelli, Documentation Engineer at [Ripple](https://ripple.com/)_ - Blockchain technology raises new questions about the roles of privacy and anonymity in the function of money. While all transactions are a matter of public record, the parties involved in the transactions are represented by pseudonyms, and information about who those parties are may be hard to come by. Even more obscure is information about those whose computing power and maintenance efforts underpin the blockchain. While there are lots of good reasons to maintain privacy around some entities and events, there are also situations that call for publicly establishing one's identity and reputation. The [`xrp-ledger.toml` specification](/docs/references/xrp-ledger-toml/) provides a flexible standard for voluntarily publishing information about who you are and what you're doing with the XRP Ledger. In this post, I explore the process of creating an `xrp-ledger.toml` file, explain why to use it, and introduce [a new dev tool for checking `xrp-ledger.toml` files](/resources/dev-tools/xrp-ledger-toml-checker/). diff --git a/blog/2019/multisignreserve-enabled.md b/blog/2019/multisignreserve-enabled.md index 6b3d861c83..3a18388902 100644 --- a/blog/2019/multisignreserve-enabled.md +++ b/blog/2019/multisignreserve-enabled.md @@ -1,3 +1,13 @@ +--- +labels: + - Amendments +category: 2019 +date: 2019-04-17 +theme: + markdown: + editPage: + hide: true +--- # MultiSignReserve is Now Available [As previously announced](https://developers.ripple.com/blog/2019/multisignreserve-expected.html), the MultiSignReserve amendment [became enabled on the XRP Ledger](https://xrpcharts.ripple.com/#/transactions/C421E1D08EFD78E6B8D06B085F52A34A681D0B51AE62A018527E1B8F54C108FB) on 2019-04-17. diff --git a/blog/2019/multisignreserve-expected.md b/blog/2019/multisignreserve-expected.md index 230ce778a7..f395d51063 100644 --- a/blog/2019/multisignreserve-expected.md +++ b/blog/2019/multisignreserve-expected.md @@ -1,3 +1,13 @@ +--- +labels: + - Amendments +category: 2019 +date: 2019-04-04 +theme: + markdown: + editPage: + hide: true +--- # The MultiSignReserve Amendment is Expected 2019-04-17 The MultiSignReserve amendment to the XRP Ledger, introduced in [`rippled` v1.2.0](https://github.com/ripple/rippled/releases/tag/1.2.0), has [gained support from a majority of trusted validators](https://xrpcharts.ripple.com/#/transactions/E394F1DA552936FD26E5BBE6BF57B27869CA897EB4AF082AD22FFE7A259FED2B). Currently, it is expected to become enabled on 2019-04-17. As long as the MultiSignReserve amendment continues to have the support of at least 80% of trusted validators continuously, it will become enabled on the scheduled date. diff --git a/blog/2019/rippled-1.2.0.md b/blog/2019/rippled-1.2.0.md index aa350b6690..2578661286 100644 --- a/blog/2019/rippled-1.2.0.md +++ b/blog/2019/rippled-1.2.0.md @@ -1,3 +1,13 @@ +--- +labels: + - Release Notes +category: 2019 +date: 2019-02-13 +theme: + markdown: + editPage: + hide: true +--- # Introducing XRP Ledger (rippled) version 1.2.0 Ripple is pleased to announce the release of **XRP Ledger (`rippled`) version 1.2.0.** diff --git a/blog/2019/rippled-1.2.1.md b/blog/2019/rippled-1.2.1.md index d61c0832a0..342fe63191 100644 --- a/blog/2019/rippled-1.2.1.md +++ b/blog/2019/rippled-1.2.1.md @@ -1,3 +1,13 @@ +--- +labels: + - Release Notes +category: 2019 +date: 2019-02-26 +theme: + markdown: + editPage: + hide: true +--- # Introducing XRP Ledger (rippled) version 1.2.1 Ripple has released **version 1.2.1 of `rippled`**, our reference implementation of the core XRP Ledger server. diff --git a/blog/2019/rippled-1.2.2.md b/blog/2019/rippled-1.2.2.md index a40f396685..0217bef486 100644 --- a/blog/2019/rippled-1.2.2.md +++ b/blog/2019/rippled-1.2.2.md @@ -1,3 +1,13 @@ +--- +labels: + - Release Notes +category: 2019 +date: 2019-03-06 +theme: + markdown: + editPage: + hide: true +--- # Introducing XRP Ledger (rippled) version 1.2.2 Ripple has released **version 1.2.2 of rippled**, our reference implementation of the core XRP Ledger server. diff --git a/blog/2019/rippled-1.2.3.md b/blog/2019/rippled-1.2.3.md index 2d523e6100..ceb57b6014 100644 --- a/blog/2019/rippled-1.2.3.md +++ b/blog/2019/rippled-1.2.3.md @@ -1,3 +1,13 @@ +--- +labels: + - Release Notes +category: 2019 +date: 2019-04-02 +theme: + markdown: + editPage: + hide: true +--- # Introducing XRP Ledger (rippled) version 1.2.3 Ripple has released **version 1.2.3 of rippled**, the reference implementation of the core XRP Ledger protocol. diff --git a/blog/2019/rippled-1.2.4.md b/blog/2019/rippled-1.2.4.md index c28c5cdfdf..986d42c216 100644 --- a/blog/2019/rippled-1.2.4.md +++ b/blog/2019/rippled-1.2.4.md @@ -1,3 +1,13 @@ +--- +labels: + - Release Notes +category: 2019 +date: 2019-04-17 +theme: + markdown: + editPage: + hide: true +--- # Introducing XRP Ledger (rippled) version 1.2.4 Ripple has released **version 1.2.4 of rippled**, the reference implementation of the core XRP Ledger protocol. diff --git a/blog/2019/rippled-1.3.1.md b/blog/2019/rippled-1.3.1.md index 2513c9d14f..6c4bf097fe 100644 --- a/blog/2019/rippled-1.3.1.md +++ b/blog/2019/rippled-1.3.1.md @@ -1,3 +1,13 @@ +--- +labels: + - Release Notes +category: 2019 +date: 2019-07-25 +theme: + markdown: + editPage: + hide: true +--- # Introducing XRP Ledger (rippled) version 1.3.1 Ripple has released **version 1.3.1 of `rippled`**, the reference implementation of the core XRP Ledger protocol. To learn more about how to build and run a `rippled` server, see [Manage the Rippled Server](https://xrpl.org/manage-the-rippled-server.html). diff --git a/blog/2019/rippled-1.4.0.md b/blog/2019/rippled-1.4.0.md index 2d7d2de882..15c73a99e1 100644 --- a/blog/2019/rippled-1.4.0.md +++ b/blog/2019/rippled-1.4.0.md @@ -1,3 +1,13 @@ +--- +labels: + - Release Notes +category: 2019 +date: 2019-12-02 +theme: + markdown: + editPage: + hide: true +--- # Introducing XRP Ledger version 1.4.0 **XRP Ledger (`rippled` server) version 1.4.0** has been released. The XRP Ledger version 1.4.0 introduces several new features and overall improvements to the codebase, including the **DeletableAccounts** Amendment, which allows users to delete XRP Ledger accounts and recover some of their account base [reserve](https://xrpl.org/reserves.html) in the process. diff --git a/blog/2019/secure-development-practices.md b/blog/2019/secure-development-practices.md index 048e2af222..4979fcded0 100644 --- a/blog/2019/secure-development-practices.md +++ b/blog/2019/secure-development-practices.md @@ -1,7 +1,17 @@ +--- +labels: + - Features + - Security +category: 2019 +date: 2019-04-05 +theme: + markdown: + editPage: + hide: true +author: Nik Bougalis +--- # Protecting the Ledger: Secure Development Practices -_By Nik Bougalis, Engineering Manager_ - The primary mission of the C++ team at Ripple is to contribute to `rippled`, the reference implementation of the protocol that underpins the XRP Ledger. The codebase—which is now over 6 years old—has contributions from over 100 developers from all over the world. As a team, our primary focus is on ensuring that the codebase is solid, that the code is robust and that it is well-suited to be the core of the next-generation of financial infrastructure, one which allows value to not only move as fast and as efficiently as information does today, but to move securely as well. diff --git a/blog/2019/statement-on-the-biased-nonce-sense-paper.md b/blog/2019/statement-on-the-biased-nonce-sense-paper.md index c393b6ae4c..db990abc37 100644 --- a/blog/2019/statement-on-the-biased-nonce-sense-paper.md +++ b/blog/2019/statement-on-the-biased-nonce-sense-paper.md @@ -1,3 +1,13 @@ +--- +labels: + - Security +category: 2019 +date: 2019-01-14 +theme: + markdown: + editPage: + hide: true +--- # Statement on the “Biased Nonce Sense” Paper In the cryptography industry, it is well known that using repeated or insufficiently random "nonces" (also called "k" values) in ECDSA digital signatures carries security risks. A new [research paper](https://eprint.iacr.org/2019/023.pdf) authored by Joachim Breitner and Nadia Heninger discloses a more serious attack than was previously known on signatures with imperfect nonces. diff --git a/blog/2019/testnet-reset.md b/blog/2019/testnet-reset.md index 5940514984..f427b84ed4 100644 --- a/blog/2019/testnet-reset.md +++ b/blog/2019/testnet-reset.md @@ -1,9 +1,21 @@ +--- +labels: + - Advisories +date: 2019-08-30 +category: 2019 +theme: + markdown: + editPage: + hide: true +--- # XRP Testnet Has Been Reset -> **Update:** The second reset occurred as planned and the Testnet became fully available by approximately 7:56 PM PDT. The amendments that are enabled on the Testnet now match the status of amendments on the production Mainnet. - On 2019-08-27 at approximately 1:00 UTC (6 PM PDT), Ripple reset their XRP Testnet. This means that all accounts, balances, and settings in the Testnet have been deleted and all contents of the Testnet's decentralized exchange have been erased. However, in the process of resetting the XRP Testnet, a procedural issue caused amendments that were previously enabled to be disabled in the fresh ledger chain. Ripple plans to reset the XRP Testnet again today (2019-08-30) at 4 PM PDT. Starting at this time, the Testnet may be unavailable for a maintenance window lasting up to 4 hours. +{% admonition type="success" name="UPDATE" %} +The second reset occurred as planned and the Testnet became fully available by approximately 7:56 PM PDT. The amendments that are enabled on the Testnet now match the status of amendments on the production Mainnet. +{% /admonition %} + The production XRP Ledger, or Mainnet, is completely unaffected. This also has no effect on other test networks not run by Ripple. diff --git a/blog/2019/websocket-tool-update.md b/blog/2019/websocket-tool-update.md index 02cf82ff22..b81792fade 100644 --- a/blog/2019/websocket-tool-update.md +++ b/blog/2019/websocket-tool-update.md @@ -1,3 +1,13 @@ +--- +labels: + - Features +category: 2019 +date: 2019-06-24 +theme: + markdown: + editPage: + hide: true +--- # WebSocket Tool Update As part of [the recent site relaunch](/blog/2019/welcome-to-xrpl-org), the XRP Ledger Dev Portal has an updated version of the [WebSocket API Tool](/resources/dev-tools/websocket-api-tool). This tool lets you communicate directly with `rippled` servers, which power the XRP Ledger network. Among several of the improvements in this new version of the tool is that you can choose which servers to connect to, including the public servers Ripple runs, servers in the XRP Test Net, or your own server running locally on your own computer. diff --git a/blog/2019/welcome-to-xrpl-org.md b/blog/2019/welcome-to-xrpl-org.md index 105550803e..cc858ef887 100644 --- a/blog/2019/welcome-to-xrpl-org.md +++ b/blog/2019/welcome-to-xrpl-org.md @@ -1,3 +1,13 @@ +--- +labels: + - Features +category: 2019 +date: 2019-06-14 +theme: + markdown: + editPage: + hide: true +--- # Welcome to xrpl.org! xrpl.org is a new, community-driven website for developers to access technical documentation, developer tools, tutorials, and network metrics for the XRP Ledger. The XRP Ledger is one of the largest, most technically mature, open-source, public blockchain networks in the world. If you are learning about, building on, and contributing to the XRP Ledger, xrpl.org is your best resource. diff --git a/blog/2019/xrpl-devnet-launch.md b/blog/2019/xrpl-devnet-launch.md index cc90ecb84c..dbf1f9efa3 100644 --- a/blog/2019/xrpl-devnet-launch.md +++ b/blog/2019/xrpl-devnet-launch.md @@ -1,3 +1,13 @@ +--- +labels: + - Features +date: 2019-10-02 +category: 2019 +theme: + markdown: + editPage: + hide: true +--- # Discover Upcoming XRP Ledger Amendments and Features with Devnet! A new XRP Ledger Devnet is now available for developers to access upcoming features of XRPL on beta build versions of `rippled`, the C++ reference implementation of the XRP Ledger. diff --git a/blog/2020/requirefullycanonicalsig-expected.md b/blog/2020/requirefullycanonicalsig-expected.md index a1fe00e4ad..f499a62fd2 100644 --- a/blog/2020/requirefullycanonicalsig-expected.md +++ b/blog/2020/requirefullycanonicalsig-expected.md @@ -8,7 +8,6 @@ theme: editPage: hide: true --- - # The RequireFullyCanonicalSig Amendment is Expected 2020-07-03 The RequireFullyCanonicalSig amendment to the XRP Ledger, introduced in [`rippled` v1.5.0](https://github.com/ripple/rippled/releases/tag/1.5.0), has [gained support from a majority of trusted validators](https://xrpcharts.ripple.com/#/transactions/4DF3E28D6920D917CE0A0A9E341BC5F792B3584E2DD5E679BD7679FE0875AEE6). Currently, it is expected to become enabled on 2020-07-03 (UTC). As long as the RequireFullyCanonicalSig amendment continues to have the support of at least 80% of trusted validators continuously, it will become enabled on the scheduled date. diff --git a/blog/2020/rippled-1.4.0-upgrade-advisory.md b/blog/2020/rippled-1.4.0-upgrade-advisory.md index a02feb6e6c..c8910c1e7a 100644 --- a/blog/2020/rippled-1.4.0-upgrade-advisory.md +++ b/blog/2020/rippled-1.4.0-upgrade-advisory.md @@ -8,7 +8,6 @@ theme: editPage: hide: true --- - # XRP Ledger version 1.4.0 Upgrade Advisory Version 1.4.0 of the XRP Ledger core server (`rippled`) contains a change that can cause upgrades to take much longer than usual. diff --git a/blog/2020/rippled-1.5.0.md b/blog/2020/rippled-1.5.0.md index ef94d10483..2a4cdb6053 100644 --- a/blog/2020/rippled-1.5.0.md +++ b/blog/2020/rippled-1.5.0.md @@ -2,7 +2,7 @@ category: 2020 date: 2020-04-10 labels: - - Advisories + - rippled Release Notes theme: markdown: editPage: diff --git a/blog/2020/running-an-xrp-ledger-validator.md b/blog/2020/running-an-xrp-ledger-validator.md index c524163613..14e38f75e6 100644 --- a/blog/2020/running-an-xrp-ledger-validator.md +++ b/blog/2020/running-an-xrp-ledger-validator.md @@ -7,9 +7,9 @@ theme: markdown: editPage: hide: true +author: Mayur Bhandary --- # Running an XRP Ledger Validator -_by Mayur Bhandary, Software Engineer at Ripple_ Validators are the lifeblood of the XRP Ledger. This post seeks to explain the function and importance of validators on the XRP Ledger network. diff --git a/blog/2021/introducing-xrpl-js.md b/blog/2021/introducing-xrpl-js.md index 13d9f43b8a..c2218d277c 100644 --- a/blog/2021/introducing-xrpl-js.md +++ b/blog/2021/introducing-xrpl-js.md @@ -7,9 +7,9 @@ theme: date: 2021-10-20 labels: - xrpl.js Release Notes +author: Team RippleX --- # Introducing xrpl.js -_by Team RippleX_ [RippleX](https://ripple.com/ripplex/) and the [XRP Ledger Foundation (XRPLF)](https://xrplf.org/) are excited to announce xrpl.js **version 2.0.0**, a JavaScript/TypeScript library for interacting with the XRP Ledger (XRPL). Formerly known as ripple-lib, the library was renamed to better represent its role in the XRPL ecosystem and overhauled to take advantage of modern JavaScript features. diff --git a/blog/2021/introducing-xrpl-py-for-pythonistas.md b/blog/2021/introducing-xrpl-py-for-pythonistas.md index e496ce1551..05651eb9c5 100644 --- a/blog/2021/introducing-xrpl-py-for-pythonistas.md +++ b/blog/2021/introducing-xrpl-py-for-pythonistas.md @@ -7,9 +7,9 @@ theme: date: 2021-04-06 labels: - xrpl-py Release Notes +author: Team RippleX --- # Introducing xrpl-py for Pythonistas -_by Team RippleX_ Today, [RippleX](https://ripple.com/) and the [XRP Ledger Foundation (XRPLF)](https://xrplf.org/) are excited to announce the launch of [`xrpl-py`](https://github.com/XRPLF/xrpl-py), a pure Python implementation for interacting with the XRP Ledger. The `xrpl-py` library simplifies the hardest parts of XRP Ledger interaction—like serialization and transaction signing—by providing native Python methods and models for [XRP Ledger transactions](https://xrpl.org/transaction-formats.html) and [core server API](https://xrpl.org/api-conventions.html) ([rippled](https://github.com/ripple/rippled)) objects. diff --git a/blog/2021/message-routing-optimizations-pt-1-proposal-validation-relaying.md b/blog/2021/message-routing-optimizations-pt-1-proposal-validation-relaying.md index 5e635e84b2..67286db785 100644 --- a/blog/2021/message-routing-optimizations-pt-1-proposal-validation-relaying.md +++ b/blog/2021/message-routing-optimizations-pt-1-proposal-validation-relaying.md @@ -7,11 +7,10 @@ theme: date: 2021-03-16 labels: - Development +author: Gregory Tsipenyuk and Nikolaos D. Bougalis --- # Message Routing Optimizations, Pt. 1: Proposal & Validation Relaying -_by Gregory Tsipenyuk and Nikolaos D. Bougalis of Ripple_ - Like all peer-to-peer networks, the XRP Ledger needs a strategy to ensure that messages are propagated across the network. Of course, some types of messages are more important or more time-sensitive than others, so the XRP Ledger uses different strategies for relaying different types of messages. This blog post discusses the message propagation strategy used for “proposal” and “validation” messages, which are part of the [consensus protocol](https://xrpl.org/consensus.html), and the improvements that the RippleX team researched and is contributing. diff --git a/blog/2021/xrpl-node-configurator.md b/blog/2021/xrpl-node-configurator.md index 850f709ad9..d9be2e9b17 100644 --- a/blog/2021/xrpl-node-configurator.md +++ b/blog/2021/xrpl-node-configurator.md @@ -7,9 +7,9 @@ theme: date: 2021-04-14 labels: - Development +author: Javier Romero --- # XRP Ledger Node Configurator -_by Javier Romero of Ripple_ The XRP Ledger is open to anyone: all you need is a computer. For many people, using one of the many available client applications, user interfaces or portals is sufficient. But if you want to go beyond [exploring the ledger](https://livenet.xrpl.org/) or sending a payment, you need to run a server to participate as a node in the peer-to-peer network that manages the Ledger. diff --git a/blog/2022/introducing-xrpl-py-2.0.0beta.md b/blog/2022/introducing-xrpl-py-2.0.0beta.md index 81ecd59317..702b3366b4 100644 --- a/blog/2022/introducing-xrpl-py-2.0.0beta.md +++ b/blog/2022/introducing-xrpl-py-2.0.0beta.md @@ -3,11 +3,13 @@ category: 2022 date: 2022-12-13 labels: - xrpl-py Release Notes -editPage: - hide: true +theme: + markdown: + editPage: + hide: true +author: Team RippleX --- # Introducing xrpl-py version 2.0.0-beta.0 -_by Team RippleX_ Today, [RippleX](https://ripple.com/ripplex/) and the [XRP Ledger Foundation (XRPLF)](https://foundation.xrpl.org/) are proud to present **xrpl-py version 2.0.0-beta.0**. This beta version introduces three new ways to generate wallets, regular key support, and some breaking changes to the `Wallet` class.