Am Mo, 24.10.2011, 16:55, schrieb Gavin Andresen:
So my first shot at this is to go through the inputs of a transaction and
see if the scriptSig field has only two opcodes. If that is the case, I
assume that it is of the structure sig pubKey and calculate the
Bitcoin address from pubKey.
But
On Tue, 2011-10-25 at 11:45 +0200, Jan Vornberger wrote:
1) Get something working reasonable fast to detect current green address
style transactions. It's fine if it is a little bit of a hack, as long as
it's safe, since I don't expect it to be merged with mainline anyway at
this point.
2)
Interesting suggestion! So if I understand correctly, greensig would be
the signature generated from signing the transaction with the key of a
green address?
Sure. Or just a key. It wouldn't have to be an actual key used in
the block chain.
Sounds good - I guess I never thought in this
scriptPubKeys that use OP_EVAL contain a hash of a script. If I
understand correctly, that means to detect a transaction in a block
that is relevant to your wallet, that means you need to pre-calculate
every possible hash that might appear.
For the case of a single payment, that's not a problem.
On Tue, Oct 25, 2011 at 6:49 AM, Mike Hearn m...@plan99.net wrote:
scriptPubKeys that use OP_EVAL contain a hash of a script. If I
understand correctly, that means to detect a transaction in a block
that is relevant to your wallet, that means you need to pre-calculate
every possible hash that
On Tue, Oct 25, 2011 at 9:21 AM, Gavin Andresen gavinandre...@gmail.com wrote:
You give the hash to whoever is paying you, and store the hash --
script mapping when you do that (assuming you're not using a
deterministic wallet; if you are, you probably just increment a
counter in the wallet).
6 matches
Mail list logo