A peek under Bitcoin’s hood: Writing a client that can create a transaction
1–10 of 67 posts
Re: A peek under Bitcoin’s hood: Writing a client that can create a transaction
#2Very cool. This could be used to implement offline wallet with minimal amount of third party code.
One issue I'd like to point is I wish the author used proper random generated private key. Examples on the internet have a nasty habits of being copy pasted and reused verbatim :(
Re: A peek under Bitcoin’s hood: Writing a client that can create a transaction
#3Article says
> This is also why address reuse in Bitcoin is encouraged as to sign a transaction you need to reveal your public key. If you don't reuse an address after sending a transaction from the address, you don't need worry about the private key of that address being exposed.
Shouldn't that say "address reuse in Bitcoin is discouraged"? Otherwise I don't think I understand what he's trying to say.
Re: A peek under Bitcoin’s hood: Writing a client that can create a transaction
#4Article says > This is also why address reuse in Bitcoin is encouraged as to sign a transaction you need to reveal your public key. If you don't reuse an address after sending a transaction from the address, you don't need worry about the private key of that address being exposed. Shouldn't that say "address reuse in Bitcoin is discouraged "? Otherwise I don't think I understand what he's trying to say.
[deleted]
Re: A peek under Bitcoin’s hood: Writing a client that can create a transaction
#5Article says > This is also why address reuse in Bitcoin is encouraged as to sign a transaction you need to reveal your public key. If you don't reuse an address after sending a transaction from the address, you don't need worry about the private key of that address being exposed. Shouldn't that say "address reuse in Bitcoin is discouraged "? Otherwise I don't think I understand what he's trying to say.
Address reuse is most certainly discouraged from a security standpoint! I expect that you are correct as to the article's intended meaning.
Re: A peek under Bitcoin’s hood: Writing a client that can create a transaction
#6Very cool. This could be used to implement offline wallet with minimal amount of third party code. One issue I'd like to point is I wish the author used proper random generated private key. Examples on the internet have a nasty habits of being copy pasted and reused verbatim :(
Not using cryptographically safe random key is very stupid, even though it is only an example. It should be very trivial to fix this example.
I think in python the right way is to use the os.urandom() function.
Re: A peek under Bitcoin’s hood: Writing a client that can create a transaction
#7Hi Sam,
If you're reading the comments, can you do this treatment but for Ethereum and the smart contracts built on top of it?
I find that your article gives a good explanation especially for beginner to understand from the code perspective.
Re: A peek under Bitcoin’s hood: Writing a client that can create a transaction
#8>> 0xFACEBEEF and sent it 0.0005 BTC.. 1 month later and someone had stolen my 0.0005 BTC! I guess people must occasionally trawl through addresses with simple/common private keys.
This made it worth reading the article. Such cyberpunk!
Re: A peek under Bitcoin’s hood: Writing a client that can create a transaction
#9Can someone explain why bitcoin adresses can be created (offline) without blockchain-validation for duplicates?
Even if the chances are very small I mean...like....gone is gone...no bank to call for a false transaction.
Re: A peek under Bitcoin’s hood: Writing a client that can create a transaction
#10Can someone explain why bitcoin adresses can be created (offline) without blockchain-validation for duplicates? Even if the chances are very small I mean...like....gone is gone...no bank to call for a false transaction.