Miner Connecting Data #51
Description
Currently, when a miner connects it sends over it's minerid, a 'random' string. This is not guaranteed to be unique. The miner should also send over a unique id being a sufficiently large number.
It should also send over metadata on authentication including:
- System hardware (CPU, arch, os, etc)
- IP (WAN and LAN?)
- Miner software agent/version
COS:
- Miner data is sent to server
- Server updates miner in miner table with it's updated information each time it connects. Miner table should use unique id to determine a unique miner