dashed-slug.net
Forum Replies Created
-
Forum: Plugins
In reply to: [Bitcoin and Altcoin Wallets] I can’t get it to workHello,
I have replied to your other post, here: https://ww.wp.xz.cn/support/topic/i-cant-get-it-to-connect-to-my-btc-core/
Let’s continue discussion in the other thread.
with regards
AlexForum: Plugins
In reply to: [Bitcoin and Altcoin Wallets] I can’t get it to connect to my BTC CoreHello,
Apologies for the late reply. For some reason I didn’t get a notification for your post, or the notification got lost somehow.
To be clear, what is not working? I assume you are trying to connect to a Bitcoin full node wallet using the built-in Bitcoin adapter.
When you go to Wallets -> Adapters, what do you see next to the adapter, in the “status” column?
Please share with me the error text and we’ll take it from there.
with regards,
AlexForum: Plugins
In reply to: [Bitcoin and Altcoin Wallets] columns argument “confirmations” not showingHello,
Please check again with version
5.0.15. I have released a fix for this.If you are still encountering issues with withdrawal confirmations, let me know. There could be more problems related to your setup: The confirmations are updated only if the TXID notifications from the full node wallet succeed.
with regards
Forum: Plugins
In reply to: [Bitcoin and Altcoin Wallets] columns argument “confirmations” not showingHello,
Thanks. It’s true that I make a consistent effort to give a first reply to all queries at least once a day, Monday to Friday.
You are very wise to test things first using the Bitcoin testnet. I wish more users would do integration testing before production.
Normally the confirmation count should be updated regularly for withdrawals. However I have now tested a withdrawal, and I see that confirmations are not updating for Bitcoin-like wallets.
I will investigate this, and will notify you again here when I have something. Thank you for reporting this issue.
with regards
Glad to hear it! Thank you for taking the time to report back.
Also, since you have pasted your
rpcauth=line here, don’t forget to change your password once you get this working.First of all, you cannot set
rpcport=8333because that’s the port that Bitcoin uses by default for its P2P communication. Better stick to the default8332for the RPC API port.1. Most likely your VPS blocks all incoming ports except for a few whitelisted ones (HTTP, HTTPS, ssh). So it’s very likely that this is the issue. Your hosting provider will be able to let you know and possibly enter a rule into their firewall for you.
2. Another potential problem that I see is that you’ve allowed incoming connections from
198.54.114. You did not provide the entire IP, but I’m not sure if this is in a public IP range. I could be wrong about this, but if this IP is in a reserved range, this is not going to work. Using therpcallowipconfig, you are saying to your wallet that you want to allow connections from this IP. If you try to connect from a machine in your local network, when your wallet filters incoming IPs, it will see an incoming connection from your local network as coming from the public IP of your router, not the local IP. If you’re sure that this is a valid public IP, then this is not the root cause of the problem.3. Finally, remember to restart your wallet after any changes to your
.conffile.If you cannot telnet from your WordPress machine to your wallet machine’s RPC port, then that has nothing to do with the plugin. This is likely a networking issue, so wait until your host replies to you about firewalls. You could also try asking for bitcoin core support. A good place to ask questions on how bitcoin core works is https://bitcoin.stackexchange.com/
Let me know if the above is not clear or if you have more questions about this.
with regards
Hello,
I can’t check your config file since it was removed. However here’s a few pointers:
1. If you can’t connect, then the plugin will recommend a few config entries in the admin screens. It’s a good idea to start from there.
2. Since the video was created, bitcoin core now requires the
rpcbindconfig entry to open up ports. Use rpcbind to specify the public IP of the machine running the wallet. This should be the same IP that you set in your Bitcoin adapter settings.3. If IPv4 doesn’t work, try IPv6 addresses.
4. Connection refused means that the WordPress machine could not connect to your wallet’s RPC port. This could be for any number of reasons. Check the firewalls between the two machines. If necessary, talk to your hosting providers about it. You basically want to allow incoming TCP connections to the wallet machine on port 8332.
Hope this helps. Please let me know if you continue facing difficulties after trying the above.
with regards,
AlexForum: Reviews
In reply to: [Bitcoin and Altcoin Wallets] The best WordPress plugin in its class !!!Thank you!!!
Hello,
There was no need to release an update as the plugin is stable for the time being. Rest assured that the plugin is currently compatible with WordPress 5.6.
with regards,
AlexHello,
The next major scheduled version of the plugin,
6.0.0will be out some time in Q2 of 2021 and will require PHP 7.2. It will be compatible with PHP 8.0.with regards
Forum: Plugins
In reply to: [Bitcoin and Altcoin Wallets] Make withdrawals happen faster@clickforafrica Thank you very much for helping with the plugin’s support! It’s true that transactions can stay in the mempool for long if the fees are set too low for the current network conditions.
@enochdavid, since you are using the CoinPayments adapter, the actual network fees are set for you, so you don’t need to worry about them.
I suspect that you are on a site that’s currently under development, or otherwise receives very little traffic. Some background:
For withdrawals to proceed, the cron jobs must be triggered a few times. Normally WordPress cron jobs get a chance to trigger only if someone visits your site. Otherwise, WordPress doesn’t get a chance to run and therefore cannot process transactions. If this is the case, then your withdrawals should be staying in an
unconfirmedorpendingstate for a long time. On the other hand, IF the transaction has already been submitted to CoinPayments and you can see it in the list of pending withdrawals in your CoinPayments screens, then this means that the plugin has done all it can, and it’s now on CP to execute the transaction.If the transactions are not being attempted (and therefore take a long time to reach the CP server), then the solution is to trigger the cron url manually from an external source. See *Wallets* → *Cron job* → *PRO TIP* for details. If you set something to trigger that url every one minute then the cron jobs can run without delays.
Hope this helps. Please let me know if something was not clear. Do your withdrawals reach the CP server quickly and then get delayed there, or do they get delayed at the plugin before being attempted?
with regards,
AlexHello,
This is by design.
40k satoshi is the withdrawal fee that the platform imposes – you cannot set the fees any lower than that or you will lose money. But you can set it higher. If you set the fees at 50k satoshi, you earn 10k on every transaction.
Hope this is clear. You can use proportional fee if you want, but there has to be a fixed fee of at least 40k.
Forum: Plugins
In reply to: [Bitcoin and Altcoin Wallets] Paypal does not workHello,
Thank you for your interest in the plugin and its extensions. If you wish to pay with cryptocurrencies, please do the following:
1. Select the membership plan that you want from https://www.dashed-slug.net/dashed-slug/membership-plans/
2. Send the equivalent of the USD amount to one of the following addresses (DOGE has the lowest fees I believe)
Bitcoin Address: 1DaShEDyeAwEc4snWq14hz5EBQXeHrVBxy
DOGE Address: DASHEDj9RrTzQoJvP3WC48cFzUerKcYxHc
LTC Address: LdaShEdER2UuhMPvv33ttDPu89mVgu4Arf3. Email me again with your selection of membership plan, the TXID and the email you used to sign up.
I will then activate your membership manually.
with regards,
AlexForum: Plugins
In reply to: [Bitcoin and Altcoin Wallets] Multiple deposit/withdrawalHello,
If I understand your question correctly, this is not possible at the moment.
Users can only issue a withdrawal to one address. They can of course issue many withdrawals and each withdrawal can be to a different address.
In the upcoming version
6.0.0of wallets I have implemented a new withdrawal batching feature. With this feature, if there are multiple pending withdrawals for a single coin at any one time, and if the wallet backend supports it, the plugin will issue a transaction with multiple outputs. This will save some network fees, but the users will still be charged the full withdrawal fee as set by the admin. Wallets 6 will be released around Q2 of 2021.Hope this helps. Please let me know if I misunderstood your question.
with regards