Technology
This is the official technology community of Lemmy.ml for all news related to creation and use of technology, and to facilitate civil, meaningful discussion around it.
Ask in DM before posting product reviews or ads. All such posts otherwise are subject to removal.
Rules:
1: All Lemmy rules apply
2: Do not post low effort posts
3: NEVER post naziped*gore stuff
4: Always post article URLs or their archived version URLs as sources, NOT screenshots. Help the blind users.
5: personal rants of Big Tech CEOs like Elon Musk are unwelcome (does not include posts about their companies affecting wide range of people)
6: no advertisement posts unless verified as legitimate and non-exploitative/non-consumerist
7: crypto related posts, unless essential, are disallowed
view the rest of the comments
The thing about proof-of-work is that, while performing the work, you have to know about which block you're creating. You aren't doing generic work. You're doing work that's specific to the block data. If you wanted to double spend, you would have to re-do the work, because the work you did is only applicable to the exact block you mined.
And therein lies the problem with using a globally observable event like you've described: It is not tied to any particular block. I can use the radiation data from the fifth of March to mine a block, then use the same data to mine a conflicting block. "Nothing at stake" problem is related.