• 0 Posts
  • 431 Comments
Joined 8 months ago
cake
Cake day: August 21st, 2024

help-circle






  • you’re calculating the sha256 (i think) hash of the previous transaction block’s hash plus your block of transactions. What’s making it proof-of-work though, is the stipulation that “the hash has to start with at least five zeroes”, with “five” being an adjustable difficulty value. To be able to get that specific hash an otherwise meaningless number (a “nonce”) is included, and by increasing this number by one you can change the hash value.

    so basically, all these servers are running hash calculations on the same thing over and over again with a single number changing between runs until they get an “approved” hash value. whoever gets there the fastest gets their block added to the chain, then everyone else has to start over with that hash as the “previous” one.

    It’s called “proof of work” because it’s difficult to find a suitable value, but it’s trivial to check that it’s correct. you just need the nonce. so by presenting that nonce to everyone, you’ve proved that you “did the work”.

    as for the reason why they do this, if each block’s hash is dependent on the hash of the block before it, it means the entire chain is resistant to tampering. you can’t insert a block in the middle without recalculating the entire chain.




  • the trademark got bought. it’s still FLOSS, and they pledged to keep it that way, for whatever that’s worth. code can’t be retroactively un-gpled, so if they did decide to close it down they couldn’t just take it offline, only do new development in private. the big fishy thing was that they added a CLA to their repo, which only affects developers. as an end-user you’re fine.

    also, the “crap” was a draft proposal of opt-in telemetry, which was subsequently scrapped. the company in question is based in the EU, anyway, so they would have to abide by the gdpr for any collected information.

    the hackaday series on this is probably the best summary.