Thanks Peter for the paper!
I'm just going to restate your 'simple explanation' to make sure I got
it...
The payee publishes a public key of theirs, which will be a long-standing
identifier, public key = 'Q', corresponding private key = 'd'.
To pay them, payee generate a keypair, private
Hello all,
I'm designing a program that needs some metrics computed from the Bitcoin
block chain (some address balances, or the occurrence or not of a specific
transaction). The kind of infos you get from http://blockchain.info/,
provided you trust this website (my program do not).
My program
Some more thoughts :
If no such project exist yet, I thought it could work with an alternate,
small and fixed-length 'metric request block chain' of some sort.
It would temporarily stores structures defined as [metric request | current
block number when request was made | hash of the response]
3 matches
Mail list logo