[alexg]

Hello,

This article guides you to:

1. install bitcoin from source

2. allow bitcoin on ufw

3. setup cron to start bitcoin on reboot

The instructions for installing from source are good.

The instructions for ufw are good if you are using ufw. This is a popular firewall for Ubuntu. If you are running a different distribution, you may have another firewall. This is why I suggested that you find an article for your distribution.

Also note that your hosting provider might be running firewalls around their network too that block access to your wallet’s RPC port.

The cron trick is something I haven’t tried, I usually set bitcoin as a service on systemd, but this may work too.

Please remember, system administration is not something that you can pick up from an article. It’s the details that get you. Can you set online backups for your wallet file? Can you check the logs if something breaks? Can you fix permission issues? Can you harden the security of your distribution? Can you keep the distribution packages updated to maintain security? All of these things are relevant when you are doing administration work.

If you are unsure about what you’re doing, then ask a professional for help. Otherwise you will be frustrated with all the details.

Best of luck

with regards

[alexg]

Hello,

You cannot run it on your Windows PC at home and expect to connect from your WordPress server.

You need to hire a dedicated Linux server to run it online. Also note the hardware requirements.

https://bitcoin.org/en/bitcoin-core/features/requirements

[alexg]

Hello,

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: LdaShEdER2UuhMPvv33ttDPu89mVgu4Arf

3. 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,
Alex

[alexg]

OK thank you for bringing this to my attention. Having looked more into this, I am decommissioning the ShapeShift extension.

It is no longer suitable for use by the plugin. The end user must sign in using OAuth2 to gain access to a number of wallets that can be extrernal, and therefore not relevant to this plugin.

If you need to provide exchange functionality, you can set up markets using the Exchange extension. If the markets have enough liquidity (limit orders on the orderbook), you can provide similar functionality using the [wallets_exchange_market_order] shortcode: https://www.dashed-slug.net/exchange-swap-ui-plus-theme-templating/

Apologies for the trouble.

[alexg]

@bayutec It looks like ShapeShift has changed since this extensions was released. They now promote shapeshift.com in favor of shapeshift.io.

The plugin extension was build to communicate with this API: https://docs.shapeshift.io/

The Satellizer token, also known as an “Authorization token”, is no longer available by default.

According to the documentation, you now have to contact support to ask for the Authorization Token to build an application/integration.

I will look more into this and update the plugin’s instructions accordingly. In the meantime, you could ask them to generate a token for you. You might have to describe to them the type of website you are building. Please let me know if you were successful to get a token from the support team.

with regards

[alexg]

Hello,

You would need to setup one wallet for each coin that is supported. I am not sure how many coins you had enabled. See the coin adapters list to determine which coins you can set up a wallet for. Forks of Bitcoin, Monero, and TurtleCoin are supported, while Ethereum, ERC-20 tokens and most stablecoins are not supported.

Starting with Bitcoin, yes, that is one way of downloading it. Please note that you will need some knowledge of Linux. If not, hire a developer or other technical person to do this. The installation is not hard, but it’s almost impossibly hard if you don’t understand Linux and the shell.

First see the requirements for the server that will run the bitcoin core client.

Set up the server that will run the wallet. Depending on what your Linux distribution is, it’s best to find installation instructions for your particular distro. For example, there are installation instructions for Ubuntu, Debian, CentOS, etc. Follow an article with instructions for your distro. If you need to build from source, you can use the github release from here, to be safe: https://github.com/bitcoin/bitcoin/releases/tag/v0.20.1

The plugin comes with a built-in adapter for Bitcoin core. (“Wallets” -> “Bitcoin Core Node (BTC)”) Enable it and configure it. I have some instructions here on how to do this: https://www.dashed-slug.net/bitcoin-altcoin-wallets-wordpress-plugin/installation-instructions/

If the wallet server is different to the WordPress server, you will also need to take care of any firewalls blocking communication.

Note that you should also turn the wallet into a service on your system. If the wallet crashes or if the system restarts, you want the wallet to be restarted and to be available again for the plugin. How you do this will again depend on your distribution. I have put some instructions here for systemd: https://www.dashed-slug.net/forums/topic/ssh-install/#post-6619

Hope this helps. As always, let me know if you have any questions.

with regards

P.S. For general information about installing Bitcoin Core, you can also get help from https://bitcointalk.org, https://reddit.com/r/Bitcoin/ and https://bitcoin.stackexchange.com/ The stackexchange QA site is excellent, lots of good info there.

[alexg]

It’s great to hear that you have the coins. That’s the important thing.

If you connect to an account that is not restricted, you could get blocked again, if you are contacting again from a now restricted country. As long as they can see a connection coming from an IP that belongs to your country, they can immediately ban the new account as far as we know. I am not sure about this, because I do not know how CoinPayments chooses to enforce their terms of service. If you were to use a server outside of your country that may be considered OK, but again I don’t know how their terms of service are interpreted.

If you manage to connect the plugin to a new account, however you do it, then the plugin will again show the same user balances and transactions. Here’s what you should do:

1. Go through the setup process for the new account: https://www.dashed-slug.net/bitcoin-altcoin-wallets-wordpress-plugin/installation-instructions-web-wallet/
Set the account’s API key permissions. Set the new secrets in the plugin settings. Enable the same coins on CoinPayments. And finally enable the same coins in the plugin settings.

2. Transfer all the user funds to the wallets of that new account. This will fill up the hot wallet balance.

3. Check to see, for each coin, that the hot wallet balance is equal to or larger than the sum of user balances.

Now the users can use the plugin again and/or withdraw their funds. You can inform them about this.

I hope to have helped, I understand that situations like these can be stressful. But all the data is in your database, and you have the funds. If it is possible for you to connect from an account that is allowed on the platform, then you can recreate the wallets without too much work.

Please contact me if you have any more questions.

regards and good luck

[alexg]

Hello,

There are several users of the plugin in your country, but this is the first time I hear about this. If what you say is true, several users will encounter issues.

A quick look confirms that your country is in the list of restricted countries: https://www.coinpayments.net/help-restricted

Your country was not on the list on the 1st of November: https://web.archive.org/web/20201101144751/https://www.coinpayments.net/help-restricted

But it was added on the 19th of November, so it must have been added within that timeframe: https://web.archive.org/web/20201119111917/https://www.coinpayments.net/help-restricted

There are two problems here. One is technical (your IP is being geo-filtered), and one legal (you are legally not allowed to access the service from your country).

There is little you can do for the legal aspect besides moving to another country. It’s their service and they can do whatever they want. But I would be surprised if they did not somehow return the coins to you. You should at least contact them about that.

This is exactly the reason why full node wallets are needed in the world: a full node wallet is borderless and un-censorable. If you use a third-party service you must play by their rules.

Unfortunately not all the coins supported on CoinPayments can be connected as full node wallets to the plugin, only the types of coins listed here: https://www.dashed-slug.net/howto-choose-between-available-coin-adapters/ Most notably, there is no ERC-20 adapter for the plugin at the moment.

For Bitcoin, Litecoin and other such coins, you could set up full node wallets and connect to them. If you do this, I can help you through by answering any questions you may have about the process. To see how you can swap a coin adapter with an alternative one, please see the FAQ under “I want to replace an adapter with another one.”

Hope this helps a little. Please let me know if you have any more questions for me.

with regards

P.S. As a sidenote, technically, you could bypass the GeoIP filter, if you used tor as an HTTP proxy. The CoinPayments platform allows anonymous connections via https://coinpaymtstgtibr.onion/. The CoinPayments adapter allows you to set a tor proxy under “Wallets” -> “CoinPayments” -> “HTTP Settings”. All of this is theoretical. I cannot actually recommend that you do this, because it might be illegal; I am not a lawyer, so I’m not sure. All I know is that if someone were to connect to the CoinPayments platform via tor, the platform would likely not know which country the connection was coming from. You would probably need to run a tor node on a server and connect to it. Again, this might not be allowed, so don’t do it if it’s not!

[alexg]

Hello,

At the moment it is not easy for me to change the existing UI because I am busy with the next iteration of wallets. However, it may be possible for you to modify the templates to produce the UI you describe.

Instructions on how to override the templates in your theme are at the wallets 5.0.0 release notes: https://www.dashed-slug.net/wallets-5-0-0/

Additionally I have provided recently some information on template editing here: https://www.dashed-slug.net/forums/topic/deposit-template/#post-9518

I’m attaching a sneak peek from wallets 6.0.0 (work in progress, will be out in Q2 of 2021):

If you are designing your own interface you can do it any way you like; all the data is there in the JSON-API. Ultimately this is just a design matter.

with regards

P.S. I have moved your query to a new thread since it is not related to your previous question.

Attachments:

You must be logged in to view attached files.

[alexg]

The admin sets the fees in the coin adapter settings via the admin interface.

Every coin adapter has its own way of doing this, but ultimately they all report back to the plugin 4 values: https://github.com/dashed-slug/wallets/blob/5.0.12/includes/coin-adapter.php#L555-L613

When you do a call to the get_coins_info JSON-API endpoint, you get back a number of fields for each coin.

The relevant fields for fees are: “move_fee”,”move_fee_proportional”,”withdraw_fee”,”withdraw_fee_proportional”:0

So, for an internal transfer, the fee paid will be move_fee + amount * move_fee proportional.

For withdrawals, the fee to be paid will be withdraw_fee + amount * withdraw_fee_proportional.

This allows for both fixed fees and fees that are proportional to the transacted amount.

with regards

[alexg]

Hello,

Transactions start off in the unconfirmed state.

As an admin, you choose in “Wallets” -> “Confirms” whether you are going to require withdrawals, and moves, to be confirmed by the user and by admin. (the slugs for these options are: wallets_confirm_withdraw_admin_enabled, wallets_confirm_withdraw_user_enabled, wallets_confirm_move_admin_enabled, wallets_confirm_move_user_enabled)

Transactions in the DB have two columns, admin_confirm and user_confirm. When these values are truthy, it means that the admin, or user, has confirmed the transaction.

The cron jobs periodically check the unconfirmed transactions that have category equal to withdraw or move. If all the required confirmations are there, the transaction gets the pending status.

You can set the user_confirm column to 1 for any transaction, and this will indicate that the user has confirmed the transaction. How you do the confirmation is up to you. Once the transaction becomes pending, it will go on to be attempted on a subsequent cron job run.

(All of this means of course that you will not be able to use your app with wallets 6.0.0, which is a complete rebuild of the plugin, and does away with the DB tables among other things. You will need to keep the wallets version to the latest 5.x. This is several months away. You should be ok with 5.x as it is going to be stable.)

Hope this helps.

with regards

[alexg]

Thank you. I have replied to your email.

[alexg]

Hello,

Refreshing the page is definitely not the way to go.

There is NO support for push notifications.

Instead, to achieve near-time data display, the frontend does polling on the JSON-API. Normally the plugin does this automatically and you can control this in the frontend settings admin screen (see: “Wallets” -> “Frontend Settings” -> “Live polling settings”.

If you are building an application, you should be doing the same. Issue polling requests to the JSON API and refresh the data that you display, accordingly.

The email confirmation can be disabled in the admin settings. Go to “Wallets” -> “Confirms”, and you will find options to disable confirmation requirement, separately for internal transfers and for withdrawals. You can also control whether an admin must confirm each type of transaction.

with regards,
Alex

[alexg]

Hello,

To override the default templates, first read this blog post: https://www.dashed-slug.net/wallets-5-0-0/

So in your case, you would want to copy to your theme the following file:

https://github.com/dashed-slug/wallets/blob/5.0.12/templates/deposit.php

You should place this file at:

/wp-content/themes/{theme or child theme}/templates/wallets/deposit.php

Then you can edit this file. Here’s some instructions:

1. Try to not mess the knockout.js data bindings (‘data-bind’ attribute), unless you know what you’re doing.

2. Try to preserve correct HTML markup.

3. Shuffle things around to your liking.

I’m not sure what your requirement is, but the name of the coin is shown under <label class="coin"> and the address is under <label class="address">. If you change the order of these things you can display them in a different order.

You can also use CSS for this. The specificity of your CSS rules must overwrite the rules in:

https://github.com/dashed-slug/wallets/blob/5.0.12/assets/styles/wallets.css

Hope this helps. Please let me know if you have any more questions about this.

with regards,
Alex

[alexg]

In addition to the above, please do the following:

1. Determine the user_id of this user. If you click on the user name, the user’s admin profile link will contain the user id.

2. Please run the following query, substituting USER_ID with the actual id number.

SELECT
	account,
	symbol,
	category,
	status,
	amount,
	fee

FROM
	wp_wallets_txs

WHERE
	account = USER_ID AND
	symbol = 'ARMS' AND
	(
		( amount < 0 && status IN ( 'unconfirmed', 'pending', 'done' ) ) OR
		( amount > 0 && status = 'done' )
	)
ORDER BY
	id;

3. Email me the result so I can determine the issue. Please send me the result as text rather than a screenshot, if possible.

To give you some background:

The user’s balance is the sum of the user’s transactions in a done state. Normally it is calculated here, but for this particular admin screen, it is calculated here.

The user’s “available balance”, is the sum of all the user’s transactions in a done state, plus any crediting transactions (amount<0) that are in an unconfirmed or pending state. It is always calculated with this code.

Thus, the “available balance” includes any outstanding withdrawals and transfers to other users, but not any outstanding deposits. It’s essentially the maximum amount that a user can withdraw, and should always be less than the total user’s balance.

Since in this case it is larger, I will need to go through each transaction to see what the problem is.

Looking forward to your reply.

with regards

[Author]

Posts