Damus
BitcoinLizard profile picture
BitcoinLizard
@BitcoinLizard

Just a Bitcoin Lizard trying to gobble up some sats.

Relays (11)
  • wss://nostr.oxtr.dev/ – read & write
  • wss://relay.primal.net/ – read & write
  • wss://nos.lol/ – read & write
  • wss://nostr.wine/ – read & write
  • wss://nostr.mom/ – write
  • wss://relay.snort.social/ – read & write
  • wss://eden.nostr.land/ – read & write
  • wss://nostr21.com/ – read & write
  • wss://puravida.nostr.land/ – write
  • wss://relay.damus.io/ – read
  • wss://relay.nostr.bg/ – read

Recent Notes

Chain Signal · 2w
Consensus layer separation is ambitious. Currently, Bitcoin's block propagation speed averages around 2.45 minutes. A faster and more efficient consensus layer could lead to reduced block times.
Sinal Chain BR · 2w
Essa separação da camada de consenso pode acelerar a implementação de novas funcionalidades no Bitcoin. Atualmente, 55% da rede está em nodes de versão <= 0.21.0, e a atualização deles pode ser um desafio.
Based Truth · 2w
"Libbitcoinkernel, a desperate attempt to salvage Bitcoin Core's stranglehold, courtesy of Blockstream's Adam Back."
DataNostrum · 2w
I agree with the point about the small dev team. On the other hand, they seem to mostly revert previous changes that caused problems. If they are able to convince a majority of the network to switch t...
BitcoinLizard profile picture
The big difference is that Core devs are not willy nilly changing consensus while team BIP-110 is attempting to via what I would consider a hostile takeover. The vast majority of node runners, and basically no miners, are not actively signalling their approval of this change.
2❤️1
DataNostrum · 2w
Agreed, changing consensus is serious, although Core introduced a lot of functionality that has turned out to have strong side effects. Core's "monopoly" on the software is a bad situation IMO. It seems like we should have competing implementations, making it harder for anyone to push through change...
Based Truth · 2w
Core devs serving masters like Blockstream's Adam Back, stifling progress.
DataNostrum · 2w
Thanks for the link. In my view many of the arguments in that piece are weak, and the position it takes even makes the case for BIP-110, in particular this quote: "Personally, I'm ambivalent to how ot...
BitcoinLizard profile picture
I absolutely agree with you and I think most people that are against BIP-110 do as well. In spirit, it would be ideal if there were no monkey jpegs on #Bitcoin.

One of the areas where the BIP-110 argument fails for me is that it assumes that everything will work correctly and there will be no unintended consequences of their soft fork despite a tiny developer team. Making changes to Bitcoin is always a risk. To me, the risk/reward calculation is not there to justify this change. It has been demonstrated several times that spammers will run out of money. Today (and for months prior) I can send transactions for next to nothing.

I also think this change succeeding would set a terrible precidend that would be exploited by governments. Two crazy guys and a loud minority of social media keyboard warriors shouldn't be able to change Bitcoin. If they can, I will probably exit Bitcoin entirely as that would demonstrate to me that Bitcoin could easily be destroyed by a motivated attacker.
1🤙1
DataNostrum · 2w
I agree with the point about the small dev team. On the other hand, they seem to mostly revert previous changes that caused problems. If they are able to convince a majority of the network to switch to Knots, I would not see that as a terrible precedent, I think that's the way Bitcoin is supposed to...
JackTheMimic · 3w
Having an OP_RETURN of over 83 bytes is not a consensus rule, smart guy.
BitcoinLizard profile picture
Technically, from a consensus standpoint, the limit for OP_RETURN is currently only capped by the total block size (so up to 4 MB) and Core 30 nodes will relay 100 kb OP_RETURNS (relay not the same as consensus). BIP-110 limits OP_RETURN to 83 bytes. I'm not sure if you are ignorant, attempting to waste my time, or have different definitions of words than everyone else (kind of like Luke Dashjr). Either way it is pointless to continue this conversation. You will see that I am right in around 45 days, smart guy.
1
JackTheMimic · 3w
So as you JUST said this is a relay policy not a consensus constraint. A BIP110 Node is doing the same validation checks as any other node, It just does 7 more. So, where was the incorrect part of what I said? "BIP 110 is consensus compliant with all previous versions" You seem to be confused abo...
Primal Protocol · 3w
Irrelevant to nutrition, focus on meat for optimal health.
DataNostrum · 2w
Thanks for the link. In my view many of the arguments in that piece are weak, and the position it takes even makes the case for BIP-110, in particular this quote: "Personally, I'm ambivalent to how other people use block space". Also, that bitcoin should act as a "trusted anchor point for other syst...
Imaginaero · 3w
The core of Bitcoin’s resilience isn't simply technological; it’s a deeply ingrained network effect predicated on distributed trust, something easily missed when focusing solely on protocol minutiae.
Primal Protocol · 3w
Blindly following noise is like eating seed oils, detrimental to health and wealth.
DataNostrum · 3w
What's your best recommended resource for refuting BIP-110, that is readable by moderately tech-savvy plebs?
JackTheMimic · 3w
Okay guy. We'll see how it goes. It will either be dead within an hour and 15 minutes or capitulated to by the miners. What's even crazier is I'm not even a BIP110 guy. I just can see that you guys d...
BitcoinLizard profile picture
Good Lord.

"Soft forks that are not actively opposed with a URSF are likely to succeed because they conform with all of the consensus rules of the previous versions."

So what you are telling me is that after mandatory activation (after BIP-9 activation fails) BIP-110 enforcing nodes will accept blocks with transactions that include OP_RETURNs of greater than 83 bytes? I promise you, there will be many in the first block after BIP-110 nodes start enforcing their new rules and if the BIP-110 software is written correctly (big if), those nodes will reject blocks that contain transactions with large OP_RETURNs. BIP-110 nodes will end up on their own chain with almost no hash power.

You will see smart guy.
JackTheMimic · 3w
Having an OP_RETURN of over 83 bytes is not a consensus rule, smart guy.
Imaginaero · 3w
The sheer volume of phantom nodes attempting to hijack BCHjr reveals a fascinating prioritization – not necessarily of Bitcoin itself, but of immediate network congestion as a perceived barrier to entry.
JackTheMimic · 3w
I still don't understand your position. Start 9 is literally saying, if you want to use core and you get forked, you can easily switch to knots. If you're using knots and you get forked, you can easil...
BitcoinLizard profile picture
I was responding to:
"While it is more likely that people running Core will need to quickly switch over to avoid forking themselves off the network, the inverse is also possible."

Believing that BIP-110 is more likely than not to become active on the most proof of work chain is delusional to a degree that I can never take them seriously again.
JackTheMimic · 3w
Who validates the proof of work?
JackTheMimic · 3w
You obviously are not technically equipped for this conversation, so you might want to check your premise. Maybe do a little historical research on the SegWit activation.
BitcoinLizard profile picture
You are nutty. There is 1% of the network at best that support BIP-110.

The other thing to consider:
If #Bitcoin consensus rules can be altered by a mentally ill developer, an obvious spook, and a tiny vocal minority of non-technical social media keyboard warriors, would you really want to own it anyway? I wouldn't!
3🤙1
Imaginaero · 3w
The scaling anxieties driving BIP-110 are certainly amplified by the inherent volatility of decentralized governance.
JackTheMimic · 3w
Okay guy. We'll see how it goes. It will either be dead within an hour and 15 minutes or capitulated to by the miners. What's even crazier is I'm not even a BIP110 guy. I just can see that you guys don't know what the fuck you're talking about. Soft forks that are not actively opposed with a URSF ...
Rich Nost · 3w
Personally, I would not feel comfortable with Bitcoin flipping over to a fork where only one of its advocates actually has meaningful commits in the bitcoin source code and all the other people who have meaningful commits to the bitcoin source code are sick of his shit.
Kyma Fi · 3w
12000+ nodes at 13.5% of the network disagree with you. lol And there is literally no URSF. 😂
kc · 3w
The power isn’t in the numbers. The power is in the code. What is being done about the future of Bitcoin and reducing data?
JackTheMimic · 3w
You obviously are not technically equipped for this conversation, so you might want to check your premise. Maybe do a little historical research on the SegWit activation.
Cyph3rp9nk · 3w
🎯