[NUT] NutCoin - The Anti Scarcity Stabilized Currency

[Snard]

Here's my address:

NMYHksBXUhhj3VPFWFg7kbyny45jVDDZcq



Still getting a bunch of orphans with the old version

Sent ya some, but still showing as unconfirmed.

[y3804]

Here's my address:

NMYHksBXUhhj3VPFWFg7kbyny45jVDDZcq



Still getting a bunch of orphans with the old version

Sent ya some, but still showing as unconfirmed.

Thanks a bunch!! really appreciated!

[Snard]

Thanks a bunch!! really appreciated!

Let me know if you receive it.

[y3804]

Thanks a bunch!! really appreciated!

Let me know if you receive it.

I did. I now have 200k

Can confirm the old version is working even on 100kh/s.. I see immature blocks in listtransactions

[jrslyrics]

So here's something weird.  once I got down to about 6 hours...it now went up to 7 hours and the blocks changed from 50~ to 37~. Weird. Nutcoin is cracked, lol.

[jrslyrics]

@Snard  / @y3808 ,

What addnode=XXXX are you using in your config?

[OrkneyCoiner]

This sucks, lol

i can't believe i missed out on this waiting on this damn blockchain to download.

Somebody...throw me a bone: NSZibgq7noaZo9oLgnxpL67igGeKFovArj

once i get sync'd i'll return the favor.

sent 100k

[r47351]

I see current block 48840

It's definitely forked then.

Restarted with the new version, clean wallet, only the two confirmed nodes from the dev and it's still synced at 24k:


21:47:36

{
"blocks" : 24837,
"currentblocksize" : 0,
"currentblocktx" : 0,
"difficulty" : 0.00024414,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 228783,
"pooledtx" : 0,
"testnet" : false
}

[JjCcc]

Will the diff ever change on this nut?......stales, rejects and orphans

NWkVoFvZ7k4dLHkmaXdopSPkpxkuuveSe9

[Snard]

So here's something weird.  once I got down to about 6 hours...it now went up to 7 hours and the blocks changed from 50~ to 37~. Weird. Nutcoin is cracked, lol.

I suggest you delete your blockchain rebuild it. See if that helps.

[y3804]

@Snard  / @y3808 ,

What addnode=XXXX are you using in your config?

This should definitely get you to 51k. Everyone use this conf!

listen=1
daemon=1
server=1
rpcuser=user
rpcpassword=pass
rpcallowip=192.168.*.*
rpcport=9385
rpcconnect=127.0.0.1
addnode=192.99.4.55
addnode=91.121.5.68
addnode=74.139.169.180
addnode=89.177.238.175
addnode=78.228.73.146
addnode=208.43.73.214
addnode=86.141.187.202
addnode=192.99.4.55:9508
addnode=91.121.5.68:9508
addnode=81.249.156.20:57552
addnode=86.2.91.151:45239
addnode=82.239.79.88:45224
addnode=192.99.4.55:9508
addnode=31.162.152.46:50398
addnode=86.26.190.235:52181
addnode=82.217.14.235:49772
addnode=91.121.5.68:9508
addnode=79.168.130.113:9508
addnode=71.94.45.245:55850
addnode=190.57.140.8:41924
addnode=84.242.79.141:55030
addnode=84.242.79.141:51874
addnode=84.242.79.141:65386
addnode=84.242.79.141:54930
addnode=62.216.7.157:55062
addnode=217.149.245.226:49671
addnode=216.165.126.117:6435
addnode=108.235.129.12:60738
addnode=50.17.222.86:60162
addnode=72.49.113.69:60506
addnode=209.112.170.107:2742
addnode=216.165.126.117:27400
addnode=61.130.147.14:43568
addnode=78.86.58.235:56933
addnode=216.165.126.117:53837
addnode=65.78.78.187:64951
addnode=61.130.147.15:50214
addnode=50.116.58.239:9508
addnode=31.31.51.7:33351
addnode=188.78.167.113:51916
addnode=103.4.18.152:33152
addnode=188.194.13.44:52784
addnode=174.19.241.199:9508
addnode=83.243.230.152:44166
addnode=67.161.154.151:56314

[OrkneyCoiner]

I see current block 48840

It's definitely forked then.

Restarted with the new version, clean wallet, only the two confirmed nodes from the dev and it's still synced at 24k:


21:47:36

{
"blocks" : 24837,
"currentblocksize" : 0,
"currentblocktx" : 0,
"difficulty" : 0.00024414,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 228783,
"pooledtx" : 0,
"testnet" : false
}

did the same.

50k blocks.

[DJTrey]

Was mining using the Mac client, but somehow it stopped working. Anybody still mining on Mac OSX client?

[dmx374]

I think the best is to rebuild the entire network from scratch. I see no other way to get it fixed if pools or some guys are mining with an old version.

1) Shutdown the whole nutcoin network (everyone removes its nutcoin folder which contains wallet.dat, nutcoin.conf and peers.dat)
2) reset the difficulty to very low, so everyone can recover the lost coins quickly (within 1 or 2 days)
3) upgrade the min version to connect to, so it will break all the connected peers (forcing them to download the new version)

[bitwho]

send some coins my way guis.

Nbhe2J34h9QPdBdvt4kskP1js54fMX6k2U


been getting orphans all day long

[jrslyrics]

I think the best is to rebuild the entire network from scratch. I see no other way to get it fixed if pools or some guys are mining with an old version.

1) Shutdown the whole nutcoin network (everyone removes its nutcoin folder which contains wallet.dat, nutcoin.conf and peers.dat)
2) reset the difficulty to very low, so everyone can recover the lost coins quickly (within 1 or 2 days)
3) upgrade the min version to connect to, so it will break all the connected peers (forcing them to download the new version)

Probably a good idea. Coordinate with guys here that are helping with the compiling and give them a bounty to collaborate and push a quality wallet. Put the dang source in a private repo until your ready to go with a clean chain, and a Windows client that works. This makes me want to launch my own damn coin, lol

[OrkneyCoiner]

I think the best is to rebuild the entire network from scratch. I see no other way to get it fixed if pools or some guys are mining with an old version.

1) Shutdown the whole nutcoin network (everyone removes its nutcoin folder which contains wallet.dat, nutcoin.conf and peers.dat)
2) reset the difficulty to very low, so everyone can recover the lost coins quickly (within 1 or 2 days)
3) upgrade the min version to connect to, so it will break all the connected peers (forcing them to download the new version)

what prevents you of mining with the (slightly) old version?

btw: the mining is hard here, I'm against reload. Having spent almost all the night with this.

[Snard]

Personally I would prefer not to do a reload, but I honestly am not sure how you can do it if everyone doesnt choose to. I will go with the majority though.

[OrkneyCoiner]

Personally I would prefer not to do a reload, but I honestly am not sure how you can do it if everyone doesnt choose to. I will go with the majority though.

we had identical starting conditions.

[jrslyrics]

Dont get me wrong, im good with either. Eventually the blockchain sorts itself out. I got those trancactions too that you and Snard sent btw.