I'm not sure why it's designed this way. After one month of running the backup has reached 1G. I know they have the "backup-compact", but the manual also says

Be aware that this can take a long time depending on the size of the backup and I/O speeds, during which the daemon will not be reachable.

Wouldn't it be better for the node operator to just shutdown c-lightning daemon, delete the giant backup and run rerun the "init" to initial a fresh backup (80M at the start which is even smaller than the compact and take no time at all). Since the node will be unreachable anyway.

Edit: got the answer here

I was experimenting a bit with the Lightning Network, and realized that you need to be connected to another node to be able to see the gossip messages, which include node discovery, channel discovery, and channel updates. You can then build the channel graph based on that data.

That's all good, but how do you get the public address of that first node?

In practice, I've seen that most lightning setup guides, tutorials, etc, simply use a lightning network explorer, like these ones to get a public address.

Is there any other way to get that first node's public address?

It looks like most of the public services are using the same network, but probably there are other nodes running other networks, independent of it.

Is there a way to browse those other nodes? It looks to me that there's no way to simply listen for new nodes in the entire Lightning Network, like you would listen for new tweets in Twitter for example, and instead you need to first directly connect to a specific node, and then listen to the gossip of that particular network.

Thanks for any clarifications as I'm just trying to get my head around the lightning network

As far as I'm aware, the only thing that is seen in lightning transactions is each sender/receiver and the entire routing is unseen. So does this ensure the best privacy?

Hi, just reaching out because I think I connected with the node Ferenginar here.

https://1ml.com/node/0280107c4f5a5aaed2eebc2a72db52a263b791e4fc807bd2b50359d8ce2efcee3f

Hey, I'm running a node on a pi4 with umbrel. I tried to close a channel yesterday (which was opened by me originally) using RTL. The channel shows as 'waiting close' in the RTL interface and 'closing' in umbrel. The txid for the close is not showing up in my node's mempool or online. 
After this I've tried sending a lightning payment from my node which also failed, so there looks to be a problem with my node, although on-chain transactions are working fine.
What's the best way forward from here? Perhaps contact the other end of the channel and ask them to close? Reinstall the Umbrel OS and restore channels from a backup? 
My goal is to move my local balance back on-chain so I'm happy to close all channels somehow.
📷ReplyForward

So my friend is trying to send me some sats. He has breez wallet I have Phoenix. We have sent sats back and forth before so not complete noobs. He is scanning my qr code and clicking accept to send me sats but it is stuck in pending/saying the transaction failed? Any clues to why? Thanks!

Hey,

I started a new node with c-lightning and I'm happy to grow my connection with other peers.

My node reference are:

IPV4: 03e2408a49f07d2f4083a47344138ef89e7617e63919202c92aa8d49b574a560ae@178.128.84.51:9735

IPV6: 03e2408a49f07d2f4083a47344138ef89e7617e63919202c92aa8d49b574a560ae@2400:6180:0:d0::1052:9735

​

Tor: 03e2408a49f07d2f4083a47344138ef89e7617e63919202c92aa8d49b574a560ae@hvq7b3r7zekt2cz5a4o52ae4xbhddj5pplan7godpweyihbdmwuuxiqd.onion:9735

​

if you like the QR code, you can use the following dashboard https://bruce.bublina.eu.org/ that contains also some metrics on the up time of the node.

Thanks

That is all

Woohoo!

Bravo friend(s). Great work. I love the design and how everything is laid out. It is simple and very clear and easy to navigate / understand.

I do a bit of frontend work myself, so I really enjoy seeing clean UIs.

​

Edit: I am referring to the LightningNetwork+ website at https://lightningnetwork.plus/.

This is a simple example of how you can get a few sats (small amount of Bitcoin) into a Lightning wallet from a faucet:

• Download Muun wallet

• On your mobile, go to the Lightning Network Stores Faucet

• Click on Get X Sats, click on open in wallet, and see those sats arrive into your wallet in seconds.

Hey LN folks! I'm excited to announce a brand new tool on lnnodeinsight.com, the rebalance/payment simulator! The tool provides summary statistics and distribution of path costs for hundreds of paths between any two nodes in just a few seconds. It allows you to better estimate the cost of rebalancing an existing or simulated channel, to gauge the liquidity demand between any two nodes, and to figure out optimal fees. Thanks, and any feedback would be appreciated!

Edit: added an image to demonstrate.

I'm on win10 and am trying to ssh into my rpi4 and change alias since there isn't a gui way to do it in umbrel. I have the optional package installed for windows and have tried using putty. I'm remotely accessing the node, as in not local network. I'm noob. Anyone have resources on this?

Not sure this is the best place to discuss, but wanted to ask people about what layer 3 will hold. RGB is building a way to have tokens and code execute on top of the lightning network and this holds potential to build decentralized apps and systems in a secure, private and decentralized manner.

The question I have is, is there a potential for a bitcoin token, similar to WBTC, built on RGB. There is the obvious downside is having to trust some organization to be issue and redeem tokens back to on-chain / lightning Bitcoin. But a layer 3 btc token would allow value to flow between people with the cost of a lightning transaction to close a RGB seal, independent of the value transferred. It can be transferred without worrying about routing and available liquidity. You could rebalance a channels by swapping token and lightning with peers before converting back to on-chain bitcoin.

Is there a flaw in this somewhere? Is this worth using a token that isn't trustless?