Re: [Bitcoin-development] [softfork proposal] Strict DER signatures
.Hi there. Thank you for your work on this. I've looked over https://gist.github.com/sipa/5d12c343746dad376c80 and https://github.com/sipa/bitcoin/commit/bipstrictder . I didn't actually audit the included reference implementation of IsValidSignatureEncoding(), and I didn't check whether the test vectors in https://github.com/sipa/bitcoin/commit/f94e806f8bfa007a3de4b45fa3c9860f2747e427 exercise all of the branches that are changed by this patch. I have the following comments: * It seems like a good idea to do this. * I don't see any problem with using the upgrade mechanism from BIP 34 for this. It's cool! I'm happy that such a mechanism seems to work in practice. * Should the bipstrictder give a rationale or link to why accept the 0-length sig as correctly-encoded-but-invalid? I guess the rationale is an efficiency issue as described in the log entry for https://github.com/sipa/bitcoin/commit/041f1e3597812c250ebedbd8f4ef1565591d2c34 . * Does this mean there are still multiple ways to encode a correctly encoded but invalid signature, one of which is the 0-length string? Would it make sense for this change to also treat any *other* correctly-encoded-but-invalid sig (besides the 0-length string) as incorrectly-encoded? Did I just step in some BIP62? * It would be good to verify that all the branches of the new IsDERSignature() from https://github.com/sipa/bitcoin/commit/0c427135151a6bed657438ffb2e670be84eb3642 are tested by the test vectors in https://github.com/sipa/bitcoin/commit/f94e806f8bfa007a3de4b45fa3c9860f2747e427 . Eyeballing it, there are about 20 branches touched by the patch, and about 24 new test vectors. * It would be good to finish the TODOs in https://github.com/sipa/bitcoin/commit/b7986119a5d41337fea1e83804ed6223438158ec so that it was actually testing the upgrade behavior. * missing comment: https://github.com/sipa/bitcoin/commit/e186f6a80161f9fa45fbced82ab1d22f081b942c#commitcomment-9406643 Okay, that's all I've got. Hope it helps! Thanks again for your good work! Regards, Zooko -- New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet ___ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
Re: [Bitcoin-development] IMPULSE: Instant Payments using the Bitcoin protocol
On 01/17/2015 08:45 PM, Rune Kjær Svendsen wrote: > Hi list > > Found this on reddit: http://impulse.is/ > > PDF: http://impulse.is/impulse.pdf > > I'd love to hear this list's thoughts. > > /runeks I'm concerned about the silence that always erupts whenever privacy-hostile products are proposed. -- Support online privacy by using email encryption whenever possible. Learn how here: http://www.youtube.com/watch?v=bakOKJFtB-k -- New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet ___ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
Re: [Bitcoin-development] IMPULSE: Instant Payments using the Bitcoin protocol
The user experience is significantly more secure than today. Presumably the future supports many payment facilitators, including m-of-n oracles, and this is perfectly compatible with that. On Thu, Jan 22, 2015 at 10:19 AM, Tom Harding wrote: > On 1/17/2015 12:45 PM, Rune Kjær Svendsen wrote: > > PDF: http://impulse.is/impulse.pdf > > > > I'd love to hear this list's thoughts. > > > > Will success be defined by "BitPay Payment Channels Accepted Here" signs > appearing in shop windows? > > > > -- > New Year. New Location. New Benefits. New Data Center in Ashburn, VA. > GigeNET is offering a free month of service with a new server in Ashburn. > Choose from 2 high performing configs, both with 100TB of bandwidth. > Higher redundancy.Lower latency.Increased capacity.Completely compliant. > http://p.sf.net/sfu/gigenet > ___ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > -- Jeff Garzik Bitcoin core developer and open source evangelist BitPay, Inc. https://bitpay.com/ -- New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet___ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
Re: [Bitcoin-development] IMPULSE: Instant Payments using the Bitcoin protocol
On 1/17/2015 12:45 PM, Rune Kjær Svendsen wrote: > PDF: http://impulse.is/impulse.pdf > > I'd love to hear this list's thoughts. > Will success be defined by "BitPay Payment Channels Accepted Here" signs appearing in shop windows? -- New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet ___ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
Re: [Bitcoin-development] Deanonymisation of clients in Bitcoin P2P network paper
> > I hear that. But I don't see why mainstream wallets and wallets > designed for crypto research should not share a common core. > I think there was some misunderstanding. I was saying they *could and should* share common cores, so we are in agreement without realising it :) I also didn't mean to imply there was anything special about bitcoinj, just that it's an example of a wallet engine that's already in use. > BIP70 is interesting, indeed, although I still fail to understand why > (according to the specs I saw) the PaymentRequest message is signed, > but not the Payment message. > Because it's intended to be submitted via HTTPS. But what would you sign the message with? Some arbitrary key bound to the transaction? -- New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet___ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
[Bitcoin-development] Ensuring security of funds and preserving anonymity when using Bitcoin for e-commerce
I wrote a blog post entitled "Ensuring security of funds and preserving anonymity when using Bitcoin for e-commerce". I thought the readers of this list might be interested. http://jonathanpatrick.me/blog/bitcoin-ecommerce -- New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet___ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
Re: [Bitcoin-development] Securing wallet on paper
On 22/01/15 10:36, U.Mutlu wrote: > Later, typing it from paper to a small converter program that recreates the > wallet file. Bitcoin Core still does not support Hierarchical Deterministic aka BIP32 Wallets. Without them it is possible to backup just one private key per backup, which is rather useless and in fact dangerous. > I would suggest the developers make such functionality available for the user. I would suggest looking at different software wallets that do support such functionality such as Electrum or Multibit. -- Best Regards / S pozdravom, Pavol Rusnak -- New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet ___ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
[Bitcoin-development] Securing wallet on paper
I don't know yet the details of how a wallet looks like internally, but I think it should be possible to print the wallet incl. acct nbr out on classical paper (as base16 or base64 etc.) for filing it in a physical home or bank safe. Later, typing it from paper to a small converter program that recreates the wallet file. IMO this is a good security against possible computer hardware disasters. Of course one has to secure this further with encryption against bank fraud/theft etc. Ie. the output on paper should be encrypted, and the owner should place the key somewhere else. I would suggest the developers make such functionality available for the user. cu Uenal -- New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet ___ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
