On Thu, Jun 14, 2012 at 10:37 AM, Peter Vessenes wrote:
> This is super cool!
>
> I have a feature request: it would be awesome to be able to provide private
> keys at the command line with the signature, turning the client into a
> wallet-less signature machine.
I like that idea.
A third argume
This is super cool!
I have a feature request: it would be awesome to be able to provide private
keys at the command line with the signature, turning the client into a
wallet-less signature machine.
Peter
On Thu, Jun 14, 2012 at 9:22 AM, Gavin Andresen wrote:
> I submitted a pull request yester
Block 177618 was rejected by BIP16-enabled backports (0.4.x and 0.5.x) due to
containing a P2SH redemption with over 200 bytes in. Since the BIP16 code uses
IsPushOnly to check the scriptSig for compliance, and IsPushOnly in these
versions also enforced the 200-byte "is standard" rule, they were
On Thu, Jun 14, 2012 at 9:22 AM, Gavin Andresen wrote:
>
> I've been asked a couple of times: why doesn't signrawtx handle the
> BIP 0010 (https://en.bitcoin.it/wiki/BIP_0010) transaction format?
>
> I considered parsing/writing BIP 10 format for raw transactions, but
> decided that reading/writin
I submitted a pull request yesterday that implements low-level "raw"
transaction, and am looking for feedback on the API and help with
trying to test/break it.
Design doc: https://gist.github.com/2839617
Pull request: https://github.com/bitcoin/bitcoin/pull/1456
Test plan:
https://secure.betterm
> filterinit(false positive rate, number of elements): initialize
> filterload(data): input a serialized bloom filter table metadata and data.
Why not combine these two?
> 'filterload' and 'filteradd' enable special behavior changes for
> 'mempool' and existing P2P commands, whereby only transact
6 matches
Mail list logo
