W3C home > Mailing lists > Public > public-interledger@w3.org > February 2017

RE: Fwd: [Ripple] settle.network

From: Ron Ginn <ron.ginn@brightway.com>
Date: Mon, 27 Feb 2017 15:57:20 +0000
To: Eric Wall <eric.wall.770@gmail.com>, Andrew Bransford Brown <andrewbb@gmail.com>
CC: Melvin Carvalho <melvincarvalho@gmail.com>, Steven Roose <stevenroose@gmail.com>, Interledger Community Group <public-interledger@w3.org>
Message-ID: <A7652EF4D72AB44F945FBB86F9378A2B7125B72D@S04-MBX02-08.s04.local>
Thanks for sharing, lack of trust lines is why I have stayed away from Ethereum.

Karma Coverage requires trust lines to move coverage across the ‘trust graph’ of users.

Karma Coverage also requires ILP, because each individual RCL would be used to escrow funds against an individual risk type. (Auto deductible, bike, phone/computer equipment, life event, etc.)

Karma Coverage enables users to network together to achieve some 10x plus leverage on their ‘rainy day savings’, and would map the trust lines that connect users on RCL #1, and RCL #2, RCL #3 .. Since each RCL is used to escrow funds for a specific risk, they could be called Risk Coverage Ledgers.

I believe “Risk is the killer app” for distributed ledger tech. Everyone is exposed to Risk and would need a wallet to join. Been very interesting watching all the attention banking has received.. Payments is also a great application


From: Eric Wall [mailto:eric.wall.770@gmail.com]
Sent: Monday, February 27, 2017 10:37 AM
To: Andrew Bransford Brown
Cc: Melvin Carvalho; Steven Roose; Interledger Community Group
Subject: Re: Fwd: [Ripple] settle.network

I read this article http://www.ibtimes.co.uk/introducing-trustlines-original-ripple-idea-ethereum-1607226

And thought it might bear relevance to this mail-conversation.

On Wed, Feb 22, 2017 at 5:39 PM, Andrew Bransford Brown <andrewbb@gmail.com<mailto:andrewbb@gmail.com>> wrote:
Yes, all you need is a list of IOUs/promises (open and completed).

Open IOUs/promises become a live exchange.  Completed transactions become reputation.

Optionally, the list of IOUs/promises can be aggregated into a currency or credit value.

On Wed, Feb 22, 2017 at 11:06 AM, Melvin Carvalho <melvincarvalho@gmail.com<mailto:melvincarvalho@gmail.com>> wrote:

On 22 February 2017 at 15:56, Steven Roose <stevenroose@gmail.com<mailto:stevenroose@gmail.com>> wrote:

In fact I've recently been thinking about a way of using Interledger to build a decentralized network like that as well.

If every person is it's own ledger with allows slight overdrafts (negative balances) for people it trusts, a network between these people could exist without having to have any actual ledgers holding deposits, it's all IOU's.

Much like Ripple or trustlines.network, but without the blockchain or the shared ledger.

love this idea!

On 22-02-17 07:18, Melvin Carvalho wrote:
---------- Forwarded message ----------
From: Giovanni P <fiatjaf@gmail.com<mailto:fiatjaf@gmail.com>>
Date: 21 February 2017 at 21:47
Subject: [Ripple] settle.network
To: rippleusers <rippleusers@googlegroups.com<mailto:rippleusers@googlegroups.com>>

Has anyone seen this[1]? It's some personal project that implements the Ripple decentralized protocol without commits, in a way that I've been thinking for a long time that would work (everyone is subject to lose money in the amount of their trust -- if the trusted party is a bad agent), with assets hosted on federated nodes.

They have a hidden Google Group[2].

[1]: https://settle.network/
[2]: https://groups.google.com/forum/#!forum/settle-public<https://groups.google.com/forum/#%21forum/settle-public>
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+unsubscribe@googlegroups.com<mailto:rippleusers+unsubscribe@googlegroups.com>.
For more options, visit https://groups.google.com/d/optout.

This email and its attachments may contain confidential information intended only for the use of the person(s) named above. If you are not the intended recipient, you are hereby advised that any disclosure, copying, distribution or the taking of any action on the contents of this information is prohibited. If you've received this email in error, please notify the sender.
Received on Tuesday, 28 February 2017 22:41:30 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:14:00 UTC