How do you insert an array, or in this situation the destination, properly? There are lots of ways I can think of...
Code:
node1, node2
{node1, node2}
[node 1, node2] etc.
None of the above works.
Topic: The Lightning Network FAQ - page 21. (Read 33787 times)
How do I open multiple channels in one transaction? Probably with multifundchannel, it's just that I can't understand the proper way to run it. It doesn't give an example in docs and I didn't find anything at github.
How do you insert an array, or in this situation the destination, properly? There are lots of ways I can think of...
None of the above works.
How do you insert an array, or in this situation the destination, properly? There are lots of ways I can think of...
None of the above works.
For example, I have read about instances in which an LN node failed, the user restored from a backup that did not have the correct channel state, which resulted in the backup-restored node trying to close the channel via an old channel state.
You're right. Although, it's fairly uncommon to run an old backup, even unintentionally. LND by default generates static backups, which can be only used to request the other party to close a channel. C-lightning's backup plugin backups the whole channel database to a remote directory/drive and it constantly overwrites old backups.
What's the best channel_capacity/network_contribution ratio? For instance, would it be more contributive to open 100 of 0.01 BTC rather than 2 of 0.50 BTC?
100 channels sound better. If someone undercut (in terms of fees) only some of your channels, it should not impact your routing effectiveness greatly. Also, you are more likely to get more routing attempts through you as long as you choose channels and set your fees reasonably.
Also, how do I choose the proper nodes to do this?
That's one of the trickiest parts of running a Lightning node. I usually select some random medium-sized nodes from either amboss.space or 1ml.com and then check the shortest path from my node to theirs using lnrouter.app. Don't forget that path finding algorithms also take the route length into consideration.
Also, how do I choose the proper nodes to do this? I had read about triangles, but I'm not sure if that's what I'm talking about.
You can learn about liquidity triangle/square/pentagon swaps here. Once you set up a mainnet node, you can use that website to find partners for the swap. Liquidity swaps might actually improve your routing performance.
Yesterday, I performed a triangle swap with two other bitcointalk members. Each of us opened a 0.05 BTC channel to the other person. This way, we gained additional 0.10 BTC capacity, which means that this swap has doubled my node's capacity. I paid 222 sat for the opening transaction. We dropped the fees to 0 and TheJuice's script took care of the rebalancing. On the same day, I routed 6 transactions from the channel I opened and I got paid 222.76 satoshi. The channel paid itself off in just a few hours.
What's the best channel_capacity/network_contribution ratio? For instance, would it be more contributive to open 100 of 0.01 BTC rather than 2 of 0.50 BTC? Also, how do I choose the proper nodes to do this? I had read about triangles, but I'm not sure if that's what I'm talking about. Are there any helpful guiding threads in here?
I just want to increase the capacity in testnet. I have few tBTC lying around (~4.5 tBTC) and I prefer using them in a way to be useful than having them in my dusty cold storage.
I just want to increase the capacity in testnet. I have few tBTC lying around (~4.5 tBTC) and I prefer using them in a way to be useful than having them in my dusty cold storage.
If you ever wondered how often someone is penalized for fraudulent behaviour, forkmonitor keeps track of all penalty transactions ever broadcast. Apparently, there have been 419 unsuccessful cheat attempts with a total of ~5.13 BTC at stake since the end of 2017.
I don't think all these transactions are necessarily "cheat attempts". For example, I have read about instances in which an LN node failed, the user restored from a backup that did not have the correct channel state, which resulted in the backup-restored node trying to close the channel via an old channel state.
If you ever wondered how often someone is penalized for fraudulent behaviour, forkmonitor keeps track of all penalty transactions ever broadcast. Apparently, there have been 419 unsuccessful cheat attempts with a total of ~5.13 BTC at stake since the end of 2017.
Plus Chain Anals’ tracking of Lightning transactions actually helps increase the liquidity in the network and helps it scale, and makes it function better. 
Just like scammers and governments support the Tor network by running their own compromised nodes 
As long as enough scammers and competing governments join, and as long as users are aware of the risks, none of this stops the network.But there’s a big difference between routing traffic in TOR, and routing transactions in the Lightning Network. Eventually, a node operator will need to take opportunity costs into account, and must be incentivized to maintain “staking” his/her capital. Chain Anals’ increasing need to montior Lightning = demand for Bitcoin.
Plus with their business model, they should be telling everyone to use Bitcoin. No users = no transactions to monitor = no Chain Anals.
Well, it's as the messages say. You have no route to Boltz.
I successfully opened a channel with Boltz to make it work. It appears that the lightning daemon just needed a restart. Okay, so I sent them 0.0025 LN-tBTC and have probably increased my receiving capacity. Shouldn't I now be able to send my node a few sats? Why do I still get the same error?Is there any other client you advice me to use instead of Electrum? No matter how much I've googled I haven't understood why this happens...
For my testing on testnet, when I need to try connections from different machines (same network, different network etc.), I usually use pruned Core with normal c-lightning or - what I once had on a laptop - lnd with Neutrino backend. Very quick to setup and light on storage. Well, it's as the messages say. You have no route to Boltz.
I successfully opened a channel with Boltz to make it work. It appears that the lightning daemon just needed a restart. Okay, so I sent them 0.0025 LN-tBTC and have probably increased my receiving capacity. Shouldn't I now be able to send my node a few sats? Why do I still get the same error?
Is there any other client you advice me to use instead of Electrum? No matter how much I've googled I haven't understood why this happens...
For a quick hack, you can kind of 'force detach' it by adding a & at the end like this: ./lightningd &
Nice! I didn't know that. Can someone solve me these queries that I have? So, I've gone to testnet.boltz.exchange to increase my receiving capacity as a lightning node. You just give LN-BTC and receive BTC, hence you've increased your receiving capacity by spending some your channel's reserve.
Alright, so I've tried this with my Electrum. I opened up a channel with somebody, sent the LN-BTC got my BTC, everything went fine. But, what exactly happens when I try the same with my lightning node?
Well, it's as the messages say. You have no route to Boltz. Might be due to them having / having had a maintenance today; not sure if it's over yet. If it is, you need to either create a channel with them directly or with someone who does.Alright, so I've tried this with my Electrum. I opened up a channel with somebody, sent the LN-BTC got my BTC, everything went fine. But, what exactly happens when I try the same with my lightning node?
Secondly, why does my lightningd log show these?
These are the various attempts to route the payment. Regarding the 'parts'; payments can / are split and sent through various routes and nodes. Especially if from one hop to the next there exists no single channel with sufficient capacity to route the whole sum.Thirdly, why does the lightning daemon closes when I close the Windows' cmd? Normally, when I'm ssh-ing using the cmd and close it, nothing changes from the RPi.
Because if you start lightning via ./lightningd, the process runs inside the SSH process; when that one is killed (by closing the SSH session), LN does as well. Probably in your other experiences with SSH, you started stuff as a service or the binaries detached into independent processes by themselves.For a quick hack, you can kind of 'force detach' it by adding a & at the end like this: ./lightningd &; however I'd recommend setting up a systemd service for your node.
For creating such service, you can refer to my OpenSUSE node setup guide, last line of step 8 as well as step 9 and 10.
Can someone solve me these queries that I have? So, I've gone to testnet.boltz.exchange to increase my receiving capacity as a lightning node. You just give LN-BTC and receive BTC, hence you've increased your receiving capacity by spending some your channel's reserve.
Alright, so I've tried this with my Electrum. I opened up a channel with somebody, sent the LN-BTC got my BTC, everything went fine. But, what exactly happens when I try the same with my lightning node?
Secondly, why does my lightningd log show these?
Thirdly, why does the lightning daemon closes when I close the Windows' cmd? Normally, when I'm ssh-ing using the cmd and close it, nothing changes from the RPi.
Alright, so I've tried this with my Electrum. I opened up a channel with somebody, sent the LN-BTC got my BTC, everything went fine. But, what exactly happens when I try the same with my lightning node?
Code:
./lightning-cli --testnet pay lntb10m1psagh4lpp5guw6fusvvxhy95auhscnh78s3sq6jmax5038n2smqsvst0r5xwmsdql2djkuepqw3hjqsj5gvsxzerywfjhxuccqzptxqrrsssp5fzl2n8tp23vrmlaza8pahr4hgn26gjy9uqxxrwmyvuhwz59khgwq9qyyssq9d9lx3y6ewauzke4uf0zelfc565e66kk95cq6gm7cufg3ruk8gwjznrpvrmf92t7vx8tzcqvchmjnggx9mhhhs97f7eg59yf05we93cpc2c3sp
{
"code": 210,
"message": "Ran out of routes to try after 971 attempts: see `paystatus`",
"attempts": [
{
"status": "pending",
"partid": 1,
"amount": "1000000000msat"
},
{
"status": "failed",
"failreason": "failed: WIRE_UNKNOWN_NEXT_PEER (reply from remote)",
"partid": 2,
"amount": "181272680msat",
"parent_partid": 1
},
{
"status": "pending",
"failreason": "No path found",
"partid": 195,
"amount": "181272680msat",
"parent_partid": 2
},
...
And lots of “No path found” messages.
{
"code": 210,
"message": "Ran out of routes to try after 971 attempts: see `paystatus`",
"attempts": [
{
"status": "pending",
"partid": 1,
"amount": "1000000000msat"
},
{
"status": "failed",
"failreason": "failed: WIRE_UNKNOWN_NEXT_PEER (reply from remote)",
"partid": 2,
"amount": "181272680msat",
"parent_partid": 1
},
{
"status": "pending",
"failreason": "No path found",
"partid": 195,
"amount": "181272680msat",
"parent_partid": 2
},
...
And lots of “No path found” messages.
Secondly, why does my lightningd log show these?
Code:
...
2022-01-04T14:51:11.145Z INFO plugin-pay: id 0 partid 878: No path found
2022-01-04T14:51:11.145Z INFO plugin-pay: id 0 partid 882: No path found
2022-01-04T14:51:11.146Z INFO plugin-pay: id 0 partid 883: No path found
2022-01-04T14:51:11.146Z INFO plugin-pay: id 0 partid 887: No path found
2022-01-04T14:51:11.146Z INFO plugin-pay: id 0 partid 888: No path found
2022-01-04T14:51:11.147Z INFO plugin-pay: id 0 partid 892: No path found
2022-01-04T14:51:11.219Z INFO plugin-pay: id 0 partid 894: No path found
2022-01-04T14:51:11.343Z INFO plugin-pay: id 0 partid 896: No path found
2022-01-04T14:51:11.400Z INFO plugin-pay: id 0 partid 901: No path found
2022-01-04T14:51:11.401Z INFO plugin-pay: id 0 partid 903: No path found
2022-01-04T14:51:11.401Z INFO plugin-pay: id 0 partid 921: No path found
2022-01-04T14:51:11.402Z INFO plugin-pay: id 0 partid 930: No path found
2022-01-04T14:51:11.402Z INFO plugin-pay: id 0 partid 931: No path found
2022-01-04T14:51:11.402Z INFO plugin-pay: id 0 partid 936: No path found
2022-01-04T14:51:11.402Z INFO plugin-pay: id 0 partid 941: No path found
2022-01-04T14:51:11.403Z INFO plugin-pay: id 0 partid 869: No path found
2022-01-04T14:51:11.403Z INFO plugin-pay: id 0 partid 870: No path found
2022-01-04T14:51:11.403Z INFO plugin-pay: id 0 partid 691: No path found
2022-01-04T14:51:11.422Z INFO plugin-pay: id 0 partid 970: No path found
2022-01-04T14:51:11.446Z INFO plugin-pay: id 0 partid 722: No path found
2022-01-04T14:51:11.145Z INFO plugin-pay: id 0 partid 878: No path found
2022-01-04T14:51:11.145Z INFO plugin-pay: id 0 partid 882: No path found
2022-01-04T14:51:11.146Z INFO plugin-pay: id 0 partid 883: No path found
2022-01-04T14:51:11.146Z INFO plugin-pay: id 0 partid 887: No path found
2022-01-04T14:51:11.146Z INFO plugin-pay: id 0 partid 888: No path found
2022-01-04T14:51:11.147Z INFO plugin-pay: id 0 partid 892: No path found
2022-01-04T14:51:11.219Z INFO plugin-pay: id 0 partid 894: No path found
2022-01-04T14:51:11.343Z INFO plugin-pay: id 0 partid 896: No path found
2022-01-04T14:51:11.400Z INFO plugin-pay: id 0 partid 901: No path found
2022-01-04T14:51:11.401Z INFO plugin-pay: id 0 partid 903: No path found
2022-01-04T14:51:11.401Z INFO plugin-pay: id 0 partid 921: No path found
2022-01-04T14:51:11.402Z INFO plugin-pay: id 0 partid 930: No path found
2022-01-04T14:51:11.402Z INFO plugin-pay: id 0 partid 931: No path found
2022-01-04T14:51:11.402Z INFO plugin-pay: id 0 partid 936: No path found
2022-01-04T14:51:11.402Z INFO plugin-pay: id 0 partid 941: No path found
2022-01-04T14:51:11.403Z INFO plugin-pay: id 0 partid 869: No path found
2022-01-04T14:51:11.403Z INFO plugin-pay: id 0 partid 870: No path found
2022-01-04T14:51:11.403Z INFO plugin-pay: id 0 partid 691: No path found
2022-01-04T14:51:11.422Z INFO plugin-pay: id 0 partid 970: No path found
2022-01-04T14:51:11.446Z INFO plugin-pay: id 0 partid 722: No path found
Thirdly, why does the lightning daemon closes when I close the Windows' cmd? Normally, when I'm ssh-ing using the cmd and close it, nothing changes from the RPi.
Plus Chain Anals’ tracking of Lightning transactions actually helps increase the liquidity in the network and helps it scale, and makes it function better.
Just like scammers and governments support the Tor network by running their own compromised nodes As long as enough scammers and competing governments join, and as long as users are aware of the risks, none of this stops the network.Agreed. Thought I'd add the following article showing the dimensions in which these TLAs are operating:
Since at least 2017, a mysterious threat actor has run thousands of malicious servers in entry, middle, and exit positions of the Tor network in what a security researcher has described as an attempt to deanonymize Tor users. The Record reports:
Tracked as KAX17, the threat actor ran at its peak more than 900 malicious servers part of the Tor network, which typically tends to hover around a daily total of up to 9,000-10,000.
...
Tracked as KAX17, the threat actor ran at its peak more than 900 malicious servers part of the Tor network, which typically tends to hover around a daily total of up to 9,000-10,000.
...
TL;DR: You are not as anonymous and private on tor as you might
Plus Chain Anals’ tracking of Lightning transactions actually helps increase the liquidity in the network and helps it scale, and makes it function better.
Just like scammers and governments support the Tor network by running their own compromised nodes As long as enough scammers and competing governments join, and as long as users are aware of the risks, none of this stops the network. There is FATF Travel Rule compliance anyway. So LN might be classified as illegal coin mixxer by default
That is not going to happen any time soon, but in theory they can classify anything as illegal, walking on street, using paper money, owning gold, owning bitcoin or any other property.... oh wait some of those things were already illegal once upon a time.
One more reason why Lightning Network won't be made illegal is because they prefer to track in and get more tax extortion from people, hence why Chainalysis recently announced they are integrating and tracking Lightning Network for regulation compliance.
It's a well know fact that Chainalysis is working with many exchanges, companies and government agencies.
It’s probably because the government doesn’t have the regulatory-framework to work on to start shutting down Lightning routing nodes. They can’t stop centralized shitcoins, how can they censor Bitcoin and any decentralized offchain layers build on top of it.
Plus Chain Anals’ tracking of Lightning transactions actually helps increase the liquidity in the network and helps it scale, and makes it function better.
There is FATF Travel Rule compliance anyway. So LN might be classified as illegal coin mixxer by default
That is not going to happen any time soon, but in theory they can classify anything as illegal, walking on street, using paper money, owning gold, owning bitcoin or any other property.... oh wait some of those things were already illegal once upon a time.One more reason why Lightning Network won't be made illegal is because they prefer to track in and get more tax extortion from people, hence why Chainalysis recently announced they are integrating and tracking Lightning Network for regulation compliance.
It's a well know fact that Chainalysis is working with many exchanges, companies and government agencies.
There is FATF Travel Rule compliance anyway. So LN might be classified as illegal coin mixxer by default
Unlikely, IMO.
First of all it's questionable whether LN node operators would fall under the definition of a VASP in the first place, as they arguably (1) merely provide ancillary infrastructure, which is explicitely excluded from the definition of a VASP and (2) acting as a VASP also implies running a business, for which the expected "profits" of running a LN node hardly qualify -- at least for 99.9% of nodes. The latter means that worst case you'd see large nodes replaced with many smaller ones. And exchanges that run their own LN nodes already know their customers anyway, if regulations tighten they can stop routing and only use LN for in- and out-going transactions.
Secondly the FATF travel rule would only apply to transactions of larger than USD 1000,- or its equivalent. Even assuming LN node operators would get ruled as VASPs and have FATF guideline-based legislation applied to them they can just adjust the maximum amount that can be sent via their channels to fall within regulation. I believe even now most LN transactions fall well below that limit anyway.
There is FATF Travel Rule compliance anyway. So LN might be classified as illegal coin mixxer by default
The cat is out of the bag. In fact, Bitcoin is classified as an illegal currency by default, but because of technical break throughs, and the genius of the implementation of HashCash/POW in Bitcoin, it could not be censored. Lightning will be the same. It will only increase in liquidity provided by Chain Anals, Routing Nodes, and Users.
There is FATF Travel Rule compliance anyway. So LN might be classified as illegal coin mixxer by default
Interesting... I guess they'll open lots of channels with lots of nodes? It seems to me that they'll need lot of liquidity.
I don't know exactly how they plan to do this, but it's with using their KYT software I am sure they will connect with all exchanges that accept LN payments.They are also monitoring many addresses from ofac list, but it's not going to be so easy with lightning network, unless they have some actors inside.
I'm very interested to see what / how they want to try spying into LN.
I a sure they won't tell anyone how they are doing that spying part but I am sure they have huge funding from governments and other big tech corporations.LN tracking for them is just one small puzzle part in much bigger picture of tracking everyone and everything.
If they were to instead create one huge node that will connect most people through 1 hop (alternative to maintaining lots and lots of nodes), it would quickly get noticed on LN observer maps and stand out as very suspicious to node operators.
Maybe you also need to run Electrum through Tor proxy? I am not sure because I used Electrum only with clearnnet nodes, but it would make sense.
Went through Tor. Results:
No outgoing transactions in history. In my node's log:
Code:
2021-12-15T14:31:34.512Z INFO 0348800b9c5e68fe052d6b240350ae5412bbfc7fee7456ec4d725f7c7beff333f2-chan#3: Parsing funding_created
Interesting... I guess they'll open lots of channels with lots of nodes? It seems to me that they'll need lot of liquidity.
I don't know exactly how they plan to do this, but it's with using their KYT software I am sure they will connect with all exchanges that accept LN payments.They are also monitoring many addresses from ofac list, but it's not going to be so easy with lightning network, unless they have some actors inside.
I'm very interested to see what / how they want to try spying into LN.
I a sure they won't tell anyone how they are doing that spying part but I am sure they have huge funding from governments and other big tech corporations.LN tracking for them is just one small puzzle part in much bigger picture of tracking everyone and everything.
Jump to: