Re: [Ripple] Classic Ripple Concept

[Ryan Fugger]

Hi Brent.  If you're wondering about the implementation at https://classic.ripplepay.com/, there's not much to it -- everything resides on a single server.  If you're wondering about designs for a distributed Ripple networks, you can peruse the old project wiki at http://archive.ripple-project.org/Main/Concept.

Ryan

On Mon, May 27, 2013 at 11:15 AM, Brent Shambaugh <brent.s...@gmail.com> wrote:

I originally posted this in the #ripple IRC channel. Unfortunately, I did not recieve a response. Perhaps someone here knows. 

 I'm trying to understand the classic ripple concept. I viewed a video by Romuldo Grillo titled  "Ripple -- An Introduction in three examples" at < a href="http://www.youtube.com/watch?v=xgGcVv04unM >. It was renamed, "Ripple: How does it work?" by HostFat.

 The concept seems fairly straightforward, but I am confused about the implementation. I interpret it as, "

 When a person at a particular node wants to send a transaction, the software will automatically find a route from the source to destination node. This automation will be made possible through continuous sending of signed messages to other nodes. In this setup, transactions can be initiated at all times."

 I inferred, "This automation will be made possible through continuous sending of signed messages to other nodes".

Is this true?  Is there a place I could read more about this?

--
You received this message because you are subscribed to the Google Groups "Ripple Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rippleusers...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Alex Kotov]

I see that all explanation videos of Classic Ripple Concept: car case and other ones, - have gone.

Guys, could you please please, share them again 

[Melvin Carvalho]

út 28. 5. 2013 v 0:41 odesílatel Ryan Fugger <a...@ryanfugger.com> napsal:

Hi Brent.  If you're wondering about the implementation at https://classic.ripplepay.com/, there's not much to it -- everything resides on a single server.  If you're wondering about designs for a distributed Ripple networks, you can peruse the old project wiki at http://archive.ripple-project.org/Main/Concept.

It would be nice to build this again with some of the new open modern tooling such as nostr, cashu, lightning network and rgb

[nerdyrugbyguy]

I attached a one page pdf I've been working on that is meant to be a model for a modern distributed ripple.  I would love to have some critical feedback and discussion.

I gave the example of a mint factory, but there can be many mint factories, existing funding sources like lightning, L-BTC, or USDT can be used, and there can be many different servers coordinating swaps.

[materise_dev]

This is a really interesting model, thanks for sharing it. The idea of multiple independent mints issuing assets, while different servers coordinate HTLC-based swaps, seems like a solid path to reduce the liquidity silos we still see across sidechains and stablecoins.

A couple of thoughts:

Having many mints is powerful, but raises the question of incentive alignment. How do we ensure each mint maintains credibility (backing, transparency) without introducing a central authority?

Your design of distributed swap servers reminds me of how Cashu / Fedimint are evolving, but you’re extending it further into a cross-asset payments layer. That’s compelling it could bridge Lightning, Liquid BTC, USDT, and beyond.

One possible use case: environmental or commodity-backed tokens (e.g., waste-to-value models I’ve been researching) could plug into this framework as “mint outputs”, instantly tradable or payable via HTLC invoices.

It would be great to hear your view on how market makers/liquidity providers would be incentivized in such a system, since that seems like the critical piece for making swaps scale without relying on a single operator.