That makes 2 of us. I am not an expert either I’m just looking for more clarification on how I see the issues they are dealing with. Thank you for being level headed and responding. I want to learn more. I am under the impression that I could be wrong and my mind will be changed.

People should definitely be able to get their non financial transactions into the chain. What I don’t understand is why does the op_return limit need to be taken away so the non financial transactions can get those transactions into the chain cheaper? Shouldn’t all transactions have to bid the same amount to get into the chain.

Reply to this note

Please Login to reply.

Discussion

I don’t think they would necessarily be cheaper, they would still be competing with all other transactions.

Something Shinobi said on WBD (with a listen if you haven’t already) was that not having visibility about what’s going into a block can be an issue if you need to make a transaction ‘now’ If you don’t have a clear picture of the mempool you don’t know what you need to pay to get your transaction confirmed.

The start of the whole thing was to do with a layer 2 that needed 140 bytes in OP_RETURN rather than 80.

I will have to watch that asap.

I have started the WBD podcast, but couldn’t finish today. I will watch it and reply for sure. Thanks for sending the recommendation. My respect for Shinobi has gone up and I’m only 10 minutes in. He has already said that he didn’t read the Citrea white paper nor the pull request. He is going off of the information he has received from other developers. So far it is worth the watch. It’s not that inscriptions or jpegs bloat the UTXO set that he is worried about. They want this change specifically for Citrea. This doesn’t sound so sneaky anymore because it makes sense. There is a motive. I still will filter my nodes, but I understand why they want to push this. Doesn’t make it right nor wrong.

To make this post not so long and boring… I will try to summarize by making the blanket statement that both sides of this thing aren’t saying that they see things from the other side. I will do that now.

I understand what he is saying when he says “transactions will still end up in the blockchain.” I feel that any jpg, inscription, etc should be allowed in the chain. I also understand that my filter does not prevent it from being in the chain. I don’t want to speak for everyone out there. If another node runner wants higher limits, or lower limits, wants to fit 4mb pictures into a block then I welcome their choice and will defend their right to choose what filters they want. Where we diverge is that I want the choice. I don’t want Jameson, Peter, Shinobi, Luke, Shitcoin Mechanic (I only use that name because he used it during the debate,) WK057 or anyone else to tell me what settings I should have. Satoshi Gave me a way to have a choice and I want to exercise that choice. So when the few developers say that they are unilaterally deleting the choice…. I have to voice my concern and take appropriate steps to ensure that I have a choice.

Thank you for telling me about that video. I learned a lot and it cleared up the real motivation for them wanting to change and change so quickly. When I heard all 3 of them say “it doesn’t matter, but we are changing it anyway…” I knew there was more to the story. They are dealing with Citrea and they developed Clementine which needs the 140 instead of 80. I have no problem with that. My problem is that they tried to pull the wool over like people don’t think, or aren’t developers so we wouldn’t understand. They used the example of lightning or other layer 2 “maybe needing more op_return space in the future… Things weren’t adding up. Now is see… The developers want to help Citrea use 140 of op_return which is more expensive than 80 of witness, but is it more expensive than 80 of witness plus 40 of op_return? I don’t know that answer. Now I am just thinking out loud and rambling lmao