Protocol /
SolutionStack
Protocol.SolutionStack History
Hide minor edits - Show changes to output
Changed lines 3-6 from:
This section of the wiki is for all the bits, additional protocols and ideas that might
sit atop or alongside the core ripple protocols that would offer a complete end-to-end, decentralized buying and selling or donating user experience. This includes but is not
limited to :
sit atop or alongside
limited to :
to:
This section of the wiki is intended to add some context to the ripple protocol details.
The aim is to list the functions of a complete end-to-end, decentralized buying and selling or donating user experience. This includes but is not limited to :
The aim is to list the functions of a complete end-to-end, decentralized buying and selling or donating user experience. This includes but is not limited to :
Added lines 22-24:
One view of the full stack from a user perspective is as follows, and aims to show where various
possible functions such as interest charges, path discover and security might sit.
Changed lines 3-4 from:
This section of the wiki is for all the bits, additional protocols and ideas that might sit atop or alongside the core ripple protocols that would offer a complete end-to-end, decentralized buying and selling or donating user experience. This includes but is not limited to :
to:
This section of the wiki is for all the bits, additional protocols and ideas that might
sit atop or alongside the core ripple protocols that would offer a complete end-to-end, decentralized buying and selling or donating user experience. This includes but is not
limited to :
sit atop or alongside the core ripple protocols that would offer a complete end-to-end, decentralized buying and selling or donating user experience. This includes but is not
limited to :
Changed lines 8-11 from:
* Marketplace Discovery - how one finds items one can buy or sell or donate with a given ripple account on a given host
to:
* Marketplace Discovery - how one finds items one can buy or sell or donate with
a given ripple account on a given host
Changed lines 13-21 from:
* Monetisation - how organisations running ripple servers offering both ripple and the kind of additional services outlined here might be able to cover their costs and be able to create reasonable profits, or benefits in the case of a charitable cause.
This section of the wiki is not intended for discussion of specific ripple use cases or deployment scenarios except as they relate to the general principles of the features listed above. The end goal is to develop additional protocols or at least the architectural principles of these additional key systems that add value to the core ripple protocol.
The term "Solution Stack" is appropriate since without these elements the core ripple protocol is not useful by itself. The obvious case is that successful path discovery is a pre-requisite to invoking a ripple payment. That said, there are multiple possible solutions to this problem and thus multiple possible Solution Stacks.
!!! Use Cases
The rippleusers mailing list has covered from time to time possible use cases of ripple, focusing on where ripple adds value to the prevailing exchange mechanisms offered by the mainstream financial system. The point of this section of the wiki is to develop more definitive ideas on how ripple might be extended and built upon to support such use cases. The aim should be to analyse the Solution Stack requirements for different use cases and formulate here the details of new protocols to enable key use cases. However the specific use cases really ought to be captured elsewhere, to which this section can then refer.
This section
The term "Solution Stack" is appropriate since without these elements the core ripple protocol is
!!! Use Cases
The rippleusers mailing list has covered from time to time possible use cases of ripple, focusing on where ripple adds value to the prevailing exchange mechanisms offered by the mainstream financial system. The point of this section of the wiki is to develop more definitive ideas on how ripple might be extended and built upon to support such use cases. The aim should be to analyse the Solution Stack requirements for different use cases and formulate here the details of new protocols to enable key use cases. However the specific use cases really ought to be captured elsewhere, to which this section can then refer.
to:
* Monetisation - how organisations running ripple servers offering both ripple and the kind of
additional services outlined here might be able to cover their costs and be able to create
reasonable profits, or benefits in the case of a charitable cause.
This section of the wiki is not intended for discussion of specific ripple use cases or deployment
scenarios except as they relate to the general principles of the features listed above. The end goal
is to develop additional protocols or at least the architectural principles of these additional key
systems that add value to the core ripple protocol.
Attach:SolutionStack.png
The term "Solution Stack" is appropriate since without these elements the core ripple protocol is
not useful by itself. The obvious case is that successful path discovery is a pre-requisite to
invoking a ripple payment. That said, there are multiple possible solutions to this problem and
thus multiple possible Solution Stacks.
April 09, 2011, at 11:04 PM
by - Ripple Non Core Solution Stack
Changed line 6 from:
* Marketplace Discovery - how one finds items one can buy or sell or donate with a given ripple account on a given host)
to:
* Marketplace Discovery - how one finds items one can buy or sell or donate with a given ripple account on a given host
Changed line 16 from:
The rippleusers mailing list has covered from time to time, possible use cases of ripple, focusing on where ripple adds value to the prevailing exchange mechanisms offered by the mainstream financial system. The point of this section of the wiki is to develop more definitive ideas on how ripple might be extended and built upon to support such use cases. The aim should be to analyse the Solution Stack requirements for different use cases and formulate here the details of new protocols to enable key use cases. However the specific use cases really ought to be captured elsewhere, to which this section can then refer.
to:
The rippleusers mailing list has covered from time to time possible use cases of ripple, focusing on where ripple adds value to the prevailing exchange mechanisms offered by the mainstream financial system. The point of this section of the wiki is to develop more definitive ideas on how ripple might be extended and built upon to support such use cases. The aim should be to analyse the Solution Stack requirements for different use cases and formulate here the details of new protocols to enable key use cases. However the specific use cases really ought to be captured elsewhere, to which this section can then refer.
Added lines 1-16:
!! Solution Stack
This section of the wiki is for all the bits, additional protocols and ideas that might sit atop or alongside the core ripple protocols that would offer a complete end-to-end, decentralized buying and selling or donating user experience. This includes but is not limited to :
* Path Discovery - how the routing onions used in the ripple protocol are created.
* Marketplace Discovery - how one finds items one can buy or sell or donate with a given ripple account on a given host)
* Host Discovery - how one finds the best host for one's own ripple account
* Monetisation - how organisations running ripple servers offering both ripple and the kind of additional services outlined here might be able to cover their costs and be able to create reasonable profits, or benefits in the case of a charitable cause.
This section of the wiki is not intended for discussion of specific ripple use cases or deployment scenarios except as they relate to the general principles of the features listed above. The end goal is to develop additional protocols or at least the architectural principles of these additional key systems that add value to the core ripple protocol.
The term "Solution Stack" is appropriate since without these elements the core ripple protocol is not useful by itself. The obvious case is that successful path discovery is a pre-requisite to invoking a ripple payment. That said, there are multiple possible solutions to this problem and thus multiple possible Solution Stacks.
!!! Use Cases
The rippleusers mailing list has covered from time to time, possible use cases of ripple, focusing on where ripple adds value to the prevailing exchange mechanisms offered by the mainstream financial system. The point of this section of the wiki is to develop more definitive ideas on how ripple might be extended and built upon to support such use cases. The aim should be to analyse the Solution Stack requirements for different use cases and formulate here the details of new protocols to enable key use cases. However the specific use cases really ought to be captured elsewhere, to which this section can then refer.
This section of the wiki is for all the bits, additional protocols and ideas that might sit atop or alongside the core ripple protocols that would offer a complete end-to-end, decentralized buying and selling or donating user experience. This includes but is not limited to :
* Path Discovery - how the routing onions used in the ripple protocol are created.
* Marketplace Discovery - how one finds items one can buy or sell or donate with a given ripple account on a given host)
* Host Discovery - how one finds the best host for one's own ripple account
* Monetisation - how organisations running ripple servers offering both ripple and the kind of additional services outlined here might be able to cover their costs and be able to create reasonable profits, or benefits in the case of a charitable cause.
This section of the wiki is not intended for discussion of specific ripple use cases or deployment scenarios except as they relate to the general principles of the features listed above. The end goal is to develop additional protocols or at least the architectural principles of these additional key systems that add value to the core ripple protocol.
The term "Solution Stack" is appropriate since without these elements the core ripple protocol is not useful by itself. The obvious case is that successful path discovery is a pre-requisite to invoking a ripple payment. That said, there are multiple possible solutions to this problem and thus multiple possible Solution Stacks.
!!! Use Cases
The rippleusers mailing list has covered from time to time, possible use cases of ripple, focusing on where ripple adds value to the prevailing exchange mechanisms offered by the mainstream financial system. The point of this section of the wiki is to develop more definitive ideas on how ripple might be extended and built upon to support such use cases. The aim should be to analyse the Solution Stack requirements for different use cases and formulate here the details of new protocols to enable key use cases. However the specific use cases really ought to be captured elsewhere, to which this section can then refer.