I haven’t seen this done yet, and can see many applications where it may be necessary (eg. reliable group permissions checks against actions in related DNAs).
I expect the logic to be something like:
- DNA requiring specific network bridge implements some configuration (perhaps simply zome attributes) to specify the allowable DNA hash for the bridge.
- Bridge genesis callback is coded to check the hash of the bridged network against the configured ID and abort if there is a mismatch.
This should enable use-cases like “I have this economic network but only resource types defined within this other external specification DNA should be allowable within the network”. Without the above restrictions, users could simply bridge any specification network they like and start recording events about resources which the network does not know how to deal with.
There are implications here for deterministic cross-DNA validation; ping @pauldaoust