cpbhu-5iaaa-aaaad-aalta-cai is the cycleOps black hole.
a7pjh-xiaaa-aaaai-atlbq-cai Is an ICRC-120 wasm orchestrator. It is used to install upgrades, stop canisters, take snapshots, start, etc. Under ICRC-137 governance, this will be the only controller that isn’t a black hole.
akiyk-waaaa-aaaai-atlca-cai - This is the Veto Lifeline canister…it will be a controller of the main 137 veto canister and the 137 veto canister will be the controller of the lifeline canister. This is a similar setup to the NNSRoot/NNSLifeline - https://dashboard.internetcomputer.org/canister/rno2w-sqaaa-aaaaa-aaacq-cai. Basically, if something goes horribly wrong, these canisters can upgrade each other to get them back online. It isn’t necessary to have this setup, but it is safer.
These two:
ufef3-ic2bp-enpmy-5ezyw-z4p5q-mzgsv-w24y3-2v2b6-ktjpk-cjik4-kae,
mctz3-uvscw-rbtha-zdzis-q46vd-vzbza-bxjk5-mleuf-jml6g-s2hq3-vqe
Are ICDevs controllers and will be removed when it exits alpha.
So if you want to deploy your own 137 governance system, you want to minimize controllers, then you really only need an orchestrator canister as your only controller. CycleOps and lifelines are optional. It would be nice if the canister were only its own controller, but you’d get stuck if you ever stopped it and upgrading would take a lot longer or have workflow issues if the stop, snapshot, upgrade, start got out of order because of vetos or voting. Using ICRC-120 makes it a single command icrc120_upgrade_to.
If you want to read more about ICRC-120 - Canister Orchestration, you can do that at ICRC-120 - Canister Wasm Orchestration Service Specification · Issue #120 · dfinity/ICRC · GitHub or ICRC-120 – Canister Wasm Orchestration Service
As a side note, who is the authority for the ICRC namespace, and/or how are available numbers determined?
It is fairly permissionless…just create an issue at GitHub · Where software is built and then write a draft.