[alexg]

The CoinPayments adapter sets the fixed portion of the withdrawal fees to be equal to whatever amount is required by the CoinPayments platform to pay for blockchain mining. Any additional fees that you set are added on top of that. The extra fees that you set are subtracted from the user’s account but not from the wallet address.

Please see this recent post to a similar question for more details: https://www.dashed-slug.net/forums/topic/failed-withdraw-and-fees/page/2/#post-2325

The video you are referring to was done before any of the web wallets were implemented, but the general idea still holds. While earning some transaction fees can make you money, you cannot expect to create a website wallet with only that as your plan. Your users need a reason to use your website as a wallet, so you need a business plan. This is where the app extensions come in. They let you provide functionality on top of wallets.

Hope this is more clear.

kind regards

[alexg]

Hello,

Yes, it seems that with the current deployment of the lightning network the mempool is becoming less congested so it’s very likely that fees will soon drop enough for your transaction to go through. If not, here is some general info about what to do with unconfirmed transactions: https://bitcoin.stackexchange.com/questions/9046/why-is-my-transaction-not-getting-confirmed-and-what-can-i-do-about-it

In the plugin, when a coin adapter determines the amount of fees, based on your settings and possibly other factors, the fees that you see in the Transactions table do not get added to any account, but to the wallet.

The plugin maintains a 1-to-N mapping of wallets to users. The wallet balance shown next to the adapter is the actual balance in the wallet. while the user balances are derived from the sum of user transactions. The fees paid cover the network fee paid to the blockchain, and if the fees are larger than that, the extra amount is subtracted from the user and remains in the site’s wallet.

kind regards

[alexg]

My email is here: https://www.dashed-slug.net/contact/

[alexg]

In your IPN history, at the deposit that was not sent successfully, click on the date/time field. This should show you details of why the IPN did not succeed.

Can you send me that error message? Thanks.

[alexg]

Hello,

Yes, thank you for changing from the Electrum wallet to CoinPayments. The CoinPayments adapter is well-tested and is being used in a lot of installations. The Electrum adapter needs some more work because the wallet has changed recently.

The plugin does a mapping of one wallet to many users. The balance you see in the adapters list and in the cold storage screen is the full balance of the wallet, not the balance assigned to each user.

For a user to have a balance, they need to do a deposit to one of their deposit addresses. When you go to the Wallets -> Transactions page, do you see any transactions with type = “deposit”? If so, do they have status = “done”? If not, then there shouldn’t be any balance on the user accounts.

Do a deposit to one of the user deposit addresses. This will work if you have set up the CoinPayments adapter correctly, by following all the installation instructions on the adapter page. Common pitfalls:

Remember that deposits work via an IPN callback from the CP platform, therefore they will not work in your local dev environment. The plugin needs to be running on an internet-facing server.

To do your tests, you can enable the Litecoin testnet coin (LTCT) and use this faucet to do your test deposits: http://testnet.litecointools.com/

Do tell me how this went and if you face any further problems. But make sure that you have followed all the installation instructions for the adapter and that your server can accept IPN callbacks.

kind regards,
Alex

[alexg]

That is my intention, yes.

[alexg]

Hello,

Thanks for your interest in this. You are very right in that I had said it would be done and it’s not.

It is still in my immediate plans and I was delayed for a number of reasons, most of which were outside my control.

In the future I will refrain from making promises and setting public deadlines. Lesson learned.

[alexg]

It’s good it works but when I open bitcoin qt j wing message Status: 0/unconfirmed, in memory pool

Do you see 0 confirmations only in the plugin or in the blockchain as well?

If you do not see your transaction having been confirmed on blockchain.info, then it is possible that your transaction has not yet been mined. This would be the case if you have set the fees too low. This is an issue with the bitcoin network at the moment as I explained before. If on the other hand you do see your transaction with confirmations on blockchain.info, then we can discuss why this is not reflected in the plugin. The plugin is notified about network confirmation changes both via the -walletnotify mechanism of the full node, and via polling the node.

thank you very much, (it has no report but what studies did you do ?)

Do you mean what I have studied personally? My academic credentials are on LinkedIn https://www.linkedin.com/in/alexandrosgeorgiou/

Let me know what happened with your transaction.

[alexg]

Yes,

As you know the Bitcoin fees are quite high at the moment due to the Lightning network not having been deployed yet.

The actual fees that your Bitcoin core wallet pays to the blockchain are controlled by your bitcoin.conf, not the plugin.

In your coin adapter there is some text about this, I’m pasting it here:

This withdrawal fee is NOT the network fee, and you are advised to set the withdrawal fee to an amount that will cover the network fee of a typical transaction, possibly with some slack that will generate profit. To control network fees use the wallet settings in bitcoin.conf: paytxfee, mintxfee, maxtxfee, etc. Refer to the documentation for details.

So you will need to configure a sensible amount of fees for a single transaction, depending on how fast you want it confirmed. The withdraw transaction is from one address to one address. You should set this in your bitcoin.conf. Then, make sure that the withdrawal fees set in the plugin are at least as high as this, or higher.

You can estimate a sensible value for the current time period from this webpage: https://bitcoinfees.earn.com/

Also take the time to read this: https://support.earn.com/digital-currency/bitcoin-transactions-and-fees/how-do-i-calculate-my-transaction-fee

Hope this helps.

[alexg]

Yes, this is the purpose of this plugin. Users whose role have the has_wallets capability automatically get wallets in all the cryptocurrencies that you have enabled adapters for.

Can you please describe in more detail what “doesn’t work”? I need some more info. What do you see in the Adapters screen? Are your coins listed there? Is the adapter status “responding”? Are the UIs displayed in the frontend?

[alexg]

You also helped me notice that I’ve misspelled “transaction”, so thank you for that! 🙂

[alexg]

Ah yes, this is a bug that was fixed in the latest version. Sorry about that.

Either update to the latest version, or add a passphrase to your wallet.

Ideally you should do both.

kind regards

[alexg]

Thanks coinstar for your input.

Since the OP is testing in a VM, it is unlikely that sendmail would be installed AND correctly set up. As you know setting up an email server is a lot of hard work. This is why I suggested the plugin solution.

As for emails going to the spam folder, this can be easily solved for testing purposes, if you just add the email to your contacts in your webmail solution.

On an actual live setup you would not have to do any of this, of course.

[alexg]

Hello,

If you are not getting emails this is not an issue with the plugin, but with your OS setup. Unless you have set up sendmail on a system, emails will not work.

Since you are testing in a VM, it makes sense that this would not be set up, while on an actual live server provided by a web host, emails would work.

The easiest workaround I can think of is to forward emails through a gmail account. You can setup a plugin such as this one: https://wordpress.org/plugins/wp-mail-smtp/

It’s what I use in my development environment.

Once you get emails working, let me know what error you get with your withdrawals.

kind regards

[alexg]

Hello,

Which adapter are you using? Fees are determined by the coin adapter. The fees are intended to cover the blockchain fees plus any more fees that you may want to charge. The actual fees paid on the blockchain are specified in your actual wallet if you are using a stand-alone wallet, or by your cloud wallet if you are using one of the cloud wallets. The fees you specify in the coin adapter settings should at least cover your actual fees.

When you attempt to send a withdrawal, it must be validated by the user and admin by default. When you visit the transactions screen, in what state is your withdrawal? If it is in a “failed” state, then the user will have received an email with an error message that will let you know what the problem was.

As for internal transfers, these are nearly instantaneous but not quite. First they must be user-verified over email by default. Then they are executed in batches on the next cron runs. You can control how often cron runs and how large a batch of transactions it processes each time.

Let me know which adapter you’re using and what error you get with your withdrawal.

kind regards,
Alex

[Author]

Posts