I have too much on my plate. I am excited about restoring Bitcoin Script, but I am more then full-time with my Lightning work.
But if someone has experience with Bitcoin's inner workings and wants to work on this, I would commit to carving out time to mentor them and help them get a grant.
It's not going to be easy, but it could be Great!
Ping me if you want to discuss 🧡
instr
how intertwined is the script interpreter with everything else?
is it possible to build a new one seperate from the old? And segregate them (huehue) by witness version?
It's possible, but my current approach is in-place, which makes for easier review. See https://github.com/rustyrussell/bitcoin/commits/guilt/varops/
hello, I would like to discuss how I can help with the grant part, I am sending you a DM.
That's quite sad news, I'm very bullish on the great script restoration, it's the most promising scaling solution to bitcoin imo.
I can't help with coding, but I can help get some funding for it. If you vouche for a contributor, I'll hussle to get him paid.
What are some of the use cases and scripts that will be possible with the additional opcodes?
Multiplying numbers, haha, groundbreaking I know!
That gets us zero knowledge verifiers though.
Haha, okay. Any more background on that use, who's working on it, discussing it, and documenting?
Seems like there is quite a bit that could be possible with more complete set of opcodes, as initially drafted in early implementations. Also sounds like some of what could be possible also needs more research.
Problems with DoS (the reason they were dropped) is also a solvable problem as far as I am concerned, given enough review and testing. I can see why they were initially dropped.
The point of scalable self-custody sounds very important.
There's a big list of second layers that currently use bitVM to hack an emulated zk verifier onchain:
I could be interested, I sent a DM.
