The specification of ocap URLs (https://github.com/MetaMask/ocap-kernel/wiki/Notes-on-ocap-urls) includes provision for locating and establishing connectivity with (in a decentralized peer-to-peer network) whatever kernel needs to be contacted in order to send messages to the object it designates. The current implementation (#578) pretty much ignores this hint feature, falling back on some hardwired testing infrastructure that certainly works in the development phase but which will be entirely unsuitable for deployment. The implementation needs to be augmented with support for location hints in ocap URLs (or whatever additional infrastructure we determine we need for establishing remote connectivity in a peer-to-peer world).
The specification of ocap URLs (https://github.com/MetaMask/ocap-kernel/wiki/Notes-on-ocap-urls) includes provision for locating and establishing connectivity with (in a decentralized peer-to-peer network) whatever kernel needs to be contacted in order to send messages to the object it designates. The current implementation (#578) pretty much ignores this hint feature, falling back on some hardwired testing infrastructure that certainly works in the development phase but which will be entirely unsuitable for deployment. The implementation needs to be augmented with support for location hints in ocap URLs (or whatever additional infrastructure we determine we need for establishing remote connectivity in a peer-to-peer world).