RE: buying me and Gregory a shared beer:
I would make a both of two btc-addresses script transaction using OP_EVAL.
And post it.
You would then not be able to know that you actually got a beer unless I told
you so in a mail.
But that transaction won't show up in my bitcoin wallet as
OK, let me try to explain what I see is the problem:
So far we the bitcoin addresses are (for all practical purposes) a one-to-one
mapping between a pubkey and uint160. This mean that your wallet is defined
solely by your privatekeys (from which you can extract pubkeys and then uint160
I think it is a very important feature to be able to extract transaction
to/from you only from your private keys. In the standard transactions this is
easily accomplished - in the case you only want to find the addr to tx mapping:
vectorpairopcodetype, vectorunsigned char vSolution;
if
On Wed, Oct 26, 2011 at 4:58 AM, Michael Grønager grona...@ceptacle.com wrote:
I think it is a very important feature to be able to extract transaction
to/from you only from your private keys. In the standard transactions this is
easily accomplished - in the case you only want to find the
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
