Replying to Avatar epsql

I'm familiar with these points. I am not sure that fixing the current instantiation of inscriptions via OP_FALSE OP_IF checks would be enough though. There are ways ways to embed arbitrary data and it seems to be the only option to remove the possibility entirely is to only allow a set of well known transaction types, much more restrictive than what Core currently categorizes as "standard".
Avatar
BitcoinIsFuture 3mo ago

They are already fixed in Bitcoin Knots. And Knots is working fine.

All legitimate transactions and use cases can be tested but as for monetary transactions that transfer value, its all fine.

Restrictions is when someone takes away your options - deprecations first, removal second.

One thing to notice is that Bitcoin Knots gives you the FREEDOM to put whatever value in OP_RETURN you like. Think about that too.

Reply to this note

Please Login to reply.

Discussion

No replies yet.