Search the Community
Showing results for tags 'documentation'.
The search index is currently processing. Current results may not be complete.
Found 4 results
Minimum search term is 4 characters long. Can't find what you want? Click here for the custom google search instead.
I've created a proposal for a file that would replace the old "ripple.txt" way of reporting information about how you use the XRP Ledger. (For reasons including the fact that "XRP" isn't "Ripple"!) If adopted, I expect this could be a key piece in how validator operators verify their identity, and may also be useful for client applications for various other purposes. (For example, if the owner of an XRP Ledger address is verified, client apps could show provided contact info or description alongside that address.) For people who run validators or actively develop tools and applications on top of the XRP Ledger, your feedback is very important because this spec doesn't serve a purpose unless you find it useful! If you fit that description, please take a look and provide your input on the draft specification here: https://github.com/ripple/ripple-dev-portal/pull/507
... and that means the Known Amendments page has been updated. rippled 1.2.0 will introduce (at least) 3 new amendments, which (if enabled following 2 weeks of support from 80+% of validators) introduce transaction processing changes. In this case, the changes are pretty small: fixTakerDryOfferRemoval fixes a bug where dry offers sometimes weren't properly removed when autobridging. Thanks to GitHub user demonstefan for contributing the code that eventually became this amendment! fix1578 makes fill-or-kill offers return a new tecKILLED code (as requested on this very forum) when they're killed. It also makes TrustSet transactions fail when they can't set the NoRipple flag, instead of "succeeding" without changing the flag. Both of these changes are meant to make the transaction engine just a little less tricksy. MultiSignReserve reduces the reserve requirement for signer lists so they occupy less XRP for just sitting there. Stay tuned for more information about the upcoming release and the features in it!
Salutations! We've published new documentation to the XRP Ledger Dev Portal! These changes include: List Your Exchange on XRP Charts - New guide for exchanges that want to see their volume show up on XRP Charts. https://developers.ripple.com/list-your-exchange-on-xrp-charts.html Ledger History - Explainer for the history that servers store and the options that exist around this. https://developers.ripple.com/ledger-history.html Online Deletion - Info on why and how the online deletion feature of `rippled` works. https://developers.ripple.com/online-deletion.html Plus, no less than three new tutorials around ledger history and deletion: Configure Online Deletion: https://developers.ripple.com/configure-online-deletion.html Configure Advisory Deletion: https://developers.ripple.com/configure-advisory-deletion.html Configure Full History: https://developers.ripple.com/configure-full-history.html As always, we welcome feedback and contributions. If these docs helped you, or if you need help figuring them out, we'd love to hear from you!