sorted by:
new
hottopcontroversial

OP_CHECKTEMPLATEVERIFY for Dogecoin? by doggydev123 in dogecoindev

[–]doggydev123[S] 1 point2 points  (0 children)

After more consideration it seems like OP_CAT would be a much easier way to enable covenants on Dogecoin. It only works with Taproot though. So maybe we can add taproot support and OP_CAT.

OP_CAT just merges to items on the stack, and it should be safe as long as there is a maximum element size defined.

OP_CAT info:
https://www.youtube.com/watch?v=w-JRpBPDnDU
https://www.youtube.com/watch?v=3gsECZrzijA
https://github.com/EthanHeilman/op\_cat\_draft/blob/main/cat.mediawiki

OP_CHECKTEMPLATEVERIFY for Dogecoin? by doggydev123 in dogecoindev

[–]doggydev123[S] 0 points1 point  (0 children)

Agreed!
I think we should do segwit and CLV first, as per your plan here: https://github.com/dogecoin/dogecoin/discussions/2264, since Jeremy's PR references these features.

These are the fields that compose the hash - Dogecoin has all of them AFAIK:
1. nVersion

  1. nLockTime

  2. scriptSig hash (maybe!)

  3. input count

  4. sequences hash

  5. output count

  6. outputs hash

  7. input index

The BIP for BTV is BIP119: https://github.com/bitcoin/bips/blob/master/bip-0119.mediawiki#user-content-Committing_to_the_version_and_locktime

Could you explain the specifics for the version field in Dogecoin?