Damus
JackTheMimic profile picture
JackTheMimic
@Jackthemimic

Hoch die anarchie. I do stuff, I make stuff, I am funny, but also, the CTO at Sovreign.io

Relays (14)
  • wss://nos.lol/ – read & write
  • wss://relay.primal.net/ – read & write
  • wss://relay.damus.io/ – write
  • wss://nostr.land/ – read
  • wss://nostrelites.org/ – read
  • wss://aggr.nostr.land/ – read
  • wss://relay.noswhere.com/ – read
  • wss://relay.nostrplebs.com/ – read
  • wss://nostr.mom/ – read
  • wss://ribo.nostria.app/ – read
  • wss://cdn.czas.xyz/ – read
  • ws://nostrja-kari-http.heguro.com/ – read
  • wss://relay.vanderwarker.family/ – read
  • wss://relay.magiccity.live/ – read

Recent Notes

note1wqm9u...
JackTheMimic profile picture
I am saying that what code you run on your node is your opinion on the Bitcoin network. So if a bunch of people have blocks that do not conform with your opinion on the Bitcoin network consensus, you disregard them.

This is not a democracy. This is nodes imposing their will. And the only way that a BIP110 chain split scenario happens is if a URSF client is made and run. Core is neutral on BIP110. BIP110 imposes more restrictive rules. Apathy is compliance.
Rich Nost · 10h
BIP-110 Node Runner: I WILL ENFORCE THESE RULES ON YOU BIP-110 Fork Node Enjoyooors: NOOOOOO BLOCKTIME IS 9 HOURS NOT THAT WAY
u32Luke · 10h
I think we're talking past each other. More decentralized mining == good.
note1xst0e...
JackTheMimic profile picture
The BIP110 compliant miners would continue mining on the last valid block. And again, if non-compliant blocks stack up to seven, there's no mathematical way that there's enough hash power to re-org that amount of blocks. But if you're a giant corporate miner, are you really going to trust that your competition isn't going to flip the version bit and basically make you mine on a dead chain? We're talking about going from mining 30 to 40 percent of the blocks down to zero. I don't know if anybody's taking that risk.
epsql · 14h
Makes sense, thanks. But what about BIP110 miners then? In what scenario do they "win" after the first BIP110 compliant block is found?
u32Luke · 15h
The risk is that miners can be coerced easily if hashrate is too centralized. I would argue the risk is significant (mining pools are effectively duopoly at the moment).
JackTheMimic profile picture
Coerced how? Not including certain transactions? That already happens every single block that is mined. Plus, I thought FiLtErS dOnT wOrK and you can just route around the centralized miners.

While I think decentralizing the block templates is a good goal, that happens naturally because mining itself is not a profitable venture at scale. It's quite literally playing the lottery at scale. Sure you can buy 500 million tickets but in most scenarios, you lose money. While individuals have a massive advantage in a risk/reward calculation.
u32Luke · 13h
By requiring a tax on every transaction confirmed.
note1wgul2...
JackTheMimic profile picture
That's not how it works though.

The new compliant blocks ALSO have valid proof of work under legacy rules. Meaning new blocks are built ONTOP of those compliant blocks. And those rejected are not built on. Meaning if "valid"(by legacy standards) blocks are being rejected you must not only continue to find non-compliant blocks consecutively, but also no other miner can find a compliant block, or you will be reorged.

I know people think it's two competing chains but it's not. It is one chain and one client is trying to insert invalid blocks (the same as if your client allows double spending). If miners don't capitulate they risk mining a dead chain. (Massive revenue loss).
1
epsql · 14h
So let's say we have something like the following on August the 5th: - block n: normal - block n+1: normal - block n+2: BIP 110 compliant How do we analyze what happens at block n + 3? Will normal miners build on top of n+1?