YEY! just found 2 block! ![](https://ip.bitcointalk.org/?u=http%3A%2F%2Fpuu.sh%2FnA23Z%2Fb36d93bfc2.png&t=663&c=RZ7pOG3sBlGrMg)
|
|
|
[wallet Np3AVm]: show_hr Unknown command: show_hr
dev why help thanks
write that to the neptunium daemon ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) which is neptiniumd.exe
|
|
|
we need a pool
Yeah, we do. I'll try to get in contact with as many as I can. Keep in mind many regular pools don't support Cryptonight, so we'll need to look for those that support the algorithm. I did pm you ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) Thanks btw
|
|
|
Everything is running smooth. For those that get crashes, rename any old neptunium folders you might have in your roaming folder and run the daemon again. I would say this was a smooth launch. Thanks dev for all the hard work in getting things going. ![Wink](https://bitcointalk.org/Smileys/default/wink.gif) I'm happy to see everything working well! Not sure why some people were scared off the difficulty so quickly, Neptunium's block reward time is 93 seconds and a block is being found every 93 seconds. I'm not sure what's causing the connection error messages, but they're not from the seed node's IP so it shouldn't have any real effect. The "WRONG NETWORK AGENT" messages are caused by people who are still running the daemon on the testnet. They will eventually disappear, and the future testnet will have different ports to prevent this. Because i dont think many people feel like they have any chance against the big people mining, like i have 53 hashrate only, i dont see it anywhere near getting a block Many other coins take hours to find a block, but are still viable for solo mining. Even if you had 10 hashrate, at the current difficulty, you'd probably find a few blocks leaving it on for a day. The probability for finding a block approaches viable values for every hash rate after a certain amount of time. 50 hashrate may be lower than the average, but you're still perfectly capable of finding blocks. Yeah, i will leave it running for a day, i would have Digital ocean credit, but i cannot get the wallet working, im kind of noob with unix systems still and i keep getting "./neptuniumd: error while loading shared libraries: libboost_system.so.1.55.0: cannot open shared object file: No such file or directory" when trying to run
|
|
|
Everything is running smooth. For those that get crashes, rename any old neptunium folders you might have in your roaming folder and run the daemon again. I would say this was a smooth launch. Thanks dev for all the hard work in getting things going. ![Wink](https://bitcointalk.org/Smileys/default/wink.gif) I'm happy to see everything working well! Not sure why some people were scared off the difficulty so quickly, Neptunium's block reward time is 93 seconds and a block is being found every 93 seconds. I'm not sure what's causing the connection error messages, but they're not from the seed node's IP so it shouldn't have any real effect. The "WRONG NETWORK AGENT" messages are caused by people who are still running the daemon on the testnet. They will eventually disappear, and the future testnet will have different ports to prevent this. Because i dont think many people feel like they have any chance against the big people mining, like i have 53 hashrate only, i dont see it anywhere near getting a block
|
|
|
current difficulty: 35749 ![Huh](https://bitcointalk.org/Smileys/default/huh.gif) Wait wut, where did you see that? :O Daemon. Testnet was good. Mined some blocks. Now I can't mine any and daemon stucks. 72k difficulty, yeah im out too
|
|
|
Mining is not working. Going to sleep.
client keeps crashing ![Sad](https://bitcointalk.org/Smileys/default/sad.gif) launch is not so smooth Not for me, my clients are working just fine, only problem i have that is im not finding any blocks
|
|
|
current difficulty: 35749 ![Huh](https://bitcointalk.org/Smileys/default/huh.gif) Wait wut, where did you see that? :O
|
|
|
I just did start mining.
This is weird tho "2016-Mar-09 05:04:52.551868 WARNING [node_server] [80.2.75.167:4460 OUT] Exception in connectionHandler: TcpConnection::read, WSAGetOverlappedResult failed, result=10054, An existing connection was forcibly closed by the remote host."
|
|
|
Im ready for the launch ![Tongue](https://bitcointalk.org/Smileys/default/tongue.gif)
|
|
|
Alright its now working for me, i did wake up 4am my time just to be ready for the launch haha
|
|
|
2016-Mar-08 22:24:32.860020 ERROR [node_server] Failed to connect to any of seed peers, continuing without seeds 2016-Mar-08 22:24:49.131951 INFO [node_server] 2016-Mar-08 22:24:49.131951 INFO [node_server] Peerlist white: 2016-Mar-08 22:24:49.131951 INFO [node_server] 2016-Mar-08 22:24:49.131951 INFO [node_server] Peerlist gray: 2016-Mar-08 22:24:49.131951 INFO [node_server] d8a73faabc79d6b6 52.0.30.115:4460 last_seen: d1.h0.m36.s34 147f6113aa5da98f 95.24.226.209:4460 last_seen: d1.h3.m14.s32 70daa9796001c3f5 67.225.110.88:4460 last_seen: d1.h13.m58.s42 d0ed0e0fbdffef19 70.31.161.113:4460 last_seen: d1.h19.m14.s39 86b2de1093ae6baf 80.2.75.167:4460 last_seen: d1.h20.m46.s13
Too bad :/
Are you running neptuniumtestnetd.exe? There's only one seed node up for the Testnet because I was having some problems with one of my VPS. I'll be hosting on a new VPS before release. Yeah that log is from neptuniumtestnetd.log. And the funny thing is that the failed release before testnet worked just fine for me
|
|
|
2016-Mar-08 22:24:32.860020 ERROR [node_server] Failed to connect to any of seed peers, continuing without seeds 2016-Mar-08 22:24:49.131951 INFO [node_server] 2016-Mar-08 22:24:49.131951 INFO [node_server] Peerlist white: 2016-Mar-08 22:24:49.131951 INFO [node_server] 2016-Mar-08 22:24:49.131951 INFO [node_server] Peerlist gray: 2016-Mar-08 22:24:49.131951 INFO [node_server] d8a73faabc79d6b6 52.0.30.115:4460 last_seen: d1.h0.m36.s34 147f6113aa5da98f 95.24.226.209:4460 last_seen: d1.h3.m14.s32 70daa9796001c3f5 67.225.110.88:4460 last_seen: d1.h13.m58.s42 d0ed0e0fbdffef19 70.31.161.113:4460 last_seen: d1.h19.m14.s39 86b2de1093ae6baf 80.2.75.167:4460 last_seen: d1.h20.m46.s13
Too bad :/
|
|
|
for some weird reason this testnet wallet is not syncing for me but the earlier launch wallet did, hmm weird.
Log:
2016-Mar-07 11:35:23.799016 INFO [daemon] NeptuniumTESTNET v1.1.1.1(0.1-g8edd998) 2016-Mar-07 11:35:23.803017 INFO [daemon] Module folder: C:\Users\User\Desktop\keke\NeptuniumTESTNETd.exe 2016-Mar-07 11:35:23.807017 INFO [daemon] Initializing p2p server... 2016-Mar-07 11:35:23.808017 INFO [node_server] Binding on 0.0.0.0:4460 2016-Mar-07 11:35:23.810017 INFO [node_server] Net service binded on 0.0.0.0:4460 2016-Mar-07 11:35:23.812017 INFO [node_server] Attempting to add IGD port mapping. 2016-Mar-07 11:35:27.815246 INFO [node_server] No IGD was found. 2016-Mar-07 11:35:27.823247 INFO [daemon] P2p server initialized OK 2016-Mar-07 11:35:27.830247 INFO [daemon] Initializing core... 2016-Mar-07 11:35:27.838247 INFO [Blockchain] Loading blockchain... 2016-Mar-07 11:35:27.844248 INFO [BlockCacheSerializer] - loading block index... 2016-Mar-07 11:35:27.851248 INFO [BlockCacheSerializer] - loading transaction map... 2016-Mar-07 11:35:27.857248 INFO [BlockCacheSerializer] - loading spent keys... 2016-Mar-07 11:35:27.861249 INFO [BlockCacheSerializer] - loading outputs... 2016-Mar-07 11:35:27.865249 INFO [BlockCacheSerializer] - loading multi-signature outputs... 2016-Mar-07 11:35:27.870249 INFO [BlockCacheSerializer] Serialization time: 26ms 2016-Mar-07 11:35:27.874249 INFO [Blockchain] Loading blockchain indices for BlockchainExplorer... 2016-Mar-07 11:35:27.881250 INFO [BlockchainIndicesSerializer] - loading paymentID index... 2016-Mar-07 11:35:27.885250 INFO [BlockchainIndicesSerializer] - loading timestamp index... 2016-Mar-07 11:35:27.888250 INFO [BlockchainIndicesSerializer] - loading generated transactions index... 2016-Mar-07 11:35:27.891250 INFO [Blockchain] Blockchain initialized. last block: 0, d1342.h4.m35.s27 time ago, current difficulty: 1 2016-Mar-07 11:35:27.897251 INFO [daemon] Core initialized OK 2016-Mar-07 11:35:27.900251 INFO [daemon] Starting core rpc server on address 127.0.0.1:4540 2016-Mar-07 11:35:27.904251 INFO [daemon] Core rpc server started ok 2016-Mar-07 11:35:27.907251 INFO [daemon] Starting p2p net loop... 2016-Mar-07 11:35:27.910251 INFO [node_server] Starting node_server 2016-Mar-07 11:35:48.256415 INFO [core] 2016-Mar-07 11:35:48.256415 INFO [core] ********************************************************************** 2016-Mar-07 11:35:48.256415 INFO [core] The daemon will start synchronizing with the network. It may take up to several hours. 2016-Mar-07 11:35:48.256415 INFO [core] 2016-Mar-07 11:35:48.256415 INFO [core] You can set the level of process detailization* through "set_log <level>" command*, where <level> is between 0 (no details) and 4 (very verbose). 2016-Mar-07 11:35:48.256415 INFO [core] 2016-Mar-07 11:35:48.256415 INFO [core] Use "help" command to see the list of available commands. 2016-Mar-07 11:35:48.256415 INFO [core] 2016-Mar-07 11:35:48.256415 INFO [core] Note: in case you need to interrupt the process, use "exit" command. Otherwise, the current progress won't be saved. 2016-Mar-07 11:35:48.256415 INFO [core] ********************************************************************** 2016-Mar-07 11:37:01.757619 INFO [node_server] Peerlist white: 2016-Mar-07 11:37:01.757619 INFO [node_server] 2016-Mar-07 11:37:01.757619 INFO [node_server] Peerlist gray: 2016-Mar-07 11:37:01.757619 INFO [node_server] d8a73faabc79d6b6 52.0.30.115:4460 last_seen: d0.h2.m40.s6 70daa9796001c3f5 67.225.110.88:4460 last_seen: d0.h3.m10.s55 d0ed0e0fbdffef19 70.31.161.113:4460 last_seen: d0.h8.m26.s52 86b2de1093ae6baf 80.2.75.167:4460 last_seen: d0.h9.m58.s26
Any help?
One of my nodes has been receiving disconnect errors. I'll try to launch the 3rd node today and we'll see if the problem still persists. Yep it does still exist, now it shows that the one node has seen recently: 2016-Mar-07 21:20:38.759477 INFO [node_server] Peerlist white: 2016-Mar-07 21:20:38.759477 INFO [node_server] 2016-Mar-07 21:20:38.759477 INFO [node_server] Peerlist gray: 2016-Mar-07 21:20:38.759477 INFO [node_server] d8a73faabc79d6b6 52.0.30.115:4460 last_seen: d0.h0.m0.s23 147f6113aa5da98f 95.24.226.209:4460 last_seen: d0.h2.m10.s21 70daa9796001c3f5 67.225.110.88:4460 last_seen: d0.h12.m54.s31 d0ed0e0fbdffef19 70.31.161.113:4460 last_seen: d0.h18.m10.s28 86b2de1093ae6baf 80.2.75.167:4460 last_seen: d0.h19.m42.s2
|
|
|
for some weird reason this testnet wallet is not syncing for me but the earlier launch wallet did, hmm weird.
Log:
2016-Mar-07 11:35:23.799016 INFO [daemon] NeptuniumTESTNET v1.1.1.1(0.1-g8edd998) 2016-Mar-07 11:35:23.803017 INFO [daemon] Module folder: C:\Users\User\Desktop\keke\NeptuniumTESTNETd.exe 2016-Mar-07 11:35:23.807017 INFO [daemon] Initializing p2p server... 2016-Mar-07 11:35:23.808017 INFO [node_server] Binding on 0.0.0.0:4460 2016-Mar-07 11:35:23.810017 INFO [node_server] Net service binded on 0.0.0.0:4460 2016-Mar-07 11:35:23.812017 INFO [node_server] Attempting to add IGD port mapping. 2016-Mar-07 11:35:27.815246 INFO [node_server] No IGD was found. 2016-Mar-07 11:35:27.823247 INFO [daemon] P2p server initialized OK 2016-Mar-07 11:35:27.830247 INFO [daemon] Initializing core... 2016-Mar-07 11:35:27.838247 INFO [Blockchain] Loading blockchain... 2016-Mar-07 11:35:27.844248 INFO [BlockCacheSerializer] - loading block index... 2016-Mar-07 11:35:27.851248 INFO [BlockCacheSerializer] - loading transaction map... 2016-Mar-07 11:35:27.857248 INFO [BlockCacheSerializer] - loading spent keys... 2016-Mar-07 11:35:27.861249 INFO [BlockCacheSerializer] - loading outputs... 2016-Mar-07 11:35:27.865249 INFO [BlockCacheSerializer] - loading multi-signature outputs... 2016-Mar-07 11:35:27.870249 INFO [BlockCacheSerializer] Serialization time: 26ms 2016-Mar-07 11:35:27.874249 INFO [Blockchain] Loading blockchain indices for BlockchainExplorer... 2016-Mar-07 11:35:27.881250 INFO [BlockchainIndicesSerializer] - loading paymentID index... 2016-Mar-07 11:35:27.885250 INFO [BlockchainIndicesSerializer] - loading timestamp index... 2016-Mar-07 11:35:27.888250 INFO [BlockchainIndicesSerializer] - loading generated transactions index... 2016-Mar-07 11:35:27.891250 INFO [Blockchain] Blockchain initialized. last block: 0, d1342.h4.m35.s27 time ago, current difficulty: 1 2016-Mar-07 11:35:27.897251 INFO [daemon] Core initialized OK 2016-Mar-07 11:35:27.900251 INFO [daemon] Starting core rpc server on address 127.0.0.1:4540 2016-Mar-07 11:35:27.904251 INFO [daemon] Core rpc server started ok 2016-Mar-07 11:35:27.907251 INFO [daemon] Starting p2p net loop... 2016-Mar-07 11:35:27.910251 INFO [node_server] Starting node_server 2016-Mar-07 11:35:48.256415 INFO [core] 2016-Mar-07 11:35:48.256415 INFO [core] ********************************************************************** 2016-Mar-07 11:35:48.256415 INFO [core] The daemon will start synchronizing with the network. It may take up to several hours. 2016-Mar-07 11:35:48.256415 INFO [core] 2016-Mar-07 11:35:48.256415 INFO [core] You can set the level of process detailization* through "set_log <level>" command*, where <level> is between 0 (no details) and 4 (very verbose). 2016-Mar-07 11:35:48.256415 INFO [core] 2016-Mar-07 11:35:48.256415 INFO [core] Use "help" command to see the list of available commands. 2016-Mar-07 11:35:48.256415 INFO [core] 2016-Mar-07 11:35:48.256415 INFO [core] Note: in case you need to interrupt the process, use "exit" command. Otherwise, the current progress won't be saved. 2016-Mar-07 11:35:48.256415 INFO [core] ********************************************************************** 2016-Mar-07 11:37:01.757619 INFO [node_server] Peerlist white: 2016-Mar-07 11:37:01.757619 INFO [node_server] 2016-Mar-07 11:37:01.757619 INFO [node_server] Peerlist gray: 2016-Mar-07 11:37:01.757619 INFO [node_server] d8a73faabc79d6b6 52.0.30.115:4460 last_seen: d0.h2.m40.s6 70daa9796001c3f5 67.225.110.88:4460 last_seen: d0.h3.m10.s55 d0ed0e0fbdffef19 70.31.161.113:4460 last_seen: d0.h8.m26.s52 86b2de1093ae6baf 80.2.75.167:4460 last_seen: d0.h9.m58.s26
Any help?
you have no whitelisted peers thats why but i dont know how to fix Yeah, i guess i need to wait for the dev to answer :/ i cant find any config file either with the nodes
|
|
|
for some weird reason this testnet wallet is not syncing for me but the earlier launch wallet did, hmm weird.
Log:
2016-Mar-07 11:35:23.799016 INFO [daemon] NeptuniumTESTNET v1.1.1.1(0.1-g8edd998) 2016-Mar-07 11:35:23.803017 INFO [daemon] Module folder: C:\Users\User\Desktop\keke\NeptuniumTESTNETd.exe 2016-Mar-07 11:35:23.807017 INFO [daemon] Initializing p2p server... 2016-Mar-07 11:35:23.808017 INFO [node_server] Binding on 0.0.0.0:4460 2016-Mar-07 11:35:23.810017 INFO [node_server] Net service binded on 0.0.0.0:4460 2016-Mar-07 11:35:23.812017 INFO [node_server] Attempting to add IGD port mapping. 2016-Mar-07 11:35:27.815246 INFO [node_server] No IGD was found. 2016-Mar-07 11:35:27.823247 INFO [daemon] P2p server initialized OK 2016-Mar-07 11:35:27.830247 INFO [daemon] Initializing core... 2016-Mar-07 11:35:27.838247 INFO [Blockchain] Loading blockchain... 2016-Mar-07 11:35:27.844248 INFO [BlockCacheSerializer] - loading block index... 2016-Mar-07 11:35:27.851248 INFO [BlockCacheSerializer] - loading transaction map... 2016-Mar-07 11:35:27.857248 INFO [BlockCacheSerializer] - loading spent keys... 2016-Mar-07 11:35:27.861249 INFO [BlockCacheSerializer] - loading outputs... 2016-Mar-07 11:35:27.865249 INFO [BlockCacheSerializer] - loading multi-signature outputs... 2016-Mar-07 11:35:27.870249 INFO [BlockCacheSerializer] Serialization time: 26ms 2016-Mar-07 11:35:27.874249 INFO [Blockchain] Loading blockchain indices for BlockchainExplorer... 2016-Mar-07 11:35:27.881250 INFO [BlockchainIndicesSerializer] - loading paymentID index... 2016-Mar-07 11:35:27.885250 INFO [BlockchainIndicesSerializer] - loading timestamp index... 2016-Mar-07 11:35:27.888250 INFO [BlockchainIndicesSerializer] - loading generated transactions index... 2016-Mar-07 11:35:27.891250 INFO [Blockchain] Blockchain initialized. last block: 0, d1342.h4.m35.s27 time ago, current difficulty: 1 2016-Mar-07 11:35:27.897251 INFO [daemon] Core initialized OK 2016-Mar-07 11:35:27.900251 INFO [daemon] Starting core rpc server on address 127.0.0.1:4540 2016-Mar-07 11:35:27.904251 INFO [daemon] Core rpc server started ok 2016-Mar-07 11:35:27.907251 INFO [daemon] Starting p2p net loop... 2016-Mar-07 11:35:27.910251 INFO [node_server] Starting node_server 2016-Mar-07 11:35:48.256415 INFO [core] 2016-Mar-07 11:35:48.256415 INFO [core] ********************************************************************** 2016-Mar-07 11:35:48.256415 INFO [core] The daemon will start synchronizing with the network. It may take up to several hours. 2016-Mar-07 11:35:48.256415 INFO [core] 2016-Mar-07 11:35:48.256415 INFO [core] You can set the level of process detailization* through "set_log <level>" command*, where <level> is between 0 (no details) and 4 (very verbose). 2016-Mar-07 11:35:48.256415 INFO [core] 2016-Mar-07 11:35:48.256415 INFO [core] Use "help" command to see the list of available commands. 2016-Mar-07 11:35:48.256415 INFO [core] 2016-Mar-07 11:35:48.256415 INFO [core] Note: in case you need to interrupt the process, use "exit" command. Otherwise, the current progress won't be saved. 2016-Mar-07 11:35:48.256415 INFO [core] ********************************************************************** 2016-Mar-07 11:37:01.757619 INFO [node_server] Peerlist white: 2016-Mar-07 11:37:01.757619 INFO [node_server] 2016-Mar-07 11:37:01.757619 INFO [node_server] Peerlist gray: 2016-Mar-07 11:37:01.757619 INFO [node_server] d8a73faabc79d6b6 52.0.30.115:4460 last_seen: d0.h2.m40.s6 70daa9796001c3f5 67.225.110.88:4460 last_seen: d0.h3.m10.s55 d0ed0e0fbdffef19 70.31.161.113:4460 last_seen: d0.h8.m26.s52 86b2de1093ae6baf 80.2.75.167:4460 last_seen: d0.h9.m58.s26
Any help?
|
|
|
Will current miners be able to send you their wallets for a swap to the re-launched coin?
PS: And maybe make the block rewards a bit smaller as the large blocks will only benefit a few.
This would actually be nice because i already mined 3 blocks...
|
|
|
found a block with 1 neptoshi worth, better do a relaunch i gues
So it was 1 or with decimals like 0.0000001 or so?
|
|
|
I'm going to relaunch Neptunium, hopefully in a few days. Please don't mine this version of the coin unless you just want to experiment. Sorry for the failed launch and everyone's time. Going to bed, I'll keep the nodes running until around 1PM EST tommorow. I really don't have high hopes for this to fix itself, but if anybody still wants to mine for whatever reason.
Alright, i will stop mining. Mind making a channel on freenode? And good night ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
Sorry for being a bit of a noob, but how do I mine this coin? Where is the mining software, and what commands do I have to type in?
Extract the wallet, run Neptiniumd, when it says that you can open simple wallet open it, make a wallet and write start_mining numberofcorestouse here, its that easy ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) Like start_mining 3 example, depends how many cores do you have
|
|
|
|