c_otto83
C-Otto 🔸

I took the 10% pledge https://www.givingwhatwecan.org/pledge

Public Key

npub12n4hxnynwh6qf76vq6tr3skasuxr9wqahzevr5m05j44z83k076smxsnq5

NIP-57 Address

carsten@c-otto.de

Profile Code

nprofile1qqs9f6mnfjfhtaqyldxqd93cctwcwrpjhqwm3vkp6dh6f263rcm8ldgppamhxue69uhkummnw3ezumt0d5q3qamnwvaz7tmwdaehgu3wd4hk6tckd7ku4

Publishing to

nostr.mom

nostr-pub.wellorder.net

Author Public Key

npub12n4hxnynwh6qf76vq6tr3skasuxr9wqahzevr5m05j44z83k076smxsnq5

Show more details

Last Notes

2024-09-14 06:55:51

- reply

It's a 20 Gbit uplink running at an average of 4 Gbit. Seems correct to me.

2024-09-13 19:46:50

- reply

If I knew how, I would add dedicated statistics for the relay on http://ftp.halifax.rwth-aachen.de. Since January (I don't have older data at hand), the server sent out 9 PByte of data. 104 TByte would be 1% of that.

2024-09-09 18:14:41

- reply

Do you know about https://github.com/bottlepay/pathfinding-benchmark?

2024-07-29 01:04:35

#nostr https://image.nostr.build/745b2ce2dfaaed32d51b75a978bed8850913b22c7da51c6851583e4c97cadaad.jpg

2024-07-01 13:33:45

Update your ssh, now.
https://thehackernews.com/2024/07/new-openssh-vulnerability-could-lead-to.html

2024-06-16 09:14:05

- reply

"read only = true" in the rsyncd.conf. If that's not secure, please let me know :)

2024-06-15 17:01:31

- reply

When the project started, FTP was still in active use und most other mirror servers had similar names. FTP still works, by the way.

2024-06-15 08:26:52

- reply

I'll stick to Tor.

2024-06-15 08:25:27

- reply

It's already running as a HiddenService: ybfe3kvc73pu3vxtizi5ppadmrmohabuwz6odabzukhi5vb6xfcfrpad.onion:8333

2024-06-15 07:51:10

On https://ftp.halifax.rwth-aachen.de you can find...
- a full Bitcoin node (top 10 according to bitnodes.io)
- a Nostr relay
- Tor relays (guard, over 2 GBit/sec)
- 28 TByte worth of open source software (with rsync access)
All of that is served via IPv4 & IPv6, up to 20 GBit/sec, with lots of fast storage. Enjoy!

2024-06-05 08:52:30

- reply

OK, it's much less interesting. 2M sats from okx to LOOP, saving 2k sat in fees. That's it. I guess I have to wait a bit longer to see interesting results 😃

2024-06-05 08:48:12

- reply

Sorry, I made a mistake in my script, this data most likely is very wrong. I'll post an update asap.

2024-06-05 08:15:29

https://stacker.news/items/562489/r/C_Otto

2024-05-18 08:50:12

Shortly after I made http://ftp.halifax.rwth-aachen.de/ a Tor relay (up to 20 GBit/sec!), rsync access to openEuler's main server in China stopped working. It's still accessible from other hosts, though. I blame politics.
https://metrics.torproject.org/rs.html#search/RWTH

2024-05-12 12:04:17

I wrote down my thoughts/rules on how I'll set inbound fee rates on my #LightningNetwork node c-otto.de once I start using lnd v0.18:
https://stacker.news/items/536820/r/C_Otto

2024-05-09 14:29:01

Which Web UI for #nostr are you using? For me, iris.to and snort.social (the same?) don't work reliably. They start with an empty "For you" list, old notifications re-appear as new, sometimes the whole page doesn't load (applies to both).

2024-05-07 09:36:22

- reply

Yes and yes. That doesn't explain why those nodes take the more expensive route, though.

2024-05-07 08:32:37

Please help me understand the lightning network. It seems running a node for 6 years isn't enough to understand what's going on.
https://stacker.news/items/531288

2024-05-03 15:27:58

- reply

I see three requests on my webserver, all of them successfull and "redirecting" the actual payment to Stacker News. Maybe the issue is on their side. I received your sats, though - thanks a lot!
2409:xxx- - [03/May/2024:17:13:36 +0200] "GET /.well-known/lnurlp/carsten HTTP/1.1" 200 3758 "-" "FreeFrom/7 CFNetwork/1494.0.7 Darwin/23.4.0"
2a02:xxx - - [03/May/2024:17:15:04 +0200] "GET /.well-known/lnurlp/carsten HTTP/1.1" 200 3757 "https://iris.to/" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:125.0) Gecko/20100101 Firefox/125.0"
44.xxx - - [03/May/2024:17:20:35 +0200] "GET /.well-known/lnurlp/carsten HTTP/1.1" 200 3774 "-" "python-requests/2.28.2"

2024-05-03 15:09:12

I just did a transaction which took advantage of negative inbound fees 🚀
https://stacker.news/items/527919
#bitcoin #LightningNetwork

2024-04-19 07:58:18

If you run lnd, don't upgrade to Bitcoin Core 27, yet.
https://twitter.com/roasbeef/status/1781086945986404559

2024-04-09 20:13:50

- reply

Vegan for life

2024-03-11 15:22:10

October 2013. Instead of completing my PhD thesis, I fooled around on the Internet and found a #bitcoin faucet. I guess I had to solve a few captchas or so, and in the end I was rewarded with 0.02 US$ worth of Bitcoin, 15,000 sats after deducting the on-chain transaction fees.
March 2024. I can now buy myself a coffee with that. Using Bitcoin. Life's crazy.

2024-01-24 11:34:26

Hi @npub1sn0…jdv9, do you run your own lightning node? If so, how do you pick your peers for (I assume) mostly personal, low-volume transactions? Thanks!

2024-01-22 12:54:27

- reply

Exactly.

2024-01-22 11:17:09

- reply

It's fixed now, caused by a low TTL (600 seconds). With a TTL of 24h everything is fine.

2024-01-21 10:50:34

- reply

I know.

2024-01-21 06:05:35

- reply

It is fast with Linux and ZFS.

2024-01-20 21:26:39

Any DNS guru out there? The mirror server ftp.halifax.rwth-aachen.de appears to have some DNS issues according to Debian's mirror report checks, but I can't see what's wrong.
https://mirror-master.debian.org/status/mirror-info/ftp.halifax.rwth-aachen.de.html
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021002

2024-01-20 19:18:01

The nostr relay at wss://ftp.halifax.rwth-aachen.de/nostr just moved to new hardware, which is much faster. Give it a try!
The nostr database is served from a fast SSD (NVMe) based HW-RAID1.
With 20 GBit/sec of network connectivity, 256 GByte of RAM, and lots of CPU power, I believe speed shouldn't be an issue for the foreseeable future. If the storage demands grow, there's also around 30 TByte of HDD based disk space available.
Hardware details are available at https://ftp.halifax.rwth-aachen.de/

2024-01-19 19:58:51

https://innn.it/afdverbot

2024-01-13 13:41:31

I have just raised the fees significantly on some channels #LightningNetwork
https://stacker.news/items/386730

2024-01-12 10:43:19

- reply

Oh, a simple rebalance might also be what you want.

2024-01-12 10:21:21

If you have a channel with c-otto.de and want to move funds to my side of the channel, you might want to deposit some sats to Kraken (and withdraw on-chain?). I have lots of liquidity to Kraken and configured a fee rate of 0ppm. #LightningNetwork

2024-01-07 20:41:14

- reply

Thank you, that's very insightful!

2023-12-31 10:36:37

I turned this FC into a little "blog" post, dissecting the invidual steps that lead to this: https://stacker.news/items/372294
#note15aj…f99z

2023-12-31 09:42:40

Hi @npub1r0c…0j93, thanks for the FC bot! I noticed that it doesn't include the fees paid for HTLCs that either timed out or didn't resolve back to the sender.
In my case that added 48k sat to one FC, in addition to whatever I need to pay in order to sweep this output. Do you think it's worthwile to add these transactions to your calculations? I realize that they only appear after a delay (cltv_expiry for the two HTLC transactions and to_self_delay for the sweeps).
PS: I always resort to https://ellemouton.com/posts/htlc-deep-dive/ in order to understand what's going on. Really helpful :)

2023-12-21 11:11:22

Hi @npub1ngu…e3pv, do you have any information why FCs happen between your own nodes? This isn't the first time I've seen this, and I believe this should never happen.
#note1vt2…zrax

2023-12-13 08:36:32

I'm a bit confused about block template creation vs. empty blocks. If you know Stratum V2 and related things, please chime in here:
https://stacker.news/items/350605
https://bitcoin.stackexchange.com/questions/120933/constructing-a-block-template-to-avoid-mining-empty-blocks

2023-12-09 12:45:18

PSA: If you run lnd with a pruned bitcoind (or maybe neutrino?), check the output of `lncli getinfo` -> "synced_to_chain". If this value is stuck at "false", you might want to restart your node. This issue is being investigated at https://github.com/lightningnetwork/lnd/issues/8250 (priority 1).

2023-12-07 15:22:02

As a routing node operator (c-otto.de) in the #LightningNetwork, I wonder which implementations are responsible for the transactions, how routing decisions are made, how pathfinding works.
For example, I suspect that WalletOfSatoshi uses some centralized solution: larger chunks of fresh inbound liquidity from their node (for example, because my node routed a large transaction TO their node) are quickly drained (most likely used for transactions originating from their node).
How do other larger nodes find routes? Do you know what BitFinex or Binance do to route user's withdrawals? What about other services/wallets? How do merchants cash out / pay their bills? How are transactions from/to LOOP or FixedFloat users routed?
I could look up the routing code details in LND and CLN, but my gut feeling is that there's more going on. Please provide insights, if you have any!

2023-12-04 10:34:25

What's a good site to watch the EUR/BTC (or USD/BTC) exchange rate climb? I was quite happy with tradeblock.com, but it seems that site vanished a while ago. I don't want to trade, I'm just looking for pretty graphs/candles.

2023-12-01 15:48:53

The mirror server at https://ftp.halifax.rwth-aachen.de will receive a nice hardware upgrade soon. Because of that, we have some disk space available and would be happy to add a few more projects to the mirror. Do you know of any (OSS) project that would benefit from this? Please share/RT!

2023-11-24 12:03:45

- reply

Same thing now also happens with snort...

2023-11-24 07:00:21

- reply

I think this function is only used for two files (some private file, and some tor cookie). I'm interested in the read accesses for block data, as this causes load on the system. The way it currently works, using some defaults and OS magic, is fine - but I'd like to tweak things (and learn, and have fun) if possible. For example, if I configure a blocksize of 1 MByte with ZFS, if then bitcoind just reads (and needs) 128 byte out of this chunk, this would cause ZFS to read 8000x the requested size from disk.

2023-11-23 10:05:05

https://twitter.com/mononautical/status/1727627818929094973

2023-11-23 09:02:30

Any idea what's wrong with iris.to? Is it just me?
{
"name": "ReferenceError",
"message": "require is not defined",
"stack": "ReferenceError: require is not defined\n at https://iris.to/assets/index-BtVqnR-H.js:2179:20918\n at C0 (https://iris.to/assets/index-BtVqnR-H.js:41:24283)\n at gc (https://iris.to/assets/index-BtVqnR-H.js:41:42406)\n at https://iris.to/assets/index-BtVqnR-H.js:41:40723\n at j (https://iris.to/assets/index-BtVqnR-H.js:26:1543)\n at MessagePort.M (https://iris.to/assets/index-BtVqnR-H.js:26:1904)"
}

2023-11-23 07:36:09

https://twitter.com/uu7201/status/1727433338825380064

2023-11-22 15:41:20

Those who know C++, how does bitcoind (Bitcoin Core) read/write data from/to disk? I'd love to tweak certain settings for my public node. Is bitcoind using specific page sizes? Please answer here, if possible:
https://bitcoin.stackexchange.com/questions/120567/page-size-of-read-and-write-operations

2023-11-17 14:26:02

New hardware for the nostr relay (among other things) ftp.halifax.rwth-aachen.de has been shipped! I'm excited, playing around with expensive hardware is a lot of fun :)
256 GByte RAM, 19x 4 TByte HDDs, 3x 800 GByte SSDs, and at least 2x 10 GBit/sec of redundant Internet connectivity

2023-11-15 14:10:37

- reply

Fromy lnd (c-otto.de): "Payment status: FAILED, reason: FAILURE_REASON_INCORRECT_PAYMENT_DETAILS"

2023-11-15 14:09:58

- reply

No route, I tried WoS and Phoenix.

2023-11-14 19:31:48

⚡️ lnd v0.17.1 has been released! ⚡️
https://twitter.com/roasbeef/status/1724507812833939950

2023-11-09 21:32:20

- reply

No, Intel Xeon Gold

2023-11-09 17:29:45

- reply

Updating https://github.com/C-Otto/BitBook/ to modern Spring Boot (3.1 from 2.6).

2023-11-08 07:06:20

- reply

It will have 256 GByte RAM. Yeah :)

2023-11-01 08:43:55

I'm pretty confident ftp.halifax.rwth-aachen.de will receive a hardware upgrade soon, thanks to a sponsor I'll name once it is official. The nostr relay (wss://ftp.halifax.rwth-aachen.de/nostr) will also benefit from this!
~75 TByte HDD disk space
several TByte SSD disk space (for caching)
192 GByte RAM (maybe 256 GByte, we'll see!)
at least 20 GBit/sec internet connectivity
7 years of warranty with on-site support
As before, the server will be hosted at RWTH Aachen University (sponsoring power, cooling, network).

2023-10-26 05:30:35

This happened again, twice. I requested 2 sat/vByte, next block is at around 3-4 sat/vByte. Both peers wanted to pay 30 sat/vByte instead. Their loss...
#note1jj9…gn86

2023-10-21 19:43:10

This is a great explanation:
https://x.com/mononautical/status/1715736832950825224?s=20

2023-10-21 07:09:42

I'm lucky to have several large (~1 BTC and more) channels and enough inbound liquidity on my #LightningNetwork node. Because of this, I also see large forward requests. Some succeed, some fail.
However, it's always saddening when my node has to reject a 0.9 BTC forward request with lots of sats attached as fees I could claim. I simply don't have that much liquidity.
I wonder how this wrks out for other node operators - Alex Bosworth with his yalls nodes as an example.
It'd be nice for LSPs/wallets to split larger payments (MPP), possibly with #PickhardtPayments. That way, my node could at least serve a (large?) fraction of the total amount. But, who knows, maybe those 0.9 BTC in my example above are just 1% of the total amount :)

2023-10-20 13:13:02

- reply

I don't know, I should watch it again :) A recent thought: smaller channels aren't worth it most of the time, I increased the minimum to 10M for my node. Larger channels are more reliable and attract more routing, cost less, ...

2023-10-18 06:58:08

Lots of activity in the #LightningNetwork. It's hard to keep up, I'm rebalancing/fixing more than usual. I kinda need more sats, though :/

2023-10-17 09:19:04

- reply

No, that should be fine

2023-10-17 06:44:28

PSA: Check your #LightningNetwork node's fee settings. I just requested a channel close with 1 sat/vByte. The mempool is empty. My peer, who has to pay the fees, wanted to pay 18 sat/vByte.

2023-10-15 12:43:15

How can I add content to my nostr relay? So far it only provides posts that I created myself, as my clients are connected to my node. How can I connect my relay to another relay, or forward missing data from my clients?

2023-10-15 10:33:41

- reply

Up and running, I think

2023-10-15 10:13:13

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!

2023-10-14 14:33:29

Is it possible to provide a nostr relay at wss://host/path, i.e. not at the root? @npub180c…h6w6
#nevent1q…pl5a

2023-10-14 14:21:31

- reply

No, see my comment regarding hostname/wss limitations.

2023-10-14 14:18:38

- reply

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?

2023-10-04 15:20:18

BitBook helps you organize your #bitcoin addresses and transactions.
https://github.com/C-Otto/BitBook
https://image.nostr.build/bf80e15788148316008693acd9a91636c2d61ce05617b7978a28460e5f1946f6.jpg
Thank you for the kind words @npub1ngu…e3pv :)

2023-10-04 12:52:55

- reply

Interesting. The note just states "Zap!", though. I'm using WoS for lnurl payments.

2023-10-04 10:43:52

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 :)

2023-10-03 13:59:40

- reply

Existing channels are not affected by this.

2023-10-03 13:58:58

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.

2023-10-03 13:32:26

- reply

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!

2023-08-28 15:42:50

- reply

It took a while, but I now see traffic.

2023-08-26 08:22:41

Did any of you actually use LN with Binance or route to/from their node?

2023-08-18 10:18:19

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.

2023-08-18 10:11:53

- reply

I'm aware of https://nostr.how/en/relay-implementations, but I'd like to have some guidance and recommendations.

2023-08-18 10:10:44

I'd like to provide a publich 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?

2023-08-18 08:57:01

First post. 🥳