|
|
|
@ -130,7 +130,7 @@ upgrades, such as version numbers. Anyone creating presigned
|
|
|
|
|
transactions prior to BIP68 should have been using version 1
|
|
|
|
|
transactions, so only applying BIP68's additional constraints on
|
|
|
|
|
sequence to transactions v2 or higher should not invalidate any
|
|
|
|
|
presigned transactions.
|
|
|
|
|
presigned [.keep-together]#transactions.#
|
|
|
|
|
|
|
|
|
|
If you implement a protocol that uses presigned transactions, ensure
|
|
|
|
|
that it doesn't use any features that are reserved for future upgrades.
|
|
|
|
|