There is curiosity about whether Go has suitable secp256k1 bindings necessary for EllSwift pubkey encoding. It is noted that the btcd library, a project by decred, employs a custom secp256k1 library. However, questions are raised about the library's currency, performance, and quality.

Another significant point of discussion is the concept of static configuration for light clients as opposed to patching them. This method avoids modifying the light client directly, which is advantageous. Nonetheless, concerns are expressed regarding this approach. One issue is whether light clients can handle adding multiple peers with the same IP address but different ports, given that proposed patches for light clients work at the socket level, making the proxy use transparent to the client's higher-level logic. Another question is how users would identify which remote peers to configure, considering the variance in peer requirements across different light clients. Despite these challenges, there's an acknowledgment of the value in experimenting with this idea.