Hello. Am I right that mytonctrl is using locally stored private key to send stakes? It means that it acts as a hot wallet. IMHO, it is a high risk to store so much coins in a hot wallet. Is there any way to use a contract to hold all the money and use mytonctrl to send messages to that contract and the contract will send stakes to the elector?

The wallet IS a contract :)

Yes, but you can move all money from it using a move coins command. And it can be done by using local pk. I don't want that that.

I would like to be able to move coins using some secure wallet.

Which is not controlled by mytonctrl.

In short, I would like to use custom contract in mytonctrl instead of the wallet generated by default.

I guess you will need to write a very specific custom contract if you would like to have various access levels and multiple keys.

I understand that. Currently I'm worried that mytonctrl stores private key locally which can be used to withdraw all the money. If a server gets compromised and private key is stolen, you will lose all the money. Am I right?

I'm afraid I will need to leave this question to a people well versed in validators. I don't want to speculate.

But your assumption sounds reasonable.

Okay, thank you for your efforts

You could also look into the nominators implementation. There should be some security measures, like funds delegation. This could set you on the right track.

I examined their contract. They use controller contract (which is not published) to perform all stake operations, and only owner (not published) contract can perform critical operations. But I do not know if they are using mytonctrl to run the actual node or just a regular full node, which should act as a validator if it finds its public key in the elector lists.

If there is someone from whales corp. Maybe, he could give an explanation.

In my opinion those contracts should be publicly available, but for some reason they are not.

I was under the impression that their solution was open sourced. Well, too bad.

It is, partly.

Only the pool and proxy contracts are published. Maybe controller and owner are just a regular wallets (too me it seems quite true) that's why they were not published.

In any case I would appreciate it if you would share your findings in the future. That is a good question.

Okay, no problem

@slavafomin is it possible to pin this message and next 2 after it?