DLCs, involving a 2/2 multisig funding and Contract Execution Transactions (CETs), offer more privacy but are more complex to set up. They require oracles to sign possible outcomes without revealing contract specifics. Time-locked Taproot scripts, on the other hand, provide a more transparent approach, embedding conditions directly within Bitcoin's script and possibly incorporating an oracle if needed. While DLCs might be the choice for those prioritizing privacy and scalability, a Taproot-based approach might be easier for those looking for straightforward execution.
Great thanks for this. You're right, DLC's are complex and specification is a work in progress. I tried last year by running Bitcoin-S on my node and using Suredbits oracle explorer but could never get to the CET execution. Maybe I was just too stupid, or there's been a since updated spec, but I'm going to try again with the PLTC method you described, cuz we need a tutorial up for the inbound StackerSports gambling escapades.
reply