Forum Replies Created
-
Posts
-
1. As an admin you can see the balances of your users if you go to Users -> All Users -> View or Edit.
2. You cannot directly edit user balances because they are derived from the sum of their transactions. To increase a user’s balance, you can send them an internal transfer via the [wallets_move] shortcode. You can also cancel an internal transfer, which will make it not count towards their balance.
kind regards
P.S. In the future can you please open a new thread for each distinct request? This helps keep the forums clean for people who look for similar info in the future. Thank you.
Unfortunately there is no such list at the moment, but I could add it in a future version. Thank you.
Hello,
The referral program of the Faucet Extension is only useful for the faucet. It cannot be used for other purposes.
I would recommend that you look for a referral-specific plugin that does what you ask.
kind regards
User balances are not stored anywhere – they are derived as the sum of all user transactions. This is safer than storing a single number that could be easily manipulated.
If you have deposited or withdrawn via cold storage then that would, by design, affect the wallet balance but not the user balances. So the difference would be expected.
The wallet balance and the users balances are not the same thing. The difference is explained in the glossary section of the documentation.
Reasons why the two amounts would diverge:
1. As users pay fees for transactions, their total balances decrease but the wallet balance stays the same.
2. If you have used the cold storage feature, or alternatively if you have deposited/withdrawn directly from the wallet and not via the plugin, then the balances will not match. See the Cold Storage section in the documentation for more.As for the block explorer, I assume you have created a coin adapter for CLAM. This is where the hook would go to add the block explorer URIs. See the Block Explorers section of the documentation for example code and instructions.
Please let me know if any of this is not clear
kind regards
Yes, thank you, I understood what you meant. My point is that the frontend cannot currently know if there are actually more than one pages, until it actually requests them. This is why I have not added buttons for pagination. I am preparing a release where there will be versioning on the JSON API. Then afterwards I can add new versions of the API in a backwards compatible way, so that things like this can be done.
regards
Hello,
Thanks for sharing your thoughts.
1. The input box for the page number is of type=”number”, therefore you do not need to type a number, you can just use the scroll buttons next to it, in all but the oldest browsers. The page numbers cannot be buttons because the frontend cannot know in advance how many pages there are.
2. Numbers can be added, but it is somewhat tricky. I will add this to the backlog and visit it after the tasks I’m currently working on. Thanks for the suggestion.
kind regards
Hello,
I’m a bit confused, why did you expect the balances on two different sites to match?
Every site should have its own set of transactions, and therefore user balances.
(I assume that you have connected both sites to the same wallet, something that I would advise against because it introduces a single point of failure for both sites in case of a hack. But in any case, just because the wallet balances match does not mean that the user balances should also match.)
Let me know. Thanks.
Hi again,
Please do the following to resolve this issue:
1. Upgrade your CoinPayments adapter to the latest version, 1.0.1
2. Go to Wallets -> Rates and enable one of the exchange rate providers. This is necessary for the WooCommerce payment gateway extension.
3. Wait for 5 minutes, or whatever the “Rates cache expiry (minutes)” option is set to.
After that, the LTCT symbol should be assigned with an exchange rate.
kind regards
Hi Andy,
You cannot simply disable that, since the WooCommerece plugin needs the exchange rates API.
The issue here is that you are correctly using LTCT to test the site, but there is not an actual coin with that symbol.
I will change the code to make sure that LTCT has an exchange rate, possibly the same as LTC, so that you can proceed with your tests.
Thank you very much for reporting.
