Topic: Design Diagrams? (Read 8029 times)
Thank you!
Is the bitcoin address a SHA-1 hash of the public key? or perhaps some other 160 bit hash? and why is it a 34 character string instead of say the more common 32 char 5 bit representation?
It's a RIPEMD-160 hash of the SHA-256 hash of the public key. It also contains version information and a check code.
So imagine that, just read the code and all my questions were answered. All but one at least!
Is the bitcoin address a SHA-1 hash of the public key? or perhaps some other 160 bit hash? and why is it a 34 character string instead of say the more common 32 char 5 bit representation?
By the way, very nice code base guys! Kudos!
Is the bitcoin address a SHA-1 hash of the public key? or perhaps some other 160 bit hash? and why is it a 34 character string instead of say the more common 32 char 5 bit representation?
By the way, very nice code base guys! Kudos!
Are there any design diagrams other than those in the white paper?
Specifically, I'm looking for details of how the block list/tree is implemented and how each transaction is represented.
UML would be nice but any other data model would do. If they don't exist, could someone point me to the appropriate header files? At the moment, I'm on limited hardware so I can't build and poke around as I normally would.
Specifically, I'm looking for details of how the block list/tree is implemented and how each transaction is represented.
UML would be nice but any other data model would do. If they don't exist, could someone point me to the appropriate header files? At the moment, I'm on limited hardware so I can't build and poke around as I normally would.
Jump to: