I’m pleased to announce version 0.12 of bitcoinj, one of the worlds most
popular Bitcoin libraries. It is used by at least four Android wallets, three
desktop wallets, blockchain.info, Circle, biteasy, CryptoCorp, Lighthouse,
BlueMatt’s relay network, bitpos, countless alt coin wallets, for
On Fri, Oct 3, 2014 at 2:49 PM, Mike Hearn m...@plan99.net wrote:
I’m pleased to announce version 0.12 of bitcoinj, one of the worlds most
popular Bitcoin libraries. It is used by at least four Android wallets,
three desktop wallets, blockchain.info, Circle, biteasy, CryptoCorp,
Lighthouse,
On 10/03/2014 02:49 PM, Mike Hearn wrote:
I’m pleased to announce version 0.12 of bitcoinj
This release represents 8 months of work. The biggest new feature is HD
wallets.
Congratulations on this release and I am quite happy that bitcoinj now
fully supports BIP32 and BIP39!
Does it also
Is there a reason why we can't have the new opcode simply replace the top stack
item with the block height of the txout being redeemed? Then arbitrary logic
could be implemented, including output cannot be spent until a certain time
and also output can ONLY be spent until a certain time, as
Oops, sorry. I meant: replace the top stack item with the block height of the
txin doing the redeeming. (So the script can calculate the current time to
some reference time embedded in the script.)
On Friday, 3 October 2014, at 10:28 am, Matt Whitlock wrote:
Is there a reason why we can't
On Fri, Oct 3, 2014 at 7:28 AM, Matt Whitlock b...@mattwhitlock.name wrote:
Is there a reason why we can't have the new opcode simply replace the top
stack item with the block height of the txout being redeemed?
This would not be soft-forking compatible.
It also would be unsafe in that it
On Friday, October 03, 2014 2:28:17 PM Matt Whitlock wrote:
Is there a reason why we can't have the new opcode simply replace the top
stack item with the block height of the txout being redeemed? Then
arbitrary logic could be implemented, including output cannot be spent
until a certain time
Alright. It seems there's no real disagreement about how the opcode
behaves. Perhaps a time limit would be appropriate to stop people creating
outputs locked for 100 years is bitcoin even likely to exist in 100
years? The entire history of computing is not even that old, seems hard to
imagine
I'm stunned by what bitcoinj can do these days. Just reading the
release notes gives one app ideas. Mike, Awesome.
On 10/3/2014 5:49 AM, Mike Hearn wrote:
I'm pleased to announce version 0.12 of bitcoinj, one of the worlds
most popular Bitcoin libraries.
On Fri, Oct 03, 2014 at 07:12:11PM -0400, Jeff Garzik wrote:
RE It's not like other software where people can choose to skip an
upgrade and things still work just like before.
If you're a minority, sure you can. Still a few nutters out there on
a 0.3.x codebase, including one or two
10 matches
Mail list logo
