Given APM's current implementation, as its own DAO built on top of aOS, it doesn't make a lot of sense for it to be bundled together with aOS. Auditors have also commented on it being a source of confusion as to how the system works and is deployed. For all intents and purposes, APM is already logically decoupled from aOS.
This also lowers the general complexity of aOS, in its contracts, tests, and deployment strategy.
A few nice things to do when migrating:
Given
APM's current implementation, as its own DAO built on top of aOS, it doesn't make a lot of sense for it to be bundled together with aOS. Auditors have also commented on it being a source of confusion as to how the system works and is deployed. For all intents and purposes,APMis already logically decoupled from aOS.This also lowers the general complexity of aOS, in its contracts, tests, and deployment strategy.
A few nice things to do when migrating:
keccak256()constants and replace them with their hashesInvestigate the APM-native apps' app IDs (e.g.(moved to apm repo: Investigate the APM-native apps' app IDs (e.g.apm-repoandapm-enssub)apm-repoandapm-enssub) apm#2)APMRegistryFactoryMockis necessary, and if so, fix the app IDs in the test mock (moved to apm repo: Investigate whetherAPMRegistryFactoryMockis necessary, and if so, fix the app IDs in the test mock apm#3)