Pre-signed transactions of Bitcoin, this gameplay is said to originate from Merlin 🧙
Pre-signed transactions lock assets by signing a transaction in advance that meets specific conditions, while allowing for flexible operations afterward. Pre-signed transactions can set conditions through Bitcoin's scripting language, such as time locks (CLTV or CSV) or multi-signatures (Multi-Sig), ensuring that the transaction cannot be executed before the conditions are met.
Technical implementation steps
The large holder generates a transaction to transfer specified UTXO to a new address (usually a script address controlled by the staking protocol).
Set condition limits, such as:
The transaction can only take effect in the next life.
The transaction requires the signatures of both the protocol and the large holder.
Other logical conditions:
The chicken finishes eating rice, the dog licks the noodles, the fire burns the lock.
(If specific events are needed to trigger)
Then sign the transaction, generating a valid but unbroadcasted transaction data (Raw Transaction). This signature proves the user's control over the funds, but the location of BTC will not change until the transaction is broadcasted.
The user submits the signed transaction data to the protocol. The protocol verifies:
Whether the signature is valid.
Whether the transaction meets the agreed conditions (the chicken finishes eating rice, the dog licks the noodles, the fire burns the lock).
After verification, the high-end staking protocol can record this pre-signed transaction as proof of stake.