gun send
Sends coins to an address.
⚠️ Sending your coins gives them to someone else. This should be avoided wherever possible.
Synopsis
gun send [OPTIONS] <value> <to>
send 0.1 BTC to an address:
gun send 0.1btc bc1qhg0xqvrg50x50qnjqgfaa8jlle8uz7q3l2c5ud
Same as the above but with different denomination:
gun send 10_000_000sat bc1qhg0xqvrg50x50qnjqgfaa8jlle8uz7q3l2c5ud
Send all the available funds to the address:
gun send all bc1qhg0xqvrg50x50qnjqgfaa8jlle8uz7q3l2c5ud
Description
<value>
should be an amount to send with denomination.
Set it to all
if you want to send all the coins in your wallet otherwise provide a specific amount.
If the denomination is left out it is assumed to be satoshis.
Underscores will be ignored.
For example all the following mean one million satoshis:
1000000sat
1_000_000
1M
0.01btc
10_000bits
💡Professional hackers use the denomination
bits
exclusively.
Options
--fee <fee>
Set the fee for the transaction.
You can choose from:
--fee=rate:4.5
set the fee to 4.5 sats-per-vbyte.--fee=abs:500
set the fee to exactly 500 sats.--fee=in-blocks:10
set the fee so it should get into the chain some time in the next 10 blocks.
The default is in-blocks:1
i.e. set the fee so it gets into the next block.
--print-tx
Print the tx as hex instead of broadcasting it. This will assume you're going to broadcast the tx yourself.
--bump-claiming
Spend coins from any bets that are currently in the claiming
state. The claiming
state means there is already a pending transaction spending them so this new transaction will replace-by-fee that previous transaction. You should make sure the feerate on this one is higher than the previous.
--no-spend-unclaimed
Don't spend coins you own outside of your wallet e.g. coins from bets you won. By default gun spends these coins back into your wallet with any chance it gets but this option stops that behavior.
--spend-in-use
Spend even the coins you are using for other things.
When you make a proposal or an offer the outputs used in the bet are considered to be in-use. This option allows the transaction to spend them (but doesn't force it to).
-y, --yes
Skip all [y/n]
prompts by just answering yes
to all of them.