RippleWiki | Main / Roadmap

December 01, 2010, at 12:31 AM by Ryan -

Changed lines 1-164 from:

This page discusses where we see Ripple going in the future. There are multiple possible ways forward, and to find the best ones will depend on user needs, so please share your thoughts. Suggestions and comments are welcome at [[mailto:info@ripplepay.com|info@ripplepay.com]].

[[#Ripplepay_v2|Ripplepay v2]]
*[[#Main_Goals|Main Goals]]
*[[#Plan|Plan]]
**[[#Rewrite_v2.0|Step 1: Ripplepay Rewrite (v2.0)]]
**[[#New_Features_v2.1|Step 2: New Features (v2.1)]]
**[[#More_New_Features_v2.2|Step 3: More New Features (v2.2)]]
[[#Future|Future Possibilities]]
*[[#Wishlist|Wishlist]]

[[#Ripplepay_v2]]
!!Ripplepay v2

What should the next version of software powering Ripplepay do?

!!! Main Goals

* Make it easy to connect to the Ripple network.
* Make it easy to discover uses for Ripple.

[[#Plan]]
!!! Plan

Rewrite the Ripplepay codebase, deploy, then add gradually release new features. Prioritize new features into to major sets in terms of priority and which ones complement each other best, keeping in mind the main goals above.

[[#Rewrite_v2.0]]
!!!! Step 1: Ripplepay Rewrite (v2.0)

The existing codebase needs to be whipped into shape to support new features. Some implementation aspects will be redesigned, and a few new features will be added if they are easy or convenient to do at this stage.

* Technical design improvements
* Pre-calculate routes (by cheapest, then shortest)
* Process payments in queue to avoid multi-thread problems

* Translations

* Data-driven news/blog

* Multiple accounts between the same two users

* New layout, skin, logo

[[#New_Features_v2.1]]
!!!! Step 2: New Features (v2.1)

* Integrate into user/merchant sites
* Pre-generated code snippets, e.g. "Donate"/"Pay with Ripple"/"Connect to me"/"Offer/request credit" buttons, etc.
* Ripplepay API
* access to Ripplepay.com accounts, payments, market data, functions, etc.
* this is different from the transaction server interface

* Record/redeem obligation
* make/request entries on existing accounts
* send invites for new account along with IOU/UOMe
* new account is registered with a balance, but zero credit limits

* Login with Open ID, Facebook, Google, etc.

* Import friends from Facebook, Yahoo, Google, etc.

* Introductory presentation
* [[https://ripplexchange.com/viewtopic.php?f=9&t=30 | screencast]]

* Sandbox to create new dummy users and make test payments; generally play around with Ripple

* Publish profile data to help build trust
* profile picture
* connections
* transaction history
* various degrees of privacy, a la facebook: private, friends, friends-of-friends, public
* request to see a user's private data; or propose to both expose private data simultaneously
* highlight the other user's dealings with those in your network; hide or minimize the rest, since it can be faked
* develop a metric so other users can quickly ascertain the quality of a user's participation in the system
* see [[#Flagging | Flag a connection as non-participatory]] below
* should probably default to letting connections see everything, and warn them if you make it so they can't
* maybe there should be no way to turn this off?

* [[http://ripple-project.org/wiki/Main/UpgradeFromLETS | Tools/materials for migrating a LETS to Ripple]]
* every user starts with an account with the central LETS collective
* users should then be encouraged to make connections among themselves

[[#More_New_Features_v2.2]]
!!!! Step 3: More New Features (v2.2)

* Marketplace
* offers/requests
* filter only those postings in my connected network
* filter by location
* search by keyword

* Subscriptions/recurring payments?

* Circular debt cancellation?

* Custom currency units?
* needs custom exchange rates?

* Custom exchange rates?
* needs cheapest-route algorithm
* pre-calculate!
* also includes same-currency exchange rates, ie, transaction fees
* risks turning Ripple into a speculators' casino

* Sponsorship?
* allow users to sign up for automated donations

* [[http://opentransact.org/ | OpenTransact]] support

* Find users near me
* geolocation
* privacy considerations

* Automatic credit limit adjustment
* allow credit limits to grow automatically on selected accounts as obligations are repeatedly issued and settled over time, which can be interpreted as a maturing of the credit relationship
* gradually shrink credit limits on stagnant accounts

* Prioritize holding/discharge of obligations on certain accounts over others?
* affects payment routing
* not compatible with naive cheapest-path routing (if custom exchange rates are implemented)
* user would need to choose cheapest vs. best, or there could be a hybrid algorithm
* affects circular debt cancellation
* search for ways to turn undesirable holdings into more desirable ones

* Identity verification
* phone number
* [[http://www.bewelcome.org/wiki/Verification | address]]

* Directory
* Searchable directory of users, by e-mail, name, etc.

[[#Flagging]]
* Flag a connection as non-participatory
* sets their credit limit to zero
* sends them a warning email and gives them a time limit to make a minimum payment (directly or indirectly?) to improve the balance of the account, otherwise it goes as a black mark on their account history that is visible to others that can see their account histories.
* if a user gets too many flags, his other partners should be warned that he may be non-participatory and to take appropriate action to limit their exposure to his obligations.

[[#Future]]
!! Future Possibilities

Ideas for features to go in future releases (could be Ripplepay v3):

* Client/server design, to allow other client platforms to register their accounts on a transaction server to form a connected payment network.
* complementary currency platforms
* virtual cash providers
* see [[potential ripple clients]]

* Inter-server accounts & payments
* allow Ripplepay and other Ripple sites to interact
* see [[Protocol/Index | protocol page]]

* Advanced output of account data
* Filters on payments or account entries, e.g. filter by sent/received, by account name, by date, etc.

[[#Wishlist]]
!!! Wishlist

Ideas in this subsection are speculative, and may not even be considered for future releases.

* UI redesign:
* [[https://docs.google.com/drawings/edit?id=1KRpRSuKQKNVYgZDTdkIR2sqGcXLKyyytQAcZwfNuIFg&hl=en | Proposal to visualize and edit credit lines]]
* [[https://groups.google.com/group/rippleusers/browse_frm/thread/a8dcd5801cb297a | Setup wizard]]

to:

The Ripplepay roadmap has moved to [[http://code.ripplepay.com/wiki/Roadmap]].

November 25, 2010, at 11:14 PM by Ryan -

Added line 75:

* highlight the other user's dealings with those in your network; hide or minimize the rest, since it can be faked

November 25, 2010, at 10:53 PM by Ryan -

Added line 74:

* request to see a user's private data; or propose to both expose private data simultaneously

November 02, 2010, at 09:45 PM by Romualdo Grillo -

Changed lines 6-8 from:

*[[#Rewrite_v2.0|Step 1: Ripplepay Rewrite (v2.0)]]
*[[#New_Features_v2.1|Step 2: New Features (v2.1)]]
*[[#More_New_Features_v2.2|Step 3: More New Features (v2.2)]]

to:

**[[#Rewrite_v2.0|Step 1: Ripplepay Rewrite (v2.0)]]
**[[#New_Features_v2.1|Step 2: New Features (v2.1)]]
**[[#More_New_Features_v2.2|Step 3: More New Features (v2.2)]]

October 27, 2010, at 08:00 PM by Ryan -

Added line 136:

* if a user gets too many flags, his other partners should be warned that he may be non-participatory and to take appropriate action to limit their exposure to his obligations.

October 27, 2010, at 07:58 PM by Ryan - flagging as non-participatory

Changed lines 74-78 from:

to:

* develop a metric so other users can quickly ascertain the quality of a user's participation in the system
* see [[#Flagging | Flag a connection as non-participatory]] below
* should probably default to letting connections see everything, and warn them if you make it so they can't
* maybe there should be no way to turn this off?

Added lines 131-135:

[[#Flagging]]
* Flag a connection as non-participatory
* sets their credit limit to zero
* sends them a warning email and gives them a time limit to make a minimum payment (directly or indirectly?) to improve the balance of the account, otherwise it goes as a black mark on their account history that is visible to others that can see their account histories.

October 25, 2010, at 08:43 AM by Ryan -

Added line 112:

* gradually shrink credit limits on stagnant accounts

October 22, 2010, at 08:51 AM by Romualdo Grillo -

Changed lines 9-10 from:

*[[#|]]
*[[#Future|Future Possibilities]]

to:

[[#Future|Future Possibilities]]

Changed lines 11-16 from:

*[[#|]]
*[[#|]]

*[[#Ripplepay_v2]]

to:

[[#Ripplepay_v2]]

October 22, 2010, at 08:45 AM by Romualdo Grillo - Adding Index

Added lines 3-17:

Added line 27:

[[#Plan]]

Added line 32:

[[#Rewrite_v2.0]]

Added line 49:

[[#New_Features_v2.1]]

Added line 82:

[[#More_New_Features_v2.2]]

Added line 130:

[[#Future]]

Added line 147:

[[#Wishlist]]

October 16, 2010, at 06:37 PM by Daniel - formatting

Changed line 132 from:

* [[https://docs.google.com/drawings/edit?id=1KRpRSuKQKNVYgZDTdkIR2sqGcXLKyyytQAcZwfNuIFg&hl=en | Proposal to visualize and edit credit lines]

to:

* [[https://docs.google.com/drawings/edit?id=1KRpRSuKQKNVYgZDTdkIR2sqGcXLKyyytQAcZwfNuIFg&hl=en | Proposal to visualize and edit credit lines]]

October 16, 2010, at 06:37 PM by Daniel - add content

Changed lines 125-133 from:

* Filters on payments or account entries, e.g. filter by sent/received, by account name, by date, etc.

to:

* Filters on payments or account entries, e.g. filter by sent/received, by account name, by date, etc.

!!! Wishlist

Ideas in this subsection are speculative, and may not even be considered for future releases.

* UI redesign:
* [[https://docs.google.com/drawings/edit?id=1KRpRSuKQKNVYgZDTdkIR2sqGcXLKyyytQAcZwfNuIFg&hl=en | Proposal to visualize and edit credit lines]
* [[https://groups.google.com/group/rippleusers/browse_frm/thread/a8dcd5801cb297a | Setup wizard]]

October 14, 2010, at 08:31 PM by Ryan -

Changed lines 16-17 from:

!!! Step 1: Ripplepay Rewrite (v2.0)

to:

!!!! Step 1: Ripplepay Rewrite (v2.0)

Changed lines 32-33 from:

!!! Step 2: New Features (v2.1)

to:

!!!! Step 2: New Features (v2.1)

Changed lines 64-65 from:

!!! Step 3: More New Features (v2.2)

to:

!!!! Step 3: More New Features (v2.2)

October 05, 2010, at 06:22 PM by Daniel - add "connect to me" and other button code snippets, plus searchable directory

Changed line 35 from:

* Pre-generated code snippets, e.g. "Donate"/"Pay with Ripple" buttons, etc.

to:

* Pre-generated code snippets, e.g. "Donate"/"Pay with Ripple"/"Connect to me"/"Offer/request credit" buttons, etc.

Added lines 108-110:

* Directory
* Searchable directory of users, by e-mail, name, etc.

October 05, 2010, at 05:28 AM by Daniel - add advanced output

Added lines 120-122:

* Advanced output of account data
* Filters on payments or account entries, e.g. filter by sent/received, by account name, by date, etc.

October 04, 2010, at 05:23 PM by Ryan - added sandbox feature

Added lines 52-53:

* Sandbox to create new dummy users and make test payments; generally play around with Ripple

October 01, 2010, at 05:57 PM by Ryan - add identity verification

Added lines 102-105:

* Identity verification
* phone number
* [[http://www.bewelcome.org/wiki/Verification | address]]

September 30, 2010, at 07:56 PM by Ryan - add obligation priority

Changed lines 81-82 from:

to:

* risks turning Ripple into a speculators' casino

Added lines 95-101:

* Prioritize holding/discharge of obligations on certain accounts over others?
* affects payment routing
* not compatible with naive cheapest-path routing (if custom exchange rates are implemented)
* user would need to choose cheapest vs. best, or there could be a hybrid algorithm
* affects circular debt cancellation
* search for ways to turn undesirable holdings into more desirable ones

September 28, 2010, at 11:08 PM by Ryan - new skin

Added lines 30-31:

* New layout, skin, logo

September 28, 2010, at 11:03 PM by Ryan -

Changed lines 102-103 from:

* allow Ripplepay and other Ripple sites to interact
* see [[Protocol/Index | protocol page]]

to:

* allow Ripplepay and other Ripple sites to interact
* see [[Protocol/Index | protocol page]]

September 28, 2010, at 11:03 PM by Ryan - Move interserver payments to future possibilities

Changed lines 99-103 from:

* see [[potential ripple clients]]

to:

* see [[potential ripple clients]]

* Inter-server accounts & payments
* allow Ripplepay and other Ripple sites to interact
* see [[Protocol/Index | protocol page]]

September 28, 2010, at 10:54 PM by Ryan - add plan

Added lines 12-15:

!!! Plan

Rewrite the Ripplepay codebase, deploy, then add gradually release new features. Prioritize new features into to major sets in terms of priority and which ones complement each other best, keeping in mind the main goals above.

September 28, 2010, at 10:47 PM by Ryan - add automatic credit limit adjustment

Changed lines 12-13 from:

!!! Step 1: Ripplepay Rewrite (v2)

to:

!!! Step 1: Ripplepay Rewrite (v2.0)

Added lines 85-87:

* Automatic credit limit adjustment
* allow credit limits to grow automatically on selected accounts as obligations are repeatedly issued and settled over time, which can be interpreted as a maturing of the credit relationship

September 28, 2010, at 10:43 PM by Ryan - Reorganize features into v2 (rewrite), v2.1, and v2.2

Changed lines 12-15 from:

!!! Required Features

These features form the release requirements for Ripplepay v2:

to:

!!! Step 1: Ripplepay Rewrite (v2)

The existing codebase needs to be whipped into shape to support new features. Some implementation aspects will be redesigned, and a few new features will be added if they are easy or convenient to do at this stage.

* Technical design improvements
* Pre-calculate routes (by cheapest, then shortest)
* Process payments in queue to avoid multi-thread problems

* Translations

* Data-driven news/blog

* Multiple accounts between the same two users

!!! Step 2: New Features (v2.1)

Deleted lines 45-54:

!!! Phase 1 Features

These are the first features to implement on top of Ripplepay v2 (i.e. they are v2.1):

* Subscriptions/recurring payments/layaway?

* Technical design improvements
* Pre-calculate routes (by cheapest, then shortest)
* Process payments in queue to avoid multi-thread problems

Deleted lines 51-56:

* Translations

* Data-driven news/blog

* Multiple accounts between the same two users

Changed lines 56-59 from:

!!! ~~Phase 2~~ Features

~~These are the second features to implement on top of Ripplepay~~ v2 (i.~~e. they are v2.~~2):

to:

!!! Step 3: More New Features (v2.2)

Added lines 64-65:

* Subscriptions/recurring payments?

Deleted lines 84-86:

* Inter-server routing
* allow Ripplepay and other Ripple sites to interact

September 28, 2010, at 04:46 AM by Daniel - add link to LETS page

Changed line 56 from:

* ~~Tools~~/~~materials for migrating a LETS to Ripple~~

to:

* [[http://ripple-project.org/wiki/Main/UpgradeFromLETS | Tools/materials for migrating a LETS to Ripple]]

September 28, 2010, at 12:23 AM by Daniel - updent post-v2 features

Changed line 92 from:

!!! Future Possibilities

to:

!! Future Possibilities

September 28, 2010, at 12:22 AM by Daniel - move geolocation to v2

Deleted lines 39-42:

* Find users near me
* geolocation
* privacy considerations

Added lines 85-88:

* Find users near me
* geolocation
* privacy considerations

September 28, 2010, at 12:21 AM by Daniel - move screencast to v2 requirements

Added lines 31-33:

* Introductory presentation
* [[https://ripplexchange.com/viewtopic.php?f=9&t=30 | screencast]]

Deleted lines 43-45:

* Introductory presentation
* [[https://ripplexchange.com/viewtopic.php?f=9&t=30 | screencast]]

September 28, 2010, at 12:15 AM by Daniel - move Recurrence to v2.1

Added lines 35-36:

* Subscriptions/recurring payments/layaway?

Deleted lines 73-74:

* Subscriptions/recurring payments/layaway?

September 28, 2010, at 12:11 AM by Daniel - move social app integration into v2 requirements

Added lines 27-30:

* Login with Open ID, Facebook, Google, etc.

* Import friends from Facebook, Yahoo, Google, etc.

Deleted lines 45-48:

* Login with Open ID, Facebook, Google, etc.

* Import friends from Facebook, Yahoo, Google, etc.

September 28, 2010, at 12:09 AM by Daniel - move Record/redeem to v2 requirements

Added lines 22-26:

* Record/redeem obligation
* make/request entries on existing accounts
* send invites for new account along with IOU/UOMe
* new account is registered with a balance, but zero credit limits

Deleted lines 37-41:

* Record/redeem obligation
* make/request entries on existing accounts
* send invites for new account along with IOU/UOMe
* new account is registered with a balance, but zero credit limits

September 27, 2010, at 10:01 PM by Daniel - restructure

Added lines 12-21:

!!! Required Features

These features form the release requirements for Ripplepay v2:

* Integrate into user/merchant sites
* Pre-generated code snippets, e.g. "Donate"/"Pay with Ripple" buttons, etc.
* Ripplepay API
* access to Ripplepay.com accounts, payments, market data, functions, etc.
* this is different from the transaction server interface

Added lines 24-25:

These are the first features to implement on top of Ripplepay v2 (i.e. they are v2.1):

Deleted lines 53-58:

* Integrate into user/merchant sites
* Pre-generated code snippets, e.g. "Donate"/"Pay with Ripple" buttons, etc.
* Ripplepay API
* access to Ripplepay.com accounts, payments, market data, functions, etc.
* this is different from the transaction server interface

Added lines 64-65:

These are the second features to implement on top of Ripplepay v2 (i.e. they are v2.2):

Added lines 94-95:

Ideas for features to go in future releases (could be Ripplepay v3):

September 27, 2010, at 09:58 PM by Daniel - link screencast donation pool

Changed lines 19-20 from:

* screencast

to:

* [[https://ripplexchange.com/viewtopic.php?f=9&t=30 | screencast]]

September 27, 2010, at 08:48 PM by Ryan - add publish profile data feature

Added lines 34-39:

* Publish profile data to help build trust
* profile picture
* connections
* transaction history
* various degrees of privacy, a la facebook: private, friends, friends-of-friends, public

September 27, 2010, at 08:35 PM by Daniel - add inter-server routing

Added lines 75-77:

* Inter-server routing
* allow Ripplepay and other Ripple sites to interact

September 27, 2010, at 07:46 PM by Ryan - Add main goals

Changed lines 7-8 from:

!!! ~~Phase~~ 1

to:

!!! Main Goals

* Make it easy to connect to the Ripple network.
* Make it easy to discover uses for Ripple.

!!! Phase 1 Features

Changed lines 50-51 from:

!!! Phase 2

to:

!!! Phase 2 Features

September 27, 2010, at 07:42 PM by Ryan - tweak a few items

Changed lines 25-26 from:

* ~~Facebook connect, google/yahoo/ms contact import~~, etc.

to:

* Login with Open ID, Facebook, Google, etc.

* Import friends from Facebook, Yahoo, Google, etc.

Deleted lines 30-33:

* Open ID login

* [[http://opentransact.org/ | OpenTransact]] support

Added lines 68-69:

* [[http://opentransact.org/ | OpenTransact]] support

September 27, 2010, at 07:40 PM by Ryan - Split into phases

Changed lines 7-17 from:

* Client/server design, to allow other client platforms to register their accounts on a transaction server to form a connected payment network.
* complementary currency platforms
* virtual cash providers
* see [[potential ripple clients]]

* Marketplace
* offers/requests
* filter only those postings in my connected network
* filter by location
* search by keyword

to:

!!! Phase 1

Changed lines 21-34 from:

* ~~Custom currency units?~~
* needs custom exchange rates?

* Custom exchange rates?
* needs cheapest-route algorithm
* pre-calculate!
* also includes same-currency exchange rates, ie, transaction fees

* Circular debt cancellation?

* Pre-calculate routes (by cheapest, then shortest)

* Process payments in queue to avoid multi-thread problems

to:

* Technical design improvements
* Pre-calculate routes (by cheapest, then shortest)
* Process payments in queue to avoid multi-thread problems

Deleted lines 40-41:

* Subscriptions/recurring payments?

Changed lines 45-75 from:

* users should then be encouraged to make connections among themselves

to:

* users should then be encouraged to make connections among themselves

!!! Phase 2

* Marketplace
* offers/requests
* filter only those postings in my connected network
* filter by location
* search by keyword

* Subscriptions/recurring payments/layaway?

* Circular debt cancellation?

* Custom currency units?
* needs custom exchange rates?

* Custom exchange rates?
* needs cheapest-route algorithm
* pre-calculate!
* also includes same-currency exchange rates, ie, transaction fees

* Sponsorship?
* allow users to sign up for automated donations

!!! Future Possibilities

* Client/server design, to allow other client platforms to register their accounts on a transaction server to form a connected payment network.
* complementary currency platforms
* virtual cash providers
* see [[potential ripple clients]]

September 27, 2010, at 06:19 PM by Ryan - Add LETS migration tools

Changed lines 3-4 from:

!!~~Ripple~~ v2

to:

!!Ripplepay v2

Added lines 63-66:

* Tools/materials for migrating a LETS to Ripple
* every user starts with an account with the central LETS collective
* users should then be encouraged to make connections among themselves

September 27, 2010, at 08:23 AM by Ryan -

Deleted line 9:

* accounts transferable among servers?

Changed lines 36-37 from:

* also includes same-currency exchange rates?

to:

* also includes same-currency exchange rates, ie, transaction fees

Changed lines 52-54 from:

* API
* access to Ripplepay.com accounts, payments, market data, etc.
* this is not the transaction server interface

to:

* Integrate into user/merchant sites
* Pre-generated code snippets, e.g. "Donate"/"Pay with Ripple" buttons, etc.
* Ripplepay API
* access to Ripplepay.com accounts, payments, market data, functions, etc.
* this is different from the transaction server interface

Changed lines 60-76 from:

* Subscriptions
* Recurring payments

* Layaway
* Manage purchases on credit

* Multiple currency accounts
* Accounts with same user in different currencies

* Multiple interest accounts
* Accounts with same user with different interest rates (e.g. asymmetric rates)

* Code snippets
* Pre-generated code snippets to let users post their public account info. e.g. code to make a "Donate to me" button should be available within a user's account.

* Sponsorship
* Allow nodes to set percentages of their exchange fee income that will automatically be redirected to destinations of their choice. They could sponsor charities, open source projects (like Ripple), service providers, etc.

to:

* Subscriptions/recurring payments?

* Multiple accounts between the same two users

September 27, 2010, at 06:55 AM by Daniel - add Sponsorship idea

Changed lines 72-75 from:

* Pre-generated code snippets to let users post their public account info. e.g. code to make a "Donate to me" button should be available within a user's account.

to:

* Pre-generated code snippets to let users post their public account info. e.g. code to make a "Donate to me" button should be available within a user's account.

* Sponsorship
* Allow nodes to set percentages of their exchange fee income that will automatically be redirected to destinations of their choice. They could sponsor charities, open source projects (like Ripple), service providers, etc.

September 27, 2010, at 12:45 AM by Daniel - add Code snippets

Changed lines 69-72 from:

* Accounts with same user with different interest rates (e.g. asymmetric rates)

to:

* Accounts with same user with different interest rates (e.g. asymmetric rates)

* Code snippets
* Pre-generated code snippets to let users post their public account info. e.g. code to make a "Donate to me" button should be available within a user's account.

September 27, 2010, at 12:38 AM by Daniel - add some more ideas

Added line 10:

* accounts transferable among servers?

Changed lines 37-38 from:

to:

* also includes same-currency exchange rates?

Changed lines 57-69 from:

* Data-driven news/~~blog~~

to:

* Data-driven news/blog

* Subscriptions
* Recurring payments

* Layaway
* Manage purchases on credit

* Multiple currency accounts
* Accounts with same user in different currencies

* Multiple interest accounts
* Accounts with same user with different interest rates (e.g. asymmetric rates)

September 27, 2010, at 12:25 AM by Ryan -

Changed lines 7-26 from:

The most important development would probably be the separation into a new server and client configuration connected by an open API.

In addition to cleaning up the code this would allow for more clients to connect to a server, more variety in clients and uses of Ripple, and a much more flexible and friendly overall user experience. A primary benefit would be integration with numerous other platforms.

Integration candidates:

* Smartphone applications
* Market applications (e.g. [[https://ripplexchange.com/|Ripplexchange]])
* Open source accounting applications
* Open source banking applications
* Open source distributed computing applications
* etc.

New features:

* "I get to knOw U": New connection that extends payment but no credit to the other user. The recipient can now make payments, but can only reduce the balance from the initial amount.

!!Ripple v3

After this, Ripple could develop fuller decentralization, i.e. servers communicating with each other and not just with clients. Other new features as well, shaped by real world use...

to:

* Client/server design, to allow other client platforms to register their accounts on a transaction server to form a connected payment network.
* complementary currency platforms
* virtual cash providers
* see [[potential ripple clients]]

* Marketplace
* offers/requests
* filter only those postings in my connected network
* filter by location
* search by keyword

* Find users near me
* geolocation
* privacy considerations

* Introductory presentation
* screencast

* Record/redeem obligation
* make/request entries on existing accounts
* send invites for new account along with IOU/UOMe
* new account is registered with a balance, but zero credit limits

* Custom currency units?
* needs custom exchange rates?

* Custom exchange rates?
* needs cheapest-route algorithm
* pre-calculate!

* Circular debt cancellation?

* Pre-calculate routes (by cheapest, then shortest)

* Process payments in queue to avoid multi-thread problems

* Facebook connect, google/yahoo/ms contact import, etc.

* Translations

* Open ID login

* [[http://opentransact.org/ | OpenTransact]] support

* API
* access to Ripplepay.com accounts, payments, market data, etc.
* this is not the transaction server interface

* Data-driven news/blog

September 26, 2010, at 11:41 PM by Daniel - Begin page

Added lines 1-26:

This page discusses where we see Ripple going in the future. There are multiple possible ways forward, and to find the best ones will depend on user needs, so please share your thoughts. Suggestions and comments are welcome at [[mailto:info@ripplepay.com|info@ripplepay.com]].

!!Ripple v2

What should the next version of software powering Ripplepay do?

The most important development would probably be the separation into a new server and client configuration connected by an open API.

In addition to cleaning up the code this would allow for more clients to connect to a server, more variety in clients and uses of Ripple, and a much more flexible and friendly overall user experience. A primary benefit would be integration with numerous other platforms.

Integration candidates:

* Smartphone applications
* Market applications (e.g. [[https://ripplexchange.com/|Ripplexchange]])
* Open source accounting applications
* Open source banking applications
* Open source distributed computing applications
* etc.

New features:

* "I get to knOw U": New connection that extends payment but no credit to the other user. The recipient can now make payments, but can only reduce the balance from the initial amount.

!!Ripple v3

After this, Ripple could develop fuller decentralization, i.e. servers communicating with each other and not just with clients. Other new features as well, shaped by real world use...

Roadmap

Main.Roadmap History