Introduction

Protocol.Introduction History

Hide minor edits - Show changes to output

March 13, 2008, at 03:03 PM by 190.33.59.5 -
Changed lines 26-28 from:
* [[Ripple Client Examples]] - examples of clients that might connect to a ripple server and use the ripple API

to:

February 18, 2008, at 08:08 PM by 190.33.186.68 -
Changed lines 26-28 from:
to:
* [[Ripple Client Examples]] - examples of clients that might connect to a ripple server and use the ripple API

Changed lines 25-26 from:
to:
* [[TCPBinding]] - a binding to the TCP protocol as a message transport layer
Changed lines 14-15 from:
to:
* Daniel Reeves
Changed lines 1-6 from:
!! %center%Ripple Protocol

%center%''Design Outline
''

%center%
''by Ryan Fugger''
to:
!! Ripple Protocol Documents

'''Main Author'''

* Ryan Fugger

December 10, 2006, at 09:40 AM by ryan - New division into core protocol and extensions
Changed lines 1-2 from:
!! %center%Ripple Application Protocol
to:
!! %center%Ripple Protocol
Deleted lines 14-17:
'''Goal'''

The goal is to define a protocol enabling nodes to make and maintain mutual-credit accounts between them, and use the network of these accounts for making payments by finding paths to the payment recipient and passing obligations down those paths.  Nodes should also be able to verify another's reputation by checking the available credit through the network to the target node.

Changed lines 17-29 from:
This document outlines in an abstract way the types of messages that need to be passed between nodes and the data contained in those messages.

'''Sections'''

*
[[Protocol/Introduction]]
* [[Protocol/Network Structure]]
* [[Protocol/Host-Level Messages]]
*
[[Protocol/Accounts]]
* [[Protocol/Initializing Payment]]
* [[Protocol/Path Discovery]]
* [[Protocol/Payment Transaction]]
* [[Protocol/Routing]]

to:
'''Documents'''

* [[PaymentProtocol]] - core network structure and transaction mechanism
* [[RoutingExtension]] - standard path-finding/payment routing
* [[ChannelExtension]] - advertisements through
the network, constructing paths for later use
*
[[AccountExtension]] - standard shared accounts between two Ripple nodes
*
[[SCTPBinding]] - a binding to the SCTP protocol as a message transport layer
Changed lines 34-36 from:
Each section has its own work page for discussion.
to:
[[Protocol/Work Page]]

Each
section has its own work page for discussion, linked to at the top and bottom of the document.
Changed line 25 from:
* [[Procotol/Introduction]]
to:
* [[Protocol/Introduction]]
Added lines 1-34:
!! %center%Ripple Application Protocol

%center%''Design Outline''

%center%''by Ryan Fugger''

'''Contributors'''

* Brandyn Webb
* Evgeni Pandurski
* Matthew Toseland
* Jiri Baum
* Stanislav Mazhara

'''Goal'''

The goal is to define a protocol enabling nodes to make and maintain mutual-credit accounts between them, and use the network of these accounts for making payments by finding paths to the payment recipient and passing obligations down those paths.  Nodes should also be able to verify another's reputation by checking the available credit through the network to the target node.

For background on the Ripple concept, see [[Money as IOUs in Social Trust Networks & A Proposal for a Decentralized Currency Network Protocol -> http://ripple.sourceforge.net/decentralizedcurrency.pdf]] (PDF).

This document outlines in an abstract way the types of messages that need to be passed between nodes and the data contained in those messages.

'''Sections'''

* [[Procotol/Introduction]]
* [[Protocol/Network Structure]]
* [[Protocol/Host-Level Messages]]
* [[Protocol/Accounts]]
* [[Protocol/Initializing Payment]]
* [[Protocol/Path Discovery]]
* [[Protocol/Payment Transaction]]
* [[Protocol/Routing]]

Each section has its own work page for discussion.