public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Tim Blokdijk <tim@timblokdijk.nl>
To: Jose Femenias via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] easypaysy - A layer-two protocol to send payments without addresses
Date: Mon, 2 Dec 2019 18:27:21 +0100	[thread overview]
Message-ID: <55cb9731-e7fb-0bfa-0cba-391ff81d263a@timblokdijk.nl> (raw)
In-Reply-To: <e300549d-4890-3cf2-e514-76bb778abef2@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1964 bytes --]

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

[-- Attachment #2: Type: text/html, Size: 4061 bytes --]

  reply	other threads:[~2019-12-02 18:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1377.1575015939.25512.bitcoin-dev@lists.linuxfoundation.org>
2019-12-02 14:00 ` [bitcoin-dev] easypaysy - A layer-two protocol to send payments without addresses Jose Femenias
2019-12-02 17:27   ` Tim Blokdijk [this message]
2019-12-02 21:10     ` ZmnSCPxj
2019-12-02 21:25 Jose Femenías Cañuelo
2019-12-05 20:00 Jose Femenías Cañuelo
2019-12-06  2:53 ` ZmnSCPxj
2019-12-06  7:56   ` Jose Femenías Cañuelo
2019-12-06 17:16     ` ZmnSCPxj
2019-12-06 18:47       ` Jose Femenías Cañuelo
2019-12-07  4:09         ` ZmnSCPxj

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55cb9731-e7fb-0bfa-0cba-391ff81d263a@timblokdijk.nl \
    --to=tim@timblokdijk.nl \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox