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

Re: Crypto-condition Spec and Status

From: Rafael Pereira <rafael@rippex.net>
Date: Mon, 29 Feb 2016 19:56:19 +0000
Message-ID: <CAFk+OKnDbM+RkgK1Z41h0TVjir_cu3wHZPc35xbqYe76mAt5Mg@mail.gmail.com>
To: Melvin Carvalho <melvincarvalho@gmail.com>, Stefan Thomas <stefan@ripple.com>
Cc: Interledger Community Group <public-interledger@w3.org>
Melvin, what kind of conditions you have in mind?

Em seg, 29 de fev de 2016 às 16:33, Melvin Carvalho <
melvincarvalho@gmail.com> escreveu:

> On 29 February 2016 at 20:07, Stefan Thomas <stefan@ripple.com> wrote:
>> Just wanted to follow up on Thursday's discussion by posting a first
>> draft and example implementation of the crypto-conditions spec:
>> https://github.com/interledger/five-bells-condition/tree/feature/binary-merkle
>> Also here are the slides I presented on Thursday. For those who weren't
>> able to join, the presentation was recorded and we will seek to make the
>> recording available as soon as we can.
>> http://www.slideshare.net/Interledger/ilp-workshop-cryptoconditions
> I like it!
> But why, 'crypto' conditions, rather than 'verifiable' conditions -- it is
> branding or do we want to limit the scope?
>> - Stefan
> --


*Rafael Olaio - CEO*
tel +55 11 2337.2225
cel +55 11 99522.7572

Esta mensagem pode conter informação confidencial e/ou privilegiada. Se
você não for o destinatário ou a pessoa autorizada a receber esta mensagem,
não poderá usar, copiar ou divulgar as informações nela contidas ou tomar
qualquer ação baseada nessas informações. Se você recebeu esta mensagem por
engano, por favor avise imediatamente o remetente, respondendo o e-mail e
em seguida apague-o.This message may contain confidential and/or privileged
information. If you are not the addressee or authorized to receive this for
the addressee, you must not use, copy, disclose or take any action based on
this message or any information here in. If you have received this message
in error, please advise the sender immediately by reply e-mail and delete
this message.
Received on Monday, 29 February 2016 19:56:57 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 February 2016 19:56:57 UTC