Message-ID: <55304321.3030300@sky-ip.org>
Date: Fri, 17 Apr 2015 02:17:53 +0300
From: s7r <s7r@sky-ip.org>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64;
	rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Mark Friedenbach <mark@friedenbach.org>
References: <552EF785.7000207@sky-ip.org>	<CAPg+sBgAhdgPPjmT5i0PMYhQo=Hk6Weo8tpX_Wyn-NJ5Ye9D_A@mail.gmail.com>	<552FDF73.6010104@sky-ip.org>
	<CAOG=w-vMjysbF5H8wWN2y45U3djFwpKMtXq3vCvB=-eFr7GqFg@mail.gmail.com>
In-Reply-To: <CAOG=w-vMjysbF5H8wWN2y45U3djFwpKMtXq3vCvB=-eFr7GqFg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] 75%/95% threshold for transaction versions
Precedence: list
Reply-To: s7r@sky-ip.org


On 4/16/2015 8:34 PM, Mark Friedenbach wrote:
> At this moment anyone can alter the txid. Assume transactions are 100%
> malleable.
>=20

Anyone can alter the txid - more details needed. The number of altered
txids in practice is not so high in order to make us believe anyone can
do it easily. It is obvious that all current bitcoin transactions are
malleable, but not by anyone and not that easy. At least I like to think =
so.

From your answer I understand that right now if I create a transaction
(tx1) and broadcast it, you can alter its txid at your will, without any
mining power and/or access to my private keys so I would end up not
recognizing my own transaction and probably my change too (if my systems
rely hardly on txid)?

> On Apr 16, 2015 9:13 AM, "s7r" <s7r@sky-ip.org <mailto:s7r@sky-ip.org>>
> wrote:
>=20
>     Hi Pieter,
>=20
>     Thanks for your reply. I agree. Allen has a good point in the previ=
ous
>     email too, so the suggestion might not fix anything and complicate
>     things.
>=20
>     The problem I am trying to solve is making all transactions
>     non-malleable by default. I guess there is a very good reason why B=
IP62
>     will not touch v1 anyway.
>=20
>     I am trying to build a bitcoin contract which will relay on 3 thing=
s:
>     - coinjoin / txes with inputs from multiple users which are signed =
by
>     all users after they are merged together (every user is sure his co=
ins
>     will not be spent without the other users to spend anything, as per
>     agreed contract);
>     - pre-signed txes with nLockTime 'n' weeks. These txes will be sign=
ed
>     before the inputs being spent are broadcasted/confirmed, using the =
txid
>     provided by the user before broadcasting it. Malleability hurts her=
e.
>     - P2SH
>=20
>     In simple terms, how malleable transactions really are in the netwo=
rk at
>     this moment? Who can alter a txid without invalidating the tx? Just=
 the
>     parties who sign it? The miners? Anyone in the network? This is a l=
ittle
>     bit unclear to me.
>=20
>     Another thing I would like to confirm, the 3 pieces of the bitcoin
>     protocol mentioned above will be supported in _any_ future transact=
ion
>     version or block version, regardless what changes are made or featu=
res
>     added to bitcoin core? The contract needs to be built and left unch=
anged
>     for a very very long period of time...
>=20
>=20
>     On 4/16/2015 8:22 AM, Pieter Wuille wrote:
>     >
>     > On Apr 16, 2015 1:46 AM, "s7r" <s7r@sky-ip.org
>     <mailto:s7r@sky-ip.org> <mailto:s7r@sky-ip.org <mailto:s7r@sky-ip.o=
rg>>>
>     > wrote:
>     >> but for transaction versions? In simple terms, if > 75% from all=
 the
>     >> transactions in the latest 1000 blocks are version 'n', mark all
>     >> previous transaction versions as non-standard and if > 95% from
>     all the
>     >> transactions in the latest 1000 blocks are version 'n' mark all
>     previous
>     >> transaction versions as invalid.
>     >
>     > What problem are you trying to solve?
>     >
>     > The reason why BIP62 (as specified, it is just a draft) does not
>     make v1
>     > transactions invalid is because it is opt-in. The creator of a
>     > transaction needs to agree to protect it from malleability, and t=
his
>     > subjects him to extra rules in the creation.
>     >
>     > Forcing v3 transactions would require every piece of wallet
>     software to
>     > be changed.
>     >
>     > --
>     > Pieter
>     >
>=20
>     -------------------------------------------------------------------=
-----------
>     BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
>     Develop your own process in accordance with the BPMN 2 standard
>     Learn Process modeling best practices with Bonita BPM through live
>     exercises
>     http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual-
>     event?utm_
>     source=3DSourceforge_BPM_Camp_5_6_15&utm_medium=3Demail&utm_campaig=
n=3DVA_SF
>     _______________________________________________
>     Bitcoin-development mailing list
>     Bitcoin-development@lists.sourceforge.net
>     <mailto:Bitcoin-development@lists.sourceforge.net>
>     https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>=20