To: Jose Femenias via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org>
References: <mailman.1377.1575015939.25512.bitcoin-dev@lists.linuxfoundation.org>
 <e300549d-4890-3cf2-e514-76bb778abef2@gmail.com>
From: Tim Blokdijk <tim@timblokdijk.nl>
Message-ID: <55cb9731-e7fb-0bfa-0cba-391ff81d263a@timblokdijk.nl>
Date: Mon, 2 Dec 2019 18:27:21 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <e300549d-4890-3cf2-e514-76bb778abef2@gmail.com>
Content-Type: multipart/alternative;
 boundary="------------79675AAED806BEF2CCF3245F"
Content-Language: en-US
Subject: Re: [bitcoin-dev] easypaysy - A layer-two protocol to send payments
 without addresses
Precedence: list

This is a multi-part message in MIME format.
--------------79675AAED806BEF2CCF3245F
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

Hello José,

Just a quick question, this is fully decentralized?

Greetings,

Tim Blokdijk

Op 02-12-19 om 15:00 schreef Jose Femenias via bitcoin-dev:
> Hi,
>
> I have just released an early preview of easypaysy, a protocol for 
> Bitcoin, that I have been working on for the past few months.
>
> (In case you are wondering, easypaysy stands for EASY - PAYment- 
> SYstem...)
>
> Long story short, easypaysy is a layer-two protocol that allows the 
> creation of non-custodial accounts directly on the blockchain, so that 
> bitcoin addresses can fully disappear from the user experience.
> In lieu of addresses, users send payments to permanent account IDs.
>
> Account IDs are implicitly assigned by the mining process, and come in 
> several flavors, like in these examples:
>
> Canonical ID: btc@543847.636/577
> Mnemonic ID: btc@cancel-mind.exhibit/motion
> Domain ID: btc@example.com/motion-custom
>
> (Note: Domain IDs are optional and require extra configuration)
>
> The protocol allows both interactive and non interactive payments.
> All payments are non-repudiable, and it is possible to implement 
> pull-payments as well as chargebacks.
>
> Most of the protocol is quite advanced, but I have refrained from 
> specifying some of the details, until the interested parties can give 
> their feedback.
>
> For more information, you can see the white paper and a short 
> introductory video at:
>
> https://www.easypaysy.org
>
> or directly, by following these links:
>
> White paper at https://www.easypaysy.org/assets/easypaysy_white_paper.pdf
> Introductory video at https://www.youtube.com/watch?v=AOGBdyZbyoA
>
> You can also get in contact with me in at:
>
> jose.femenias@gmail.com
>
> or using the project's email at:
>
> easypaysy@gmail.com
>
> Best regards.
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev

--------------79675AAED806BEF2CCF3245F
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>Hello José,</p>
    <p>Just a quick question, this is fully decentralized?<br>
    </p>
    <p>Greetings,</p>
    <p>Tim Blokdijk<br>
    </p>
    <div class="moz-cite-prefix">Op 02-12-19 om 15:00 schreef Jose
      Femenias via bitcoin-dev:<br>
    </div>
    <blockquote type="cite"
      cite="mid:e300549d-4890-3cf2-e514-76bb778abef2@gmail.com">
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      Hi,<br>
      <br>
      I have just released an early preview of easypaysy, a protocol for
      Bitcoin, that I have been working on for the past few months.<br>
      <br>
      (In case you are wondering, easypaysy stands for EASY - PAYment-
      SYstem...)<br>
      <br>
      Long story short, easypaysy is a layer-two protocol that allows
      the creation of non-custodial accounts directly on the blockchain,
      so that bitcoin addresses can fully disappear from the user
      experience. <br>
      In lieu of addresses, users send payments to permanent account
      IDs.<br>
      <br>
      Account IDs are implicitly assigned by the mining process, and
      come in several flavors, like in these examples:<br>
      <br>
      Canonical ID:    <a class="moz-txt-link-abbreviated"
        href="mailto:btc@543847.636/577" moz-do-not-send="true">btc@543847.636/577</a><br>
      Mnemonic ID:    <a class="moz-txt-link-abbreviated"
        href="mailto:btc@cancel-mind.exhibit/motion"
        moz-do-not-send="true">btc@cancel-mind.exhibit/motion</a><br>
      Domain ID:    <a class="moz-txt-link-abbreviated"
        href="mailto:btc@example.com/motion-custom"
        moz-do-not-send="true">btc@example.com/motion-custom</a><br>
      <br>
      (Note: Domain IDs are optional and require extra configuration)<br>
      <br>
      The protocol allows both interactive and non interactive payments.
      <br>
      All payments are non-repudiable, and it is possible to implement
      pull-payments as well as chargebacks.<br>
      <br>
      Most of the protocol is quite advanced, but I have refrained from
      specifying some of the details, until the interested parties can
      give their feedback.<br>
      <br>
      For more information, you can see the white paper and a short
      introductory video at:<br>
      <br>
      <a class="moz-txt-link-freetext" href="https://www.easypaysy.org"
        moz-do-not-send="true">https://www.easypaysy.org</a><br>
      <br>
      or directly, by following these links:<br>
      <br>
      White paper at <a class="moz-txt-link-freetext"
        href="https://www.easypaysy.org/assets/easypaysy_white_paper.pdf"
        moz-do-not-send="true">https://www.easypaysy.org/assets/easypaysy_white_paper.pdf</a><br>
      Introductory video at <a class="moz-txt-link-freetext"
        href="https://www.youtube.com/watch?v=AOGBdyZbyoA"
        moz-do-not-send="true">https://www.youtube.com/watch?v=AOGBdyZbyoA</a><br>
      <br>
      You can also get in contact with me in at:<br>
      <br>
      <a class="moz-txt-link-abbreviated"
        href="mailto:jose.femenias@gmail.com" moz-do-not-send="true">jose.femenias@gmail.com</a><br>
      <br>
      or using the project's email at:<br>
      <br>
      <a class="moz-txt-link-abbreviated"
        href="mailto:easypaysy@gmail.com" moz-do-not-send="true">easypaysy@gmail.com</a><br>
      <br>
      Best regards.<br>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <pre class="moz-quote-pre" wrap="">_______________________________________________
bitcoin-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.linuxfoundation.org</a>
<a class="moz-txt-link-freetext" href="https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev">https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev</a>
</pre>
    </blockquote>
  </body>
</html>

--------------79675AAED806BEF2CCF3245F--