Up and running, I think
There might be a new relay at wss://ftp.halifax.rwth-aachen.de/nostr adding 20 GBit/sec to the network. I'll reconfigure, restart and migrate the relay until things are settled, but please feel free to give it a try!
Is it possible to provide a nostr relay at wss://host/path, i.e. not at the root? nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6
No, see my comment regarding hostname/wss limitations.
I'd like to provide a public Nostr relay on ftp.halifax.rwth-aachen.de, which currently has 20 GBit/sec of network connectivity, in addition to lots of CPU and disk space.
I have a strong preference for self-contained implementations making use of some strongly typed language (Go, Rust, Java, ...), and I'd be happy to provide some PostgreSQL backend. Could you recommend a mature implementation that is fit for the purpose?
I'm aware of https://nostr.how/en/relay-implementations, but I'd prefer some guidelines and hear from your experiences.
One important limitation: I'd rather not add a new DNS entry for the host and can't dedicate port 80/443 to the service as the host already offers http(s). It seems relays require websocket at the root, though?
BitBook helps you organize your #bitcoin addresses and transactions.
https://github.com/C-Otto/BitBook
Thank you for the kind words nostr:npub1ngumlqmus6xkrmvvee4yc7swh9h4uk7vpq4ddt7a2jtvkc22y0asrse3pv :)
Interesting. The note just states "Zap!", though. I'm using WoS for lnurl payments.
Just got my first zap, out of the blue, anonymously. I've been using Bitcoin for more than 10 years now, and this technology still feels exciting! Oh, and thanks - I'll hodl on to those 21 sats :)
From now on my #LightningNetwork node c-otto.de only accepts channels with a size of at least 10 million sat (0.1 BTC). In the past, I often had to close smaller channels (see https://github.com/C-Otto/lnd-manageJ/blob/main/rating.md) and I hope that larger channels offer a better user/routing experience.
Existing channels are not affected by this.
From now on my #LightningNetwork node c-otto.de only accepts channels with a size of at least 10 million sat (0.1 BTC). In the past, I often had to close smaller channels (see https://github.com/C-Otto/lnd-manageJ/blob/main/rating.md) and I hope that larger channels offer a better user/routing experience.
The **third change** is that outgoing paid channels are opened with a mandatory requirement to support anchor channels from your side!
For most, this change will go unnoticed, but for the owners of the old lightning nodes software, this means that they will not be able to open a paid channel outgoing to them from the LNBiG network (of course, funds for payment will not be taken thanks to the HODL invoice).
I have to do this for the reason that in the current situation it is very dangerous to have channels without anchor support. Such channels are difficult to close if the bitcoin network fee market is growing and remains with a high fees for a very long time.
#LightningNetwork #LNBiG #News
nostr:nevent1qqsdzh8e5r9vgklhu9t9fhmq4a432cvw8rx6akscgun3w9347m62aegppemhxue69uhkummn9ekx7mp0wj7fdw
I see that you renamed those seven nodes to three "hub" and four "leaf" nodes. Could you please explain the underlying idea? What's the difference between a hub and a leaf? Thanks!
It took a while, but I now see traffic.
Did any of you actually use LN with Binance or route to/from their node?
I'd like to provide a public Nostr relay on ftp.halifax.rwth-aachen.de, which currently has 20 GBit/sec of network connectivity, in addition to lots of CPU and disk space.
I have a strong preference for self-contained implementations making use of some strongly typed language (Go, Rust, Java, ...), and I'd be happy to provide some PostgreSQL backend. Could you recommend a mature implementation that is fit for the purpose?
I'm aware of https://nostr.how/en/relay-implementations, but I'd prefer some guidelines and hear from your experiences.
I'm aware of https://nostr.how/en/relay-implementations, but I'd like to have some guidance and recommendations.
First post. ๐ฅณ