Avatar
Jestopher
391819e2f2f13b90cac7209419eb574ef7c0d1f4e81867fc24c47a3ce5e8a248
Co-founder of Amboss Technologies, Inc. "Never before has greed tempted me to live a very simple life." Mostly #memes & #lightningnetwork thoughts https://amboss.tech

Rails - Self-custody yield from Lightning

https://a4s.me/rails

It's wild to see this waitlist for Rails and it gives me a ton of hope about bitcoiners' desire to help the network as well as earn self-custody yield.

Our biggest challenge is to balance the market and that balance comes from liquidity subscriptions and lightning payments.

https://a4s.me/rails

Right; this isn't reproducible by most routing nodes.

You have to be driving massive volume and actually paying out via lightning.

Payroll providers could reproduce this.

There's actually a lot more to this!

The directionality of their traffic is a massive factor here. This isn't a result of cash app users paying fees to c=; is because users are paying OUT.

Replying to Avatar HERMETICVM

I’m considering to run my own Lightning node with a self-hosted nostr:npub1getal6ykt05fsz5nqu4uld09nfj3y3qxmv8crys4aeut53unfvlqr80nfm Hub but I'm not sure I fully understand what that entails yet.

Here is what I’ve understood so far: Opening my own channel makes sense if I start with at least 100.000sats, though 1.000.000sats is recommended. I’d stick with 100k sats for now while I get my feet wet but I’d increase it as I gain experience and confidence in my node.

How do I decide if I run a private or public or private channel? So far I mostly use Minibits and Wallet of Satoshi for my zapping needs.

If I were to run a public channel intending on making a few sats by handling lightning transactions for others, how would anyone know of my channel? Do they even need to know my channel or would my peers offload some of their transactions to my node?

If I were to handle transactions for others, is there a good tutorial on how to debug transaction issues?

#asknostr #lightning

I'm always a fan of public nodes, because it provides public infrastructure for payments and gives you a potential revenue stream. Public channels use "gossip" in BOLT 7 of the lightning spec to advertise channels existence.

Handling public transactions is at the protocol level and doesn't require any debugging. The only thing you need to worry about is doing channel backups regularly and the health of your channel database.

Try bootstrapping your new node with a small liquidity subscription at ~$5/month, which will ensure that your node can route, not just send:

https://a4s.me/ls

Generous benefit package

Just tidying up

#memes #funny

What service

#memes #funny

No one saw disco coming back...or anything at all

#memes #funny

Thank you for all the zaps!

Together we can go far

'tis but a scratch