Open extra topbar

Cold Storage address balance no longer updating

If you are new here, please see some information on how to ask for support. Thank you!

Cold Storage address balance no longer updating

dashed-slug.net Forums Full Node Multi Coin Adapter extension support Cold Storage address balance no longer updating

This topic contains 3 replies, has 2 voices, and was last updated by  alexg 3 weeks, 2 days ago.

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #5608

    killthrash
    Participant

    The cold storage wallet balance for one of my coins is stuck at 0, and when I deposit coins to that address the balance does not update.

    #5622

    alexg
    Keymaster

    The hot wallet balance is cached internally via WordPress transients for performance. Can you check with the setting:

    “Frontend” -> “JSON API settings” -> “Disable transients (debug)”

    Then go to the adapters list and see if the Hot Wallet Balance is correct.

    If this setting makes a difference, then it means that your server-side cache is misconfigured so that transients are not expiring properly.

    Please let me know once you try this.

    with regards

    #5657

    killthrash
    Participant

    Changing that setting worked, now the Hot Wallet Balance is displaying correctly, and is updating when depositing coins to it.

    How do I address the caching issue? I use Autoptimize. Would this have an affect?

    #5661

    alexg
    Keymaster

    Hello,

    I tested the plugin and Autoptimize does not cause any issues with the default settings. It is possible that with your settings it does cause issues with Transient expiry. Uncheck the “Disable transients” option again as it creates a lot of overhead to the plugin.

    I would recommend the standard procedure for such cases: deactivate all other plugins, then check if the balance updates. Once you determine that the plugin works with all other plugins deactivated, then you can activate some more plugins, then a few more, until you find out which one causes the problem.

    If you do find something, I would be very interested if you could share your findings. A lot of people have reported issues due to transients not expiring properly, but none so far has the technical expertise to debug the issue, and I cannot recreate these conditions on my machine in order to investigate myself.

    If I knew what can cause transients to persist after their expiration time, I would be able to make the plugin detect these conditions and warn the user to take appropriate action. If you are using memcached or anything that uses a server-side key-value cache, or otherwise messes with transients, then these are your suspects.

    Looking forward to your reply if you do find anything.

    with regards

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.