Great post! Now we can use this as a resource for noobs to learn the basics. You should post this on the Noobs section so they can take advantage of this.
Thanks!
Topic: Bitcoin Glossary (Read 1345 times)
AWESOME, thanks for posting this!
Some things to consider....
No entry for Silk Road, Tor, . I guess you are taking the High Road on that?
51% attack is distinct from double-spend.
There are many examples of double-spend type attacks (spawning multiple instances of virtual machines from the same wallet and sending the same coins from each creating a race condition to be resolved in the proof of work, would be another type).
51% is more a takeover of the mining authority, which can (among other things) enable double-spending, but it is much more than that.
Some things to consider....
No entry for Silk Road, Tor, . I guess you are taking the High Road on that?
51% attack is distinct from double-spend.
There are many examples of double-spend type attacks (spawning multiple instances of virtual machines from the same wallet and sending the same coins from each creating a race condition to be resolved in the proof of work, would be another type).
51% is more a takeover of the mining authority, which can (among other things) enable double-spending, but it is much more than that.
While writing documentation to CoreBitcoin (Objective-C implementation) I tend to explain some terms over and over again. To avoid repetition, I decided to come up with one more-or-less complete glossary of all technical Bitcoin terms from "difficulty" to "scriptPubSig". This glossary immediately answers a lot of questions that I myself had while learning how Bitcoin works. I hope it will greatly help newcomers to understand what people are talking about.
Here's the latest version of the glossary:
https://github.com/oleganza/CoreBitcoin/blob/master/GLOSSARY.md
Feel free to comment or even edit it on Github if you find mistakes. Thanks!
Here's the latest version of the glossary:
https://github.com/oleganza/CoreBitcoin/blob/master/GLOSSARY.md
Feel free to comment or even edit it on Github if you find mistakes. Thanks!
Jump to: