When I was reading the MLS protocol last year, I was picturing using it to rearrange destinations for the usual NIP-17 gift wraps such that Clients would use the group ratchet to find where the group is at. In that way, it would simply reuse the usual NIP 17 messaging scheme.
However, the unclear part to me is how much metadata leaks in the key exchange procedures. There will be messages going back and forth between member to rotate the group into new keys and I think that has a change of being traceable. Time correlations could allow the public to reassemble the hierarchy of keys.
It feels like MLS authors were trying to solve group chats so that they forgot about metadata tracing on all intermediate needs of the protocol.
But I also think that the metadata leak is solvable. We just need to invest the time to do it.
Vitor Pamplona
npub1gcx…nj5z
2024-06-24 04:15:43
in reply to nevent1q…4q6p
Author Public Key
npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5zPublished at
2024-06-24 04:15:43Event JSON
{
"id": "13f2fd44919b196765ed1d7a1c7e9322c49e1d2606086a8473d0f4d930e431b1",
"pubkey": "460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c",
"created_at": 1719195343,
"kind": 1,
"tags": [
[
"e",
"3d71f2d1148d912d4cec27d8f39eed7535efb33dfdad76991baf466a0ff1fc30",
"",
"root"
],
[
"e",
"5d88e68785232f4128159278417b23a906d39cd70794b4db128523b19160b4a7"
],
[
"e",
"49d177bdae604a482166d67ccb1d0204226e2c33ad3db88a6e61bd19b8b5cafb",
"",
"reply"
],
[
"p",
"460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c"
],
[
"p",
"7adb520c3ac7cb6dc8253508df0ce1d975da49fefda9b5c956744a049d230ace"
],
[
"p",
"1739d937dc8c0c7370aa27585938c119e25c41f6c441a5d34c6d38503e3136ef"
],
[
"p",
"1577e4599dd10c863498fe3c20bd82aafaf829a595ce83c5cf8ac3463531b09b"
]
],
"content": "When I was reading the MLS protocol last year, I was picturing using it to rearrange destinations for the usual NIP-17 gift wraps such that Clients would use the group ratchet to find where the group is at. In that way, it would simply reuse the usual NIP 17 messaging scheme.\n\nHowever, the unclear part to me is how much metadata leaks in the key exchange procedures. There will be messages going back and forth between member to rotate the group into new keys and I think that has a change of being traceable. Time correlations could allow the public to reassemble the hierarchy of keys. \n\nIt feels like MLS authors were trying to solve group chats so that they forgot about metadata tracing on all intermediate needs of the protocol. \n\nBut I also think that the metadata leak is solvable. We just need to invest the time to do it. ",
"sig": "76ead0f49decd03e113ea7bafc54a24eb1c65586ffe03c887aa6f90a059a0a2e0aa7ea682a62c6fa7e21e33af430228c67d51e6716bf7e22e567b4d74a988291"
}