Quote from: achow101 on July 23, 2019, 10:01:47 PM

-printtoconsole doesn't make it magically start mining. It's literally just an option that causes the debug messages that normally go into the debug.log to also be printed to stdout. It's the same as doing tail -f debug.log while your node is running.

Your node, or some other node in your network, is continuously mining and -printtoconsole has nothing to do with it except that now you are seeing the debug messages.

Are you sure that you are the only node on your network?

What block time did you choose?

Yes I am aware that -printtoconsole is simply just an extension asking to print to console. I'm actually wondering if there is a different flag to DISABLE whatever mining this node is doing. Currently I have one node hosted on digital ocean and two wallets on virtual ubuntu desktops. I have not released any code or wallet software to allow for others to join. This is further proven by the wallet displaying "1 active connection to TigerStripe network" (which in this case is my full node). My block time is targeted at around 5 minutes. The mining itself works great on any wallet, taking 5-10 minutes, but this node seems to just process a block out of thin air every thirty seconds.

I did, after rechecking the full node console, notice a strange IP that seemed to trace back to Russia? Would any mining that IP is doing show up on the full node's console? I guess my main confusion is whether the full node on digitalOcean is mining or if some wallet out there compiled using my source code from the public Github is doing it. Then again, I don't know why anybody would go through the trouble of cloning, compiling, and mining my coin which is basically worth nothing.