Comment Re:How long until R supports this? (Score 2) 89
Support exists now:
Support exists now:
Say you had received 10 bitcoins, you would have a private key which could generate a matching signature to unlock the public key it was transferred to.
When you spend say 4 coins, you create a transaction and publish it to the network. This transaction consists of
1) A point to the place in history where it was transferred to you
2) An amount, 4 bitcoins and an address of a recepient public key
3) An amount, 6 bitcoins and an address of a new public key you have just generated, and hold the private key for
Any attempt to respend this coin would be rejected by the network as it has been marked as used. To spend the remaining 6 you would have to point to its new location and if you had restored your wallet to an old version you'd have lost the private key for that, thus losing you all 10 sadly.
I've not deployed DNSSEC, but i was interested by your comments about exposing zone data at least.
I did a quick google and it suggests that used to be the case but from bind 9.6.0 onwards it can use NSEC3 to hash the child names.
Worth looking into for anyone who is concerned.
What the hell is a bad performance improvement?
Must be similar to a positive regression.
I've noticed several design suggestions in your code.