45ff08b6aa
* Revert 0efb929898
* Advisory delete setting of 0 (never) does not affect history fetching
The previous commit addressing RIPD-1112 could interact with
advisory delete and cause some history not to be acquired even
configured to acquire. This reverts that commit and provides
a better fix.
The advisory delete setting protects ledgers from being
removed by online delete by exempting them until they are
approved for purge by administrative command. However, not
connecting this with history acquisition could cause new
ledgers in the protected range not to be acquired if the
server loses sync.
With this change, the default advisory delete setting, zero (never)
causes the regular server history setting to control the acquisition
of history. Setting advisory delete to a value greater than zero,
if advisory delete is enabled, will cause the server to fetch and
maintain history back to that point.
This should produce sane behavior across server restarts, losses of
sync, and so on. You can no longer use the "hack" of setting
advisory delete to zero to tell the server to fetch and keep as much
history as possible, but you can achieve the same effect by setting
it to one.
#The World’s Fastest and Most Secure Payment System
What is Ripple?
Ripple is the open-source, distributed payment protocol that enables instant payments with low fees, no chargebacks, and currency flexibility (for example dollars, yen, euros, bitcoins, or even loyalty points). Businesses of any size can easily build payment solutions such as banking or remittance apps, and accelerate the movement of money. Ripple enables the world to move value the way it moves information on the Internet.
What is a Gateway?
Ripple works with gateways: independent businesses which hold customer deposits in various currencies such as U.S. dollars (USD) or Euros (EUR), in exchange for providing cryptographically-signed issuances that users can send and trade with one another in seconds on the Ripple network. Within the protocol, exchanges between multiple currencies can occur atomically without any central authority to monitor them. Later, customers can withdraw their Ripple balances from the gateways that created those issuances.
How do Ripple payments work?
A sender specifies the amount and currency the recipient should receive and Ripple automatically converts the sender’s available currencies using the distributed order books integrated into the Ripple protocol. Independent third parties acting as market makers provide liquidity in these order books.
Ripple uses a pathfinding algorithm that considers currency pairs when converting from the source to the destination currency. This algorithm searches for a series of currency swaps that gives the user the lowest cost. Since anyone can participate as a market maker, market forces drive fees to the lowest practical level.
What can you do with Ripple?
The protocol is entirely open-source and the network’s shared ledger is public information, so no central authority prevents anyone from participating. Anyone can become a market maker, create a wallet or a gateway, or monitor network behavior. Competition drives down spreads and fees, making the network useful to everyone.
###Key Protocol Features
-
XRP is Ripple’s native [cryptocurrency] (http://en.wikipedia.org/wiki/Cryptocurrency) with a fixed supply that decreases slowly over time, with no mining. XRP acts as a bridge currency, and pays for transaction fees that protect the network against spam.
-
Pathfinding discovers cheap and efficient payment paths through multiple order books allowing anyone to trade anything. When two accounts aren’t linked by relationships of trust, the Ripple pathfinding engine considers intermediate links and order books to produce a set of possible paths the transaction can take. When the payment is processed, the liquidity along these paths is iteratively consumed in best-first order.
-
Consensus confirms transactions in an atomic fashion, without mining, ensuring efficient use of resources.
###Join The Ripple Community
 |
 |
 |
|---|---|---|
| Transact on the fastest payment infrastructure | Build Imaginative Apps | Contribute to the Ripple Protocol Implementation |
#rippled - Ripple P2P server
##
This is the repository for Ripple's rippled, reference P2P server.
###Build instructions:
###Setup instructions:
###Issues
Repository Contents
./bin
Scripts and data files for Ripple integrators.
./build
Intermediate and final build outputs.
./Builds
Platform or IDE-specific project files.
./doc
Documentation and example configuration files.
./src
Source code directory. Some of the directories contained here are external repositories inlined via git-subtree, see the corresponding README for more details.
./test
Javascript / Mocha tests.
License
Ripple is open source and permissively licensed under the ISC license. See the LICENSE file for more details.
###For more information:
- Ripple Wiki - https://ripple.com/wiki/
- Ripple Primer - https://ripple.com/ripple_primer.pdf
- Ripple Primer (Market Making) - https://ripple.com/ripple-mm.pdf
- Ripple Gateway Primer - https://ripple.com/ripple-gateways.pdf
- Consensus - https://wiki.ripple.com/Consensus
Copyright © 2015, Ripple Labs. All rights reserved.
Portions of this document, including but not limited to the Ripple logo, images and image templates are the property of Ripple Labs and cannot be copied or used without permission.