Does #reticulum RNS have the concept of ports?
Like RNSADDRESS:18089
#Monero
Does #reticulum RNS have the concept of ports?
Like RNSADDRESS:18089
#Monero
It has the concept of destinations.
It would give you a destination hash based on your identity (public key), app and aspects, e.g:
app name : node
aspects : monero, spending
full name : node.monero.spending
hash : 4faf1b2e0a077e6a9d998ee051f256038
https://reticulum.network/manual/understanding.html#destinations
So
App name : Monero
Aspects : wallet, unrestricted, rpc
Full name : monero.wallet.unrestricted.rpc
Hash : auto generated by reticulum
If somebody else were to use the exact same naming scheme like that, then the hashes would be different, which is how you would tell the destinations apart?
The destination would be different because of different identies.
Also, wouldn't I have to somehow point that at 127.0.0.1:18089?
Or would Monero itself need to add code to do reticulum and or a middleware created that would take the Monero TCP packets and turn them into reticulum?