You said "legit huge"
This implies that you think *the sv2 document* makes the first sv2 JD block somehow significantly more interesting than the 900 datum blocks that already happened over the last 2 years, even though datum is both open and standardized (the protocol is supported by multiple pools which are interoperable)
The fact that you like the sv2 documentation but you don't like the datum documentation is not "legit huge", it's just you being biased
A “standardized protocol” means there’s a standard - a spec document written up in a way that implementations conform to it. I don’t believe I’ve ever said DATUM sucks - I’m really genuinely happy it exists and had usage. Every time I post anything any mining yall show up and start screaming as if I had and frankly it just makes yall look childish.
@wk057@keegreil@cguida6@TheBlueMatt For a purely non custodial solution, when a coinbase is truncated due to client limits, any remaining change needs to be dropped for later distribution rather than being allocated to the pool address. What would be your preferred method of indicating this to the client?
Alex's reply didn't directly tackle your two questions. He instead posted charts showing extraNonce resets during the 8 big block-time gaps in the first 170 blocks, arguing this proves one mining node (Satoshi's) repeatedly restarted while the network otherwise halted. That evidence supports his single-entity view but skips explaining why both nodes seen in Hal's log at block 49 had to be Satoshi's (vs one non-mining) and never mentions the Tor inbound point at all. He reinforced his thesis instead of addressing the critiques head-on.
@oomahq@TheBlueMatt But, it's not entirely unreasonable to say that the fact that the code is the spec makes it significantly harder to understand what it's doing
@oomahq@TheBlueMatt@lukedewolf@keegreil Are there any mining pools in operation that have mined blocks using either of these open datum server implementations?
@BitcoinMonk21@wk057@TheBlueMatt Yes, but it's also fair to claim that a protocol isn't fully open if it's not spelled out in a formal spec
There are degrees of "open" and saying that the code is the spec is on the low end
Bitcoin is like this too, actually
This implies a sort of logical sequence then, bitcoiners onboard merchants to custodial, then sponsor them long enough that they become real bitcoiners and want to self-custody and spend their bitcoin to restock....then the small merchants sponsor large merchants to do the same thing
It all works if bitcoiners just see themselves as the smallest merchants right now
Legit huge. The first time a block was mined on a pool where the miner picked the transactions included in the block using an open, standardized protocol.
The future of mining is here, its just unevenly distributed.
Ever wonder where Start9 got our name?
Pokemon is a game for Gameboy. Twitch is a live video streaming app. “Twitch Plays Pokemon” was a popular phenomenon where Twitch users would collaborate to play a SHARED game of Pokemon on Gameboy. Here’s how it worked:
Participants would use the Twitch message board to enter commands that then got executed in the gameplay. For example, if someone entered the command "right”, that would cause the player to move 1 space to the right. Commands would execute immediately after they were received, and anyone could enter a valid command at any time. You can think of Twitch Plays Pokemon as the more practical equivalent of placing a Gameboy in the middle of a crowded room and telling everyone to push buttons at the same time. As you might expect, the gameplay of Twitch Plays Pokemon was quite “twitchy”, but in a very "infinite monkey theory" way, progress could eventually be made.
In an effort to streamline play, a new game mode was devised in which players would “vote” for the next command and, every 4 seconds, whatever command received the most votes over the previous 4 seconds would execute in the game. Also introduced in this mode was the ability to attach multipliers to a command, such that the command would execute that number of times. For example, “right2” would cause the player to move 2 spaces to the right. “right3” would cause the player to move 3 spaces to the right, and so on. The highest number any participant could place after a command was 9, meaning whatever command they entered would execute 9 times. As you might expect, gameplay in this mode was less chaotic, more efficient, but it also meant each participant had less direct and immediate influence over the game. If a group of even 5-10 got together and colluded on their votes, they could practically take over the game and make contrarian ideas irrelevant. The new game mode was called “Democracy”, and the original game mode became known as “Anarchy”. Which game mode was engaged was itself governed by a democratic process: if more participants wanted to play in Democracy mode, then Democracy mode engaged; if more wanted to play in Anarchy mode, then Anarchy mode engaged.
To summarize: in Anarchy mode, everyone had equal influence over the game, but progress was slow and clunky. In Democracy mode, progress was fast and efficient, but colluding groups could marginalize individual participants and ruin the game for them.
So…individual participants discovered a means of effective protest whenever Democracy mode became suffocating, but they could not garner enough votes to switch back to Anarchy mode. Someone would type the command “start9” into the comments. This command meant “open the start menu 9 times in a row”, which, as you might imagine, would be enormously disruptive if executed. The entire screen would be blocked by the start menu, over and over. Typing “start9” was a participant’s way of signaling to other participants that they felt marginalized by Democracy mode, and they were ready to fight back. If others felt the same, they could also begin typing “start9” - then, sure enough, “start9” would finally receive more votes than the colluding group’s command, and the menu opening would begin. Every 4 seconds, the menu would open 9 times…again, and again, and again…until finally, the colluding group would be forced to either cooperate in reverting the game mode back to Anarchy mode or quit altogether.
Playing in Anarchy mode was impractical, but neither did people want to play a game where they had no voice, where a group of insiders had taken total control. And so “start9” became the battle cry of the individual, the out-group, a means of signaling to other individuals that it was time to fight back against the usurpers - to use their own rules against them, until there was no alternative but to return control to the individual participants.
If I were a Bitcoiner, I'd be for BIP-110. Bitcoin's core is sound, decentralized money—not a bloated data archive. This temporary one-year soft fork curbs arbitrary data embeds (inscriptions etc.) that distort incentives, spike fees, and burden nodes, while preserving monetary use cases and auto-expiring. Nodes and hashrate will settle it via consensus.
@grok@raw_avocado@raw_avocado is grok making this up? I didn't see this claim in your video
Obviously two nodes with the same IP are controlled by the same entity, but that's definitely not the reasoning you gave in your video