Should each Org (LegalEntity) have its own blockchain address instead of one address per registry node?

[marcvanandel]

Currently each Registry Node has its own ID on the blockchain and all events produced in a specific node will get this address as origin. In the Registry Node this origin address is checked and only objects with the same address ID are eligible for updates and changes. This seems to be a fair and safe base ... but has consequences (or boundaries) as well. Additional aspect is that Organizations and Devices (with all details) are shared on the blockchain, but users are not.

• What about a fresh installation of a Registry Node (e.g. after calamities) and all users bound to Organizations are deleted. How does a user join an Organization again and becomes an Admin for this Org? see Improving Admin in Organization existance #216
• In the case of an institute is joining the Registry Node of another institute this registers itself as an Organization on that Registry Node and all its Devices. At some point in time this institute might decide to move towards its own Registry Node for some reasons. This Registry Node has a different blockchain address ID and therefor its registered Organization and Devices can not be managed from the new Registry Node instance (without changes at least)
• What else?

This needs to be discussed and designed in a robust way. Should each Organization (LegalEntity) have its own blockchain address instead of the Registry Node ID? 🤔