What kind of “contract engineering” roles could emerge from current Bitcoin Script primitives?
I’ve been testing simple opcode combinations — CHECKSIG, CSFS, IK+CSFS....trying to get a feel for what each one actually binds.
It feels like the challenge is less about expressiveness, and more about choosing the right kind of binding.
I’m wondering:
Do developers see this as its own discipline — not Ethereum-style contracts, but something like designing Bitcoin’s contracts within constraints?
Does that map to a distinct kind of engineering role over time?
Or is this still just considered script work?
from Recent Questions - Bitcoin Stack Exchange https://ift.tt/7xwDKoX
via IFTTT