Laundry list of inter-peer wire protocol changes

The email discusses proposed changes to the Lightning Network protocol. One suggestion is the use of open-coded messaging instead of protobufs or JSON encoded objects. Another suggestion is implementing a length prefix for initial key exchange and other packets. Additionally, the author recommends designing an equivalent testnet. There is also discussion about the complexity of HTLC pipelining and the potential adaptation of protobufs.Regarding security and efficiency, the Lightning Network protocol includes several features such as exchanging two sets of version bits during the initial handshake after key setup. The protocol also uses AES/HMAC-SHA256 or Chacha20/Poly1305 for wire protocol crypto and separate encoding streams for packet lengths to make traffic analysis harder. Shachain and elkrem are tools used to generate revocation secrets to minimize storage and computation for old commitment transactions. The protocol can allow re-anchoring of channels to add or remove funds, and multi-sig transactions can enable escrow-style services by allowing more than one signature on commit transactions. However, there is debate over the use of R value vs. a keypair scheme to decorrelate transactions. The author encourages individuals to clone the lightning-core repository and write up their specifications for easier commit once discussion is done. Other potential areas of discussion include connection/node failures and designing for various node failure modes.