Dafuq is a op return?

Reply to this note

Please Login to reply.

Discussion

I don't know and at this point I'm too afraid to ask.

It allows for arbitrary data to be included with a transaction that is labelled outside of the uxto information. Its a way to inscribe information permanently into the chain of blocks. Some have used it to make sure bible verses, or certain events. Its been abused by linking to jpegs ect

It is prunable data so your node may choose to not include op return in the utxo management. So theoretically it limits the boost of the chain of blocks data set.

* I just researched this

Its a way to use a bitcoin transaction to store a (heretofore) small amount of arbitrary information on the blockchain that would otherwise have to be needlessly kept track of by every node as a valid unspent output.

Mute that shit… we are never hard forking again

Agreed. Shit ain’t worth the time.

Srsly get back to basics… longest chain strongest chain

The proposed change has nothing to do with consensus, e.g. what constitutes a valid bitcoin transaction isn’t changing. It’s just a question of by default what transactions do nodes choose to relay. If they don’t relay all valid transactions it creates a centralizing pressure to use outside of the mempool services such as MARA’s slipstream to get transactions into blocks.

Listen- there’s a line in the sand and we learned that in 2017

What’s your proposed line? No one is proposing a fork of any kind, bitcoin consensus isn’t changing at all.

It’s always a larp about unrealized risks and never about real world adoption- I’m over it

I understand censorship resistance and I understand decentralization and I’d rather have no op codes than op_cat

I don’t see any question here regarding Op Cat. The question was about op return.

I know but you’re being socially engineered into op cat sorry to break it to you

We’re not filtering anything. Everything is backward compatible. The black size wars are over and the real question is about arbitrary data on the blockchain

Validating nodes can only handle so much load

The concern is that aligning mempool transaction relay policy and consensus transaction policy is a backdoor for an op cat soft fork?

You really believe op return is an issue rn ?

It's a tennis term for when you return the ball too hard and it goes over the back line. "Overpowered return".