[Bitcoin-development] Bitcoin Core 0.10.0 final was tagged

2015-02-13 Thread Wladimir
Hello,

I've just tagged 0.10.0rc4 as final (with a small packaging change to 
avoid tar nastiness). The tag is 'v0.10.0'.

Start your gitian builders!

For a guide on how to do gitian builds see 
https://github.com/bitcoin/bitcoin/blob/master/doc/gitian-building.md

Please wait with a release announcement until there are 3
builders and the binaries have been uploaded.

Cheers,
Wladimir

--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
___
Bitcoin-development mailing list
Bitcoin-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-development


Re: [Bitcoin-development] BIP for deterministic pay-to-script-hash multi-signature addresses

2015-02-13 Thread Ruben de Vries
The idea is more like BIP44/45 to have a 'standard' that software can
comply by and express they do
so that it makes a step towards compatibility between (wallet) software.

On Fri, Feb 13, 2015 at 8:53 AM, Peter Todd p...@petertodd.org wrote:

 On Thu, Feb 12, 2015 at 10:13:33PM +, Luke Dashjr wrote:
  Where is the Specification section?? Does this support arbitrary
 scripts, or
  only the simplest CHECKMULTISIG case?

 It might be enough to rewrite this BIP to basically say all pubkeys
 executed by all CHECKMULTISIG opcodes will be in the following canonical
 order, followed by some explanatory examples of how to apply this
 simple rule.

 OTOH we don't yet have a standard way of even talking about arbitrary
 scripts, so it may very well turn out to be the case that the above rule
 is too restrictive in many cases - I certainly would not want to do a
 soft-fork to enforce this, or even make it an IsStandard() rule.

 --
 'peter'[:-1]@petertodd.org
 13cf8270118ba2efce8b304f8de359599fef95c3ab43dcb1




-- 
BlockTrail B.V.
Barbara Strozzilaan 201
1083HN Amsterdam
The Netherlands

Phone: +31 (0)612227277
E-mail: ru...@blocktrail.com
Web: www.blocktrail.com
Github: www.github.com/rubensayshi

BlockTrail B.V. Is registered with the Dutch Chamber of Commerce in
Amsterdam with registration No.:60262060 and VAT No.:NL853833035B01
--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/___
Bitcoin-development mailing list
Bitcoin-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-development


Re: [Bitcoin-development] replace-by-fee v0.10.0rc4

2015-02-13 Thread Mike Hearn

  history. Lots of miners have dropped out due to hardware obsolescence,
 yet
  massive double spending hasn't happened.

 How many thousands of BTC must be stolen by miners before you'd agree
 that it has, in fact, happened?
 (https://bitcointalk.org/index.php?topic=321630.0)


Hmm. I think this is a disagreement over the term massive. I was meaning we
don't see double spending like we see carding fraud in the traditional
online payments world. We can talk about Finney attacks by linking to
specific discussions of specific events, because they are very rare, which
is why merchants generally ignore the possibility. I didn't mean the
numeric value of lost coins added up so far.
--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/___
Bitcoin-development mailing list
Bitcoin-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-development


Re: [Bitcoin-development] BIP for deterministic pay-to-script-hash multi-signature addresses

2015-02-13 Thread Thomas Kerin

On 12/02/15 22:13, Luke Dashjr wrote:
 Where is the Specification section?? Does this support arbitrary scripts, or 
 only the simplest CHECKMULTISIG case?

The BIP is a process for deriving only the type of scripts you would
encounter doing addmultisigaddress. More complicated scripts would
require more metadata to be shared, but the only case we describe is
when given public keys and the number of signatures required.

You're right, we're missing a Specification. I have tweaked the document
to cover this now.



On 13/02/15 07:53, Peter Todd wrote:
 It might be enough to rewrite this BIP to basically say all pubkeys
 executed by all CHECKMULTISIG opcodes will be in the following
 canonical order, followed by some explanatory examples of how to
 apply this simple rule. OTOH we don't yet have a standard way of even
 talking about arbitrary scripts, so it may very well turn out to be
 the case that the above rule is too restrictive in many cases - I
 certainly would not want to do a soft-fork to enforce this, or even
 make it an IsStandard() rule.

It would be interesting, but I agree it should not be brought into these
validation rules - just a convention for people to follow for now. I
think it's fair that implementers are free to order them however they
please. But I think there is good reason for wallets to opt in to the
convention and declare this, for ease of recovery, and for
interoperability reasons. 


-- 
Thomas Kerin


My PGP key can be found here 
http://pgp.mit.edu/pks/lookup?op=getsearch=0x3F0D2F83A2966155



0xA2966155.asc
Description: application/pgp-keys
--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/___
Bitcoin-development mailing list
Bitcoin-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-development