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)"
}
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
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
Fromy lnd (c-otto.de): "Payment status: FAILED, reason: FAILURE_REASON_INCORRECT_PAYMENT_DETAILS"
⚡️ lnd v0.17.1 has been released! ⚡️
Updating https://github.com/C-Otto/BitBook/ to modern Spring Boot (3.1 from 2.6).
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).
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...
nostr:note1jj9gcyjd44f4hmevx5f4drcm85nsq3rp9j332s39aq20tdx8ljvsk7gn86
This is a great explanation:
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 :)
nostr:npub12n4hxnynwh6qf76vq6tr3skasuxr9wqahzevr5m05j44z83k076smxsnq5 any updates on that matter? Or would you say that your insights in that video are still up to date? #lightning
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, ...
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 :/
No, that should be fine
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.
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?