average_gary on Nostr: Talked about covenants today. What they are conceptually and then sole light details ...
Talked about covenants today. What they are conceptually and then sole light details on op codes for it.
Learned a ton about previous soft forks.
SegWit and Taproot were two massive engineering shifts. Adding new data structures and script interpretation logic.
Comparing those changes to covenants proposal. Covenant op_codes are way less "changing" to bitcoin since it's not an engine change. It's just one of option for bitcoin script, which is how users decide how their UTXOs are spent.
I wonder if covenants can disallow op_return use in future spends? 🤔
Published at
2025-09-26 01:08:02 UTCEvent JSON
{
"id": "c2d3cf1a130a8d1d29d111ec98f97ef4e0e30b418fd8aeb80d2fe54d12be16ab",
"pubkey": "d3d74124ddfb5bdc61b8f18d17c3335bbb4f8c71182a35ee27314a49a4eb7b1d",
"created_at": 1758848882,
"kind": 1,
"tags": [
[
"alt",
"A short note: Talked about covenants today. What they are concep..."
]
],
"content": "Talked about covenants today. What they are conceptually and then sole light details on op codes for it.\n\nLearned a ton about previous soft forks. \n\nSegWit and Taproot were two massive engineering shifts. Adding new data structures and script interpretation logic. \n\nComparing those changes to covenants proposal. Covenant op_codes are way less \"changing\" to bitcoin since it's not an engine change. It's just one of option for bitcoin script, which is how users decide how their UTXOs are spent.\n\nI wonder if covenants can disallow op_return use in future spends? 🤔",
"sig": "8814ac1eb023065339707bab116fd56fe4b7048970b568c648a310209475945d42d530a6c8d4ec2f897ed40c75517173f1a57a97aca9da56cc23a6ada1615621"
}