[ ] Future of NodeConfig.
It made sense before, when status-go was a StatusNode. And we were starting StatusNode by calling startNodeWithConfig(nodeConfig).
But now it seems redundant and too heavy. I believe that we should split it into configs for particular modules.
Also, the way we load/store the NodeConfig now is very complicated. Some of the fields are stored in both node_config , settings and other tables.
Also, some fields are stored in DB, some defaults are hardcoded and some values are overridden by client.
Context: https://github.com/status-im/status-go/issues/6260, basically I need to override the whole ClusterConfig from client.
Own thought: follow the path done for Networks? 🤔
[ ]