Bitcoin and Altcoin Wallets


Custodial cryptocurrency wallets.

At a glance

Bitcoin and Altcoin Wallets is a FREE WordPress plugin by dashed-slug.

Your users can deposit, withdraw and transfer Bitcoins and other cryptocurrencies on your site.

Free wallet adapter extensions

You can extend this plugin to work with other coins if you install wallet adapters.

There is a built-in wallet adapter that lets you connect with Bitcoin core and similar wallets, such as: Dogecoin core, Bitcoin ABC (Bitcoin Cash wallet), Litecoin core, etc. Any wallet that uses the Bitcoin core RPC API is compatible.

The following wallet adapters are available for free to all dashed-slug subscribers.

You do not have to pay for membership to get the wallet adapters.

Premium app extensions

Premium dashed-slug members get unlimited access to download all the premium extensions:

Premium members get auto-updates for any installed extensions. See how to set up auto-updates.

follow the slime

Find the dashed-slug on the web:


This is a free plugin built by the dashed-slug team!

  • Bitcoin: 1DaShEDyeAwEc4snWq14hz5EBQXeHrVBxy
  • Litecoin: LdaShEdER2UuhMPvv33ttDPu89mVgu4Arf
  • Dogecoin: DASHEDj9RrTzQoJvP3WC48cFzUerKcYxHc


  • [wallets_deposit] – Users can view their deposit addresses, create new addresses, and associate them with a label.
  • [wallets_move] – Users can transfer funds to other users on the system, off-chain. Whether they pay fees to your site is up to you.
  • [wallets_withdraw] – Users can request to withdraw funds to an external wallet.
  • [wallets_balance] – Users can view their balances, either one-by-one, or as a list. Equivalent amounts can be shown in USD, EUR, BTC or other currencies that you choose.
  • [wallets_transactions] – Users can view paginated details on their past transactions. You can choose which columns are rendered and in what order.
  • Wallets post type – Easily manage your various wallet backends via the Wallet post type.
  • Wallet post type – The wallet post type encapsulates all connection settings with your wallet’s API and displays wallet status.
  • Currency post type – Associate the currencies you want to offer with your wallets, using the Currecy post type. Easily edit settings related to each currency. Group currencies together using a special Currency Tags taxonomy.
  • Address post type – Keep track of deposit and withdrawal addresses. Easily edit address details, or list transactions associated with addresses. Group addresses together using a special Address Tags taxonomy.
  • Transaction post type – Easily edit transaction details or create new transactions. Group transactions together using a special Transaction Tags taxonomy.
  • Capabilities settings – Since version 6.0.0, all settings are neatly organized into tabs, both for the plugin and for its premium extensions.


To get started, install the plugin and follow the on-screen installation wizzard.

You can also consult the documentation. In the WordPress admin screens, see Wallets Admin DocswalletsInstallation instructions.


By using this free plugin, you accept all responsibility for storing and handling user funds.

Under no circumstances is or any of its affiliates responsible for any damages incurred by the use of this plugin.

By continuing to use the Bitcoin and Altcoin Wallets plugin, you indicate that you have understood and agreed to this disclaimer.


Where is the plugin’s documentation?

Since version 6.0.0, the plugin displays its own documentation in the admin screens. Just go to the Wallets Admin Docs menu, where you’ll find the documentation for the plugin, and for any plugin extensions you have installed.

Developers can study the PHPdocumentor pages at:

How secure is it?

When users issue transactions, these can require verification via an email link by the user. Additionally, you can require that an admin also verifies each transaction. (See “Confirmations” in the documentation).

Of course, the plugin is only as secure as your WordPress installation is.

You should take extra time to secure your WordPress installation, because it will have access to your hot wallets. At a minimum you should do the following:

  • Install a security plugin such as Wordfence.
  • Read the Codex resources on Hardening WordPress.
  • If you are connecting to an RPC API on a different machine than that of your WordPress server over an untrusted network, tunnel your connection via ssh or stunnel. See here.

Some more ideas:
– Add a user auditing tool such as Simple History.
– Add a CAPTCHA plugin to your login pages.
– Only keep up to a small percentage of the funds in your hot wallet (See Cold Storage in the documentation).

I am installing a bitcoin full node on my server. How can I run it as a service so that it is always running?

This will depend on the Linux distribution on your server.

To setup bitcoin core as a service on systemd I used this guide.

Here is my /etc/systemd/system/bitcoin.service file:

Description=Bitcoin wallet service



You will need to edit the user name to match yours, and possibly the path to your bitcoind binary.

Follow the article to set the service to run automatically on system restart. You should never have to enter the bitcoin command directly in the shell. Always let the system start it automatically as a service.

After that, you must check with your hosting provider (the provider who supplies the server for your bitcoin daemon) to see if there are any firewalls, blocking incoming communication with TCP port 8332. Also check any local firewalls that you may be running, such as ufw.

Can I control which users have a wallet?

Yes, simply assign the has_wallets capability to the appropriate users or user roles. You should also assign more capabilities, such as list_wallet_transactions, send_funds_to_user, and withdraw_funds_from_wallet.

You can control the capabilities per user role by navigating to: SettingsBitcoin and Altcoin WalletsCapabilities.

Can I use the plugin to create an investment / interest paying site?

Yes, you can use the premium Airdrop extension to perform recurring airdrops. These can effectively be paid out in the form of an interest on the user’s wallet.

Can I use the plugin to create a WooCommerce store that accepts cryptocurrencies?

Yes, you can use the premium WooCommerce Cryptocurrency Payment Gateway extension. With it, users can use their on-site balance to checkout their shopping carts.

Can I use the plugin to create a crypto faucet?

Yes, you can use the premium Faucet extension to let users earn crypto by solving CAPTCHAs.

Can I use the plugin to create a crypto exchange?

Yes, you can use the premium Exchange extension to create market pairs. However the markets are local only, which means that no liquidity is imported from other exchanges. Read the disclaimers.

Can I use the plugin to do a token sale?

No, this plugin is not suitable for token sales.

However, you could, of course, setup markets using the Exchange extension, and set a large limit sell order with your admin account. This will allow users to buy your shillcoin. You can even disable buying or selling separately.

Can I use the plugin to accept tips for articles?

Yes, you can use the premium Tip the author extension. This lets you attach a tipping UI to posts/articles. You can control where the tipping UI is shown, by post type, category, tags, or even author. Only authors with the receive_tip capability can receive tips, and only users with the tip_the_author capability can send tips.

Can I use the plugin to create a paywall?

Not yet. However, a premium extension to let you do just that is currently in development.

How can I change the plugin’s code?

The plugin and its extensions are yours to edit. You are free to hack them as much as you like. However, you are generally discouraged from doing so, for the following reasons:

  • I cannot provide support to modified versions of the plugin. Editing the code can have unintended consequences.

  • If you do any modifications to the code, any subsequent update will overwrite your changes. Therefore, it is not recommended to simply fire away your favorite editor and hack away themes or plugins.

Whenever possible, use an existing hook (action or filter) to modify the behavior of the plugin. Then, add your code to a child theme, or in separate plugin file. Any PHP file with the right headers is a valid plugin file.

If you can’t find a hook that allows you to do the modifications you need, contact me to discuss about your need. I may be able to add a hook to the next patch of the plugin.

Why is my CSS not being applied to the UI elements?

This is usually due to the plugin’s CSS rules hiding your own rules. Don’t just spam !important, instead take the time to study CSS rule specificity. If you are unsure how to apply a particular rule on the plugin’s UIs, you can contact me.

How can I change something in the UI elements?

There are several ways to do this, depending on what type of change you want to apply. Please check the documentation under Frontend and ShortcodesModifying the UI appearance.

How can I perform transactions from my PHP code?

There are two ways to do this:

  1. You can create DSWallets\Transaction objects, populate all the fields, then save the obects to the DB. For details, check the documentation under: Developer referenceWorking with custom post type objects, and the PHPDocumentor page for the Transaction class for example code.

  2. You can use the Legacy PHP-API. This is compatible with previous versions of the plugin.

How can I perform transactions from the JavaScript frontend?

There are two ways to do this:

  1. You can use the WP-REST API. Consult the documentation under: Developer referenceWallet APIsWP-REST-API.

How can I change the wallet backing a particular currency?

It is possible that, for a particular cryptocurrency you may want to replace the wallet backing it with another wallet. For example, you may be offering Bitcoin via the CoinPayments service, and want to start using a Bitcoin core full node wallet. Or you may be using Bitcoin core, and you want to move to a new wallet.dat file.

This has become a lot easier with versions 6.0.0 and later, because Currencies and Wallets are now decoupled:

  1. Create the new Wallet with the built-in Bitcoin adapter for full nodes. Connect to your new full node wallet.
  2. Edit your Currency, in this case, Bitcoin. Set the Wallet to your new full node wallet entry, and Update the Currency.
  3. Transfer the hot wallet balance from one wallet to the other. Transfer all the funds to an address generated by new Hot Wallet. The address must NOT be a deposit address assigned to a user. For example, you can use the deposit address shown in the Cold Storage tool for your new wallet.
  4. Delete all the old deposit addresses for that currency. This will force the plugin to generate new deposit addresses from the newly connected wallet.
  5. Inform your users that they must no longer use the old deposit addresses, if they have them saved somewhere.

If unsure about this process, please contact me.

How does the plugin work in multisite installations?

How it works depends on whether the plugin (and its extensions) are network-activated or not. In network-activated setups, users have one balance ber currency, across all sites the network. If the plugin is NOT network-activated, users have a different balance on each site on the network, and each site can have different currencies and wallets.

Note that the plugin and its extensions MUST either all be network activated, OR all must be activated on individual blogs. Do not mix-and-match network-activated and non-network-activated wallets plugins.

Consult the documentation section Multisite for more information.

How to handle a hack/cyberattack?

While the latest WordPress version is often secure, the same cannot be said about all the WordPress plugins out there. Every day new security vulnerabilities are found involving WordPress plugins. Since WordPress is such a popular software platform, it gets a lot of attention from hackers.

Take an immediate backup of the site, and the server it runs on, if possible. This will preserve any traces that the hackers may have left behind. Funds theft is a crime and you can report it to the police, just like any other hack.

It’s best if you are prepared beforehand: Keep the software on the site updated regularly. Take the time to harden your server and WordPress installation. Try to use only reputable plugins on your site and keep them updated. Use a security plugin.

Finally, only keep a small percentage of the user balances on the hot wallet, utilizing the Cold storage feature to transfer the remaining funds to offline wallets. That way, in case WordPress is compromised, you don’t lose all your users’ funds! Please take wallet management seriously. There is no software that will automatically do opsec for you. Have a plan on how to act in case of theft.

If you think you have discovered a security vulnerability in this plugin, please let me know over email (not on a public forum).

How can I become a premium member and get access to the app extensions?

Paying members can download the available App extensions and can download updates to those extensions.

Study the available Membership plans

What payment methods are available

The site accepts Bitcoin and Ethereum. Please deposit the correct amount to your account, then choose a subscription.

Since 1 November 2022,
membership is implemented using the plugin itself. The downloads are protected behind a paywall
using the Paywall extension.

Previously the site accepted PayPal recurring payments. If you have already signed up using PayPal, you can continue to use it to pay for membership. New PayPal accounts are no longer available.

If you wish to pay via a different method, contact me by email.

You can send a PayPal payment to my business email address and let me know. I will then activate your membership manually, within 1 business day.

I cannot download the premium plugins after paying for membership.

If you have paid for an EU business plan, you must provide a valid VATIN. Please enter the VATIN without the country code prefix, and enter the correct City and Country for your business, in your profile details.

If you have paid for a regular plan, and for some reason you still cannot download the premium plugins, please contact me by email.

How can I cancel my membership?

If you have signed up with a PayPal recurring payment, you can go to your PayPal dashboard to cancel the recurring payment.

Additionally, if you wish, you may delete your account from the profile screen on the dashed-slug website. Deleting your account does not automatically cancel your PayPal subscription. Simply visit your profile

If you have paid via cryptocurrencies, there is no need to cancel. You can delete your account if you want, by visiting your profile. There is usually no need to do so.

I am not happy with the plugin. Can I ask for a refund?

You can ask for a refund of any payment within 30 days from the day of payment, no questions asked. Please contact me by email.

Are you available for custom development work?

Unfortunately I am not available for custom development work.

Can you install the plugin for me?

I do not undertake installations. I remain available to assist and answer any questions about the installation and configuration process.

Regarding plugin installations, please consider this: Unless you know how the plugin works, you will not be able to provide support to your users, or fix issues when these arise. If you are not a developer, you should probably hire a developer to perform the installation and maintenance.

Can you add XYZ feature?

You can always suggest a feature to me. If it makes sense and I have the time, I might implement it. I do not make promises on this, therefore I do not accept payment for features.

I am encountering some problem or I have another question.

First check the Troubleshooting section of the documentation. The answer to your question may be listed there.

If you cannot find the answer to your question, please consult the documentation under Contact Support.

How can I reach you over IM?

I speak daily with many people, while I also do the development, testing, management, marketing, and everything else.

For this reason, I am NOT reachable over chat apps.

Please state your request on the forums or over email, and I will respond within 24 hours, Monday to Friday. If you are encountering an error, please show me the error message in a screenshot. Try to explain what you did so far and how you arrived at the error.


April 13, 2024 2 replies
A very interesting person.I ordered a plugin from him.I paid, but I can’t download it.I write to him, he writes to me.As a result, minus a week of time, minus 10 euros of money and no plugins.But I had an interesting time.Thank you Alex.
December 3, 2020 1 reply
I appreciate all your efforts on this plugin. It solved all my issues, thank you
Read all 27 reviews

Contributors & Developers

“Bitcoin and Altcoin Wallets” is open source software. The following people have contributed to this plugin.


“Bitcoin and Altcoin Wallets” has been translated into 1 locale. Thank you to the translators for their contributions.

Translate “Bitcoin and Altcoin Wallets” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.



  • Fix: Issue preventing the plugins from running on Windows (XAMPP).
  • Fix: Deprecation warning in WP-REST API currency endpoints.
  • Fix: Plugin header now correctly indicates that the plugin requires PHP 7.0 or later.
  • Fix: DSWallets\Transaction objects now correctly load the timestamp field from the DB.


  • Fix: Issue with Fiat Withdrawals not checking for the has_wallets capability correctly is now fixed.
  • Add: Extensible way to exclude some currency tags from [wallets_deposit] and [wallets_withdraw] shortcodes, for the upcoming Taproot Assets adapter.


  • Fix: Clicking the re-scrape button in Bitcoin-like wallet adapters now refreshes the page again.


  • Fix: Issue introduced in 6.2.0 where wallets were prevented from being enabled/disabled, now fixed.
  • Fix: Minor warning in logs when saving bitcoin wallet adapters.
  • Add: The debug tab in the Dashboard panel now shows the database version.
  • Add: Mention of rpcbind in accompanying installation instructions.


  • Fix: Issue introduced in 6.2.0 where the wallet admin screen would crash on new installations is now fixed.
  • Add: Generic error handling for when the metabox of a wallet adapter crashes.
  • Add: New REST API endpoint for retrieving an Address by its post ID. See the REST API documentation for details.
  • Change: The wording for the description for the “Contract Address” field under Addresses is now changed to include Taproot Asset IDs for the upcoming tapd Wallet adapter.


  • Add: New feature for Bitcoin Core (and similar) wallet adapters: Admin can now restart scraping from a specific block height.
  • Fix: If another theme or plugin loads an old version of Parsedown, causing ParsedownExtra to fail to load, the documentation viewer falls back gracefully to whatever Parsedown is currently loaded.
  • Change: The “Contract address” field for “Currency” entries can now accept Asset ID hex strings. This is necessary for the upcoming Taproot Assets Wallet Adapter.
  • Improve: If cron jobs are not running, the warning message in the admin screens now links to the relevant documentation.


  • Fix: Fixed issue where the PHP curl library would not return meaningful error messages to the admin user in case of connection failures.
  • Add: When actions are initiated via the frontend UIs by clicking a button, the button is now animated until the action completes. Additionally, the actions are performed asynchronously for a better user experience.
  • Remove: Duplicate display of Confirmation link in withdrawal transactions is now removed. The Confirmation link is shown once at the top left part of the screen.
  • Remove: The “post slug” metaboxes are not useful and have been removed from the following CPTs: Wallets, Currencies, Addresses, Transactions.
  • Remove: The plugin’s CPTs are no longer available to be added to frontend menus, since the posts themselves are only useful in the backend.
  • Add: The PHP templates now come with a warning about not editing the templates in-place. The warning links to the documentation where the admin can learn more about this.
  • Add: Troubleshooting section in documentation now has more information on how to restore the manage_wallets capability to the admin user.


  • Fix: Silly syntax errors introduced right before summer vacation.


  • Add: New setting allows for deposits to be ignored if they have a timestamp earlier than a set cutoff value.
  • Add: When initiating an addresses and balances-only migration, the deposit cutoff value is set to the current timestamp.


  • Fix: Issue introduced in 6.1.6 which prevented admin transaction editing is now fixed.
  • Fix: If you have setup walletnotify for Bitcoin core and similar wallets, the notification API is now disabled while migration is underway.
  • Change: The walletnotify and blocknotify WP-REST API endpoints associated with Bitcoin core and similar wallets now returns uniform error messages. The HTTP status is not always 200, but reflects the error that was encountered. The value of the returned status field is no longer success/error but is the HTTP response code, which is 200 when the call was successful.


  • Change: In the plugin’s general settings, the maximum deposit address limit is now applied per user and per currency. Was previously applied per user only over all currencies.
  • Fix: When listing transactions in the admin screens, if the associated currency has block explorer URIs, these are now used to link addresses and TXIDs to a block explorer.
  • Add: New filter wallets_tags_exclude_min_withdraw allows a currency’s minimum withdrawal amount to not apply to transactions with the specified tags. This will allow the upcoming lnd extension to bypass this restriction for Layer2 transactions.
  • Improve: Transactions that are not modified will no longer be re-written to the DB. This improves performance, plus it allows the last modified timestamp to remain intact in case of no actual modification of transaction data.
  • Fix: The new mechanism for detecting whether a camera is available for scanning QR-Codes, introduced in 6.1.4, was buggy and is now fixed.


  • Fix: Usage of words “debit” and “credit” is now correct according to how the terms are used in everyday language, as opposed to their usage in accounting.


  • Fix: Shortcode [wallets_fiat_withdraw] does not submit withdrawal requests with invalid amount.
  • Add: Shortcode [wallets_fiat_withdraw] now accepts atttributes: currency_id, symbol to specify the default currency.
  • Add: New WP-REST API endpoint /users/U/currencies/C for retrieving a single currency C and the balances of user U for that currency.
  • Improve: Added a new withdrawal check: It is now impossible for a withdrawal to be executed as long as it has a TXID assigned. If you need to repeat execution, you must clear the TXID.
  • Improve: The [wallets_withdraw] UI now uses a getUserMedia() call to determine if a camera is available to scan QR-Codes. Previous method using CSS media queries was not optimal.
  • Improve: The included copy of moment.js is now upgraded to version 2.29.4.


  • Fix: Setting the currency_id attribute on the [wallets_deposit] shortcode now works again.
  • Fix: Listing the addresses of a specific user now works again.
  • Fix: Listing the addresses of a specific type (deposits, withdrawals) now works again.
  • Improve: The transactions editor now loads faster on sites with many thousands of users. The user dropdown is replaced with an text input where you type a user_login and it autocompletes with AJAX.
  • Improve: It is now possible to search addresses by keyword, and the keyword is matched against the address title AND the address string.
  • Add: Addresses with the archived tag will not be shown in the REST API and frontend. This will be useful for the Lightning adapter later, among other things.


  • Fix: Issue with editing transactions in admin when system holds too many transactions is now fixed.


  • Fix: Issue with transactions search in admin is now fixed.
  • Fix: When editing wallet adapter settings, it is now possible to uncheck boxes for boolean values.


  • Add: New option “Admin must approve withdrawals”. When on, pending withdrawals must be approved by an admin in the Transactions list screen using the “Approve” batch action.
  • Add: The frontend “VS amounts”, i.e. the equivalent amounts expressed in “VS currencies”, are now shown with a number of decimals that is configurable by the admin.
  • Add: Admin can now search transactions by TXID.
  • Fix: Admin can now search for cancelled or failed transactions.
  • Fix: When filtering posts, all enabled filters are now shown in bold and with ARIA accessibility attributes.
  • Add: For pending withdrawals, admin can view the results of withdrawal pre-checks.
  • Fix: Daily withdrawal counters for currencies are now correctly enforced at all times.
  • Add: Daily withdrawal counters are now visible in the profile screen of each user.
  • Add: For pending withdrawals, developer can add withdrawal pre-checks with action wallets_withdrawal_pre_check and with filter wallets_withdrawals_pre_check.
  • Fix: When showing [wallets_account_value] shortcode without any enabled “VS currencies”, the account value is now shown as ‘?’ and not ‘Undefined ?’.
  • Fix: Documentation updated to reflect changes in premium plugin payment method and added mention to new Paywall extension.
  • Fix: Improved logging for wallet adapters cron task.
  • Fix: Added guard clause in currency icons cron task to protect against missing returned data from remote service.


  • Change: Sourcecode rewritten from scratch and modernized for PHP7.x compatibility: Namespaces, callbacks, etc.
  • Change: Coin adapters removed and replaced with wallet adapters. Wallet adapters are a more versatile abstraction of external wallets.
  • Change: All amounts stored on the DB are now stored as integers. This avoids FP/rounding errors, but requires the admin to specify the number of decimals on a Currency explicitly.
  • Add: Wallets now have their own CPT and editor screen. Connection information for wallet APIs is now decoupled from currency details.
  • Add: Currencies now have their own CPT and editor screen. Currency details are now decoupled from wallet connection information details.
  • Change: Currencies are no longer identified by their ticker symbol, since these can clash. Currencies are now uniquely identified by their post ID.
  • Change: Transactions now have their own CPT and editor screen. Transactions are no longer stored in custom SQL tables, but are stored as posts.
  • Add: If a transaction is saved without a comment, a basic comment is entered as a title.
  • Change: Addresses now have their own CPT and editor screen. Addresses are no longer stored in custom SQL tables, but are stored as posts.
  • Add: When creating a new address, if admin sets the address string empty, a new address string is created from the wallet.
  • Add: Currencies, Transactions and Addresses can be organized via tags. These are implemented as WordPress custom taxonomies.
  • Add: When listing Wallets, these can be filtered by Wallet Adapter type.
  • Add: When listing Currencies, these can be filtered by associated Wallet or Currency tag.
  • Add: When listing Transactions, these can be filtered by Currency, User, Type (deposit/withdaw/move), Status (pending, done, cancelled, failed), or Transaction tag.
  • Add: When listing Addresses, these can be filtered by Currency, User, Type (deposit/withdaw/move), Status (pending, done, cancelled, failed), or Transaction tag.
  • Add: When editing Wallets, Currencies, Transactions, or Addresses, there are now metaboxes that let an admin easily jump between associated CPTs. For example, can click a link to go from a Currency to the Transactions of that Currency.
  • Add: A new “Migration” tool helps users transfer balances from the old custom SQL tables to the new format. Please study the documentation for details.
  • Add: A new Object-Oriented way to create and manipulate Wallets, Currencies, Addresses and Transactions. Lots of example code snippets included in the docs and PHPdocumentor files.
  • Add: A documented library of helper functions can be used by PHP developers to interface with the plugin. This lives in the DSWallets namespace.
  • Change: The old PHP-API is renamed as “Legacy PHP-API”, but not removed. Only the wallets_api_adapters filter is removed, since there are no more Coin Adapters.
  • Add: A new cron job scheduler that runs jobs based on priorities. Can be triggerred externally to improve site performance.
  • Add: New email queue system based on cron, handles large volumes of outgoing emails by sending them in batches.
  • Add: New cron job that iterates over defined currencies and pulls icons/logos from CoinGecko when possible. Adds images to the WordPress media collection, and sets the logo as Currency featured image. Admin can override the featured image.
  • Change: All the plugin’s settings are now placed under the Settings menu, and organized in tabs. Extensions, when installed, add tabs to the settings screen.
  • Change: Capability settings are now in a settings tab. The existing capabilities are retained. It is also possible to edit the capabilities related to the new CPTs (Wallets, Currencies, Addresses, Transactions).
  • Add: Fiat currencies are now created automatically by a cron job when you enter a API key. Fiat currencies can be associated to the built-in wallet adapter that handles manual Bank transfers. The Fiat Coin Adapter extension is removed.
  • Change: It is now possible to define any number of Bitcoin-like wallets and currencies without any plugin extensions. The Full Node MultiCoin Adapter extension is removed.
  • Change: The UIs are now self-contained. All the HTML markup, knockout.js attributes, JavaScript code, and CSS rules are encapsulated within the template files, and are overridable.
  • Change: The UIs are now rendered independently. This improves frontend performance. If one UI crashes, the remaining UIs continue to work.
  • Remove: There are no more static templates. All templates are dynamic. This reduces confusion about how templates work.
  • Add: Currencies can be used by users even if not associated with a Wallet, or if the wallet API is unreachable. If wallet API is unreachable, only deposits and withdrawals will not be available, but on-site transactions are still possible.
  • Add: New shortcode [wallets_status] informes users if a wallet is online.
  • Change: The exchange rates mechanism now relies on CoinGecko. If the admin provides the CoinGecko ID for a Currency, the exchange rates are retrieved automatically via cron.
  • Improve: In the Currency editor, if a currency is not associated with a CoinGecko ID, it is still possible for an admin to setup a fixed exchange rate for a currency.
  • Improve: The admin can choose against which well-known currencies the exchange rates are stored (these are the “VS currencies” and correspond to CoinGecko data).
  • Improve: The frontend UIs, when they display equivalent amounts in other currencies, no longer display amounts in one fixed site currency. User can click to rotate between displaying the equivalent amounts in all available “VS currencies”.
  • Add: Daily withdrawal limits per Currency. Can be set for all users, or per user role.
  • Add: More information in the plugin’s widget in the dashboard screen.
  • Add: A new WP-REST API which utilizes the RESTful API mechanism built into WordPress replaces the old JSON-API.
  • Change: The old JSON-API is now marked as deprecated and is disabled by default. Can be enabled in settings for backwards compatibility.
  • Add: A new system that displays documentation in the admin screens. Some screens feature direct links to the relevant documentation. As extensions to the plugin are installed, their documentation books are added to the system.
  • Change: The user profile screen has been improved. Lists all balances held by a user and links to the user’s lists of Addresses and Transactions.
  • Change: The cold storage UI screens have been improved.
  • Remove: The frontend Widgets have been removed. Please use the shortcodes instead.


  • Fix: The shortcode [wallets_depositextra template="static_textonly" symbol="???"] now displays address extra info correctly if such info is present.
  • Fix: Another issue related to the display of the cold storage screen.


  • Fix: Issue while sending emails to names that contain a comma symbol (,) is now fixed.
  • Fix: Prevent issue in cold storage screen that caused error in PHP8 and warnings in PHP7 or earlier.
  • Change: Referral links in cold storage screen are now updated.


  • Improve: When crypto ticker symbols clash with fiat ticker symbols, fiat symbols take priority for now. This issue will be ultimately fixed in the next major release.
  • Improve: Using blockchair as the default block explorer for multiple well-known cryptocurrencies.
  • Fix: Added guard clause to suppress minor warning in admin editor.


  • Improve: The exchange rates for coins with a dot in their symbol (e.g. USDT.ECRC20) are those of the coin with symbol only the characters before the dot (e.g. USDT). This mostly helps the CoinPayments adapter.
  • Fix: Bad logic in wallets_transaction action prevented confirmation counts from updating on withdrawal transaction notifications. Is now fixed.


  • Fix: If, during a withdrawal, a coin adapter fails due to a phpcurl timeout, consider the withdrawal done, not failed. Fixes double-spends with Monero or TurtleCoin forks on slow wallets.
  • Fix: In some situations, email notifications to admins about transaction verifications were not being sent. This is now fixed.
  • Change: By default, withdrawals are now executed once, for extra safety. This number of retries can be changed in the cron job settings.
  • Fix: If a coin adapter throws on get_block_height(), this no longer crashes the “Coin Adapters” admin screen.


  • Fix: Bug with network_active plugin in the admin screens “Deposit Addresses” and “User Balances”, is now fixed. Some data from other blogs was previously not shown.
  • Fix: The Bitcoin RPC coin adapter now recommends that the admin enters into the .conf file: rpcbind=IP where IP is the address of the hot wallet, not the WordPress host.
  • Fix: Typo in documentation.
  • Add: Link to pre-release notes for the upcoming Bitcoin and Altcoin Wallets 6.0.0.


  • Fix: Reverting change from 5.0.11. The original way to store data was to always maintain one set of tables for all the sites in a network. See release notes for details.


  • Fix: When activating the plugin on a single site, on a network WordPress installation, the plugin now creates the independent DB tables correctly, for each site on the network.


  • Add: PHPdoc for the wallets_get_template_part as per the WordPress coding style.
  • Add: New button in [wallets_withdraw] and [wallets_move] now allows users to easily transact their entire available balance without typing the amount.


  • Fix: Issue with deposit timestamps not being inserted into some DBs is now fixed.
  • Fix: Issue with [wallets_transactions template="rows"] introduced in version 5.0.6 is now fixed.
  • Fix: Previously issuing an internal transfer (move) via the PHP API with skip_confirm=true would not trigger email notifications, is now fixed.


  • Fix: Maximum number of symbol characters changed from 8 to 10. Allows for USDT.ERC20.
  • Improve: Some DB columns now use the latin1_bin character set to save space and help with DB indexing. Affects new installs.
  • Add: The debug tab in the admin dashboard now reports the type of Object Cache that is currently active.
  • Improve: In the coin adapters list, the withdrawal lock icon is now accompanied by text. This solves issues where the combination of font and screen antialiasing makes the state of the padlock difficult to read.


  • Fix: Issue with shortcode [wallets_deposit template="list"], introduced in 5.0.6 is now fixed.
  • Fix: Dynamic shortcodes [wallets_deposit] and [wallets_withdraw] apply the HTML classes crypto-coin and fiat-coin according to the selected coin in those UIs, not the page-wide selected coin, which could be a custom coin (Fiat Coin adapter extension).


  • Add: Many elements in the frontend templates now have the HTML classes crypto-coin and fiat-coin to allow differential styling of fiat and crypto coin information.
  • Fix: When full node adapter RPC settings are saved, the cached value of the adapter status is evicted, forcing an immediate refresh of the adapter status in the admin screens.
  • Fix: Already minified JQuery UI CSS is no longer re-minified.
  • Add: Several new shortcode templates and shortcodes allow for displaying “textonly” values. e.g. [wallets_api_key template="textonly"] displays the user’s API key in a <span> tag that can be inserted in text paragraphs.
  • Fix: Some HTML classes that were previously doubled are now fixed, e.g. deposit-deposit, etc.


  • Change: In confirmation/notification templates, ###USER_LOGIN###/###OTHER_USER_LOGIN### is no longer described as “account nickname”, since it is the user_login and not the nickname.
  • Add: In confirmation/notification templates,###USER_NICKNAME###/###OTHER_USER_NICKNAME### is introduced as a variable that is substituted for the user’s nickname.
  • Change: Confirmation/notification templates now use the variable ###EXTRA_DESCRIPTION### to accurately display the name of the extra description (such as Payment ID, Memo, etc.)
  • Add: New column in coin adapters list indicates max block height up to which the wallet is synced for compatible coin adapters.
  • Fix: Coingecko exchange rates are now loaded with asynchronous buffering, to prevent high memory usage.
  • Add: New TurtleCoin adapter is showcased in the “About” admin screen.


  • Fix: In [wallets_balance template="static"] the symbol next to the equivalent (fiat) amount was incorrect, is now fixed.
  • Add: Variable substitutions in email templates now allow for new variables: ###USER_LOGIN###, ###OTHER_USER_LOGIN###, ###USER_NICENAME###, ###OTHER_USER_NICENAME###, ###DISPLAY_NAME###, ###OTHER_DISPLAY_NAME###
  • Change: The variable substitution ###USER_ACCOUNT### is now deprecated. New email templates use the user’s display name by default (###DISPLAY_NAME###).


  • Fix: Exchange rates subsystem no longer attempts to access the old public CoinMarketCap API that has been recently discontinued. An API key is now required, no longer optional.
  • Improve: The efficiency of CoinMarketCap API queries has been improved, both in terms of performance, and API debits used.


  • Improve: More JavaScript assets are not loaded if not needed in current front-end page. This also prevents unneeded JSON-API hits when not logged in.
  • Add: Map files for minified knockout-validation.js and sprintf.js assets are now added.
  • Add: Instruct users to use square brackets when entering IPv6 IP addresses.
  • Fix: Undefined warning in dashboard prevented TX count totals from being shown, is now fixed.
  • Fix: Warning shown in logs when stats on previous cron run were not available, is now fixed.
  • Fix: When plugin is NOT network-activated on a multisite installation, the cron job trigger URL now displays the correct sub-site domain.
  • Fix: Transaction summaries dashboard widget, introduced in version 5.0.0, is now shown in network admin dashboard if plugin is network-activated.
  • Change: Upgraded included library knockout.js from 3.5.0-rc2 to 3.5.1.
  • Change: Upgraded included library knockout.validation.js from 2.0.3 to 2.0.4.
  • Change: Upgraded included library bs58check.js from 2.1.2 to latest commit.
  • Change: When plugin is network-activated, the Admin Transactions list screen displays domains without a trailing slash.


  • Add: The coin adapters admin page now includes a helpful link to a page explaining the concept and showcasing the available coin adapters.
  • Improve: The template loader introduced in 5.0.0 is improved to allow use by other extensions.
  • Change: The JavaScript code that detects HTML comments that have been stripped by minifiers now outputs to the browser console, not alert box.
  • Fix: When adding a deposit UI via the Widgets admin screen, the default size for the QR code is no longer 10 pixels. It is now blank, which sets the size automatically to match the container.
  • Fix: Incompatibility with Two Factor Authentication plugin that was originally fixed in 4.3.1 regressed in version 5.0.0 but is now fixed again.
  • Fix: Remove unminified copy of jQuery UI stylesheet.
  • Fix: A CSS issue previously made it impossible to remove wallet widgets from the admin widget area, on desktop screens. This is now fixed.


  • Improve: The UIs are now more easily overridable by themes. A template loader can load markup for these UIs from a theme or child theme, falling back to the plugin’s templates if needed.
  • Change: The wallets_views_dir attribute and filter are removed. Use theme templates instead to provide your custom markup.
  • Add: The [wallets_withdraw] shortcode can now scan addresses from QR code in devices that support it.
  • Add: The opacity of UIs while loading data over AJAX can now be controlled in Customizer.
  • Add: The border radius of UIs (corner roundness) can now be controlled in Customizer.
  • Add: The colors used in [wallets_transactions] shortcodes to signify transaction status can now be changed in Customizer.
  • Add: Admin dashboard widget now shows multiple tabs with statistics on recent transactions.
  • Add: When the plugin is network-active across a multisite install, the admin transactions list shows extra column Site.
  • Improve: All operations that modify transaction data now also refresh the time on the updated_time column.
  • Improve: Better integration with Simple History plugin. Transactions are now logged with clearer information, including links to user profiles and block explorers.
  • Improve: The cold storage admin screens now also display the amount of funds locked in unaccepted & pending transactions.
  • Add: The third-party service is now available as an Exchange Rates provider.
  • Improve: In admin transactions list screen, amounts are now in fixed-font and align vertically for easier visual inspection.
  • Improve: For Bitcoin-like adapters, the RPC secret is not shown in the markup, but bullets are shown instead. Improves security.
  • Add: The [wallets_api_key] shortcode can now be used as a widget.
  • Fix: Adapters for fiat coins are no longer shown in the cold storage section, as these adapters are not backed by wallets.
  • Improve: The Bitcoin address validator used in [wallets_withdraw] now correctly allows Bitcoin testnet addresses. Useful for testing using testnet.
  • Improve: When creating database tables for the first time, the WordPress default is used for character collation and encoding.
  • Fix: When Bittrex is used as an Exchange Rates provider, if the last price is not available, the plugin falls back to using the average of the Bid/Ask values, or one of the two values if only one is available. Helps determine exchange rates in low liquidity markets.
  • Improve: In the [wallets_balance template="list"] UI, the text “Show zero balances” is clickable and toggles the checkbox. Improves usability.
  • Improve: The plugin will now warn the user in the frontend if HTML comments have been minified, as this is a common pitfall for new users.
  • Improve: In the debug tab of the admin dashboard, memory values are now shown with thousand separators and units (bytes) for easier visual inspection.
  • Change: Bitcoin-like adapters now rescan the entire wallet’s transaction list from the start weekly rather than monthly. This is a fail-safe mechanism that detects transactions that would otherwise slip through undetected if curl calls from walletnotify were to fail for any reason.
  • Fix: Issue in email notifications for deposits, where the fees would not be shown correctly, is now fixed.
  • Add: The cron-related debug information from the admin dashboard is now also shown in the admin cron job settings screen for easier reference.
  • Change: Tradesatoshi is removed from list of Exchange Rate providers as the service is shut down.
  • Change: JavaScript assets are now loaded only in pages where they are needed. Improves frontend performance.
  • Fix: Issue with writing out CSVs when exporting transactions is now fixed.
  • Improve: When manually adding a transaction using the wallets_transactions action, it is now possible to specify an initial transaction status for withdrawals.
  • Fix: In admin adapters screen, sorting by pending withdrawals no longer triggers a warning in the debug logs.
  • Fix: When user requests a new deposit address via the [wallets_deposit] shortcode, the other deposit addresses are now marked as old, and only the new one is current.
  • Add: The [wallets_balance template="list"] UI now includes a column for unavailable balance, i.e. balance that is locked in pending transactions or trades.
  • Fix: The plugin now correctly calculates amount of wallet balance that is unavailable due to staking in more wallets, including PotCoin and Dash.
  • Change: The plugin now warns the admin if the available balance is less than 5% of the total balance (previously the threshold was 1%).
  • Fix: Some error messages that get printed only to the debug log are no longer translatable.
  • Improve: Reduce number of calls to is_plugin_active_for_network().
  • Fix: Some HTML markup errors in sidebar widgets are now fixed.


  • Fix: The capability repair cron job, introduced in 4.4.4 is improved to be more fail-safe. If no admin user has manage_wallets, it now assigns manage_wallets to all admins and to the Administrator role. Prevents admins from being locked out.
  • Fix: CoinMarketCap signup link (for API access) is now updated.
  • Improve: Admin menu icon follows style guide more closely (is a data-uri encoded SVG).
  • Fix: The JSON-API requests are now excluded from the service worker’s cache if the SuperPWA plugin is installed.


  • Fix: Workaround that restores compatibility with the Bitcoin ABC full node wallet (Bitcoin Cash), due to improperly deprecated accounts feature in that wallet (github issue #360).


  • Add: If a withdrawal cannot proceed due to low hot wallet balance, the withdrawal remains in pending state (would previously fail), and the site’s admin or admins receive emails about this.
  • Add: Italian translations for frontend, submitted by Fabio Perri,,
  • Fix: When reloading the User balances page, the ordering is now predictable and stays the same.
  • Add: User balances can now be sorted by balance and coin.
  • Fix: Affiliate link to trezor was broken in cold storage pages, now fixed.


  • Fix: Removed Novaexchange and Cryptopia from exchange rates providers since their APIs are now unavailable.
  • Improve: Attempt to disable PHP max execution time while importing transactions from csv files. Can help with importing very large files.
  • Add: The [wallets_move] shortcode will now auto-suggest usernames of people that the current user has had internal transfers with before.
  • Improve: Reduce HTTP timeout when retrieving exchange rates.


  • Fix: Several settings can now be saved on network-active installation, previously could not be saved.
  • Add: If no users in the Administrator role have the manage_wallets capability, this capability is assigned to the Administrator role.
  • Add: It is now allowed again to modify the capabilities of the Administrator user role via the WalletsCapabilities screen.


  • Fix: Issue where moment.js library was not loaded in 4.4.2 is now fixed.
  • Fix: When cron job selects old transactions to cancel, it now takes the local timezone into account.
  • Fix: When cron …