 Show Posts
|
|
Pages: « 1 2 3 [4]
|
Have you tried to add addnode=192.168.0.X:8333 under your Bitcoin.conf? X should be replaced with your full node IP where you want to connect to. You can also use the RPC command bitcoin-cli to addnode check this link below it will force you to connect to that node. - https://developer.bitcoin.org/reference/rpc/addnode.html You can also use connect=192.168.0.X:8333 and put it in your bitcoin.conf same goes for the RPC command as a reference link above. I don't think this is what I need because I do not want to connect to a new node, instead I want to ensure that local (running on localhost) services that need access to the 8333 port of my full node can always connect to it. |
|
|
|
You can try to use: -whitebind=<[permissions@]addr>
Bind to the given address and add permission flags to the peers
connecting to it. Use [host]:port notation for IPv6. Allowed
permissions: bloomfilter (allow requesting BIP37 filtered blocks
and transactions), noban (do not ban for misbehavior; implies
download), forcerelay (relay transactions that are already in the
mempool; implies relay), relay (relay even in -blocksonly mode,
and unlimited transaction announcements), mempool (allow
requesting BIP35 mempool contents), download (allow getheaders
during IBD, no disconnect after maxuploadtarget limit), addr
(responses to GETADDR avoid hitting the cache and contain random
records with the most up-to-date info). Specify multiple
permissions separated by commas (default:
download,noban,mempool,relay). Can be specified multiple times.
-whitelist=<[permissions@]IP address or network>
Add permission flags to the peers connecting from the given IP address
(e.g. 1.2.3.4) or CIDR-notated network (e.g. 1.2.3.0/24). Uses
the same permissions as -whitebind. Can be specified multiple
times. So using whitelist=127.0.0.1 would allow localhost not to be counted amongst the connections subjected to maxconnections, correct? Thanks! |
|
|
|
|
Hi,
On my (RPI) node I use maxconnections to control the maximum number of connections to my node, but my understanding is that this limit applies to both onion and regular connections. I am trying to connect to the 8333 port on my node from localhost, but my connection does not work and I think it is due to maxconnections being reached. So I am trying to reserve some connection room for my local services. How can I do that? Thanks!
|
|
|
|
|
Hi,
so if someone has a cold HD wallet and wants to use JoinMarket's sendpayment to spend only a fraction of the wallet, what is the proper way to do that? The only good way I can think of is to first move the required balance to a JoinMarket hot wallet, then use sendpayment, because otherwise add-utxo would be required, but I don't want utxo private keys from a cold HD wallet to touch the hot computer if that system has access to the HD pub key. Is that correct?
Another question I have is how much should I be concerned about the timing of transactions when using JM along with other transactions? Is it possible to figure out the original utxo (prior to the coinjoin) based on the timing of transactions (i.e. if the timing/velocity of my transactions from my cold wallet, to the JM hot wallet, to the final destination somewhat differs from the timing of transactions that involve the other CJ utxos)?
Thanks!
|
|
|
|
Spark works reasonably well and works with CLN's built in APIs. From reviews I have read, it said that the spark wallet can be used on Android without entering a phone's PIN... |
|
|
|
|
Hi,
I am new to lightning. I just finished installing c-lightning on my full node, but I cannot find any sensible mobile wallet that can connect to it using an onion address? It seems that Zap is defunct according to GitHub, Spark has serious security issues according to the reviews on the Google Play Store, and Zeus does not seem to be in a working state. All the other wallets I have found seem to only support LND? Is there a practical way to use C-Lightning with a phone?
Thanks for your help!
Assuming that there is working mobile wallet for C-Lightning, how do people use it in practice? Is it through RTL?
So initially I thought that wallets could connect directly to CLN, but after coming across RTL, I learned that the CLN's REST API is required. Another possibility would have been through CLN's JSON ROC I assume? RTL uses the REST API to control CLN. My Zeus wallet is now able to connect to the REST API as well.
Moderator's note: multiple posts merged
|
|
|
|
|
