Forum Replies Created
-
Posts
-
Yes, this is correct.
Third party services introduce a counter-party risk. I have been saying this from day one. I no longer recommend block.io, even though I never had problems with it myself, because I have seen some complaints about the service.
My first plan was to create a plugin that can directly interact with full node wallets. Third-party services were an after-thought, once I realized that most web “developers” don’t know Linux 🙂
I am aware of Blockonomics. Unfortunately, developing a new coin adapter is out of the question for me at this time.
My current recommendation is that people need to first understand the trade-offs, and decide if they want security or convenience. See HOWTO: Choose between available coin adapters.
with regards
Hello,
This has been discussed several times, and I am somewhat uncertain about providing this functionality, at least in the form of a coin adapter. If possible, I would like to have a 1 to many relation between fiat coins and methods of payment. I realize that many people want this, and it will have to be done.
I plan to devote the immediate future towards writing more how-tos about the products, and there will be an article on how to insert/edit/delete transactions in the DB. This will be all that’s needed for others to implement various deposit methods. After this is done, I might give it a go myself, but others can do so too, because the fiat payment methods/gateways are simply too many.
I will check out bitnovo, thank you. But the issue here is not to find a credit card processor, there are numerous out there. It’s just that this has to be done right, so that no payment methods are precluded by the design.
with regards
Hello,
No, because the back-end wallet, whether it’s CoinPayments or a full node wallet, does not know about users and balances. If you were to do that, the two sites would simply share a hot wallet, but the users, deposit addresses, transactions and balances on each site would be different. The coin adapter is an abstraction for the wallet back-end, and therefore does not have any effect on how balances are stored on your MySQL DB.
It is possible to use the same CoinPayments account as a back-end for two sites but this introduces a single point of failure for both sites and is thus not recommended. You would also need to keep track of the hot balance so that it’s always enough for people to be able to perform withdrawals on both sites.
The only situation where users can share balances across sites is if you have a multisite installation and you have network-activated the wallets plugin (and all of its extensions).
Have a great year too!
with regards
Hello,
I can help you debug this. Please tell me the following:
1. What is the issue? Is this on a new site or did withdrawals work before?
2. In the admin dashboard, under “Bitcoin and Altcoin Wallets”, what do you see next to “Cron jobs last ran on” and “Cron jobs last runtime (sec)”?
3. Go to the Wallets -> Transactions admin screen. After submitting a new withdrawal, does its status stay at “unaccepted” ? Or does it become “pending” and eventually “failed” after a while?
4. If the withdrawal becomes “failed”, does the user receive an email with an error message?
5. Please check that you have enough funds in your hot wallet.
6. Please check that the CoinPayments API key has the correct permissions. This is described in step #23 of the installation guide: https://www.dashed-slug.net/bitcoin-altcoin-wallets-wordpress-plugin/installation-instructions-web-wallet/
Please reply to all of the above if possible. If after checking all of the above the problem remains, I can login myself to investigate.
P.S. I have moved your post to a new thread as it was not relevant to the other thread.
Hello,
Perhaps this is a good idea, but don’t you think that this should be directed to the developers of WC Marketplace? **The job of a payment gateway is simply to execute payments, not perform logic on what needs to be paid.** (This is again the separation of concerns principle that we have discussed before.) If you think that cashback is a useful feature, why is it only relevant to a cryptocurrency payment gateway? I would argue that it would be relevant to all types of payment, therefore it is the concern of the eshop, not its payment gateway. I am not saying this only because I am not able to devote time on it, but because it really is a feature that does not fit in a payment gateway. Ask yourself this: Would you ask this feature from a developer of a PayPal or Stripe gateway?
Happy holidays
Please see my previous reply at https://www.dashed-slug.net/forums/topic/i-have-account-premium-and-i-cant-donwload-content-premium/#post-7526
When you sign up for a tax-exempt membership but you are not providing your EU tax details, I am the one who is being scammed, because I will then have to pay for your tax.
This is why I do not allow downloads in this case. There is ample information about this on the site.
In general I try to be professional in my online communication, but I do not appreciate being called a scammer over multiple emails during the weekend when I am out of office.
I have been doing this gig for a few years now, and in my experience people who call me a scammer are usually scammers themselves.
If that is the case, I can provide a refund, and you can take your business elsewhere.
If you have a legitimate business situated in the EU, please provide your tax details. If not, I can provide a refund so that you can sign up with a non-tax exempt plan.
Hello,
Thank you for paying for membership!
You cannot download because you have signed up for an EU business plan but have not entered a valid VATIN that can be verified with VIES.
Please go to your profile at https://www.dashed-slug.net/membership-login/membership-profile/ and enter your VATIN, without the country code.
Once the number is verified you will be able to download the premium extensions.
Please let me know if you face any problems.
with regards,
AlexHmm,
5 euros per month for a static IP sounds very reasonable, but I’ve never heard of a 100 euro set up fee; that sounds like a lot.
Are you sure that you cannot find an ISP in your area that offers static IP with 5 or 10 euros per month but without an upfront fee?
In any case, it is possible to make this work even with a dynamic IP, but it’s somewhat harder, and it will involve connecting to your WordPress machine via ssh.
If you can get the IP of the server via a Linux command, you can use
wp-clito insert it into your WordPress DB. Let’s say that you have a command that pulls the IP from somewhere, then you can do:wp option update wallets-bitcoin-core-node-settings-rpc-ip $(command that pulls your ip) --path=/path/to/wordpressJust replace “command that pulls your ip” with the actual command and replace
/path/to/wordpresswith your actual path.The difficulty here is to have a command that pulls the dynamic IP. Since your web server already has a static IP, you’d have to push your dynamic IP FROM your wallet server TO your WordPress server. For example:
Wallet server:
curl https://api.ipify.org >>myip.txt
scp myip.txt wordpress:~WordPress server:
wp option update wallets-bitcoin-core-node-settings-rpc-ip $(cat ~/myip.txt) --path=/path/to/wordpressDo this once manually to see that it works. Then, on both ends these should be on the crontabs of the two machines. This way the setting will get updated shortly after your dynamic IP changes. There might be up to a minute of downtime when the IP changes.
Let me know if you are having trouble implementing this.
Thank you for all the feedback. To clarify:
1. You would like vendors to be able to request their own withdrawals. I agree that the current solution is not ideal. However this issue is not easy for me to investigate. It would take too much time, and most users are interested in other things that are more urgent. As it is right now, the admin simply has to verify commissions before they are paid out, which is not a bad idea I believe.
The core issue here is that the original author of this codebase (probably before grey parrots) had intended for the vendors to maintain a ledger, and then commission payments and payouts modify that ledger. The wallets plugin has its own ledger, so the vendor has to “withdraw” balance from the wcmp ledger to the wallets ledger. There is no clear API for communicating with the WCMp ledger, so I had to hack the database for all of this to work. Not a clean solution. To make a single payment, we now have commissions, transactions, internal transfers and two completely different types of withdrawals. Very confusing.
2. You mention that there is some issue with partial refunds. Could you please open a new thread so we can track this issue? If you can, please be clear on what you tested and what you would expect to see.
You then mentioned that you think this is a WCMp bug. Did you experience a problem using other gateways besides the dashed-slug one? If you can please also provide this info in the new thread.
3. You mentioned something about cron jobs, but I did not understand what. The WCMp payment gateway is in no way related to cron jobs and does not use them. If this is a separate issue, can you please open a new thread and provide more details?
Thank you for the clarifications and for all your help with testing. I feel like we’re getting there!
Hopefully once this gateway evolves I will write a complete guide on how to set up a marketplace and more people will be using it.
with regards
It is possible to add this code in your functions.php file if you want.
The best way would be to add this code as a new file under
wp-content/plugins.You may want to change the name and other metadata at the top of the file (the large comment block).
Then, go to your list of plugins and activate your new plugin.
I will be adding a guide on all of this soon, in the brand new how-tos section on this site.
with regards
Hello,
It’s at least remotely possible that cloudflare is causing this. Or your server-side cache is preventing the API call, although I find this unlikely: Even if a single such URL is cached, that can’t affect any other transactions, since the TXID is part of the request URL and it’s different every time.
The plugin’s JSON API2 and API3 should be equivalent as far as the notify mechanism is concerned so it makes no difference. To use API2 with the latest version of the plugin, you’d first need to enable “Legacy JSON APIs” from the frontend settings. I wouldn’t do this if I were you. Since you already know that you can trigger the notify mechanism from your browser, the issue is not with the plugin.
You can try any transaction ID to see if you get a response. The call simply tells the plugin to go query that transaction, if it is a fake or non-existend transaction then nothing happens. But in any case you should see a JSON response with result: success, meaning that your request was submitted successfully, not that the transaction was found necessarily.
Since you know that the plugin works when you trigger the URL manually, this is something that has more to do with the wallet than with the WordPress plugin. You should focus on why the actual wallet does not do the same call. Perhaps you can redirect the output of the curl call to some log file, for example:
walletnotify=curl -k --verbose https://www.urcryptodepot.com/wallets/api3/notify/FCK/wallet/%s >>~/walletnotify.logThen your
~/walletnotify.logfile should contain some output.Or check your webserver’s access log and see if the wallet is making the calls you expect to see.
Hope this helps.
with regards
P.S. I am happy to answer any specific questions, such as yours. It’s my choice to work alone so it’s cool. I can usually handle the context switching, and when I can’t, I just answer everything on the next morning 🙂
The question is whether your wallet is able to trigger that url.
– Did you restart the wallet?
– Is there a firewall in the middle blocking the call?Perhaps you can try the curl command from the machine that runs the wallet and see if it works. Remove the silent (
-s) argument to be able to see errors. So, you might try, from your wallet machine:curl --verbose -k https://www.urcryptodepot.com/wallets/api3/notify/FCK/wallet/SOMETXIDand see if the command fails.
