lightning-dev

OP_Expire and Coinbase-Like Behavior: Making HTLCs Safer by Letting Transactions Expire Safely

OP_Expire and Coinbase-Like Behavior: Making HTLCs Safer by Letting Transactions Expire Safely

Original Postby Jorge Timón

Posted on: November 7, 2023 19:12 UTC

The recent discussion on naming conventions for operational codes in multi-asset blockchain implementations reveals a preference for maintaining original terminologies, as evidenced by the retention of the name 'op_expiry' rather than opting for an alternative like 'op_maturity' which was renamed to 'op_checkLockTimeVerify'.

This highlights a deviation from the principle that once a transaction is valid, it remains so unless explicitly replaced. The implications of this change are particularly significant for multi-asset chains such as those developed using the Elements Project or designed following the Freimarkets model.

In these multi-asset chain environments, the ability to set expiration conditions on operations paves the way for new functionalities. One notable application is the facilitation of peer-to-peer trades through the signing of incomplete transactions. These "offers" can then be completed and published by others who find the terms agreeable. While the concept extends beyond Bitcoin and may not be directly relevant to its protocol, it holds particular value for colored coin implementations.

Among the emerging use cases for this feature, the one that appears to be garnering the most interest is related to the Lightning Network. This demonstrates that innovations in operational codes and their applications have the potential to significantly enhance trade mechanisms and smart contract functionality within blockchain ecosystems.