Is BOB really NNS controlled now

General
1

is BOB really NNS controlled now?

2

[Regarding NNS controlling application canisters

Unless dfinity changes their position, no third party canister can be controlled by the NNS because dfinity will proactively reject any attempt to upgrade the canister.(and they currently trigger 90% of the vote in that topic)

I’m sure that if this position changes dfinity will let everyone know well in advance, especially those waiting for the procedure to allow this.

2 Likes
3

hi, thanks for your reply, but I am looking for an an understanding on how BOB is now controlled by NNS, was that done through a ICP transaction etc,

4

It was not done(properly). The understanding you should have is that they submitted their canister to NNS control and now it can’t be upgraded if they find a bug unless dfinity changes their mind.

1 Like
5

just curious, how should it have been done?

6

It should not have been done. DFINITY does not want 3rd party canisters controlled by the NNS until:

  1. The voting power has been disbursed enough that DFINITY doesn’t have de facto control(and thus responsibility) of approving the code to be installed.
  2. and/or a process is in place to give voters assurance that the code being deployed has been audited and will not cause a block of an NNS upgrade/ subnet recovery if something goes wrong.
1 Like
7

but then what is so special about BOB that Dfinity made an exception and agreed to take it under NNS control

8

DFINITY did not agree as far as I know. Anyone can change their controller to the nns. I did so with the subscription utility before they announced this policy and now the canister is dead because we couldn’t upgrade it when it was necessary.

dfx canister --network ic update-settings add-controller nns-principal is all you need to do to give the NNS control. Once you do, at the current moment you are SOL if something goes wrong or you need to make a change.

9

got it, thanks for the insight!
If that’s what the BOB team do, then it was an opportunistic move by BOB to claim NNS fame and provide legitimacy to BOB, not that it needed any legitimacy.
A better solution would have been to create a new canister under SNS control and change the BOB controller to this new SNS-BOBCanister and give the ICP-neurons voting power(not sure if that is possible). regular ICP(Neurons)–>vote==> SNS-BOBCanister–>deploys changes to ==> BOBCanister

10

BoB now has the NNS root canister as an additional controller so that NNS proposal could be used to upgrade the canister if needed. The original controller dmhsm-cyaaa-aaaal-qjrdq-cai has not been removed though and thus BoB can also be upgraded in a centralized way as before. You can check out the IC dashboard to see the current controllers.

2 Likes
11

Very curious noob here, is it possible for Caffeine AI, once released, could perform the code upgrades instead of involving the devs @ Dfinity?

12

if you mean if Caffeine AI can enhance the code of the canister and then initiate
a SNS vote to upgrade the canister, I think so yes

1 Like
13

Correct, the whole point of decentralization is to present to the community before upgrading.

14

How does one add dmhsm-cyaaa-aaaal-qjrdq-cai or oh4fn-kyaaa-aaaaq-aaega-cai for bob under oisy or the nns to see transaction history

or is it something else we need to add, and if so what is the canister id/index canister?

15

I don’t think Bob has an official index canister, but anyone could deploy one. They are fairly expensive to operate.