mirrors/bisq
1
0
Fork 0
mirror of https://github.com/bisq-network/bisq.git synced 2025-02-24 15:10:44 +01:00
Code Issues Projects Releases Packages Wiki Activity

Merge pull request #1995 from blur-network/list-blur-asset

Browse source 
Blur: Add instructions for GUI Wallet in pop-up
This commit is contained in:
Manfred Karrer 2018-11-29 15:05:08 +01:00 • committed by GitHub
commit ba38fcc24d
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 13 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

21
core/src/main/resources/i18n/displayStrings.properties
View file

@ -1008,14 +1008,19 @@ If you are not sure about that process visit (https://www.getmonero.org/resource
or the Monero forum (https://forum.getmonero.org) to find more information.
account.altcoin.popup.blur.msg=If you want to trade BLUR on Bisq please be sure you understand and fulfill \
the following requirements:\n\n\
To send BLUR you must use the Blur Network CLI wallet (blur-wallet-cli). After sending a transfer payment, the\n\
wallet displays a transaction hash (tx ID). You must save this information. You must also use the 'get_tx_key'\n\
command to retrieve the transaction private key. In the event that arbitration is necessary, you must present\n\
both the transaction ID and the transaction private key, along with the recipient's public address. The arbitrator\n\
will then verify the BLUR transfer using the Blur Transaction Viewer (https://blur.cash/#tx-viewer).\n\n\
If you cannot provide the required data to the arbitrator, you will lose the dispute case.\n\
The BLUR sender is responsible for the ability to verify BLUR transfers to the arbitrator in case of a dispute.\n\n\
If you do not understand these requirements, seek help at the Blur Network Discord (https://discord.gg/5rwkU2g).
To send BLUR you must use the Blur Network CLI or GUI Wallet. \n\n\
If you are using the CLI wallet, a transaction hash (tx ID) will be displayed after a transfer is sent. You must save \
this information. Immediately after sending the transfer, you must use the command 'get_tx_key' to retrieve the \
transaction private key. If you fail to perform this step, you may not be able to retrieve the key later. \n\n\
If you are using the Blur Network GUI Wallet, the transaction private key and transaction ID can be found conveniently \
in the "History" tab. Immediately after sending, locate the transaction of interest. Click the "?" symbol in the \
lower-right corner of the box containing the transaction. You must save this information. \n\n\
In the event that arbitration is necessary, you must present the following to an arbitrator: 1.) the transaction ID, \
2.) the transaction private key, and 3.) the recipient's address. The arbitrator will then verify the BLUR \
transfer using the Blur Transaction Viewer (https://blur.cash/#tx-viewer).\n\n\
If you cannot provide the required information to the arbitrator, you will lose the dispute. In all cases of dispute, the \
BLUR sender bears 100% of the burden of responsiblity in verifying transactions to an arbitrator. \n\n\
If you do not understand these requirements, do not trade on Bisq. First, seek help at the Blur Network Discord (https://discord.gg/dMWaqVW).
account.altcoin.popup.ccx.msg=If you want to trade CCX on Bisq please be sure you understand the following requirements:\n\n\
To send CCX you must use an official Conceal wallet, either CLI or GUI. After sending a transfer payment, the wallets\n\
display the transaction secret key. You must save it along with the transaction hash (ID) and the recipient's public\n\