--- Log opened Thu Apr 29 00:00:40 2021 00:43 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 240 seconds] 06:54 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #rust-bitcoin 07:56 < BlueMatt> ariard: did you see https://github.com/rust-bitcoin/rust-lightning/pull/893#discussion_r622655211 ? 08:30 -!- ghost43_ [~daer@gateway/tor-sasl/daer] has quit [Quit: Leaving] 08:30 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #rust-bitcoin 09:00 -!- awesome_doge [awesome-do@gateway/shell/matrix.org/x-sgdrymxrtfyrvqyv] has quit [Quit: Idle for 30+ days] 12:03 < ariard> BlueMatt: yes mentioning in the docs sounds good to me for now, and i'm making a mental note to verify the dosability in the future of our whole client API 12:03 < ariard> in case it's accessible to third-party on public servers like you're pointing to 12:05 < BlueMatt> yea, good point. I mean if we're concerned with "someone can cause us to do unbounded storage", sadly, just accepting a payment implies that :( 12:05 < BlueMatt> or even accepting a forwarded payment that we dont have the preimage for 12:18 < ariard> BlueMatt: right and we have timer before cancelling a payment iirc? but in practice your storage is bounded by your channel slots 12:18 < ariard> like N * 483 where N is number of channels 12:19 < BlueMatt> yea, well 483 per [100, 500] milliseconds isnt nothing either 12:20 < ariard> hmmmm we're concerned by memory DoS, not CPU ones? 12:20 < ariard> though we should check onion decode in the future 12:23 < BlueMatt> i mean, I'd assume we're concerned about all of the above, but cpu-wise its kinda bounded by what our immediate counterparty is able to forward to us 12:33 < BlueMatt> ariard: ok, see #905 12:37 < BlueMatt> ariard: do you want me to dig into fuzz for the dust_limit_satoshis constant change? I'm hoping to get 0.0.14 out the door tomorrow, so that needs to either land or slip to 0.0.15 12:37 -!- jonatack [jon@gateway/vpn/airvpn/jonatack] has quit [Ping timeout: 252 seconds] 12:38 -!- jonatack [jon@gateway/vpn/airvpn/jonatack] has joined #rust-bitcoin 13:22 < ariard> BlueMatt: yep goodwith #905 13:23 < ariard> BlueMatt: looking on dust_limit_satoshis in a hour, will elt you know if i can't figure it by myself :) 13:30 < BlueMatt> ariard: gotta leave that ack :) 15:07 < ariard> BlueMatt: it's done for the ack, also open an issue to track the scope question on #895 15:07 < ariard> *opend 15:07 < BlueMatt> thanks 15:07 < ariard> *opened 16:43 -!- shesek [~shesek@unaffiliated/shesek] has quit [Remote host closed the connection] 16:43 -!- shesek [~shesek@164.90.217.137] has joined #rust-bitcoin 16:43 -!- shesek [~shesek@164.90.217.137] has quit [Changing host] 16:43 -!- shesek [~shesek@unaffiliated/shesek] has joined #rust-bitcoin 17:02 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #rust-bitcoin 17:05 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 252 seconds] 17:07 -!- belcher_ is now known as belcher 17:13 < ariard> BlueMatt: still debugging dust_limit_satoshis fuzz, there was at least a superflous feerate request at channel acceptance 17:13 < ariard> but i still have another unsolved failure, last commitment tx broadcast isn't detected and thus doesn't trigger HTLC failure 17:14 < ariard> so dunno if it's the commitment tx never registered or the broadcasted commitment tx which is malleated 17:14 < ariard> BlueMatt: i'll finish to look it on tmrw but if you wanna look on it meanwile up to you! 17:15 < BlueMatt> ariard: ok, if I find time I will, trying to ship a java bindings update tonight, though 17:35 -!- tibo [~tibo@2400:4050:2a83:7000:655e:70e9:a1a3:b5bb] has joined #rust-bitcoin --- Log closed Fri Apr 30 00:00:41 2021