public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Kalle Rosenbaum <kalle@rosenbaum.se>
To: bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: [bitcoin-dev] Fix or withdraw BIP120/121?
Date: Fri, 26 Jan 2018 16:52:10 +0100	[thread overview]
Message-ID: <CAPswA9zXRhw6j-88VDuHtUT_vk0-biUq=FyAQEWshVvNmQ_5HQ@mail.gmail.com> (raw)

Hi

There is an inherent problem with BIP120, Proof of Payment: If there
is a soft fork, a server that verifies PoPs will accept a PoP as valid
without checking any of the new Bitcoin rules.

For example, a server will be fooled by a segwit transaction, because
the server doesn't have a witness to verify and consequently will
accept any PoP with an empty scriptSig.

Besides this problem, on-chain payments are not hot anymore and
interest, or need, for PoP as a concept seems low.

I have no good solution for the soft fork problem. Requiring all
software that uses PoP to upgrade to a new PoP specification on each
soft-fork is not good enough. Do you have any ideas on how to fix it?

If there is no good solution to the soft-fork issue, I suggest that I
withdraw BIP120 and BIP121.

As for current implementations: I know that Mycelium implements
BIP120, but I'm not sure if there is any other software, besides my
own, implementing it. If you know of any, please let me know so I can
discuss it with them.

Regards,
/Kalle


                 reply	other threads:[~2018-01-26 15:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAPswA9zXRhw6j-88VDuHtUT_vk0-biUq=FyAQEWshVvNmQ_5HQ@mail.gmail.com' \
    --to=kalle@rosenbaum.se \
    --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