This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
trade_portal_coin_recovery [12/05/2021 08:13] – old revision restored (2021/11/21 06:57) gfactor | trade_portal_coin_recovery [10/06/2022 14:50] (current) – [LTC, DOGE, DGB, or RVN Recovery] caldescent | ||
---|---|---|---|
Line 3: | Line 3: | ||
{{: | {{: | ||
- | ===== QORT Recovery ===== | + | ===== LTC, ARRR, DOGE, DGB, or RVN Recovery ===== |
- | This only relates to QORT refunds on the seller side, on the rare occasion that a trade fails half way through. LTC/DOGE refunds on the buyer side are unaffected. | + | If you are buying |
- | The AT becomes eligible | + | If for some reason you have not received the LTC / ARRR / DOGE / DGB / RVN refund (or the purchased QORT) after 2 hours, you can call the refundAll API to retry any failed refunds. |
- | Since 2.1 (sleeping ATs) you need to issue a cancel request to trigger | + | For this, you will need your node's API key, which can be found in the apikey.txt file in the folder |
- | We thought there was a button in the UI, but after checking the code it looks like the UI hides it in this state. We’ll see about modifying that in the next version. | + | [[http:// |
- | This new requirement to cancel was an unintended consequence of sleeping ATs - essentially a bug. So it may take a little while to smooth things | + | Under "POST / |
- | An alternate option | + | `true` will be returned if anything was able to be refunded. `false` will be returned if there is nothing |
- | - Find the trade' | + | As an alternative |
- | - In the UI, go to ‘Send Coin’ | + | |
- | - Select QORT | + | |
- | - In the amount, enter `0.00000001` | + | |
- | - In the ‘To’ field, paste the `atAddress` value that you copied | + | |
- | - Click ‘Send’ | + | |
- | If the AT has reached its refund timeout (the exact time is still being determined) then it should then enter REFUNDING mode. CalDescent is going to try and keep an eye on failed trades on the network and will take care of this process on behalf of users, so most shouldn't need to worry about this. | + | ''curl -X POST " |
- | ===== LTC/DOGE Recovery ===== | + | Either method is fine and they both achieve the same result. |
- | There is currently a bug in the core that can cause it to go into the BOB_REFUNDED state even though the coins have sold. Generally calling the < | ||
- | You should be able to run this command directly in a terminal window. It has to be on the same machine that you originally listed | + | If refundAll returned `false`, you may need to import your archived trades and try again. To do this, you can use the API documentation again: http:// |
- | < | + | Under " |
- | + | ||
- | Alternatively, | + | |
- | + | ||
- | [[http:// | + | |
- | + | ||
- | Either method is fine and they both achieve the same result. | + | |
- | If you have replaced the db folder since originally listing the QORT, there are a couple of possible options | + | The command line alternative |
- | 1. If you still have a copy of the old db folder, just stop the core, then rename the current one to something else like “db_new”, | + | '' |
- | 2. If you don't have the old db folder, search your system for both “TradeBotStates.script” and “TradeBotStates.json”. These would normally be found in your qortal directory, or in the “qortal-backup” subfolder. You would then need to import | + | Once archived trades are imported, |