Avatar
thunderbiscuit
5df936e47d5d114a2b1c27b9bb6955c2e86cd5614386a96252029187d35e7206

I have finally completed the encyclopedia section of https://opcodeexplained.com/. One page for each opcode, all 256 of them. You can use them as references in blog posts, stack overflow answers, general online discussions.

There is much more to be done, including all of the tapscript variants on them, but it's in a good place to start using it! Next up is beefing up the bitcoin Script section...

If you know a lot about bitcoin script (and particularly tapscript!) and would like to help out, send me a DM!

I was trying to decide what bitcoin conferences to go to this year and wasn't able to find a clean, simple list of them. So I just built one. Hopefully it's helpful to others. Help me fill it out!

https://bitcoinconferences.info

Yeah not a bad idea for sure. But it somehow feels odd that I can't get coins for even the most official of signets... Is it too much to ask for? It just might be apparently.

I'm looking for signet coins for the BDK CI. The only faucet I know of is down. Anyone has any to spare? (or a tip on where to get any?). Feel free to send some to tb1qlf9shgxdnvvw397j6n7c5ltw4sqzasrreqetrq if you have extra!

Replying to Avatar Wilfred Allyn

nostr:npub1thunderat5g552cuy7umk624ct5xe4tpgwr2jcjjq2gc0567wgrqnya79l you have the sweetest npub. what did you use to mine it? how long did it take?

Ha thanks! I don't remember what it was called. It was a Rust cli tool. Worked right out of the gate. I tried a few short ones on a local machine and once I got the gist of it just set it up in a small cloud instance. Took about a week I think. Maybe a bit more. I do agree it's pretty sweet! I don't want to have to key rotate too often...

Sorry I'm just getting started with nostr and not sure yet what I should do for my zap setup...

The goal of the website is to become a strong reference point that can be used to learn about opcodes one at a time of course, but also to be a resource you can always point to when writing formal documentation and referencing opcodes, for example in Stack Exchange questions and answers, library documentation, or blog posts.

For a few months I've been putting an hour or two every week on building a small encyclopedia of opcodes, mostly because I felt my opcode game was not strong enough to participate and reason clearly about all the new soft fork proposals.

There are 256 opcodes: I'm 80% done writing a small page for each of them. Today is the day I share this work publicly and invite people to come and join the fun.

Check out the website here: https://opcodeexplained.com/