[alexg]

I also tried to enter an exclusion in the “Public REST APIs” box:

wp-json/wp/dswallets/v1/transactions/validate/<id>

But it didn’t work. Perhaps you can ask them how to exclude a public GET endpoint such as:

https://www.example.com/wp-json/dswallets/v1/transactions/validate/tKTENjpMfzZCtjaJ

Then you wouldn’t have to turn the “Private REST APIs” setting off.

[alexg]

Hello,

I got a chance to install BuddyBoss and try this out.

The problem you encountered occurs when the following setting is turned on:

BuddyBoss -> Settings -> Privacy -> Private REST APIs

If you turn this off, then validation links will work again.

The response you got appears to me as if it’s canned. I am not sure if they checked their code. Did you explain to them everything I posted here, including the fact that the REST API of other plugins (Event Tickets and Registration) is affected? The plugin is actively disrupting access of other plugins to the WP REST API. If it’s a security feature then maybe it works as intended, but it seems a little strange to me.

In any case, you can turn off this setting and use both plugins together.

Hope this helps.

with regards

[alexg]

Hello,

I could not see your screenshot because it’s too big for upload. Can you downscale it, or maybe copy the text?

In any case, I already explained the situation to you: As far as I can tell, BuddyPoss seems to disallow all calls to the WP REST API except for a few ones that they need. Hence the problem with other plugins as well. It really seems like it’s something that they should fix, unless if I’m somehow mistaken, which is possible.

What you should do is tell them what I told you. They should be able to either fix the issue, or at least explain to you why it’s not their fault. You can open an issue at their github.

I don’t see how you can go around this as long as their plugin is enabled.

[alexg]

Hello,

Thank you for reporting this error.

It looks like this error is related to BuddyBoss, since it has also been reported in the past for a completely different plugin (Event Tickets and Registration):

https://wordpress.org/support/topic/error-when-connecting-to-stripe-or-paypal/

The validation link is normally handled by a WP-REST API endpoint in the wallets plugin. It does not require you to be logged in or authenticated. The only requirement is that you are the bearer of the correct nonce.

For some reason, BuddyBoss doesn’t like other plugins using the WP-REST API.

This function removes all REST API endpoints, except for their own endpoings:

https://github.com/buddyboss/buddyboss-platform/blob/2.3.90/src/bp-core/bp-core-functions.php#L6061-L6098

This is hooked to rest_request_before_callbacks. See here:

https://github.com/buddyboss/buddyboss-platform/blob/2.3.90/src/bp-core/bp-core-actions.php#L486

So basically the BuddyBoss plugin doesn’t seem to allow other plugins to use the WordPress REST API. Not very nice of them. Please tell them.

with regards

[alexg]

Hello,

Ethereum is an often requested feature, mainly because people want to offer ERC-20s.

I have debated this back and forth for some time, and I have decided against it. I have ranted elsewhere on this forum on the difficulties, but to keep it short, the main problem is the accounts model. The plugin needs all the user funds to be in one pot, not on separate accounts, because:

1. it does a lot of off-chain transactions, and
2. it helps you do cold storage, so not all funds can be online

In short, an Ethereum wallet would have to manage transfers of deposits to a central address, and that costs gas which has to be somehow managed and this is very flaky and hard to implement. But if someone is interested to implement a wallet adapter that does this, I am happy to provide help.

If what you’re looking for is to introduce custom tokens, then this is not possible at the moment.

I am planning to soon release LND support. After that, I will look into maybe integrating Tarot, which introduces custom tokens/assets on the Lightning network.

If what you’re interested in is smart contracts, then this is definitely out of scope of this plugin, and would require a different plugin altogether.

Thanks for understanding. Let me know if you have any more thoughts on this.

with regards

[alexg]

Hello,

This plugin holds user balances on its own DB-based ledger.

It can interface with hot wallets such as Bitcoin core. The complete list of available wallet adapters is here: https://www.dashed-slug.net/howto-choose-between-available-wallet-adapters/

Users can deposit and withdraw to and from the blockchain (including exchange wallets) using the UIs [wallets_deposit] and [wallets_withdraw]. You can see screenshots of the UIs here: https://wordpress.org/plugins/wallets/#screenshots

If you are interested in connecting to a full node wallet, then you need to setup a Bitcoin core wallet on a server with sufficient resources (static public-facing IP, enough disk space for the blockchain, uninterrupted power supply). See: https://github.com/dashed-slug/wallets/blob/master/docs/install.md

Note that there will soon be a new wallet adapter for this plugin, based on LND by Lightning Labs. This will allow you to offer deposit/withdraw functionality to Bitcoin Layer1 and Layer2 (lightning network). Since LND will be usable via a wallet adapter, there will be the possibility to back your Bitcoin (or Litecoin) wallets with a lightweight Neutrino client. This means that, even if you are not interested in Lightning integration, you can use this to offer Layer 1 Bitcoin services without requiring a server with a huge disk. Neutrino does not download the blockchain but instead uses Bloom filters.

This new option will be available very soon. If you follow the dashed-slug on facebook or twitter, you will see the release announcement.

Please let me know if you have more questions about the plugin. I reply to all queries once per day, Monday to Friday.

with regards

[alexg]

Hello. My apologies for the late reply. For some reason I didn’t see your question.

You can head over to https://www.dashed-slug.net/dashed-slug/membership-plans/ and follow the instructions.

Please let me know if you have any more questions.

with regards

[alexg]

Hello,

It’s true that CoinPayments is no longer available in the United States.

You can use Bitcoin or Monero with your own full node, or with any full node that is compatible with one of these two technologies (Litecoin, Bitcoin cash, Dogecoin, etc), as described here: https://www.dashed-slug.net/howto-choose-between-available-wallet-adapters/

There is no Kraken or Coinbase integration for technical reasons.

There will not be any additinal support for ERC-20 tokens unfortunately. The only ERC-20 support is for a few select tokens via CoinPayments, and only if you are not based in one of the restricted countries.

In a few days or a couple of weeks tops, I will be releasing a Bitcoin Lightning adapter I have been developing, which is compatible with lnd. The advantage here is that you can have Layer1 and/or Layer2 bitcoin transactions without setting up a Bitcoin core full node which requires a lot of resources. This is because lnd can be installed with a light neutrino client which is based on bloom filters. More on that on the blog on the time of the release. If you follow the dashed-slug on facebook or twitter you won’t miss it.

Hope this helps. Please let me know if you have any more questions.

with regards

[alexg]

For the record, this has been resolved in version 2.0.0 of the Exchange (and later), which is compatible with version 6.0.0 of the parent plugin (and later). Sorry for the long delay guys.

[alexg]

Hello,

I have since developed this stand-alone script.

Please study the instructions in the script carefully. If you decide to use it, take a backup of your site first.

The script will migrate balances only, not transactions. There is currently no way to migrate transactions quickly. If you have any questions, please let me know.

with regards,
Alex

[alexg]

Hello,

My apologies for the late reply. Your message was marked as spam for some reason.

Thanks for bringing this to my attention.

There were several issues involved. One was that it was not possible to disable the tor setting once enabled. However, tor was not being actually used unless you had it enabled in the plugin’s HTTP settings (Settings -> Bitcoin and Altcoin Wallets -> HTTP settings -> Tor enabled).

Please update the parent plugin to 6.1.1 and the CoinPayments wallet adapter to 2.0.6. These updates fix the issues mentioned above.

However, I do not believe that this will the issue you report (i.e. API key not having permission for get_basic_info). You should definitely re-check the permissions on the API key you are using.

Additionally, it is possible that this is a cached error. In the screen with the wallet adapter settings, click on “Clear Cache”.

If you do all of the above and you continue to face problems, please let me know.

with regards,
Alex

[alexg]

Hello,

Thank you for your continued interest in the plugins.

As per GDPR regulations, I delete all accounts with more than 2 years of inactivity.

Was your account inactive? If so, you would need to pay for new membership.

If you have been paying for membership until now and your account was deleted, please email me.

with regards

[alexg]

Hello,

From the title of the transaction in the screenshot, it looks like you have selected to transfer “Addresses and Balances” only, not “Addresses and Transactions”.

In this mode, the migration will look at each user’s balance and create a new deposit, giving to the user the balance that they had in the old ledger. The transactions are not migrated. This is the recommended way because the time this takes scales with the number of users on your system, not with the number of transactions. The obvious downside to this is that transaction history is not preserved.

If it is important for you to preserve all the transactions, you can:

1. Revert the migration. This will remove all Currencies, Addresses and Transactions with the migrated tag, effectively letting you start again. Reverting will take a few cron runs, but not too many.
2. Ensure that all the currencies are created. The migration process will try to guess currencies by their ticker symbol, but it’s better if you do it manually so that there won’t be any problems. Also, if you are using any currencies that are not on CoinGecko, then you should definitely define them yourself.
3. Finally choose to migrate “Addresses and transactions” instead. This will take longer. It is also possible that some transactions may not be migrated for whatever reason, in which case all the admins (users with the manage_wallets capability) will receive emails about these transactions.

For more information, please check the documentation: https://github.com/dashed-slug/wallets/blob/6.0.0/docs/migration.md#which-one

If, while migrating transactions, you do get any errors in your emails, please let me know, so we can see what’s wrong.

If, after all transactions are migrated, the sums of user balances on the old custom SQL ledger and on the new CPT ledger will be the same, then migration was successful.

Hope this makes things a little more clear. Please let me know if you have any more questions.

with regards,
Alex

[alexg]

Hello,

This is by design:

In versions 3.0.0 and later of the payment gateway, which are designed to work with version 6.0.0 of the plugin, the funds are simply subtracted from the user’s balance, with a credit transaction. Since the user will have deposited funds to gain that balance, any funds subtracted from their balance simply belongs to the site.

Also see the glossary definitions for “Hot wallet balance” and “User balance” for more details on this.

It’s best to think of it with an example. Say user A deposits 1 Litecoin. Then, their LTC balance is 1, and the site’s hot wallet balance for LTC increases by 1. Then, user A purchases a product that costs 0.5 LTC and checks out. Now the user’s balance is 0.5 LTC, but the hot wallet balance remains on the site, and can be withdrawn to an external wallet using the Cold Storage tool.

In case of a refund, the user’s balance is increased again and the order is marked as refunded. Nothing else changes. You can see an example of a checkout transaction and a refund transaction here:

(In versions prior to 3.0.0, the WooCommerce payment gateway did indeed transfer funds from the buyer to a designated admin account. This is no longer the case.)

Hope this is clear, please let me know if it’s not, or if you have any more questions.

with regards,
Alex

[alexg]

Hello,

Thank you for reporting this issue. I need more information.

1. To be clear, can you please tell me which wallet adapter the transaction was executed with? CoinPayments, Bitcoin-like, or other? Also, what was the currency?

2. Which version of the plugin and extensions are you using? The latest version for the parent plugin is 6.0.0 on WordPress.org, and the latest CoinPayments wallet adapter is at version 2.0.3.

Please check the plugin versions, because there was an issue related to this that I solved in RC9 (and therefore the current 6.0.0 stable).

3. Does this happen with all withrdrawal transactions? Do you have other withdrawals that succeed, and only this one got cancelled?

If you can, please email me screenshots of the transaction details in the plugin. If the withdrawal was done with the CoinPayments wallet adapter, please also show me the transaction details in the CoinPayments withdrawal history, or the IPN message.

Thank you.

with regards

[Author]

Posts