In #825, we ran into the orphan rule where we couldn't implement LDK's serialization traits for Vec<T> (even though we own T, we don't own Vec<T>). The proposed solution is:
We only need to start writing the full vec for prev/next_htlcs when we turn trampoline on, which isn't happening in the imminent 0.3 tag of LDK so it's not critical that the upstream LDK changes land quickly (though ofc would be nice).
In #825, we ran into the orphan rule where we couldn't implement LDK's serialization traits for
Vec<T>(even though we ownT, we don't ownVec<T>). The proposed solution is:prev_htlcs/next_htlcs) in Bump rust-lightning to include trampoline changes #825, which is okay because we haven't turned on trampoline in LDK yet so we're only every expecting a single HTLC in / outdefault_for_vec- see util: add default_value_vec for defaults without LengthReadable rust-lightning#4507We only need to start writing the full vec for prev/next_htlcs when we turn trampoline on, which isn't happening in the imminent 0.3 tag of LDK so it's not critical that the upstream LDK changes land quickly (though ofc would be nice).