Geth’s golang contract bindings need “RPC subscription features that are still under review” to process event logs. What are those features?

The documentation for Geth’s golang contract bindings start out with Please note, events are not yet implemented as they need some RPC subscription features that are still under review. What subscription features are needed, in order to implement events? I’m asking because I’d like to assess the feasibility of making golang’s contract bindings a full-fledged…

What additional considerations are there for dual-funded payment channels?

Naively, it seems like a dual-funded channel should not be much more complicated than a single funded channel; You’d just have an extra input from Bob and it would be reflected in the balances of the first commitment tx. I’m guessing dual-funded channels are more complicated though, since it’s not currently specified in the BOLTS.…