balance/ folder created by balio
or balance.zip / payment.zip file
generated by WebUI - you move it from online PC to wallet machine.| If you have no client: use balio tool | If you have a running client: use WebUI | ||||
|
There is a tool balio that can fetch a balance of your wallet from a public block explorers. Run the tool from a command line with the file name of your wallet as the command line parameter (e.g. balio wallet.txt).Eventually enter the list of space separated BTC addresses that you want to fetch the balance for ( balio 1Hz96kJKF2HLPGY15JWLB5m9qGNxvt8tHJ 3NEDeMiXubepj68RGCTXJyJc83cYXMpusw).
This should create the balance/ folder in the current directory, ready to be moved your wallet machine.Note: fetching the balance this way exposes your privacy. To use balio through Tor, set TOR environment variable in your system, pointing it to your tor's socks proxy (e.g. TOR=localhost:9050).Additionally, despite of using Tor, to further protect your privacy try to fetch balance of single addresses instead of entire wallets. |
From the moment a content of wallet.txt file is properly stored in your browser, you can check and export your balance.
Do it on the Wallet tab.To spend your coins, you can choose one of the two ways here. It is recommended to use MakeTx page that allows you to assemble a transaction using a convenient, interactive way.
|
balance/ folder, from online PC to wallet machine.wallet command only on offline machine - one that never was nor will be connected to Internet. wallet -send 1JbdKe4eBwtexisGTbCKY5v5CfphtdZXJs=0.01-fee) allows you to control the transaction's' fee.wallet -h
-send ... command,
it will create a text file with a signed transaction.
The file is named like 01234567.txt - this is the file you need to move
to your online node in order to notify the network about your payment.
Before you broadcast your signed transaction to the network,
verify carefully that it does exactly what you intended.
| Wallet | WebUI (requires client) |
To see a decoded content of a transaction, execute: wallet -d rawtxdata.txt
|
Use PushTx button or Upload Transaction File form. After you upload the transaction, you should see it decoded. |
| WebUI (requires client) | TextUI (requires client) | Web services |
| Load the transaction using the client's WebUI. Click on the envelope icon with a green arrow to broadcast a loaded transaction to the network. Coming back to Transactions tab later, press the button in the "Own TXs" row, to see all the transactions you've loaded (those with a red background are yours). You can also unload a previously loaded transaction by clicking on the red X icon. |
Use stx command with the transaction ID as its parameter (you had the ID printed, when loading it).
|
Use any web page that allows you to push a raw transaction to the bitcoin network. For instance: • https://mempool.space/tx/push • https://blockstream.info/tx/push • https://coinb.in/send-raw-transaction.html • More at https://en.bitcoin.it/wiki/Transaction_broadcasting Just copy the text from the transaction file, paste it into the form and push the button. Note: being concerned about exposing your IP, you may want to access the web page via Tor. |
| Re-broadcasting transactions | ||
|
The client never broadcasts transactions unrequested, so if your transaction does not appear in the chain soon enough, you may want to re-broadcast it, using the same method as for the initial broadcasting. There may of course be other reasons why your transaction does not get confirmed (usually because the fee was too low), in which case re-broadcasting it will not help you much. There is also a TextUI command stxa that re-broadcasts all the transaction that have been loaded, but not yet confirmed by the network. Note that when a transaction gets mined into a block it gets removed from the list automatically.
| ||