mirror of
https://github.com/bisq-network/bisq.git
synced 2025-02-22 22:45:21 +01:00
Merge pull request #1902 from aejontargaryen/update-altcoin-account-popups
Update altcoin accounts info popups
This commit is contained in:
commit
c2cb0e2965
2 changed files with 33 additions and 7 deletions
|
@ -987,11 +987,14 @@ not a {2} specialist and cannot help in such cases.
|
|||
account.altcoin.popup.wallet.confirm=I understand and confirm that I know which wallet I need to use.
|
||||
account.altcoin.popup.xmr.msg=If you want to trade XMR on Bisq please be sure you understand and fulfill \
|
||||
the following requirements:\n\n\
|
||||
For sending XMR you need to use either the official Monero GUI wallet or the Monero simple wallet with the \
|
||||
store-tx-info flag enabled (default in new versions).\n\
|
||||
Please be sure that you can access the tx key (use the get_tx_key command in simplewallet) as that \
|
||||
would be required in case of a dispute to enable the arbitrator to verify the XMR transfer with \
|
||||
the XMR checktx tool (http://xmr.llcoins.net/checktx.html).\n\
|
||||
For sending XMR you need to use either the official Monero GUI wallet or Monero CLI wallet with the \
|
||||
store-tx-info flag enabled (default in new versions). Please be sure you can access the tx key as \
|
||||
that would be required in case of a dispute.\n\
|
||||
monero-wallet-cli (use the command get_tx_key)\n\
|
||||
monero-wallet-gui (go to history tab and click on the (P) button for payment proof)\n\n\
|
||||
In addition to XMR checktx tool (https://xmr.llcoins.net/checktx.html) verification can also be accomplished in-wallet.\n\
|
||||
monero-wallet-cli : using command (check_tx_key).\n\
|
||||
monero-wallet-gui : on the Advanced > Prove/Check page.\n\
|
||||
At normal block explorers the transfer is not verifiable.\n\n\
|
||||
You need to provide the arbitrator the following data in case of a dispute:\n\
|
||||
- The tx private key\n\
|
||||
|
@ -1000,8 +1003,9 @@ You need to provide the arbitrator the following data in case of a dispute:\n\
|
|||
If you cannot provide the above data or if you used an incompatible wallet it would result in losing the \
|
||||
dispute case. The XMR sender is responsible to be able to verify the XMR transfer to the \
|
||||
arbitrator in case of a dispute.\n\n\
|
||||
There is no payment ID required, just the normal public address.\n\n\
|
||||
If you are not sure about that process visit the Monero forum (https://forum.getmonero.org) to find more information.
|
||||
There is no payment ID required, just the normal public address.\n\
|
||||
If you are not sure about that process visit (https://www.getmonero.org/resources/user-guides/prove-payment.html) \
|
||||
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\
|
||||
|
@ -1021,6 +1025,23 @@ Because Conceal is a privacy coin, block explorers cannot verify transfers.\n\n\
|
|||
If you cannot provide the required data to the arbitrator, you will lose the dispute case.\n\
|
||||
If you do not save the transaction secret key immediately after transferring CCX, it cannot be recovered later.\n\
|
||||
If you do not understand these requirements, seek help at the Conceal discord (http://discord.conceal.network).
|
||||
account.altcoin.popup.drgl.msg=Trading Dragonglass on Bisq requires that you understand and fulfill \
|
||||
the following requirements:\n\n\
|
||||
Because of the privacy Dragonglass provides a transaction is not verifyable on the public blockchain. If required you \
|
||||
can prove your payment thru use of your TXN-Private-Key.\n\
|
||||
The TXN-Private Key is a one-time key automatically generated for every transaction that can \
|
||||
only be accessed from within your DRGL wallet.\n\
|
||||
Either by DRGL-wallet GUI (inside transaction details dialog) or by the Dragonglass CLI simplewallet (using command "get_tx_key").\n\n\
|
||||
DRGL version 'Oathkeeper' and higher are REQUIRED for both.\n\n\
|
||||
In case of a dispute, you must provide the arbitrator the following data:\n\
|
||||
- The TXN-Private key\n\
|
||||
- The transaction hash\n\
|
||||
- The recipient's public address\n\n\
|
||||
Verification of payment can be made using the above data as inputs at \ (http://drgl.info/#check_txn).\n\n\
|
||||
If you cannot provide the above data or if you used an incompatible wallet it would result in losing the \
|
||||
dispute case. The Dragonglass sender is responsible to be able to verify the DRGL transfer to the \
|
||||
arbitrator in case of a dispute. Use of PaymentID is not required.\n\n\
|
||||
If you are unsure about any part of this process, visit Dragonglass on Discord (http://discord.drgl.info) for help.
|
||||
account.altcoin.popup.ZEC.msg=When using {0} you can only use the transparent addresses (starting with t) not \
|
||||
the z-addresses (private), because the arbitrator would not be able to verify the transaction with z-addresses.
|
||||
account.altcoin.popup.XZC.msg=When using {0} you can only use the transparent (traceable) addresses not \
|
||||
|
|
|
@ -165,6 +165,11 @@ public class AltCoinAccountsView extends ActivatableViewAndModel<GridPane, AltCo
|
|||
.useIUnderstandButton()
|
||||
.show();
|
||||
break;
|
||||
case "DRGL":
|
||||
new Popup<>().information(Res.get("account.altcoin.popup.drgl.msg"))
|
||||
.useIUnderstandButton()
|
||||
.show();
|
||||
break;
|
||||
case "ZEC":
|
||||
new Popup<>().information(Res.get("account.altcoin.popup.ZEC.msg", "ZEC"))
|
||||
.useIUnderstandButton()
|
||||
|
|
Loading…
Add table
Reference in a new issue