can not start threebot server using a 3bot account in mainnet

[Pishoy]

steps : 1 - we asks 3bot guy to delete his account (ThreeFoldFarmer.3bot) and we creates a new 3bot account again with the same name as we have not the phrase words

2 - @zaibon reset and fix public key of new user ThreeFoldFarmer.3bot https://explorer.grid.tf/explorer/users/94 https://login.threefold.me/api/users/ThreeFoldFarmer.3bot

3 - when try to install jsx we got error while installing

4 - try to reconfigure account again j.me.configure()

• sdk version 3sdk_v10.6rc1_windows.exe

[grimpy]

@zaibon I remember in the past we made all usernames in the explorer lowercase, seems we forgot todo this for mainnet?

[Pishoy]

@grimpy fixed public key of the new user of lowercase https://explorer.grid.tf/explorer/users/180 but we still stuck as we got an error while user trying to update his farm as below

we are waiting for @zaibon on that

[zaibon]

@grimpy what exactly what the problem ? Cause the public key were correct so why did the installation complained and refuse to let it continue ? I don't see how a the case of the username would impact that ?

Regarding the signature verification error. There is nothing more I can do either. The signature sent to the server is wrong. So it means the code that does this request is not using the right key pair to sign the request.

[grimpy]

@zaibon the pubkey in explorer was not the same as in the threefold 3bot app. For this signature verfication I assume it checks the pubkey of the threebot_user of the farm? https://explorer.grid.tf/explorer/farms/161434

so in this case it should be using user 180 it's key to verify the signature?

[zaibon]

@zaibon the pubkey in explorer was not the same as in the threefold 3bot app.

This is impossible the public key in 3bot connect was fzxkDZhRUwqonZD2U5NvCAHVDnkv/pPpaJDeVpYhe7I= and I set it to 7f3c640d9851530aa89d90f653936f0801d50e792ffe93e96890de5696217bb2 on the explorer.

In [4]: b = b64decode('fzxkDZhRUwqonZD2U5NvCAHVDnkv/pPpaJDeVpYhe7I=')                               

In [5]: binascii.hexlify(b)                                                                         
Out[5]: b'7f3c640d9851530aa89d90f653936f0801d50e792ffe93e96890de5696217bb2'

So this means the account on 3bot connect was reset another time after I set this up.

so in this case it should be using user 180 it's key to verify the signature?

from what I can tell yes.

[Pishoy]

adding wallet to farm fixed but we still getting error of authorized when login to SDK and try to change in farm settings

As per @zaibon

that means the wrong identity is used by the farm mangement actors I guess..

[Pishoy]

closing as it wass solved