[alexg]

Thank you for reporting this error. I see it as well, it’s a bug introduced in the latest release.

I will release a patch ASAP and notify you again here.

with regards

[alexg]

OK thanks for checking.

I am really not sure why this happens. As mentioned before, if the time to retain is 0 and the correct passphrase is entered afterwards, it is saved as a WordPress option, so that the plugin can unlock the wallet at any time.

To find the option name, go to the coin adapter’s settings and inspect the wallet passphrase input box. The id and name of the field is the name of the option where the passphrase is saved. For example, for the built-in Bitcoin adapter, the option name is wallets-bitcoin-core-node-settings-rpc-passphrase.

I wonder if something deletes this option in your system. Can you check? Ideally, attempt to check the option value once after first entering the passphrase, and once more after the wallet is locked.

To check via the MySQL console:

SELECT option_name,option_value FROM wp_options WHERE option_name LIKE 'wallets-%-settings-rpc-passphrase';

To check with wp-cli from the linux command line:

wp option get wallets-bitcoin-core-node-settings-rpc-passphrase (substitute with your actual option name)

Apologies for the confusion, but I don’t see any other way to debug this. I am not able to reproduce the problem on my end.

Please let me know if you need any help with inspecting the passphrase option, and also let me know what you find.

with regards

[alexg]

Hello,

This feature has been added to version 4.3.5. Please see “Wallets” -> “Notifications” -> “Notification settings for ALL events” -> “Forward ALL notifications to admins”.

with regards

[alexg]

Hello,

You can see some example code on how to provide an exchange rate to the plugin, here: https://gist.github.com/alex-georgiou/492196184f206002c864225180ca8fbb

Copy this file into your wp-content/plugins directory, and edit the part where the value is set. You might need to use php curl (requires the module to be installed) or file_get_contents (requires allow_url_fopen), or better yet, use wp_remote_get().

Then, activate the plugin from your plugins list in WordPress admin.

You can then go to “Wallets” -> “Exchange Rates” and hit the “Clear/Refresh data now!” button.

If all works correctly, the value should appear in “Wallets” -> “Exchange Rates” -> “Exchange rates debug views” -> “Exchange rates”.

Let me know if you get stuck or need help with anything.

with regards

[alexg]

Hello,

Please check the setting “Wallets” -> “Cron job” -> “Withdrawal locks” -> “Time to retain secret”. If you want the passphrase to be retained indefinitely, you should keep the value at 0.

When the value is 0, the passphrase is saved into a WordPress option, while if the value is not 0, the passphrase is simply used to unlock the wallet once for the duration specified, but is not saved: https://github.com/dashed-slug/wallets/blob/4.3.4/includes/coin-adapter-rpc.php#L602-L623

If the time to retain secret is 0, the wallet is unlocked every time a withdrawal is attempted. https://github.com/dashed-slug/wallets/blob/4.3.4/includes/coin-adapter-rpc.php#L510-L551

There is nothing else that you are missing. If you have set the time to retain secret to 0, and if afterwards you have set the correct passphrase, then that’s all you need to do.

Please let me know if you have done this. I am currently double-checking if the passphrase gets deleted on my end, but this will take 24 hours for me too.

with regards

[alexg]

Ah, OK. Now I understand.

The setting you are tweaking is for coins – and it affects UIs for the parent plugin, Bitcoin and Altcoin Wallets.

What you actually want to do is affect the default market, within the context of the exchange extension.

Right now it’s not possible to affect the ordering of markets, but it is possible to select one market that is pre-selected when the page loads:

Go to “Wallets” -> “Exchange” -> “Markets” and use the radio button under the “Site-wide default” column, to select the default market.

Hope this helps.

with regards

[alexg]

Actually, the whole point of cryptocurrencies is to run your own node. The situation you describe with KYC/AML is simply due to the fact that most people are too lazy to run their own node (yes, it takes some effort, but without it, all you have is the same banking system as before). My intention with this plugin was to be able to connect to your own wallet, the CoinPayments platform was an afterthought, because many people asked for more convenience. If you introduce centralized components into crypto you have something that is much worse than the banking sector (the worst of both worlds). The good news is that these legal hurdles might be exactly what’s required to push people to care about being independent and to actually set up their own nodes.

Personally I would not trust Dash as much as Monero if I wanted to stay anonymous. If you want strong anonymity, I believe right now Monero is the way to go. Yes you pay a premium for strong anonymity, but the fees will be addressed in Monero layer 2.

Personally I see Dash and most coins being overhyped, and only Bitcoin and Monero really have something to offer right now out of all the coins out there. It remains to be seen if Ethereum is useful, depending on whether someone comes up with a real use case for smart contracts, and there are strong arguments against their usefulness as a whole (the whole debate with decentralization vs oracles, identity, etc).

Right now we’re waiting to see if new technologies like Schnorr signatures can be added to Bitcoin layer 1 to provide strong anonymity, because you cannot do anonymity in layer 2 effectively. Monero has strong anonymity in layer 1, and it can now add scaling in layer 2. This is why I find it so promising. Dash on the other hand has been overhyped and some do not even consider it a privacy coin at all. It definitely has much less privacy than Monero and other Cryptonote forks.

Best of luck if you decide to set up a node.

[alexg]

Hello,

I am not sure I understand. The default coin selection should not change the ordering of the coins. Additionally, this setting does not make sense if you are not logged in, since you should not be seeing the frontend shortcodes anyway. The default coin selection simply chooses the default coin if you are logged in.

What did you expect to see instead?

[alexg]

I was able to pass the verification process with my Greek national ID. The first time I got rejected because I used a black and white copy, they need a color copy. Other than that, the process was relatively easy.

Next I would like to put some more work into the Monero coin adapter, because personally I am not too optimistic about strong anonymity being introduced into Bitcoin layer 1. Let’s hope I’m wrong.

[alexg]

@davej Thank you, I also want to solve this issue very badly, as it has been first reported so long ago.

Usually even shared hosting does give you some limited DB access, but OK.

Since it’s not easy to look at the database tables, here’s one more thing that might help me understand the problem:

Go to https://www.example.com/?__wallets_exchange_action=get_user_orders&__wallets_exchange_open=1 (replace example.com with your actual domain).

What do you see? Please copy the output here or email it. Thank you for your help.

[alexg]

@davej Hello,

I have been trying to reproduce this issue again but without success. If you like, there’s two things you could do, either one would help me reproduce the problem and thus solve it.

1. Can you locate the SQL console? If you have access to phpMyAdmin then you can find the SQL console there. Alternatively, your host can help you locate it. Please try the following query.

SELECT * FROM wp_wallets_orders WHERE ( amount - filled ) < 0.00001 and status='open';

You might have to replace wp_ in the query with your actual DB prefix. The DB prefix is shown in the dashboard section under “Bitcoin and Altcoin Wallets”.

2. If you cannot execute the query, could you please describe the exact steps that produced the problem? I might be able to recreate the problem by following the actions you performed.

Let me know please. Thank you.

with regards

[alexg]

Hello,

Yes, you can copy the entire views directory somewhere else on your server (as long as the webserver has access). Then, provide the full path to that directory to the wallets_views_dir filter. Please see the documentation under “Frontend” -> “Alternative knockout templates” to see a full example of how to hook to the filter. Alternatively, you can use the views_dir shortcode attribute. This is also explained in the manual.

with regards

[alexg]

Hello,

You could delete all the transactions from the DB that involve LTC, but you do not really have to do this.

What you do need to do, is refresh the deposit addresses, and transfer the funds from CP to the new full node wallet.

Please see the FAQ under “I want to replace an adapter with another one.”

Then, send your LTC to a new address from the new wallet. Use an address that is not associated with any plugin users. Once you transfer the funds, the users will be able to withdraw their LTC from the new wallet, or deposit LTC to the new wallet.

If you absolutely insist on deleting all user balances, you can delete the LTC transactions:

DELETE FROM wp_wallets_txs WHERE symbol = 'LTC';

Don’t forget to backup your DB before you go deleting things 🙂

EDIT: I see now that the old balances are Litecoin testnet. You can delete these, but Litecoin testnet on CP has the symbol LTCT, not LTC so there is no chance of these being confused in the plugin.

[alexg]

Hello and thanks,

I have already received such a request a few days ago and have implemented a solution for this.

It will be out once I have a few more changes accumulated for the plugin.

I will notify you again here when I push out a new patch release with this change.

with regards

[alexg]

@davej Hello again,

The errors you see are because you tried to enter SQL queries into the command shell, rather than the DB console.

Nevermind, I will try to recreate the issue on my end and will get back to you.

with regards

[Author]

Posts