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

Re: Skuchain use case for interledger and cryptographic notary

From: Stefan Thomas <stefan@ripple.com>
Date: Tue, 2 Feb 2016 21:17:11 -0800
Message-ID: <CAFpK0Q27+vb+Pu1piXf4h+A=wVgND_MRi=5Q0YEjStRFxpVd6w@mail.gmail.com>
To: Zaki Manian <zaki@skuchain.com>
Cc: Interledger Community Group <public-interledger@w3.org>
Wow, yeah that seems indeed very much up your alley. The notary's job is
essentially to decide whether the payment should happen and then sign a
message stating what their decision was. In the future, we hope that there
will be notaries that aren't just a single server, but a group of servers
that run a round of consensus to decide.

I think the main thing we'd have to work out is the format in which the
signatures are provided. We want ILP to be pretty flexible in that respect
and are currently working on a first draft for a spec that gives us that.
I'll post it here as soon as I get a chance to add some rationale and
background. We're a bit bottlenecked on writing things down, because we
also want to get some more demos running before the face-to-face.

You guys are based in Mountain View, correct? Feel free to shoot me an
email if there is any interest in getting together ahead of the Interledger

On Mon, Jan 25, 2016 at 12:24 PM, Zaki Manian <zaki@skuchain.com> wrote:

> Hi all,
> I'm hoping to contribute to the wiki a more detailed description of
> Skuchain's use case for Interledger in facilitating international trade.
> I suspect our use case is broadly similar to the functioning of 5 bells
> public notary. https://github.com/interledger/five-bells-notary
> The high level discussion in the README sounds precisely like what I'm
> working.
> Is there anything a bit more detailed on how the notary works that is non
> public that can be made public? The discussion in github references a
> specification that doesn't seem to be available.
> Founder @skuchain.com
> Public Key:https://keybase.io/zmanian
Received on Wednesday, 3 February 2016 05:18:00 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 3 February 2016 05:18:00 UTC