Enable statusd to be run as community control node

[osmaczko]

Problem

There is a need to run the control node in a headless configuration on a server. In such cases, all manual community management tasks would be handled by token-masters and admins.

I have identified two potential approaches:

Option A: Simple

statusd --data-dir="/helium/status/data" --pasword="xyz"

1. Manually set up the control node.
2. Export the data dir to the server.
3. Execute statusd using the specified data dir.

Option B: Convenient (but more complex and error-prone)

statusd -controlNode --seed-phrase="test test test ... test test"

1. Execute statusd using the owner's seed phrase.

NOTE: Both options expose owner's master private key. To mitigate that, one can create an ad-hoc chat account and specify it as signer in owner token contract.

Implementation

Option A

• Enhance statusd to accept a --data-dir flag.

Option B

• Enhance statusd to accept a --controlNode flag.
• First Run:
  • Restore the account and log in.
  • Ensure the specified community is fetched from the backup (this will require an additional --community-id command line option).
  • Promote the statusd owner's instance to a control node.
• Subsequent Runs:
  • If the controlNode data directory for the given seed phrase already exists, use it instead of restoring the account.