[alexg]

Hello,

OK it’s great news to hear that you can use wallet-api with your blockchain! You brought up several points, let me address all of them:

mbstring is not a required PHP module, so it is not an issue if you don’t have it.

The wallet password is saved in a transient, so it’s not necessarily in the DB. Assuming your coin’s symbol is ARMS, the transient name is trtl-ARMS-settings-wallet-passphrase. You can check what the value is using wp-cli:

wp transient get trtl-ARMS-settings-wallet-passphrase

Where transients are stored depends on whether you have a server-side object cache installed. Some object caches store transients on their own memory rather than the DB, so this is why you should use wp-cli to check transients, not MySQL/phpMyAdmin.

To see exactly how the password is saved, see the function update_value_if_not_empty(). It’s hooked on the save pre_update_option_ filter for option trtl-ARMS-settings-wallet-passphrase. The function gets a value and if it’s not empty, it tries to save it in a transient. If the value of the option wallets_secrets_retain_minutes is 0 or empty, then the transient is saved forever. Otherwise it’s saved for however many minutes you’ve set secrets to be saved for.

I’m not sure why your daemon IP and port are not saved in your DB. They should be in trtl-ARMS-settings-daemon-ip and trtl-ARMS-settings-daemon-port respectively.

I also noticed that, according to your settings as shown in the screenshot, your coin symbol is “2acoin” not “ARMS”. How are you defining your coin? I have included 2acoin/ARMS as a default coin, so you shouldn’t have to use wallets_turtlecoin_adapter_filter at all. If you are using this filter, delete it. Your coin’s name is 2ACoin and its symbol is “ARMS”: https://www.coingecko.com/en/coins/2acoin

Hope this helps. Good luck. Please let me know what you found. I think you are looking at the wrong options in your DB (wallets-2acoin-* rather than wallets-ARMS-*).

with regards

[alexg]

Hello,

OK thank you for the clarification.

I still can’t reproduce the issue on my machine, so I’m not sure why it happens.

I can’t understand how you checked out. To check out using a crypto coin, you must go to checkout, select “Bitcoin and Altcoin Wallets”, and then there is a dropdown with all the currencies that have enough balance to pay for the cart. You are not allowed to select a currency that has insufficient balance.

Could you please help me reproduce this issue? Please answer all of the questions below:

1. Are you using the latest version of the gateway? It’s 2.3.2.

2. Are you using any other WooCommerce plugins?

3. What’s your store’s default currency? Your store’s default currency is at “WooCommerce” -> “Settings” -> “Currency options” -> “Currency”.

4. What’s the cryptocurrency you paid with? The currency you paid with is the currency chosen in the dropdown on the checkout page.

5. Most importantly: Is the exchange rate between these currencies available? To see the available rates, go to “Wallets” -> “Exchange Rates” -> “Exchange rates debug views” -> “Exchange rates”.

(For example, if you have the BTC_USD rate and the LTC_BTC rate and you try to pay with LTC, while the store currency is USD, then the exchange rate is available i.e. can be computed from available data.

thank you

with regards

[alexg]

To further clarify, please see https://docs.turtlecoin.lol/developer/resources under “TurtleCoin Core RPC APIs”

the turtle-service API is deprecated.

[alexg]

OK, first of all there is the TurtleCoind service that syncs the blockchain.

Then, you also need a program that connects to this blockchain service to present addresses/wallets to your business logic.

If I have understood correctly, in the past the turtle-service was used for this. Nowadays there is the newer wallet-api service.

You will NOT be able to use 2acoin-service, because the TurtleCoin adapter is not built to communicate with turtle-service.

I have built the TurtleCoin adapter to communicate with the wallet-api service.

If your coin is a fork from an earlier TurtleCoin repo, then it may not have wallet-api.

HOWEVER, it’s very likely that you may be able to use the wallet-api service to connect to your 2acoind. Only the 2acoin developer or the TurtleCoin developer would know for sure, since I’ve never tried this.

[alexg]

Hello,

wallet-api is not a variable. It is a program that comes with TurtleCoin: https://turtlecoin.github.io/wallet-api-docs/

It connects to the turtlecoind service to present, well, a wallet API!

Does 2acoin not come with a similar program?

[alexg]

Thank you.

I have provided a fix for this in version 1.1.5 of the extension.

with regards

[alexg]

Hello,

Not sure why this happens. Are the logs you show me from wallet-api? According to the documentation, wallet-api does not return error 404 for the /status endpoint. Could it be that you’re connecting to the blockchain daemon rather than the wallet-api?

Additionally, the secret would get deleted after a while, if you haven’t set “Wallets” -> “Cron job” -> “Withdrawal Locks” -> “Time to retain withdrawal secrets” to 0.

I’d recommend that you try with a new wallet and follow the installation instructions again. If this works, then we can look into replacing the wallet with your existing one.

with regards

[alexg]

Yes, of course. I thought that your current wallet did not have a password.

In that case, do this:

1. rename your current wallet to n2aa.org.wallet
2. enter the password in the “Wallet Settings” -> “Password” setting.
3. click on “Wallets” -> “Adapters” -> “A2Coin” -> “Renew deposit addresses”.

[alexg]

Not really. The adapter doesn’t allow your wallet file to not be encrypted. And having your wallet file encrypted is a really really good idea. If someone gains access to your wallet file but not your WordPress DB, they can not steal your users’ funds.

Here’s what you could do:

1. Enter a password in the plugin’s settings.
2. Move the existing wallet in another directory and let the plugin create a new wallet file with the new passphrase.
3. Get the cold storage deposit address for your new wallet, shown in “Wallets” -> “Cold Storage” -> “A2Coin” -> “Deposit”.
4. Start your old (unencrypted) wallet and transfer all the funds to this address. The funds will now appear in the “hot wallet balance”.
5. Go to “Wallets” -> “Adapters” -> “A2Coin” -> “Renew deposit addresses”. This will force all user deposit addresses to be refreshed from the new wallet.

The only downside is that the old deposit addresses that users had will not work in the new wallet. This is why we force the plugin to re-create deposit addresses from the new wallet. If the users had saved these deposit addresses elsewhere and then they try to reuse them, the funds will go to your old wallet. i.e. they won’t be completely lost, but you could then transfer the funds to the new cold storage deposit address.

Please let me know if you have any questions about this.

with regards

[alexg]

Hello,

Looks like you’re getting close!

You would only get the error “Cannot open wallet %s until the admin provides the passphrase” if you had not entered a password in the field: “Wallet Settings -> Password”.

This is the secret that encrypts/decrypts your wallet files. You need to keep this safe.

When the plugin first creates a wallet file for the site, it uses this password. So, do this:

1. Set a strong password for the wallet file in the coin adapter settings (Wallet Settings -> Password).

2. Delete your wallet file (assuming it’s empty). The wallet file has a name beginning with your site’s domain and ends with the .wallet extension. It is probably in the same directory as your binaries.

The plugin will now create a new wallet and encrypt it with the password you provided.

[alexg]

OK, here’s a few notes about the withdrawal issue you’re experiencing:

1. About the SSL error triggered on cron_discover_withdrawals: This is a job that replaces the CPID with the actual blockchain TXID for withdrawals. For this job to succeed or fail, the withdrawal must have been completed already. This error could occur at random from time to time. So please tell me this: When you performed the BNB withdrawal, in “Wallets” -> “Transactions” the TXID column in your admin screen would initially show CWEG3KI3F9QZTE5X0M14MG4OMM. After the withdrawal was processed, there would be an actual TXID assigned by the blockchain. As the cron_discover_withdrawals cron jobs runs, it replaces these CPIDs with TXIDs when they become available, in this case DAE8DC0546BEB259C31101A00AB2FF1B4C56FBA212E17B7BE3AD8F4AAC595429. Do you see the TXID in “Wallets” -> “Transactions”, or do you see the CPID? By now the TXID should be shown.

2. The error you get when attempting to withdraw Ethereum is something else entirely, and has nothing to do with CoinPayments. Unfortunately this is not an error I’ve seen before and I can’t imagine what’s causing it, so I have to check everything. If you want me to investigate, I will have to debug this on your server. Please contact me over email. Let me know if this is a live site or not, and take a full site backup if it is, just in case. I will have to disable plugins and enter debugging code into the plugin to investigate (I will need admin priviledges). And I will also need access to your PHP log to check how far the code runs before it breaks.

3. You mentioned that you went through the checklist. What did you mean by “completed every step”? You have already mentioned that the withdrawal is not shown in the admin screens, so surely all the checks must have failed.

[alexg]

OK this problem is likely due to the error you reported. Let me do some research on it and I’ll get back to you.

In the meantime, since this could be an SSL issue, you could check to see if your server’s date and time is set correctly.

with regards

[alexg]

OK, I have gone through the list of coins and identified the new coins that need a destination tag, in addition to the ones that were supported before.

In version 1.1.3 of the CoinPayments adapter, in addition to BCN, XMR, XRP, SBD, STEEM and XEM, the withdrawal extra field now works for the following coins: APL, BNB, ETN, LOKI, WAVES.

Thank you for reporting this issue.

with regards

[alexg]

Version 0.5.3-beta has been released but, again, I don’t think it’s related to your issue. If you continue to see the error “Page not found”, please open a new thread and describe your issue in full.

thank you

with regards

[alexg]

Hello,

Unfortunately, as mentioned before, the plugin does not support multisig.

The plugin’s withdrawal feature creates transactions with one source and one destination.

Therefore, the Monero coin adapter extension and the other coin adapter extensions do not use multisig.

with regards

[Author]

Posts