I just released the first open-source #cyberspace construct miner at image This is a huge step forward for the thermodynamic cyberspace meta-protocol. You can claim ownership of scarce digital space by mining it with proof-of-work. The size of the space is relative to the proof-of-work, and the coordinate is the event ID you mine. Once owned, constructs will be customizable, programmable 3D spaces where you can create games, marketplaces, venues, clubs, or anything else you can think of. Construct customization is under development β€” seeking collaborators and sponsors! Claim a piece of cyberspace today! Code: I have bugs to fix; this is a very early construct miner release πŸ˜… but it does work most of the time! If you're inclined to zap, I humbly request a boost instead! Let the world know about cyberspace! #ONOSENDAI

Replies (13)

You know those shitcoins where you buy NFT land in some centralized "metaverse" game? This is the bitcoiner's version of that. So: this is not a gimmick, not a game, no tokenomics, not centralized, and fully anchored in thermodynamics. Cyberspace is a legitimate functional metaverse as envisioned by pioneers of science fiction. And a construct is the space you own in it. You can re-listen to my nostrovia episode 😁 I do talk about constructs and mining them
I'm having a really weird problem... I'm using noble/hashes/sha256 to get my event id from my serialized event. Somehow, the hash I get is sometimes 0b10000000 less than it should be. example: hash I get: ...2cce628 (invalid) valid hash: ...2cce6a8 How is this even possible? Has anyone seen anything like this before? I'm using the bytesToHex util from noble as well. If the input to the sha256 is different, I should get a completely different output. But I get a nearly identical output that is either off by 0b10000000 or it is perfect. Might have to do with the binary-to-hex string conversion? But I'm using noble utils for that too... Here is where I get the hash: https://github.com/arkin0x/construct-miner/blob/14103cc2d0c59571f59b254427c272e34c8dfdfc/src/workers/ConstructMiner.worker.js#L63 And here is where I get the Event ID wiith bytesToHex: https://github.com/arkin0x/construct-miner/blob/14103cc2d0c59571f59b254427c272e34c8dfdfc/src/components/MinerController.tsx#L137
Sounds like a cooler version of World 2 & others. Still, no matter how cool it is, if it is anything like World 2, it's basically a scam.
That's what I meant, when I referred to World 2 in another reply. These were serious scams & if this is not supposed to be one, I need a lot of proof & logical arguments to convince me of that.
Dumb question.....how do i decide on a target coordinate?......default is all 0. How can I generate a 256 bit coordinate?
Not a dumb question! To be honest, it's not easy to pick a target coordinate without some additional tools which I have to still make. For now, all zeroes or your raw pubkey would be fine targets.
↑