Split mycelium binary into public network and private network
LeeSmet opened this issue · 3 comments
Currently the mycelium binary can be used to connect both to public and to private networks. This means also that the binary to contains the additional code (mostly openssl currently) needed for private networks. While the flexibility to connect to both types of networks with a single binary could be useful, in practice users have a specific use case. As such, it is better to split this into 2 binaries. This also makes it easier to add private network related code later (such as private networks based on certificate authority).
Binaries are now split, however because of the way cargo works and the fact that this is a workspace, a build on the workspace will also include private network code in the non private network build (since they share a single build of the library which unifies required features). The way forward might be to remove (one of) the binaries from the workspace.
Binaries removed from workspace, now need to extract the common code as much as possible.
Remainder to be done in follow up issue