<j​pk68:matrix.org> As it seems the new Trezor wallets rely on Noise for their wire protocol, I was wondering what the preferred approach might be to implementing such a protocol in core. Regarding Noise, specifically

<j​pk68:matrix.org> Neither libsodium or OpenSSL support Noise (just its primitives), so it would have to use an existing Noise library (of which none are very widely adopted), or we could roll our own, I suppose

<o​frnxmr:xmr.mx> Nobody is looking at it

<j​pk68:matrix.org> Yes, I know :)

<v​tnerd:monero.social> Their new protocol looks like a beast. That's all I got so far

<j​pk68:matrix.org> Just curious for the future

<o​frnxmr:xmr.mx> Id say: look at some other chain that implemented it (if any did)

<j​pk68:matrix.org> Haha, I came to the same conclusion. I did read your writeup on the proposed P2P encryption support... did you have a Noise implementation in mind to use for that?

<j​pk68:matrix.org> There is also the option of using Trezor's Rust library if/when it comes out, or making some sort of wrapper for their Python code

<v​tnerd:monero.social> I initially proposed noise based on feedback from discussions at a monerokon then pivoted to ssl

<v​tnerd:monero.social> There were some interesting features, but it didn't seem worth the effort. In the end the ssl patch has received little reviews anyway, so perhaps I should've just gone for the noise implementation

<v​tnerd:monero.social> We can probably roll our own for trezor if needed, it's not terribly difficult assuming they pick just one specific algorithm

<j​pk68:matrix.org> It's just Noise_XX

<j​pk68:matrix.org> Someone made a Bitcoin-only library for the protocol already, which apparently works and could perhaps be a useful reference:

<j​pk68:matrix.org> github.com/coreyphillips/trezor-connect-rs

<v​tnerd:monero.social> The noise protocol is just for safe 7 right? The others use the older existing protobuf scheme?

<j​pk68:matrix.org> Yes, I believe so

<v​tnerd:monero.social> I guess they did it because Bluetooth (and maybe) nfc, but damn is it annoying from our perspective

<v​tnerd:monero.social> Actually nfc power limits should be too low for monero txes but maybe I'm craY

<v​tnerd:monero.social> *crazy

<j​berman:monero.social> maybe we should get the p2p SSL patch running on beta to get it some good testing

I'm very much not a fan of adding a large number of rust crates or re-introducing Python to our supply chain to support one vendor's custom wire protocol.