Behavior on unknown chainslug about socket-dl HOT 5 OPEN

Currently socket stores the plug config for each toChainSlug which is used at outbound to get the capacitor address where the messages are queued in the packets which are transmitted to toChainSlug.

We have 2 cases here:

1. If there is no switchboard for toChainSlug, plugs cannot register for that slug and hence call will revert.
2. If someone registers the switchboard for this unsupported toChainSlug, plugs will be able to register and hence outbound call will go through. But the transmission will not happen.

from socket-dl.

I think plugs cannot connect in case there is no capacitor. So unless someone connects a switchboard to some remote chain, plugs cannot send messages.

from socket-dl.

makes sense, I can totally imagine a transmitManager has an open function that allows anyone to seal for unregistered destChainSlug

from socket-dl.

ok makes sense and its basically upto the transmtiter managers to decide if they serve the toChainSlug or not, people can keep sending messages all day long

from socket-dl.

Only if transmitter has the role. Transmitters are chain specific, so they can only seal/propose if we grant roles for this new toChainSlug.

from socket-dl.