You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current architecture within Elixium is fine for the short term but it will eventually become unscalable (on the development side). We should restructure the project to have a single daemon which our clients can use. We currently have a problem where a user can't run both the wallet and the miner on the same machine (and if they do, they're on different ports and unnecessary work is performed by the machine, and the two processes can interfere with each other). If we have a daemon, we can have that connect to the network and do work, and the miner and wallet will be light and just have to communicate with the daemon.
We'll need to check if a daemon is running and start it if it isn't on boot.
We'll also need to conditionally download the daemon if one isn't already installed on the user's machine when they download one of our clients (miner, node, wallet, etc)
The text was updated successfully, but these errors were encountered:
The current architecture within Elixium is fine for the short term but it will eventually become unscalable (on the development side). We should restructure the project to have a single daemon which our clients can use. We currently have a problem where a user can't run both the wallet and the miner on the same machine (and if they do, they're on different ports and unnecessary work is performed by the machine, and the two processes can interfere with each other). If we have a daemon, we can have that connect to the network and do work, and the miner and wallet will be light and just have to communicate with the daemon.
We'll need to check if a daemon is running and start it if it isn't on boot.
We'll also need to conditionally download the daemon if one isn't already installed on the user's machine when they download one of our clients (miner, node, wallet, etc)
The text was updated successfully, but these errors were encountered: