Eirikr70
Reading a little bit the documentation, it seems that Reticulum is focused on decentralized communications and mesh networks.
To my understanding, it's just a way to send bytes from point A, to point B.
The encryption seems solid enough to prevent relays from sniffing random data, but this doesn't prevent the application that receive the message to be bug free.
To better say, Reticulum will take care of the delivery of the data, then you will have a program that will use this data.
Part of your security (if not most of it) is tied to how the "responder" is coded.
The first thing I can think of, is that Reticulum doesn't provide any meaningful way to address who is the sender, so you cannot discern if the messages come from a trusted device or not.
This will require you to take care of that to prevent people from misuising whatever program you have after Reticulum delivery.
To use a real world example, if you look into LXMF you will see that they are including the sender into the message, to let the destination correlate future messages.