To: bitcoin-dev@lists.linuxfoundation.org
References: <mailman.1377.1575015939.25512.bitcoin-dev@lists.linuxfoundation.org>
From: Jose Femenias <jose.femenias@gmail.com>
Message-ID: <e300549d-4890-3cf2-e514-76bb778abef2@gmail.com>
Date: Mon, 2 Dec 2019 15:00:57 +0100
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:52.0) Gecko/20100101
 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <mailman.1377.1575015939.25512.bitcoin-dev@lists.linuxfoundation.org>
Content-Type: text/html; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Subject: [bitcoin-dev] easypaysy - A layer-two protocol to send payments
	without addresses
Precedence: list

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#333333" bgcolor="#FFFFFF">
    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">btc@543847.636/577</a><br>
    Mnemonic ID:    <a class="moz-txt-link-abbreviated" href="mailto:btc@cancel-mind.exhibit/motion">btc@cancel-mind.exhibit/motion</a><br>
    Domain ID:    <a class="moz-txt-link-abbreviated" href="mailto:btc@example.com/motion-custom">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">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">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">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">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">easypaysy@gmail.com</a><br>
    <br>
    Best regards.<br>
  </body>
</html>