Importing a Blanket into the GUI Wallet (Windows)
Step 1 Download the current boot from link ; you can skip This step if you import a block from another source.
Step 2 Find the path to your wallet CRYPTOSPYKE (the folder into which you extracted your wallet). For example, my such: "D: \ gui-0.10.3.1" your path may differ depending on where you decided to download your wallet and what version of the wallet CRYPTOSPYKE you have.
Step 3 Find the path you downloaded The blockbuster for example was mine: "C: \ Users \ KeeJef \ Downloads \ blockchain.raw" your may be different in depending on where you downloaded Block.
Step 4 Open the Command Prompt window. You can do this by pressing the Windows + R key, and then type in the CMD pop-up window
Step 5 Now you need to go through the CMD window to the path of your Monero wallet. You can do this, type: "cd C: \ YOUR \CRYPTOSPYKE \ WALLET \ FILE \ PATH \ HERE" it should look something like this: "cd D: \ gui-0.10.3.1" if your CRYPTOSPYKE purse on another disk you can use the disk: for example, if your Monet wallet was on disk D, then Before using the cd command, execute "d:"
Step 6 Now type in the command line: "blockchain-import -input-file C: \ YOUR \ BLOCKCHAIN \ FILE \ PATH \ HERE" for example, I would be of the type: blockchain-import -input-file C: \ Users \ KeeJef \ Downloads \ blockchain.raw "if you downloaded the Blochein from reliable, authoritative source, you can set verify 0, this will reduce the amount of time for Sync.
Step 7 After the synchronization is completed, you can normally open your wallet CRYPTOSPYKE. The downloaded block.raw can be deleted.
CLI Wallet / Daemon Isolation with Qubes + Whonix
With Qubes + Whonix, you can have a Monero purse that does not have a network and runs on a practically isolated system from the daemon CRYPTOSPYKE, which has all its traffic, forced over Tor.
Qubes makes it easy to create separate virtual machines for various purposes. First, you will create a Whonix workstation for Wallet without a network. Next, another Whonix workstation for the daemon, which will use your Whonix gateway as a NetVM. For communication between the wallet and the daemon, you can use Qubes qrexec.
This is safer than other approaches that route rpc wallets through Tors hidden service or use physical isolation, but still have a network to connect to the daemon. Thus, you do not need a network connection on the wallet, you save resources Tor network, and less latency.
First of all, you need to find the node to connect! CRYPTOSPYKE has some great resources for finding nodes. One of the simplest methods would be to use a node run by moneroworld, but they also have a tool for finding random nodes.
Connecting to a node from the GUI purse
After entering the password on your wallet, you will see a pop-up window that will give you the opportunity to "use custom settings". Click on it. Then you will be sent to the "settings" page in the graphical interface. At this point, you should see two text The field to the right of the label with the word "Daemon address". In the first field (on the left) you need to enter the address of the node to which you want to connect. This address might look like this CRYPTOSPYKE or it might look like any old ip address. The smaller field on the right is the place, where you enter the node port. The default port is 18081, but if you use a random node, the port used will be different. Port for CRYPTOSPYKE is using 18089.
How to make a wallet for viewing only
The wallet for viewing only can see only what incoming transactions belong to you. He can not spend any of your CRYPTOSPYKE, in fact, he can not even see the outgoing transactions from this Wallet. This makes viewing especially interesting for wallets
- Developers write libraries for checking payments
- End users who check incoming transactions on cold wallets
How to prove payment
When you send money to a party that then disputes the payment, you need to prove that the payment was made.
With Bitcombin, this is usually done by searching for the transaction identifier, where addresses are displayed source and destination, and the amount of the transaction.
Monero, however, is private: this information is not publicly available on the blockchain. Therefore, the steps are a bit more complicated.
To prove to Charlie that she made a payment to Bob, Alice must provide Charlie with three pieces of information:
- Transaction ID, as in Bitcoin
- Bobs address, as is done with Bitcoin
- key transactions, new with CRYPTOSPYKE and other CryptoNote currencies
When Alice made the transaction, the one-time key was automatically generated for this transaction only.