Bah non ça ne fonctionne pas comme ça... enfin bon tu crois ce que tu veux...
Gateways
A gateway is any person or organization that enables users to put money into and take money out of the Ripple network. They accept currency deposits from users and issue balances into Ripple’s distributed ledger. Furthermore, gateways redeem ledger balances against the deposits they hold when currency is withdrawn.
In practice, gateways are similar to banks, yet they share one global ledger known as the Ripple network. Depending on the type and degree of interaction a user has with a gateway, the gateway may have Anti-money laundering (AML) or Know your customer (KYC) policies requiring verification of identification, address, nationality, etc. Such policies are designed to prevent criminal activity.
Trustlines
Users must ‘extend trust’ to the Ripple gateway that holds their deposit. This manual creation of a trustline indicates to the Ripple network that the user is comfortable with the gateway’s counterparty risk. Furthermore, the user must put a quantitative limit on this trust and create a similar limit for each currency on deposit at that gateway. For example, if a user deposits $50 and BTC 2.00 at The Rock Trading, the user will have to grant trust of at least that much in both currencies to the gateway for the monies to be available in the Ripple network. It is not recommended for a user to grant trust to other parties unless the user fully understands the ramifications.
Rippling
When establishing a trustline, an option will present itself in the client to allow ‘rippling’. If this option is checked and a new trust is established in the same currency as an existing trustline, the Ripple client will present a warning to the user. Trusting multiple gateways in the same currency and allowing the rippling feature will subject the user’s balance of that currency to automatically switch (or ripple) between one gateway and another. This will not change the user’s total balance, but will alter the issuer of the balance. This advanced tab feature may be a source of confusion for some.
Users who wish to allow rippling can earn a small transit fee for providing inter-gateway liquidity. It is not recommended for a user to allow rippling unless they fully understand the ramifications.
Consensus ledger
(...)
The goal of consensus is for each server to apply the same set of transactions to the current ledger. Servers continually receive transactions from other servers on the network. These transactions form a pool of transactions waiting to be added to the ledger. This pool is called a candidate set. At the same time, the server receives proposals from other servers on the network. A proposal is a set of transactions to consider applying to the ledger.
The server routes incoming proposals based on something called the ‘unique node list’ or UNL. A UNL is simply a list of external servers.
Proposals from servers not on the UNL are ignored. The server only pays attention to proposals from servers that are on its UNL. The transactions in the incoming proposals are compared against the server’s candidate set. When a transaction in an incoming proposal matches a transaction in the candidate set, that transaction receives one vote. The server continues to check the incoming proposals against the candidate set until a timer expires.