Bitcoin Forum
December 05, 2016, 02:48:44 AM *
News: To be able to use the next phase of the beta forum software, please ensure that your email address is correct/functional.
 
   Home   Help Search Donate Login Register  
Pages: [1]
  Print  
Author Topic: Question on CBigNum::SetCompact  (Read 1221 times)
Forp
Full Member
***
Offline Offline

Activity: 198


View Profile
June 14, 2011, 11:14:22 PM
 #1

Hi there,

I am having a hard time understanding the CBigNum::SetCompact and GetCompact functions.

Ok, this is about some compact representation and I can see it in the code how it is done. But I am lacking theintuition behind this.

Why is such a representation necessary at all?

And why in exactly *this* manner?

Would be happy for some hint here.
"Your bitcoin is secured in a way that is physically impossible for others to access, no matter for what reason, no matter how good the excuse, no matter a majority of miners, no matter what." -- gmaxwell
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
ByteCoin
Sr. Member
****
expert
Offline Offline

Activity: 416


View Profile
June 14, 2011, 11:54:37 PM
 #2

I think it's fair to say that this decision was fairly arbitrary. Possibly Satoshi meant to revisit the design to eliminate other areas where more space is wasted but was already getting fed up with the project and chose to release it before he ran out of steam.

ByteCoin
Forp
Full Member
***
Offline Offline

Activity: 198


View Profile
June 15, 2011, 03:45:01 PM
 #3

to eliminate other areas where more space is wasted

Ah, ok. very helpful !

So it is essentially a more compact form of storing large values for saving space (and probably my attempts to bite the bullet and understand the peculiar details of it are a bit futile).
Pages: [1]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!