(ANN) Netcoin has gone POS! With PIR & OWI

[Trimegistus]

2.4 generated stakes are not accepted... ok, after all this is a hard fork!

But why is my 2.5 wallet still refusing to stake and crashing as soon as I unlock it?

Any ideas?

[1713894966]

1713894966

[1713894966]

1713894966

[o0o0]

2.4 generated stakes are not accepted... ok, after all this is a hard fork!

But why is my 2.5 wallet still refusing to stake and crashing as soon as I unlock it?

Any ideas?

Mine is doing the same and Arjan the coder is looking into it. I've been pm'ing him. It happens for a few people. Maybe we can gather some info.

1. What operating system are you using?
2. How many inputs in each of your addresses
3. How many coins in the largest input?

At present i am resyncing the blockchain from only 2.5 nodes and i am going to try a stake after backing it up at that point. If this fails im going to try and import the priv key. If this fails arjan is going to send me 20,000 netcoin to a new wallet.dat address to see if this works.

Its working for the majority there must be some small thing causing us issues.

[o0o0]

2.4 generated stakes are not accepted... ok, after all this is a hard fork!

But why is my 2.5 wallet still refusing to stake and crashing as soon as I unlock it?

Any ideas?

You'll get a way bigger than normal stake when its fixed. Granted we miss the compound for that time but don't fear too much. Bittrex is on v2.5 chain so i wouldn't be using v2.4 at all.

[Trimegistus]

2.4 generated stakes are not accepted... ok, after all this is a hard fork!

But why is my 2.5 wallet still refusing to stake and crashing as soon as I unlock it?

Any ideas?

Mine is doing the same and Arjan the coder is looking into it. I've been pm'ing him. It happens for a few people. Maybe we can gather some info.

1. What operating system are you using?
2. How many inputs in each of your addresses
3. How many coins in the largest input?

At present i am resyncing the blockchain from only 2.5 nodes and i am going to try a stake after backing it up at that point. If this fails im going to try and import the priv key. If this fails arjan is going to send me 20,000 netcoin to a new wallet.dat address to see if this works.

Its working for the majority there must be some small thing causing us issues.

Reading your post gave me an idea...

I sent all my coins to another address and that was enough to be able to unlock it, not only to send the coins but also to stake!

Let's see if really works and produces some valid stakes.

Fingers crossed!

[o0o0]

2.4 generated stakes are not accepted... ok, after all this is a hard fork!

But why is my 2.5 wallet still refusing to stake and crashing as soon as I unlock it?

Any ideas?

Mine is doing the same and Arjan the coder is looking into it. I've been pm'ing him. It happens for a few people. Maybe we can gather some info.

1. What operating system are you using?
2. How many inputs in each of your addresses
3. How many coins in the largest input?

At present i am resyncing the blockchain from only 2.5 nodes and i am going to try a stake after backing it up at that point. If this fails im going to try and import the priv key. If this fails arjan is going to send me 20,000 netcoin to a new wallet.dat address to see if this works.

Its working for the majority there must be some small thing causing us issues.

Reading your post gave me an idea...

I sent all my coins to another address and that was enough to be able to unlock it, not only to send the coins but also to stake!

Let's see if really works and produces some valid stakes.

Fingers crossed!

Have you actually achieved a stake doing this? Can you please tell me how many coins you had as your input as mine are really large.

Did you use a fresh wallet.dat? I did this and imported keys and got an error but that was without resyncing from only 2.5 nodes.. im 20 weeks away from full resync to test. Can you answer the above questions please it might help arjan to fix the wallet code for others... it should be a simple swap overall to not cause hardship to people less techy.

[o0o0]

guys who explerience crashes, may i guess you jumped from 2.4 to 2.5 and back
with the same wallet.dat ?
did you try to import private keys to a new .dat file and run it under v2.5 ?

network forked, dev please ask presstab to check explorer
i'd say network is still damn sick, this is what i see right now:

Code:

#2.3.1
addnode=81.89.56.170:11310
addnode=113.203.219.4:61100
addnode=184.96.200.187:49816
addnode=67.60.163.208:46767
addnode=184.21.170.128:60607
addnode=79.73.156.181:11310
addnode=178.157.251.148:6538
addnode=94.244.132.13:54771
addnode=47.197.76.73:50333
addnode=79.8.1.204:52249
addnode=173.57.104.222:11310
addnode=75.108.65.64:53066
addnode=67.1.203.237:11310
addnode=81.195.148.82:57479
addnode=92.13.133.24:60506
addnode=82.229.201.131:11310
addnode=158.69.27.82:58791
addnode=172.74.183.126:55034
addnode=172.93.110.218:24015
addnode=173.21.50.85:11310
addnode=71.9.170.207:63102
addnode=78.56.42.41:11310
addnode=84.234.52.190:42565
addnode=24.156.179.111:58155
addnode=14.201.144.59:62260
addnode=78.51.52.204:55289
addnode=72.74.138.99:56350
addnode=108.24.2.193:54643

#2.4.0
addnode=78.211.155.235:11310

#2.5.0
addnode=81.64.200.182:11310
addnode=74.118.192.18:11310
addnode=73.214.14.51:11310
addnode=84.105.200.241:56839
addnode=98.115.147.74:11310
addnode=109.153.240.250:11310
addnode=187.169.121.157:11310
addnode=162.245.17.83:59150
addnode=125.238.73.30:11310

why the hell still so many 2.3.1 out there ?

because 2.4 wasn't a mandatory update so 2.3.1 worked fine... 2.4 cleaned interface up and removed irc stuff thats it. However now since 2.5 with hard fork and bittrex runs correct chain all those 2.3 and 2.4 users are on the wrong chain and staking for nothing.

Can the new client be made to just ignore the all peers less than 2.5 the orphan warnings aren't helpful.... peer wise it would be great to just ignore those nodes.

[Lafu]

This nodes working fine v2.5

addnode=58.182.252.117
addnode=93.123.163.96
addnode=173.21.50.85
addnode=81.89.56.170
addnode=173.54.215.165
addnode=82.229.201.131
addnode=5.20.100.185
addnode=73.108.21.214
addnode=71.9.170.207
addnode=71.230.245.166
addnode=194.135.161.180
addnode=176.14.89.237
addnode=49.147.111.86
addnode=72.241.237.18
addnode=162.245.17.83
addnode=96.248.111.169
addnode=88.79.173.189
addnode=74.118.192.18
addnode=125.238.73.30
addnode=50.36.228.182
addnode=98.115.147.74
addnode=84.105.200.241
addnode=81.64.200.182
addnode=37.146.73.236
addnode=109.153.240.250
addnode=73.214.14.51
addnode=187.169.121.157

[Lafu]

This nodes working fine v2.5

getblockhash 1301108
50700911349bbae5c3995c67a14cfc232c454a71251886401e1a01e4b2c96075

yours ?

1301111

[Lafu]

This nodes working fine v2.5

getblockhash 1301108
50700911349bbae5c3995c67a14cfc232c454a71251886401e1a01e4b2c96075

yours ?

1301111

hash please

SetBestChain: new best=2ffbc35ad06cf6300a3d8ae73605ceb57a43662de928cd9de47e9d5c5f634ee2  height=1301112  trust=42899659188850436  blocktrust=1378738485  date=2016-09-18 02:35:46 UTC
ProcessBlock: ACCEPTED


1301111
130f37dc2ccf19ea556de06fc4fa538c23c9ee788b593bfd52ab76d8a2d17b3f

[Lafu]

This nodes working fine v2.5

getblockhash 1301108
50700911349bbae5c3995c67a14cfc232c454a71251886401e1a01e4b2c96075

yours ?

1301111

hash please

SetBestChain: new best=2ffbc35ad06cf6300a3d8ae73605ceb57a43662de928cd9de47e9d5c5f634ee2  height=1301112  trust=42899659188850436  blocktrust=1378738485  date=2016-09-18 02:35:46 UTC
ProcessBlock: ACCEPTED

ok, it's 1301112, at least 2 of us on the same chain

1301111
130f37dc2ccf19ea556de06fc4fa538c23c9ee788b593bfd52ab76d8a2d17b3f

[o0o0]

Can the new client be made to just ignore the all peers less than 2.5 the orphan warnings aren't helpful.... peer wise it would be great to just ignore those nodes.

in theory - yes, practically it's lotta load on the node,
of course depends on coding, but what i'v seen up to date is not very encouraging

A lot of load on the node? Ok ive done programming in the past but its all gui stuff sys admin scripting and c++ apps so im not fluent or i'll admit even moderately knowledgable on peer to peer stuff and bitcoin crypto in general with respect to source so have patience with me on this but

can't they just ignore accepting of the peer when it looks to add to its node list if its a node less than 2.5? surely at the stage where its listening it just rejects? Im not understanding on what load that would take. To me seems more load burden to reject the orphan blocks and process that stuff.


As to the code encouraging Arjan is doing a good job for where he's at. He's a great guy to chat to and while i don't know him in depth he's always been helpful. Netcoin to me has a great staking concept and im glad they reduced the third year apr amount to stop crazy inflation. Honestly Arjans doing it for fun with what free time he has and im sure we could get more expertise onboard if everyone donated a portion of their stake to a fund. I'd like to see netcoin get more adoption and be listed at poloniex. Unfortunately this sort of dev and listing won't happen unless more independant community members work with teams towards it. I think its sort of expected by everyone that when you grab some coins of any altcoin that its the teams duty to keep updating at their cost. Normally i'd agree here when there are premines and icos and all that other garbage that is manipulated now a days but netcoin didn't have an ico or premine. So basically the team use their own time and money.

Arjan in a pm to me mentioned he paid his own funds to have someone setup a dnsseeder for it.

I think if we want netcoin to continue growing we should all consider donating to an address arjan runs and uses so long as the fund use is transparent and shown. It wouldn't be much for everyone to donate 5% of each stake to this... in the long run if you donate 5% and get more than that in dev value we all benefit... thoughts?

Below are the pms i received from arjan (arjan is tepelstreeltje) with my issues. I hope he doesn't mind me sharing

Hey o0o0,

I feel awefull that i couldn't contact you any sooner for assistance but i was away from home this whole week for work and on top of that didn't had internet there so it was not a good week for me.

Anyway i apologize for the issues you encounter but it seems you are on the wrong chain and trying to stake/send on it which explains it got picked up by the old wallet so you need to redownload the chain.

As for the fork itself i couldn't tell a definitly block number on where the fork would happen because i just extended the final PoW setting so anyone mining the first PoW block or creating a accepted stake with the v2.5 wallet would be the start of the fork as that block is created with the new protocol version.

For me the wallet has run since sunday i released v2.5 as node only and when i got home today is was running and synced still so i unlocked it and it staked immediatly without issues.
At the time of writing the correct chain is on block 1298624 and the old chain is on 1296967 so it's quite a bit behind which was expected because of the PoW.

Your wallet might have failed to find some v2.5 nodes that are on the correct chain so i included some v2.5 nodes from my nodelist for addnodes you could try for redownload of the chain or you could try the bootstrap from the thread though i do not reccommend it.

If you want to verify yourself the wallet is on the right chain after redownload and you are ready to stake again you can visit https://prohashing.com/explorer/Netcoin/ as they are updated to v2.5 and are on the correct chain and compair the last block number.

I contacted presstab already and he said he updated just yesterday so he was on the old chain aswell but he is redownloading from a backup now.

For bittrex i contacted them saturday and got a reply back yesterday that they updated though i didn't had the time yet to verify it myself by sending some coins with my own wallet.
Hopefully i get to that tonight and i will let you know if i verified they are on the correct chain or not.

Best regards,
Arjan

v2.5 addnodes:
71.230.245.166
194.135.161.180
176.14.89.237
49.147.111.86
72.241.237.18
162.245.17.83
96.248.111.169
88.79.173.189
74.118.192.18
125.238.73.30
50.36.228.182

Again sorry for the inconvienience and the lack of notice of the fork but for now it's only BJ and me and i wasn't really sure i got the update finished and tested on time and i had to release before the PoW ended in the old wallet but appreciete your understanding.

It seems that some people when they are trying to sync even from scratch their wallet has a hard time finding/connecting good v2.5 nodes for some reason. Think it might have something to do with the dnsseeder i paid someone to setup

I have some recent v2.5 addnodes you can try to connect with. I saw someone put up a few nodes aswell but some change overtime so they might have too.

Also i put up a copy of the correct blockchain online so you can use that if you want to speed things up though i normally don't reccommend it ( can result in a corrupted wallet.dat) and ofcourse you can try with a clean wallet.dat and i will send you some coins to test it out if you are on the right chain before you copy/import your main wallet.dat.

Main thing you need to look out for when you are synced is the blockheight. Correct chain is on block 1299517 while the old one is on 1297157 at the time of writing so the old one is quite a bit behind. If you want to check out the latest blockheight yourself you can visit https://prohashing.com/explorer/Netcoin/ as they are updated and on the correct chain.

So i suggest you try to clean the datafolder again. Add the nodes in the conf file (do connect="ip" first and if you synced up and are good change it to addnode="ip") and if you like try the copy of the chain.

If you encounter issues still or have a question let me know.
Not sure you use skype still but im online there for the whole day.

Copy of the blockchain:
<removed incase he didn't want link shared>

v2.5 nodes:
84.105.200.241
194.135.161.250
49.147.111.86
186.145.237.69
93.215.45.219
104.52.248.27
108.174.171.46
162.245.17.83
69.43.42.57
81.64.200.182
125.238.73.30
24.119.187.242
162.255.117.105
88.79.173.189
50.36.228.182
98.202.147.55
68.108.10.35
188.134.72.213
96.248.111.169
74.118.192.18
98.115.147.74

He offered to send me 20,000 netcoin to try to fix for myself. If you're all interested i think they have a skype channel. Jump in and contribute. In the end the coin is the communities and can benefit for all assistance. Not too many POS coins around with normal interest rates that work in a passive staking nature as opposed to having to dick around with block sizes and compete.

[o0o0]

This nodes working fine v2.5

getblockhash 1301108
50700911349bbae5c3995c67a14cfc232c454a71251886401e1a01e4b2c96075

yours ?

1301111

hash please

SetBestChain: new best=2ffbc35ad06cf6300a3d8ae73605ceb57a43662de928cd9de47e9d5c5f634ee2  height=1301112  trust=42899659188850436  blocktrust=1378738485  date=2016-09-18 02:35:46 UTC
ProcessBlock: ACCEPTED

ok, it's 1301112, at least 2 of us on the same chain

this is the correct chain and the one bittrex uses so don't fear. If you want to test it send 1 netcoin to bittrex to validate. my staking crashes but its a wallet issue that i can see that im working on but i was able to send to bittrex fine.

[o0o0]

already tested everything, just too many 2.3.1 yet, and presstab, i hope they'll soon update, nothing to worry
too little Führers of Cryptopia may j*** off until xmas, let them be happy

i don't understand that last part... fuhrers of cryptopia may jerk off? let them be happy? what do you mean

[6436346346]

already tested everything, just too many 2.3.1 yet, and presstab, i hope they'll soon update, nothing to worry
too little Führers of Cryptopia may j*** off until xmas, let them be happy

i don't understand that last part... fuhrers of cryptopia may jerk off? let them be happy? what do you mean

They are butthurt cause out NET wallet forked on 2.5, and now they think abusing us will fix it overnight.

[o0o0]

already tested everything, just too many 2.3.1 yet, and presstab, i hope they'll soon update, nothing to worry
too little Führers of Cryptopia may j*** off until xmas, let them be happy

i don't understand that last part... fuhrers of cryptopia may jerk off? let them be happy? what do you mean

They are butthurt cause out NET wallet forked on 2.5, and now they think abusing us will fix it overnight.

It was meant to fork on 2.5 i thought though.. so isn't that normal behavior. Or do you mean it didn't stay on correct chain?

[6436346346]

already tested everything, just too many 2.3.1 yet, and presstab, i hope they'll soon update, nothing to worry
too little Führers of Cryptopia may j*** off until xmas, let them be happy

i don't understand that last part... fuhrers of cryptopia may jerk off? let them be happy? what do you mean

They are butthurt cause out NET wallet forked on 2.5, and now they think abusing us will fix it overnight.

It was meant to fork on 2.5 i thought though.. so isn't that normal behavior. Or do you mean it didn't stay on correct chain?

Our 2.5 went off on its own fork (twice), we are resyncing now and battling the abusive support tickets from NET users, never a dull moment.

[o0o0]

already tested everything, just too many 2.3.1 yet, and presstab, i hope they'll soon update, nothing to worry
too little Führers of Cryptopia may j*** off until xmas, let them be happy

i don't understand that last part... fuhrers of cryptopia may jerk off? let them be happy? what do you mean

They are butthurt cause out NET wallet forked on 2.5, and now they think abusing us will fix it overnight.

It was meant to fork on 2.5 i thought though.. so isn't that normal behavior. Or do you mean it didn't stay on correct chain?

Our 2.5 went off on its own fork (twice), we are resyncing now and battling the abusive support tickets from NET users, never a dull moment.

I can understand. The fork was rather rushed and sudden so it needs to be spread around a bit. Unfortunately crypto dev stuff is taken as a given but like i explained when there is no ico or premine its rather hard to place the blame on a team. Everyone wants profits i can see but im amazed that the community doesn't get more onboard with all altcoins they have in the way of actually providing a use mechanism in shops etc or private projects.

A lot of coins would have more use than btc converters if that was the case.

Its why i suggested some donations happen it could provide more value and attract devs. O well.

How did your 2.5 go off on its own fork? I thought if consensus had enough 2.5 that shouldn't happen? What can cause the fork?

Why are you getting so much net user abuse in emails? The volume on bittrex is like 0.5btc a day and cryptopia lower... i'm unsure why there would be so much anger when the likelihood is most of your users have a netcoin usd equivilant of like $5

[o0o0]

2.4 generated stakes are not accepted... ok, after all this is a hard fork!

But why is my 2.5 wallet still refusing to stake and crashing as soon as I unlock it?

Any ideas?

Mine is doing the same and Arjan the coder is looking into it. I've been pm'ing him. It happens for a few people. Maybe we can gather some info.

1. What operating system are you using?
2. How many inputs in each of your addresses
3. How many coins in the largest input?

At present i am resyncing the blockchain from only 2.5 nodes and i am going to try a stake after backing it up at that point. If this fails im going to try and import the priv key. If this fails arjan is going to send me 20,000 netcoin to a new wallet.dat address to see if this works.

Its working for the majority there must be some small thing causing us issues.

Reading your post gave me an idea...

I sent all my coins to another address and that was enough to be able to unlock it, not only to send the coins but also to stake!

Let's see if really works and produces some valid stakes.

Fingers crossed!

Ok fresh sync with only 2.5 nodes in my connect list still crashes with both old wallet.dat and importing priv key and stake.

Can you confirm you've had good stakes ever since sending coins to new address? Did you try and send back to your original address? Its the only common thing i can see now.

Can you confirm what your input size on stake was? I have one that is > 10 million coins so im hoping its not the issue with input size. Could be something simple in the wallet code breaking due to out of bounds size?

[Trimegistus]

2.4 generated stakes are not accepted... ok, after all this is a hard fork!

But why is my 2.5 wallet still refusing to stake and crashing as soon as I unlock it?

Any ideas?

Mine is doing the same and Arjan the coder is looking into it. I've been pm'ing him. It happens for a few people. Maybe we can gather some info.

1. What operating system are you using?
2. How many inputs in each of your addresses
3. How many coins in the largest input?

At present i am resyncing the blockchain from only 2.5 nodes and i am going to try a stake after backing it up at that point. If this fails im going to try and import the priv key. If this fails arjan is going to send me 20,000 netcoin to a new wallet.dat address to see if this works.

Its working for the majority there must be some small thing causing us issues.

Reading your post gave me an idea...

I sent all my coins to another address and that was enough to be able to unlock it, not only to send the coins but also to stake!

Let's see if really works and produces some valid stakes.

Fingers crossed!

Unfortunately, my little trick didn't work... The wallet will stay unlocked for a few seconds but it'll crash as soon as it tries to stake  

Therefore, I tried another trick; sent all my coins to Bittrex, deleted my wallet.dat, created a new wallet and sent the coins to my new address.

Everything appears to be in order but I'm still waiting for my first 2.5 stake   and it's been 4 hours now...  

1. What operating system are you using? Win10x64
2. How many inputs in each of your addresses All my coins in a single block
3. How many coins in the largest input? Over 4 million

[o0o0]

2.4 generated stakes are not accepted... ok, after all this is a hard fork!

But why is my 2.5 wallet still refusing to stake and crashing as soon as I unlock it?

Any ideas?

Mine is doing the same and Arjan the coder is looking into it. I've been pm'ing him. It happens for a few people. Maybe we can gather some info.

1. What operating system are you using?
2. How many inputs in each of your addresses
3. How many coins in the largest input?

At present i am resyncing the blockchain from only 2.5 nodes and i am going to try a stake after backing it up at that point. If this fails im going to try and import the priv key. If this fails arjan is going to send me 20,000 netcoin to a new wallet.dat address to see if this works.

Its working for the majority there must be some small thing causing us issues.

Reading your post gave me an idea...

I sent all my coins to another address and that was enough to be able to unlock it, not only to send the coins but also to stake!

Let's see if really works and produces some valid stakes.

Fingers crossed!

Unfortunately, my little trick didn't work... The wallet will stay unlocked for a few seconds but it'll crash as soon as it tries to stake  

Therefore, I tried another trick; sent all my coins to Bittrex, deleted my wallet.dat, created a new wallet and sent the coins to my new address.

Everything appears to be in order but I'm still waiting for my first 2.5 stake   and it's been 4 hours now...  

1. What operating system are you using? Win10x64
2. How many inputs in each of your addresses All my coins in a single block
3. How many coins in the largest input? Over 4 million

ok thanks for update. arjan sent me 20,000 coins. i have them in 1 input ready to stake in 5 hours though bed soon so will try in 10 hours.

just out of curiosity im starting to think that stake issues are large inputs. bittrex isnt staking to my knowledge so wallet likely fine as just send and receives. i bet there is some wallet change code using int data types or the like associated with stake routine that crashes it. the issue will be before stake called.

If you are keen to troubleshoot with me more try having 4 addresses in each put
- 60,000
- 100,000
- 500,000
- 1,000,000

export the priv keys make sure to backup. import each of those addresses into a new wallet and test stake each one. i suspect the 1 million input stake to crash.

need to test each address in its own wallet so others dont stake as well.