[alexg]

Additionally, if you are using Bitcoin core v18.0.0, check these changes about rpcallowip and rpcbind:

https://bitcoin.org/en/release/v0.18.0#configuration-option-changes

If you are using the latest version, you might need to specify your WordPress host’s IP with rpcbind. Worth a try.

[alexg]

Hello,

Thank you for providing more information on this. I think I know what’s going on now.

You mentioned that the cron job is stalling, but the moment you shut down the wallet on your VPS, then the cron job finishes. This is a clear sign that the communication to the wallet is stalling and running into a timeout. I am guessing that the cron job is stalling for about 30 seconds, since this is usually the default PHP timeout value.

Please check again that you can connect to the wallet on your VPS from your WordPress machine. If you ran that PHP code you found on another machine, this is not helpful as a test. The wallet checks the incoming IP.

Remember, firewalls can be either on the VPS side, or on the side on the WordPress server. It would be best to talk to each of your hosts. Explain to them that you need TCP communication on the port you are using for the wallet RPC, outgoing from the WordPress server, and incoming to the VPS.

Additionally, check the rpcallowip setting in your wallet’s .conf file. https://en.bitcoin.it/wiki/Running_Bitcoin Check that you’re using correct CIDR notation to specify the netmask. See here: https://bitcoin.stackexchange.com/a/32268/8738

with regards

[alexg]

Hello,

Thank you very much for reporting this and for providing detailed information on the problem.

I can confirm that this error occurs, and I am able to reproduce it on my machine.

This issue will not prevent you from updating to the latest version of the CoinPayments adapter, it only prevents you from seeing the changelog before updating. The changelog is also found in the plugin’s zip file, in CHANGELOG.html. I am posting here the latest entry in case you wish to review it:

1.1.0

• Add: It is now possible to edit fee settings per individual coin.
• Add: It is now possible to edit the minimum withdrawal amount for each individual coin.
• Add: The minimum withdrawal amount is initialized to the amount enforced by the platform.
• Add: The fixed withdrawal fees for each coin are initialized to the fees incurred by the platform.
• Add: If the admin enters a withdrawal fee or minimum withdrawal amount less than that allowed by the platform, the value from the platform is used instead.
• Fix: Do not show admin warnings to users who do not have manage_wallets.

I will investigate further this issue on my end and will report here any findings.

with regards

[alexg]

Thank you for your feedback!

The adapter deletes all its settings when you uninstall it, so if you performed a clean uninstall, this would be the reason. Since this information is sensitive, I think it’s a good idea to wipe it when uninstalling the plugin.

It’s great to hear that it works for you. I appreciate it.

with regards

[alexg]

Hello,

Thanks for your suggestion. I appreciate it.

I looked at the plugin and actually this is not very helpful. If I could find the time to properly study this plugin, it would be a lot easier and faster to develop a new ERC20 adapter from scratch.

I am aware that many people want ERC20 but it is not something I can work on at this time.

with regards

[alexg]

Actually, the CoinPayments wallets are used to back the wallets of all the users, not just the administrator. All the user funds are placed in one wallet. The plugin retains information on who owns what so it can display user balances and allow withdrawals. There is a 1-to-N relation between actual wallets and users. This is the case with all coin adapters. Coin adapters allow the plugin and its app extensions to communicate in a uniform way with any backend wallets.

With the Fiat Coin Adapter, there is no wallet, hence no wallet API to communicate with. The administrator is responsible to actually carry out bank deposits and withdrawals, and to record these changes to the plugin, with the help of the provided tools. When a user requests a withdrawal, the administrator must actually carry it out and mark it as done in the plugin. Similarly, when a user performs a deposit, the administrator is responsible to check that the deposit was performed to the site’s bank account, and then to mark the user’s deposit as done.

Hope this is a bit clearer. If you like to learn more about the plugin you can have a look at the glossary section of the plugin’s documentation where all the concepts are explained.

Please let me know if you have any more questions.

with regards

[alexg]

Hello Nicholas,

I am not sure what you mean.

In this plugin every user has an account, and each account can hold balances, for each of the enabled coins.

The CoinPayments Adapter extension merely facilitates communication with the third-party wallets (i.e. notifies the plugin about deposits and withdrawals). Coin adapters have nothing to do with accounts.

Could you please try to rephrase your question, because I believe that I did not understand what your query is. What are you trying to achieve?

thank you

with regards

[alexg]

Hello,

Unfortunately I will not be adding ATM integration or paper vouchers as withdrawal methods.

I will see what I can do about WCMP. To be clear, the issues you mentioned are not defects but feature requests. Generally I prioritize defects over feature requests.

with regards

[alexg]

OK thanks, now I understand.

Static templates are static and are only rendered on the server side once, but:

It is possible to add a checkbox to [wallets_balance template="list"] so that the end user can toggle between seeing all balances, or only those that are not zero. This is customary in most exchanges and I will be able to include this in the next release.

Thank you again! I will notify you here when this is done.

with regards

[alexg]

Hello,

Once you install the latest version 4.3.1 of the plugin, the incompatibility should now be fixed.

Just to make sure, try to not use the [wallets_deposit] shortcode in the same page where you use the [twofactor_user_qrcode] shortcode. If you do, then the QR codes might not appear with the correct size, but should otherwise be ok.

Again, thanks for spotting this issue!

with regards

[alexg]

Hello again,

The issue with minimal withdrawal amounts is addressed in version 1.1.0 of the CoinPayments adapter. As an admin, it is now possible to set the minimum withdrawal amount, and the amount is first initialized to the platform default. The admin can increase this value, but it cannot be decreased below what the platform’s minimum is.

with regards

[alexg]

Hello,

Thanks for the additional info. In version 1.2.5 all categories are shown even if they are not being used in posts.

Custom posts are likely rendered with custom theme/plugin templates so this might be the reason the UI is not displayed in your theme. In general, the UI is appended to the content using the the_content filter (see here), to avoid such problems. Do you experience the same problem in other themes too?

[alexg]

Looks like it is not possible at the moment to use BTC.LN in CoinPayments to perform deposits/withdrawals.

The API returns “This coin does not support deposits and withdrawals!”. This is in fact reflected in the CoinPayments wallets page, where it is not possible to perform any actions on BTC.LN, besides locking your balance in the vault.

[alexg]

Hello,

The CoinPayments platform has added support for Bitcoin.LN since my last adapter release.

For some reason it cannot be enabled in the adapter settings, I will check to see why this is so, and will keep you informed.

Thank you for reporting this.

with regards

[alexg]

Hello,

I have been working on a solution to this issue that will allow you to easily set minimum withdrawal amounts. Additionally it will be possible to specify withdrawal and internal fees in detail per each coin (both fixed amounts per transaction, and proportional to the transacted amount). The plugin will start off with the same values as those used by the CoinPayments platform, and the admin can then increase these values if needed.

As a sidenote, I do plan to implement a maximum withdrawal amount, but I plan to do this differently, as part of the parent plugin. I would like the admin to be able to say that a user can withdraw up to the equivalent of X USD per day, and the total will be over all types of currencies. I believe this is more useful as a safety precaution.

I will notify you again here, when the solution I’m working on is out.

with regards

[Author]

Posts