Damus
jb55 · 2d
op_cat may seem simple but will just lead to more complexity off chain. Ideally we just get covenants that actually express what we want to do offchain so we don’t need to jump through hoops or have...
nostrich profile picture
If we can't get even string concatenation we won't get anything custom or specific. That being said my position on the best opcodes is evident here https://gitHub.com/nuhvi/sake

Yes anything you express through the script army knife (or MATT) is a fraud proof system, but I have concluded that ANY L2 solution is guaranteed to require that minimum livenees to challenge at least Data Availability attacks.

The only solutions I am aware of for DA is to either challenge withdrawals and demand full state on Bitcoin which flat out doesn't scale, or the good old merge mining that so many hold their noses at even though it literally allows honest people to challenge DA in the same way they challenged private forks in Bitcoin.

If I am wrong and you are aware of black magic that doesn't require people to be vigilant and challenge withdrawals within a time window or risk losing their money, let me know. As far as I am aware only L1 is passively secure and that comes at the expense of scalability because it demands that everyone downloads everything forever and never prune or compress anything or else risk a reorg.

But I am excited to hear if I missed something
1
jb55 · 2d
i was just saying cat by itself, we should just do GSR and fix script