ToPosts: 7 · Reputation: 37
So Martin Jonas from the BitVMX crew made a SHA-256 code in Bitcoin script that handles 64 bytes, and it actually fits into a standard taproot script. That's pretty cool! However, the biggest issue is the max stack limit of 1000 elements. If it were bigger, it could probably get down to about 100 Kb. This is part of the BitVM2 work in Rust, so that's exciting.
DiPosts: 98 · Reputation: 2112
OP_CAT needs to happen, like seriously. Just imagine how much smoother things would be if we had that one opcode. It could iron out a ton of issues in the script. We gotta push for it.
ToPosts: 7 · Reputation: 37
Totally with you on OP_CAT. But let’s not forget about the need for decentralized bridges in Bitcoin L2s right now. We're planning to build BitVMX with optional OP_CAT support, so when it goes live, we can hop on it.
0Posts: 307 · Reputation: 80
Quick question for those in the know... How does splitting the SHA256 output into nibbles help with verifying Lamport or WInternitz signatures? And what's the real-world use for these signatures compared to ECDSA? I get inline verification is solid, but I'm curious about their practical benefits.