[alexg]

For the record, this has now been implemented in version 2.3.1. Sorry for the long delay. 😊

[alexg]

Even if you have disabled your firewall, the hosting provider has their own firewall to protect their systems. You must contact them and ask them to add a specific exception for incoming TCP ports to your RPC port on your host’s IP.

Bottom line, the plugin must be able to contact the wallet. No other way around it.

[alexg]

Hello,

1. Ensure that rpcallowip is set to the IP of your WordPress installation in CIDR notation.
2. Ensure that rpcbind is set to the public-facing IP of your wallet node. This tells the wallet to listen on the correct NIC.
3. If your wallet node is on a hosting provider, contact your hosting provider, and ask them to open their firewall for your server and for incoming TCP connections to your RCP port.

Hope this helps. Please let me know if you continue to face problems.

with regards

[alexg]

If you are using a strong password with rpcpassword, does it contain the equals (=) character?

If so, you would be getting this problem. The equals character is used to assign values in the config file, and it can’t be used as part of the password.

[alexg]

Hello,

HTTP_UNAUTHORIZED simply means that you have not entered the username/password correctly.

Make sure that you understand the difference between using rpcuser/rpcpassword and rpcauth.

You should use either user/pass or auth.

(The values foo and bar I gave above are examples, you should replace them with the credentials you are planning to use.)

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

with regards

[alexg]

Hello! Try a simple config at first (the following is only for connecting from localhost, if your WordPress is elsewhere, change the IP):

server=1
rpcallowip=127.0.0.1/8
rpcbind=127.0.0.1
rpcport=8332
rpcuser=foo
rpcpassword=bar

If this works, then you can expand on it.

If you tell me what error you are encountering, perhaps I can help. You can also get general help on bitcoin core installation at: bitcoin.stackexchange.com

Hope you have a happy new year 2024!

with regards

[alexg]

In the latest version 6.2.0 of the plugin, it is now possible to set a block height to your wallet and the wallet will restart scanning for transactions from that height.

For more information, please see the documentation at:

https://github.com/dashed-slug/wallets/blob/6.2.0/docs/troubleshooting.md#i-am-unable-to-setup-the-transaction-notification-mechanism-on-a-bitcoin-like-full-node-wallet-how-can-i-ensure-that-transactions-are-eventually-scraped-from-the-wallet-and-appear-in-the-plugin

[alexg]

In the latest version 6.2.0, if the ParsedownExtra class is not loadable, then the plugin will fall back to whatever Parsedown was loaded by another component. This is not optimal, and some features of the documentation will not work correctly, but the documentation will be readable overall.

[alexg]

Hello,

OK, if you are only concerned with scraping one transaction, just notify the plugin about this TXID:

1. Create the deposit address on the plugin. Go to Addresses -> Add New, then set the User, Address string, Type: deposit, Currency, and hit Update to create the deposit address on the plugin.

2. Determine the post ID of the currency that was deposited. Let’s say it’s 123 for this example.

3. Determine the TXID of your deposit. You should be able to get this from the command line with:

litecoin-cli listtransactions

Let’s say your TXID is 01234566789ABCDEF

2. Let’s also assume your site is https://example.com . Visit the following URL in your browser:

https://example.com/wp-json/dswallets/v1/walletnotify/123/01234566789ABCDEF

This will force the plugin to look for this deposit and create it on the plugin.

If you want to restart the process of scraping transactions from the wallet: https://github.com/dashed-slug/wallets/blob/6.1.10/adapters/class-bitcoin-core-like-wallet-adapter.php#L934-L1024

First determine the post ID of your litecoin wallet (not currency). Let’s say your Litecoin Wallet ID is 456.

You will need to set the transient dsw_bitcoin_456_height to 1.

You can do this from the command line using wp-cli if you have shell access to your WordPress with the following shell command:

wp transient set transient dsw_bitcoin_456_height 1

Or you can do this using the wp-console plugin. Just type the following in the console (find the console on the top right on the admin screens):

DSWallets\set_ds_transient( ‘dsw_bitcoin_456_height’, 1 );

Note: Don’t change “bitcoin” to “litecoin”. “Bitcoin” refers here to the bitcoin wallet adapter, which is also used for litecoin.

You make a valid point in that there should be a button to easily restart the scanning process. I will add this for the next release.

Let me know if you have any more questions.

with regards

[alexg]

Hello and thanks for reporting this issue.

The error occurs because another plugin, or possibly even a theme, is loading an older version of Parsedown on your site.

If you want to find out which plugins use Parsedown, assuming you have shell access to your WordPress, you can do:

find /path/to/wordpress -name Parsedown.php

If it’s a plugin you don’t need you can uninstall it. Or you can tell the developer to update their plugin to the latest Parsedown.

Fortunately the documentation is markdown, so you can read it with any text editor or markdown editor: The documentation is in the docs folder of each plugin.

For the main plugin, you can also read the documentation online via the github pages:

https://github.com/dashed-slug/wallets/tree/master/docs

I will see if I can make the plugin not require ParsedownExtra in the next release.

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

with regards

[alexg]

Hello,

Thank you for reaching out.

Unfortunately I have decided that the Ethereum ecosystem is not one of my priorities, despite popular requests.

The Ethereum accounts model does not fit well with the plugin, which requires funds to be in one wallet despite what address they come from. It would require complex gas management to transfer funds from deposit addresses and the solution would be ugly, errorprone and costly

Furthermore, the framework you show me is a JavaScript framework, not a PHP framework. The plugin is a custodial (i.e. server-side) solution.

Finally, I want to give priority to developing support for taproot assets (aka tarot) when I find the time to do so.

If you or someone else is interested in developing a wallet adapter for the Infura API, I can provide some guidance. The place to start from is here: https://github.com/dashed-slug/wallets/blob/6.1.10/docs/developer.md#developing-wallet-adapters-wallet-adapters

Again, thanks for the suggestion. Sorry that I can’t give you a better answer.

with regards

[alexg]

Hello,

1. You would need to hire a Linux server with adequate system resources. Check the requirements for Bitcoin core.

2. Then, follow any installation instructions for Linux. For example: https://bitcoin.org/en/full-node#linux-instructions

3. Finally, follow the plugin-specifc instructions: https://github.com/dashed-slug/wallets/blob/master/docs/install.md

The plugin-specific instructions ask you to setup the bitcoin daemon as a service.

You would also need to setup automatic backups to your wallet file in a secure manner.

Finally, it’s not strictly necessary, but would be a good idea to harden your Linux installation’s security. How you do this depends on your distribution. For example, if you are on Debian: https://wiki.debian.org/Hardening

Start by installing Bitcoin core on a Linux server and let me know where you get stuck.

Please note, the advantage of this plugin is precisely the ability to connect to full node wallets. If you find it difficult to install and maintain a full node wallet, I am unable to undertake this for you. You may need to hire someone. However, I am always available to answer any questions you have about the process.

with regards

[alexg]

OK, I thought you had installed the lightning terminal because you managed to enter a tls.cert file. The installation instructions clearly call for installing the lightning terminal on Linux.

You can use bitcoin core, which also must be installed on a Linux server. The installation instructions are in the plugin’s documentation:

https://github.com/dashed-slug/wallets/blob/master/docs/install.md#install-a-bitcoin-core-wallet

If you have any questions please post in General Discussion. This forum is for the LND adapter.

[alexg]

Hello,

I logged in to check. You had entered the IP address of the WordPress host. Instead, you should have used the IP address of the host where you have installed the Lightning Terminal. Additionally, the IP address is a v4 address, so I removed the square brackets. Square brackets are for v6 addresses.

I am confused. You say that you are not using Linux. How did you follow the installation instructions then? Where have you installed the Lightning Terminal? The installation instructions require you to install the Lightning Terminal on a Linux host. Please clarify.

with regards

[alexg]

Hello,

I logged in to your site to investigate.

You are attempting to connect to an LND node on the localhost. However, the host is on a free WordPress hosting service that doesn’t seem to provide any SSH access. Have you really installed LND on the localhost?

You are attempting to connect to port 9050 on localhost, which is the WordPress server itself. However this port doesn’t appear to be open. I checked with: $socket = @fsockopen('localhost', 9050, $errno, $errstr, 5);

This returned an error indicating that there is no LND node, or other daemon, listening to this port on the WordPress host. Alternatively,

Also please note that, the gRPC port is 8080 by default. If you want to use 9050 instead, you should have also set this port in the lncli.conf file, before starting your lncli service. I don’t recommend that you use 9050, because that’s usually the Tor port, which you may want to use now or in the future. Using Tor is optional.

When the litd server starts, look for a log line that reads:

[INF] RPCS: gRPC proxy started at 127.0.0.1:8080

In this case 8080 is the gRPC port. The IP however will be the public-facing IP of the server, not 127.0.0.1.

If I’m wrong or I misunderstood something, please let me know.

To clarify, installing the LND wallet adapter requires you to install the Lightning Terminal on a Linux host.

I see that you have entered a tls.cert file, which indicates that you have installed lncli somewhere. Is it really on the same machine?

If you have installed the Lightning Terminal on another server, you should input the IP of that server into the “lnd host” field.

Conclusion:

1. If you have installed Lightning Terminal on a different server, change localhost to the IP of that server. Ensure that the port matches the gRPC port that your lnd node is listening to.

2. If you are certain that the host and port you entered is correct, then this is a firewall issue. Contact your hosting providers about this. You want the gRPC port to be available for incoming connections from the IP of your WordPress site. The hosting providers of the server where the Lightning Terminal is installed will be able to help you with this.

Hope this helps. Please let me know if you had success with the installation or if you encounter any more difficulties.

with regards

[Author]

Posts