Difference between revisions of "Trading Monero"
Plebeian9000 (talk | contribs) (add details on proving and verifying from payment account pop-up) |
Plebeian9000 (talk | contribs) (update auto-confirm section with details on the process for users) |
||
Line 41: | Line 41: | ||
* the XMR seller provides a valid transaction key or viewkey | * the XMR seller provides a valid transaction key or viewkey | ||
* the XMR buyer has auto-confirming trades turned on in Bisq settings | * the XMR buyer has auto-confirming trades turned on in Bisq settings | ||
+ | |||
+ | == How it works == | ||
+ | |||
+ | === XMR Seller === | ||
+ | |||
+ | The XMR seller will get a pop-up upon clicking <code>Payment Sent</code> asking for the XMR tx ID and XMR tx key. | ||
+ | |||
+ | [[File:Autoconfirm-xmrseller-input.png|600px|thumb|left|The XMR seller can choose to enter this information, or not.]] | ||
+ | |||
+ | <div style="clear: both;"></div> | ||
+ | |||
+ | The trader can choose to enter this information, or not. '''It is not mandatory'''. If the trader chooses not to, they'll be informed that their trading peer will not be able to use auto-confirm. | ||
+ | |||
+ | === XMR Buyer === | ||
+ | |||
+ | The XMR buyer must have auto-confirm turned on in Bisq settings. | ||
+ | |||
+ | [[File:Auto-confirm-status.png|500px|thumb|left|Auto-confirm status on the trade screen. In this particular instance, the XMR seller didn't specify the information needed for auto-confirm to work.]] | ||
+ | |||
+ | <div style="clear: both;"></div> | ||
+ | |||
+ | Explorer nodes are queried every 90 seconds for 12 hours. If 12 hours pass without success, auto-confirm fails for the trade. If Bisq receives just 1 failure of any kind (related to transaction, network issues, etc), auto-confirm is considered failed. '''This does not mean the XMR transaction was invalid.''' It just means the user should check the transaction manually. | ||
+ | |||
+ | The user can mark the transaction as received any time by clicking <code>Confirm Payment Receipt</code> themselves, and auto-confirm will stop running for that trade and the trade will be completed normally. | ||
+ | |||
+ | == Settings == | ||
+ | |||
+ | On the Bisq settings screen, you can set: | ||
+ | * Maximum amount of BTC that can be confirmed per trade (default: 1 BTC) | ||
+ | * XMR explorer node address (default: nodes run by Bisq contributors; see [[#Set_up_your_own_node|below]] for how to run your own) | ||
+ | * Number of required confirmations (default: 5) | ||
+ | ** Minimum value is equal to the number of explorer nodes defined | ||
+ | |||
+ | Please note the following: | ||
+ | * Any change to the required number of confirmations setting takes effect immediately. '''All other settings require a restart to take effect'''. | ||
+ | * Disabling auto-confirm altogether will take effect immediately too. Re-enabling the feature will only take effect after a restart. | ||
+ | |||
+ | [[File:Screenshot from 2020-09-03 12-41-19-touched.png|600px|thumb|left]] | ||
+ | |||
+ | <div style="clear: both;"></div> | ||
== XMR explorer nodes == | == XMR explorer nodes == | ||
− | By default, the Bisq auto-confirm feature relies on 2 XMR explorer nodes run by Bisq contributors. | + | By default, the Bisq auto-confirm feature relies on 2 XMR explorer nodes run by Bisq contributors. Below we outline how to run your own Monero explorer node. |
=== Set up your own node === | === Set up your own node === | ||
Line 54: | Line 94: | ||
# Once the Monero blockchain is synced, run the explorer with <code>xmrblocks --enable-json-api</code>. | # Once the Monero blockchain is synced, run the explorer with <code>xmrblocks --enable-json-api</code>. | ||
# Specify your explorer's address on the Bisq settings screen. | # Specify your explorer's address on the Bisq settings screen. | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− |
Revision as of 17:33, 3 September 2020
Monero (XMR) is one of the most active markets on Bisq. This article covers some things you should know when trading it.
Contents
Instant payment accounts
By default, all altcoins trades on Bisq have trade periods of 1 day. But you can set up an Altcoins Instant account on Bisq for 1-hour trade periods.
Proving payments
Some details of XMR transactions are not publicly available on the blockchain. In order for a mediator or arbitrator to handle disputes, the XMR seller must make sure they send XMR using a wallet that provides the following 3 items to prove the payment was made:
- transaction key (Tx Key, Tx Secret Key, or Tx Private Key)
- transaction ID (Tx ID or Tx Hash)
- recipient's address
This information can be found in the following wallets: official Monero GUI and CLI wallets, MyMonero, Exodus (desktop), Cake Wallet, and Monerujo (mobile):
- Monero GUI: on the Transactions tab.
- Monero CLI: use the command
get_tx_key <TXID>
. The flagstore-tx-info
must be enabled (it's enabled by default in new versions). - Other wallets: go to transaction history and look for transaction key (sometimes called "tx key" or "secret key") and destination address in a sent transaction. For Cake Wallet, the "Save recipient address" option must be enabled in settings.
If you are using another wallet not mentioned above, be sure you can still access the 3 items mentioned above.
Since transaction keys and destination addresses are stored in Monero wallet software and not available anywhere else, be careful not to delete or restore your Monero wallet before a Bisq trade is complete.
Failure to provide the required transaction data will result in losing disputes.
Verifying payments
To verify that a certain sum of Monero was sent to a specific address:
- Monero GUI: change wallet to Advanced mode and go to
Advanced
>Prove/check
>Check Transaction
- Monero CLI: use the command
check_tx_key <TXID> <TXKEY ADDRESS>
- XMR Check Transaction tool
- Explore Monero website
If you still have questions, see this guide on the Monero home page or ask a question on the Monero support subreddit.
Auto-confirming trades
Auto-confirming trades verify receipt of XMR payment automatically. Typically, XMR buyers must check their wallet and manually mark a payment as received in Bisq. Auto-confirming trades do this automatically, making trades quicker and more efficient for both traders.
This feature is currently available for XMR trades where:
- the XMR seller provides a valid transaction key or viewkey
- the XMR buyer has auto-confirming trades turned on in Bisq settings
How it works
XMR Seller
The XMR seller will get a pop-up upon clicking Payment Sent
asking for the XMR tx ID and XMR tx key.
The trader can choose to enter this information, or not. It is not mandatory. If the trader chooses not to, they'll be informed that their trading peer will not be able to use auto-confirm.
XMR Buyer
The XMR buyer must have auto-confirm turned on in Bisq settings.
Explorer nodes are queried every 90 seconds for 12 hours. If 12 hours pass without success, auto-confirm fails for the trade. If Bisq receives just 1 failure of any kind (related to transaction, network issues, etc), auto-confirm is considered failed. This does not mean the XMR transaction was invalid. It just means the user should check the transaction manually.
The user can mark the transaction as received any time by clicking Confirm Payment Receipt
themselves, and auto-confirm will stop running for that trade and the trade will be completed normally.
Settings
On the Bisq settings screen, you can set:
- Maximum amount of BTC that can be confirmed per trade (default: 1 BTC)
- XMR explorer node address (default: nodes run by Bisq contributors; see below for how to run your own)
- Number of required confirmations (default: 5)
- Minimum value is equal to the number of explorer nodes defined
Please note the following:
- Any change to the required number of confirmations setting takes effect immediately. All other settings require a restart to take effect.
- Disabling auto-confirm altogether will take effect immediately too. Re-enabling the feature will only take effect after a restart.
XMR explorer nodes
By default, the Bisq auto-confirm feature relies on 2 XMR explorer nodes run by Bisq contributors. Below we outline how to run your own Monero explorer node.
Set up your own node
For maximum privacy and security, users are recommended to run their own XMR explorer node for verifying receipt of funds.
- Build Monero from source. Check out this guide for further guidance. If on a Debian-based distro, Ubuntu (18.04 in particular) tends to work better than plain Debian.
- Build the Monero explorer from source.
- Run
monerod
. - Once the Monero blockchain is synced, run the explorer with
xmrblocks --enable-json-api
. - Specify your explorer's address on the Bisq settings screen.