Damus
nonymous profile picture
nonymous
@nonymous

Privacy, Freedom and Bitcoin

Relays (6)
  • wss://nos.lol – read & write
  • wss://eden.nostr.land – read & write
  • wss://relay.snort.social – read & write
  • wss://nostr.orangepill.dev – read & write
  • wss://relay.damus.io – read & write
  • wss://relay.current.fyi – read & write

Recent Notes

Rob Hamilton · 19w
Important to call out Dathon Ohm is now lying (misleading?) the consensus process by removing the rejected langauge about a reactive activation method, but may have to employ it anyway? It'll get cir...
nonymous profile picture
Don’t panic. He is building consensus and it is a very good thing to remove that activation method as it was rejected by most users. If Luke wants the reactive way he can make his own fork proposal to do it. Indeed I think it is a good idea to separate both. I would support one and reject the other one.
Luke Dashjr · 19w
The whole concept (as I originally designed it) was for an emergency/reactive UASF. I'm not sure it makes sense any other way. For a non-eventful softfork, you'd want to start it 1-1.5 years into the ...
nonymous profile picture
Why not separating both? 1.- Reactive/emergency UASF and 2.- UASF planned 1y ahead but permanent, not temporary.
I think Emergency UASF will have way less consensus around it and when/if the offending block happens IMO it will generate a split chain. The chain with the offending block will be considered bitcoin by most people (including miners, exchanges and businesses)
Planned UASF can have way more consensus around it. I think we could limit OP_Return to 80 in CR and also make inscriptions way more expensive. Maybe we could just remove the segwit discount, or at least, change the 4x to 2x (with the additional benefit of having blocks smaller)
❤️1👎1
Luke Dashjr · 19w
I do not support the rules in BIP444 on a permanent basis.
Vitor Pamplona · 32w
Can't it ask for the blocks this transaction's coins are coming from? If all 10 connected nodes send the same old blocks, it's which trustworthy. There is always a risk, but nothing that simply warning msg can't solve. It's similar to the 0-conf stuff.
Pierre · 89w
One of the greatest managers I had at work always used to say “perception is reality”. That’s certainly true in a work environment, but sadly more and more true in the real world too.
Newton · 97w
Any comment from experts about this. I'm curious too.