Matt Corallo
Matt Corallo
I think we do force-close in ~all the cases where the spec says we should, modulo it being unclear what we should do if we're "waiting on a message" from...
A straw-man for this: let's not worry about the general (non-shutdown) case - just document more clearly that users should consider timing out channels after a while, aside from tracking...
> Because the HTLCs will expire or something else? Yea, they'll expire and we'll close. > they send back shutdown and disconnect: do we wait N blocks again for them...
Dropping the milestone as its not entirely clear to me we *want* to do anything here, vs letting the user handle the FC if shutdown is hung (we do now...
Thanks! Now that we have a script, can we run `download_bitcoind_electrs.sh` directly from git CI yaml and then cache the outputs? That way we can avoid wasting all of bitcoincore.org's...
Any update here, looks like we currently can't build due to an MSRV bump in the `time` crate which this would fix.
Is it possible it only caches when running on a merge and not on PRs?
> so I'll need a few more tries to get this right I guess. Alright, let us know when its there :)
> If we recommend it to clients, isn't it better to have it as part of documentation? It is ok to remove this when it is no longer needed imo....
Ah, okay, yea, I guess we can specify that. ISTM we should probably do that in the `Persist` interface docs, though, and would be good to clarify that we're talking...