pull down to refresh

There's no obvious good (nor bad). One important factor is what kind of node you'd like to run, and all of the following is about running a routing node. If you send/receive a lot (for whatever reason), things are very different.

I wrote down some ideas on https://c-otto.de. If you decide to open a channel to my node (c-otto.de), it needs to be 10M sats or more. Furthermore, I regularly close channels if they don't perform (in comparison to the other channels). For this I take into account how many sats are "stuck", see https://github.com/C-Otto/lnd-manageJ/blob/main/rating.md for a more detailed explanation.

In general I'd recommend opening (and maintaining!) just a few larger channels, instead of having a higher number of smaller channels. This, of course, depends on how many sats you'd want to have on your node (which, then, is a hot wallet). If that amount is below 5 BTC, I'd recommend not running a routing node.

I personally really liked Alex Bosworth's talk (from five years ago): https://www.youtube.com/watch?v=HlPIB6jt6ww

If you're inexperienced, I suggest you start slow. Just a few channels, not a whole lot of liquidity, to get your feet wet. You'll learn a lot (and you have to learn a lot), and you'll need some time to adjust your tooling.

reply

I'm going to jump in here and comment as I'm the author of that article.

I originally wrote that piece to warn the Bitcoin community of you and your teams generally shitty behavior at obelisk to your customers.

Your competitors were not aware of that piece until I published it as a PSA. They had no involvement in it's writing or publishing.

Some of the behavior I experienced as an obelisk customer personally from you:

A) promising compensation for delayed miners, crediting it to users accounts, and then NEVER PAYING THEM OUT
B) being personally named for good reason in the subsequent lawsuit, since you yourself promised compensation in the obelisk discord at the time was coming, including honoring of coupons for future products such as hardware wallet devices https://www.classaction.org/news/class-action-filed-over-obelisks-sale-of-sc1-dcr1-cryptocurrency-miners
C) generally stringing your obelisk customers along to get them to not join the lawsuit
D) over promising on delivery times, which were late by months if I recall correctly

Or absolve Ken from obelisk/foundation of

D) over promising on the hashrate of the ASICs your team produced by 1/3rd!

When confronted with these facts on twitter you yourself dmed me in a rage, then blocked me. Your company twitter then blocked me. Then your staff blocked me so I can't respond to their comments saying the article was "debunked."

News flash: calling something debunked doesn't make it debunked. You have to actually provide evidence to the contrary. Which you haven't done. All I've seen you do is hand wave this sordid chapter away as a nuisance to your current enterprise. When it's very very relevant.

I encourage your customers to take a close look at you and your teams history. To verify the information in that article independent of my valid points.

You would rather have me silenced.

I would rather see you recognized for the animal you are.

reply