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.
As previously announced, the fixMasterKeyAsRegularKey amendment became enabled on the XRP Ledger on 2019-10-02.
The fixMasterKeyAsRegularKey amendment to the XRP Ledger, introduced in rippled v1.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.
The fixMasterKeyAsRegularKey amendment to the XRP Ledger, introduced in rippled v1.3.1, has gained support from a majority of trusted validators. 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.
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.
The production XRP Ledger, or Mainnet, is completely unaffected. This also has no effect on other test networks not run by Ripple.
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.
This release supersedes version 1.3.0. Version 1.3.1 addresses deadlock conditions reported by some users late in the release cycle for 1.3.0.
By Rome Reginelli, Documentation Engineer at Ripple
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 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.
Today, a new XRP Ledger explorer is available for both test net and production at explorer.xrpl.org.
As part of the recent site relaunch, the XRP Ledger Dev Portal has an updated version of the 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.
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.