Title: Full Node Acting Very Strange (Please Help!) Post by: TigerStripeRIT on July 23, 2019, 09:22:53 PM Hello everyone. So over the last week, I've created my own altcoin using the Litecoin v0.8 source code for a university side project. Currently, the coin is fully functional, with a working wallet, send/receive, mining rewards, and even auto-connection to a DNS seed leading to a VPS (my full node hosted on DigitalOcean). Everything seems to be working great, except some really strange behavior from the full node (which also acts as the default DNS seed). When I run my node with either
Code: ./tigerstriped -server -printtoconsole Code: ./tigerstriped -server -listen=1 -printtoconsole Code: ./tigerstriped setgenerate false Code: ./tigerstriped stop I've attatched a few pastebins for hopefully more clarity. Please let me know if there is any debug.log or file or console you need me to share in order to help out. Full Node VPS Console (Startup message): https://pastebin.com/LuTFi09L Full Node VPS Console (Processing blocks automatically): https://pastebin.com/JFfDga2m ^^^ These same messages show up in the debug.log in all of my valid wallets! What??? I have absolutely no idea where to turn. Any idea on where to look, what to change, or which pastebins to make for further clarity would be greatly appreciated. Title: Re: Full Node Acting Very Strange (Please Help!) Post by: 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? Title: Re: Full Node Acting Very Strange (Please Help!) Post by: TigerStripeRIT on July 23, 2019, 10:09:46 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. Title: Re: Full Node Acting Very Strange (Please Help!) Post by: achow101 on July 23, 2019, 11:18:24 PM From the log snippets you have posted, it is clear that your node is not mining. There would be different messages if your node were mining. Rather, you see messages like:
Code: received block 7a78eb489bc70e40d39700e2c3a54b1ea688cf0df0e5b9195a6715695b7e8640 It is highly likely that someone has found your code on GitHub and is running their own node on your network. It is common for people with ASICs to jump onto new altcoin networks and just mine tons of blocks at insane rates using their ASICs. Typically they then leave once they bring the difficulty up very high such that once they leave, no one else using that coin will be able to mine on it, effectively killing it. |