Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1XWTGi-0002dy-Dz for bitcoin-development@lists.sourceforge.net; Tue, 23 Sep 2014 16:48:48 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.216.178 as permitted sender) client-ip=209.85.216.178; envelope-from=etotheipi@gmail.com; helo=mail-qc0-f178.google.com; Received: from mail-qc0-f178.google.com ([209.85.216.178]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1XWTGd-0004eO-EI for bitcoin-development@lists.sourceforge.net; Tue, 23 Sep 2014 16:48:48 +0000 Received: by mail-qc0-f178.google.com with SMTP id x13so1995135qcv.37 for ; Tue, 23 Sep 2014 09:48:37 -0700 (PDT) X-Received: by 10.229.73.70 with SMTP id p6mr1235108qcj.13.1411490917213; Tue, 23 Sep 2014 09:48:37 -0700 (PDT) Received: from [192.168.1.85] (c-69-143-221-64.hsd1.md.comcast.net. [69.143.221.64]) by mx.google.com with ESMTPSA id a3sm6912700qaa.49.2014.09.23.09.48.36 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 23 Sep 2014 09:48:36 -0700 (PDT) Message-ID: <5421A462.6030205@gmail.com> Date: Tue, 23 Sep 2014 12:48:34 -0400 From: Alan Reiner User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: bitcoin-development@lists.sourceforge.net References: <54219CF9.7080500@gmail.com> <5421A1C0.6080605@monetas.net> In-Reply-To: <5421A1C0.6080605@monetas.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Spam-Score: -1.6 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (etotheipi[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1XWTGd-0004eO-EI Subject: Re: [Bitcoin-development] Proposal: "No-Collision" mode for Multisig BIP32 Wallets X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Sep 2014 16:48:48 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 09/23/2014 12:37 PM, Justus Ranvier wrote: > Would be nice if you'd at least mention our work, since we did share > it with you back in January and have been publicly documenting it ever > since. > > Or does the fact that we're implementing it in btcwallet mean what > we're working on is unmentionable here? > Please don't assume poor intentions or sneaky motives. I get a lot of emails from a lot of people about a lot of things. Nine months ago was an eternity in this world, and it can't be ruled out that I simply forgot= =2E I have no problem giving credit where it is due, and I mentioned in my first email that I wasn't sure if my stuff was original. Please recap/link it here so that it can be part of this discussion. - -Alan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJUIaRiAAoJEBHe6b77WWmFcBgP/2IiQWda5diBIrd8MjbtYz/X pF+B1zOipClil151pKN5h9f4CI75qwSBSG6pUS+QH1lCz97nr5AoVYV5SAaRzv0z L9Bz0PiHJFHd4IRbfuFqlPZB8mw2TMD7QWJx/1U+WmpnYYOGsUeJn25psIVZSRTU FTCsmYrA4cGZ4bZoUKI/eiXrHao8rm/zQ7QHKOMSFWZT57sNea67vlxPXKu+AkmK nEYa4hD0kD7/R/TrNcmRmOlmbqCnyjICd/yp8Lj26CdHPv3PAvaxUwSX3VhWPbdc UOiGeo+lXqRnBVpwMd+k7oFddwrc2k9ISRdUVsU86z3JdAXKl/dLS5UoOtfC1JA9 m90TuRtq4QuuzjLF3brI9FthuHNowA//qaVfjo/AYgsKy15td9UBtFbt4E9w263M NiFEmFkXfbE1JmIvmPG3AQEEdQ1/nmWiN5UcLrBfauEHMDQ1fGd89A8IBpus7bWM kYXboW3E9RBN4lB6OdyYU4AuH0YQhZodmry4iElMPox/tclmNiaeqDR8UYhD5BMd eQN9zAALyR1IY1167Ki/abVfWVf5jF7b0Eeu/wAfwcble3sCFrvWWAwzHjNi3GjY gNfy1eDTbwLj2M63QbtB+YqzQBZx3+SY4euGKYQ1s1CVV9ibAFI52oxeMhwzVOWF ofeDK5BPL8H+5L3tk+1o =3DtX2n -----END PGP SIGNATURE-----