rich1.0Antoine Riard [ARCHIVE] (npub1vj…4x8dd)https://yabu.me/npub1vjzmc45k8dgujppapp2ue20h3l9apnsntgv4c0ukncvv549q64gsz4x8ddnjumphttps://yabu.me📅 Original date posted:2020-01-30 📝 Original message: Hi Max, Sorry by transaction format I didn't mean a binary transaction format, but format like we use in BOLT3 : https://github.com/lightningnetwork/lightning-rfc/blob/master/03-transactions.md My concern is, e.g LN implementations setting nLocktime to 0x00000000, Coinjoin wallets always disabling nSequence and core wallet transactions doing anti-fee snipping. Now even if all of them are using Taproot outputs you're still leaking what protocol/tooling you're using to an external observer due to discrepancies in transaction fields. So we should obfuscate or using standard values as much as protocol semantics let us doing it to break chain analysis heuristics. Le mer. 29 janv. 2020 à 21:00, lisa neigut <niftynei at gmail.com> a écrit : > hi max — great question. PSBT is a great protocol for wallet interop but a > bit overweight for tx collaboration between two peers > > On Wed, Jan 29, 2020 at 17:29 Max Dignan <maxdignan at gmail.com> wrote: > >> Hey Antoine, >> >> Would PSBT (BIP 174 - >> https://github.com/bitcoin/bips/blob/master/bip-0174.mediawiki) be a >> good solution to this? >> >> -Max >> _______________________________________________ >> Lightning-dev mailing list >> Lightning-dev at lists.linuxfoundation.org >> https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20200129/9921c64a/attachment.html>