ryanthegentry

Default is “the maximum msats worth of HTLCs that can be pending (or in-flight) on our side of the channel.” And `lncli openchannel —remote_max_value_in_flight_msat` allows you to adjust beyond that default upon channel open.
https://github.com/lightningnetwork/lnd/commit/a66a1e113fb04912ac2e8ae62446bce8fed8d12a

2023-04-04 23:38:29 GMT

- reply

Afk but can check later. What default would you consider proper?

2023-04-04 22:50:46 GMT

- reply

Lnd allows you to set both max_value_in_flight and remote_max_value_in_flight_msat per channel. Is that what you’re talking about? Both set “the maximum amount of coins in millisatoshis that can be pending in this channel.”

2023-03-29 17:31:45 GMT

LND 0.16 is officially here, upgrade today!
https://lightning.engineering/posts/2023-03-29-lnd-0.16-launch/

2023-03-27 14:07:15 GMT

- reply

Pls gib ☠️

2023-03-23 18:23:43 GMT

- reply

🤣☠️

2023-03-22 14:28:57 GMT

- reply

It’s (gonna be) raining sats, hallelujah!

2023-03-22 01:12:31 GMT

The WSJ wants Zaps, they just don’t know it yet ⚡️
https://www.wsj.com/articles/algorithms-ai-humanity-psychology-ebf1364c
https://nostr.build/i/nostr.build_d02489d0806216f3e6dbba9ce8d8dc42d3d38cdca67909c20fcd6bd2810296c9.jpg

2023-03-21 17:10:57 GMT

- reply

Love to see it

2023-03-21 17:08:42 GMT

- reply

💯
Not an excuse to not prioritize self-custody as a first class citizen at the protocol layer! But def an important check that I wish people considered when catastrophizing about custodial product usage.

2023-03-21 14:50:14 GMT

- reply

Tyvm. Very cool application! Excited to try it out 🤙

2023-03-21 14:44:00 GMT

- reply

🤝

2023-03-21 14:35:15 GMT

Is the habla.news developer on here? I’m trying to figure out how it works after #[0] showed me the new #[1] integration last week. Very cool serverless Medium/Substack replacement.
Am I correct in thinking it only displays NIP-33 events? Trying to figure out why I can’t find habla.news posts on Damus or nostr.band.

2023-03-21 13:51:49 GMT

- reply

In terms of lowering systemic risk, is there a better potential step-wise improvement than eltoo (whether the anyprevout way or the ctv+something else I’m forgetting way) for enabling cheap watchtowers and generally less toxic state?

2023-03-21 13:42:55 GMT

- reply

If I misread the hot potato comment, and you meant in terms of passing risk around, sorry! Realized that after my post. Yes agreed that on a system-wide scale risk is constant and one user sub swapping out just passes their risk to another, we’re on the same page there now.

2023-03-21 13:40:32 GMT

- reply

So when a channel depletes, the receiver should splice out and the liquidity provider should JIT splice in, incurring two on-chain txs? That seems coordination-heavy and expensive, I guess best case a 2 input (splice in + og channel) 2 output (splice out + new channel) with some musig coop magic? Sub swaps are just 1 in 1 out in the best case, no cooperation with peer necessary.
Re hot potato, kind of but there’s additional nuance imo. If you’re paying routing fees your tx is an economically viable one is my book, same as on-chain 🤷‍♂️ What keeps LN from being zero sum today is 1) new entrants opening new channels adding liquidity to the network and 2) sub swap providers facilitating liquidity exiting the network while leaving channels open. Activity might not be perfectly economically rational, but it’s significantly improved over the last several years and trending very positively imo.
I think a worse outcome long term than lost money from a mass exit attack would be node operators locking down the permissionlessness of new channel peers. That would be very sad and harmful to the incentives of the network. So please don’t do it to make a point, lol!

2023-03-21 13:08:44 GMT

- reply

🤝

2023-03-21 13:07:56 GMT

- reply

How do you reclaim inbound liquidity to continue receiving payment after a splice out?
Yeah good point re the second hop past the attacker, I was missing that thank you! Though if they’re doing the same thing, and pushing received sats to a submarine swap provider (which I did suggest generally and there are open source versions of!) or just an exchange, maybe the reason we haven’t seen any mass exit attacks is that routing nodes are being well compensated enough for the services they provide that the economics of a mass exit attack just haven’t made sense yet. If you’re consistently making a few % by providing and managing liquidity, and there’s no asymmetric payoff available by rugging, why would you rug and forgo all the potential future earnings? In DeFi we generally saw that calculus change when growth reversed.

2023-03-21 12:53:12 GMT

- reply

#[2] wrote a great article on this last year!
https://bitcoinmagazine.com/technical/community-banks-improve-bitcoin-adoption

2023-03-21 12:51:44 GMT

- reply

Few understand that one way for BTC to fulfill its destiny as a medium of exchange is as a global routing currency at the core of LN
#[0]

2023-03-21 12:43:53 GMT

- reply

Not bad advice, but it is vitally important that anybody who wants to run a routing node can. The free market economics of LN and most of its other valuable properties depend on the permissionless entry/exit of routing nodes into the network. We should endeavor to make the barrier to entry as low as possible for anybody who wants to compete in the market, though ofc not everybody can win and some people will end up losing some sats instead of profiting.

2023-03-21 12:38:08 GMT

- reply

Correct me if I’m wrong, but in my mind the mass exit attacker controls one or several routing nodes. During a full mempool, the attacker closes channels with bad states paying themself all the money in the channels, and prevents counterparties from publishing justice txs, right? So they claim all the funds in all the closed channels, regardless of prior inbound/outbound balance of each channel.
This attack is maximally effective theft-wise if the prior state of all channels is 100% inbound to the attacker, as they’ll go from having a claim on 0% of funds, to owning on-chain 100% of funds. This attack is minimally effective theft-wise if the prior state of all channels is 100% outbound from the attacker, as they’ll go from having a claim on 100% of funds to owning on-chain 100% of funds. So honest nodes can mitigate the damage from such an attack (and collectively lower the potential returns to an attacker) by consistently Looping out received funds from their local balance and realizing them on-chain.
I don’t necessarily consider that “hot potato,” with fees so low it makes sense for funds in LN to be high velocity! For this scenario, I always use the comparison to old timey brick and mortar merchants and their cash registers. During the day, the register fills up with cash. At the end of the day, to avoid theft, the proprietor would physically take their cash to the bank for safekeeping, and leave an empty register in their store. With bitcoin, you ofc can be your own bank by owning funds on-chain, so instead of taking cash to a 3rd party you can just send funds received on LN to an on-chain address you control. Loop or submarine swaps more generally help you do that without closing channels, to reward your liquidity providing peers for their service.

2023-03-21 03:21:50 GMT

- reply

Yeah true. Maybe we just got lucky that amounts were too small in LN while security was bad, that juicier targets existed while amounts increased, and now there’s pretty good remote signer stuff across different implementations to help mitigate 🤷‍♂️

2023-03-21 00:42:47 GMT

- reply

🎤💧

2023-03-21 00:41:39 GMT

- reply

It’s a really good question. I’d say it’s been really hard for a single attacker to actually steal funds en masse due to lack of single honeypots and isolation of funds in different channels with different counterparties. This might change as amounts get bigger, but the incentive design means payoffs should never be asymmetric like we see if DeFi (tiny effort, huge theft potential).
It’s not as hard to grief a node via channel jamming but the attacker can’t directly steal money, can just enjoy the pleasure of being an asshole for a while. Hence why lower hanging fruit attacks haven’t really been exploited yet.

2023-03-17 16:34:28 GMT

- reply

We have read-only mode in Terminal Web. Will be able to easily connect from voltage to TW 🔜

2023-03-15 17:07:31 GMT

- reply

Relevant: https://twitter.com/xiaowang1984/status/1634745335099666433

2023-03-15 17:05:37 GMT

- reply

Dario is the man, excited to listen!

2023-03-15 17:02:20 GMT

- reply

Nice! Think the monthly DM subscription model should work well. Excited to test it!

2023-03-13 20:28:15 GMT

- reply

K.R.E.A.M!
iykyk 😤
#[0]

2023-03-10 14:39:27 GMT

- reply

shifty eyeballs dot gif

2023-03-09 15:48:58 GMT

I finally finished Mandibles last week and oh god now I’m turning into #[0] 😱

2023-02-27 19:36:44 GMT

- reply

More to come on this soon ™️

2023-02-22 22:09:58 GMT

- reply

1000 sats?

2023-02-22 14:59:47 GMT

Yooo #[0], zaplife.lol is super cool! Real time dashboard displaying zaps, and tracking top notes and profiles based on their zap count ⚡️

2023-02-20 20:28:21 GMT

- reply

Oh nice! Do you know anything about this? #[5]

2023-02-20 20:26:47 GMT

- reply

Well from looking at NIP-11 idk if a given user’s “paid” status is even discoverable by the client. Seems like rn it’s kinda honor code “give relay your npub, pay invoice, relay promises to store your events and serve you new events” which is fine, but should relays have a public index of which npubs have paid to make it less trusted?

2023-02-20 20:16:41 GMT

- reply

Nice, thanks! One thing I wanted to test was the nice green $ icon in Damus’s relay page… would be awesome if it was not-green for paid relays that hadn’t been paid yet. Looks like NIP-11 is the spec governing that relay info doc, but not sure if user payment status is discoverable like that… do you know?

2023-02-08 21:03:57 GMT

I've never been more bullish on the #bitcoin builder community. So many exciting new things being built in public today, and so much more to come later this year! 🚀

2023-02-06 20:36:33 GMT

- reply

wen “uncle and his nephews private relay” ?

2023-01-23 21:01:47 GMT

- reply

ser wen NIP-05 verification
https://mutatrum.com/nostr-verification-through-github-pages/

2023-01-20 01:30:48 GMT

- reply

Thought it was cool to show LL is supporting nostr!

2023-01-19 22:43:34 GMT

- reply

Oh gotcha. Maybe I should've said "employer" instead of "company" to be more clear, since I just changed my NIP-05 from my personal website to my employer's website.

2023-01-19 22:34:20 GMT

- reply

What’s not a company? Who said anything about payment?

2023-01-19 22:15:59 GMT

Does your company offer NIP-05 verification services?

2023-01-18 19:03:07 GMT

- reply

I’m pretty sure, what say you #[3]?

2023-01-18 18:49:54 GMT

- reply

Teens love free food, give them enough sats to buy a large pizza through Fold or Bitcoin Company or a similar vendor?

2023-01-17 19:17:01 GMT

- reply

Yes they provide inbound through their Flow product, and will provide Autoloop 🔜

2023-01-17 14:10:11 GMT

- reply

Added 🤙

2023-01-17 14:08:34 GMT

- reply

Voltage supports LNBits!
https://voltage.cloud/blog/feature-updates/lnbits-now-available-on-voltage/

2023-01-14 19:08:17 GMT

- reply

LFG 🤙

2023-01-14 15:44:57 GMT

- reply

Maybe I saw #[3] posting about it…?

2023-01-14 13:17:47 GMT

- reply

Awesome. Is there an event associated with each tip? It would be cool to sort the feed by “most tips in last 24hrs” or something

2023-01-12 22:17:00 GMT

- reply

Lol fixed, thank you!

2023-01-12 22:16:41 GMT

- reply

🤦‍♂️🤦‍♂️🤦‍♂️

2023-01-12 20:59:01 GMT

V heartwarming to see BTC outpumping alts again. Nature is healing ❤️‍🩹

2023-01-12 13:26:03 GMT

- reply

It was a good post!

2023-01-12 13:25:09 GMT

- reply

Welcome 🤙

2023-01-12 13:24:24 GMT

- reply

Gotcha so an example would be a new RPC `lncli publishevent`?
Tbh I think it would be a cleaner separation to have an external nostr client use the `lncli signmessage`RPC. And maybe we could include that in the litd bundle? So users running the bundle could hit `litcli publishevent` which calls the nostr client which generates a message for lnd to sign… what would you think about that?

2023-01-12 00:17:39 GMT

- reply

What changes would need to be made to enable native nostr support on LND? We already have secp256k1 Schnorr sigs, don’t we?

2023-01-11 17:59:41 GMT

- reply

wen “indefatigable titan” in bio? 😂
Nice read!

2023-01-11 13:19:35 GMT

- reply

Humility being key to broader dev adoption is such a great and underrated point

2023-01-11 12:27:07 GMT

- reply

😇