<p>If I have a segwit UTXO  with for example 10 BTC , can I make some raw transactions ready to get broadcasted?</p>

CC BY-SA 4.0
2020-12-24T16:46:23.797Z
What is the question?
Claris
CC BY-SA 4.0
2020-12-24T18:14:35.947Z
@Pseudonymous can I make some raw transactions ready to get broadcasted? for example if I don't want to reveal my private key ,  can I sign some raw transactions and broadcast them in the future?
Newdude
CC BY-SA 4.0
2020-12-24T18:15:57.557Z
Yes. There is no restriction on broadcasting a transaction hours, days or even years after they are signed. You can add a lock time to prevent them from being valid until a certain time if you choose.
Claris
CC BY-SA 4.0
2020-12-24T19:07:02.070Z
@Pseudonymous What if I don't use a segwit UTXO?
Newdude
CC BY-SA 4.0
2020-12-24T19:08:00.307Z
Really has nothing to do with segwit either way.
Claris
CC BY-SA 4.0
2020-12-25T11:31:52.710Z
@Pseudonymus If the utxo and receiver are same is the transaction hash the same?
Newdude
CC BY-SA 4.0
2020-12-25T11:33:16.343Z
I mean the signed transaction not the transaction hash
Newdude
<bitcoind><utxo>
Signing transaction for later use
Newdude
# Signing transaction for later use

(Asked by: username_0 on 2020-12-24)

If I have a segwit UTXO with for example 10 BTC , can I make some raw transactions ready to get broadcasted?

**Tags:** bitcoind, utxo

> **Comments:**
> **username_1**: What is the question?  
> **username_0**: @Pseudonymous can I make some raw transactions ready to get broadcasted? for example if I don't want to reveal my private key ,  can I sign some raw transactions and broadcast them in the future?  
> **username_1**: Yes. There is no restriction on broadcasting a transaction hours, days or even years after they are signed. You can add a lock time to prevent them from being valid until a certain time if you choose.  
> **username_0**: @Pseudonymous What if I don't use a segwit UTXO?  
> **username_1**: Really has nothing to do with segwit either way.  
> **username_0**: @Pseudonymus If the utxo and receiver are same is the transaction hash the same?  
> **username_0**: I mean the signed transaction not the transaction hash  

---

## 0 answers

