krile (OP)
|
|
October 22, 2016, 02:36:01 PM Last edit: October 22, 2016, 03:08:22 PM by krile |
|
The code on GitHub is updated to version 1.3 if anyone wants to compile it. Compiled binaries will be released in the following days, I might change other things before I make an official release. Current changes: -remove Alert functionality ( -disconnect from nodes older than protocol 65005 (all pre-fork nodes) -remove mining button (difficulty too high to be usable anymore, setgenerate still works) -added additional seed nodes -add checkpoints It is not a mandatory update. If you want to use the gui mining button in the wallet keep using v1.2.3.
|
|
|
|
crysx
|
|
October 23, 2016, 04:38:09 AM |
|
The code on GitHub is updated to version 1.3 if anyone wants to compile it. Compiled binaries will be released in the following days, I might change other things before I make an official release. Current changes: -remove Alert functionality ( -disconnect from nodes older than protocol 65005 (all pre-fork nodes) -remove mining button (difficulty too high to be usable anymore, setgenerate still works) -added additional seed nodes -add checkpoints It is not a mandatory update. If you want to use the gui mining button in the wallet keep using v1.2.3. tanx ... ill look at this today mate ... see if i can compile it on the servers - centos 7 x64 ... #crysx
|
|
|
|
grimdin
Newbie
Offline
Activity: 46
Merit: 0
|
|
October 26, 2016, 07:39:55 AM |
|
Nevabutton game, nevabutton.grimdin.xyz goes down tomorrow(thursday)
I will shutdown that server.
Its very possible that i will install new server and bring it up again.
|
|
|
|
crysx
|
|
October 26, 2016, 11:00:14 AM |
|
the code has compiled successfully ...
after some testing tomorrow - ill setup the full nodes and sync them all if all the tests go well ...
#crysx
|
|
|
|
cryptostiltskin
|
|
November 13, 2016, 09:41:31 PM Last edit: November 13, 2016, 10:14:19 PM by cryptostiltskin |
|
There is new interest in NEVA at yobit. I love having an online wallet at poswallet.
|
|
|
|
krile (OP)
|
|
November 13, 2016, 11:19:08 PM |
|
There is new interest in NEVA at yobit. I love having an online wallet at poswallet.
Yes the coin is doing pretty good. Have a big user base in Brazil They even have a Telegram group, too bad I dont speak Portuguese :/
|
|
|
|
krile (OP)
|
|
November 13, 2016, 11:29:29 PM |
|
Nevacoin will probably get listed on https://bitsquare.io/I just have to solve this stupid malware warning for http://nevacoin.pwI think it is because I did not filter one of the add placements for "shady" content... Should be solved in a few days...
|
|
|
|
|
Draax
Newbie
Offline
Activity: 21
Merit: 0
|
|
November 23, 2016, 04:45:41 PM |
|
There is something fundamentaly wrong with protocol. While running minimum of 2.5Ghz constantly (meaning that i fluctuate between 25% and 8% of total hash minimum) with average of about 14%, in 12 hours i received only 9 blocks. As for the aim time of 90 seconds fluctuations in difficulty aint that big (i mean even with spikes to 35Ghz of total network I should be able to solve at least by 10 times average slower, lets use statistics), including pos double that. Plus observing "nothing happens for 1 hour then lots of stuff happening in 5 minutes" i dont think that i can be attributed to "it has to equal out etc", the jums are to double, not to infinity, meaning blocks should be solved no?
can it have something to do that we for example find that 1/3rd of solved difficulty blocks are rejected (not orphaned, rejected) without reason? while doing well over difficulty requrements? we are running 1.2.3 client.
I am planning on a semi/pro webgame esport head to head and team based website, that we are secretly working for a long time, with adds only with crypto add site and betting and etc, and i was thinking about first coins to add in there, as a launch, so far we have 3 planned and we were searching for fourth, and were thinking to choose from "lower" ones. Can anyone explain how to include this into schema if people have to wait up for one hour for confirmations? its slower than btc...
Lots of questions, will play here for 48 more hours before deciding, but so far doesnt seem so good, without any prospective and work done from devs or opening it up for public.
Disclaimer: we are looking into coin as it had no premine and was fair start. We will not use any of that premine and secret launch coins...
|
|
|
|
Draax
Newbie
Offline
Activity: 21
Merit: 0
|
|
November 24, 2016, 07:36:02 AM Last edit: November 24, 2016, 04:27:46 PM by Draax |
|
Actually making it more then half rejected (not orphaned, block not found, just solution rejected). at the state of 7/18 accepted only through 10 hour period... Seems like something is wrong.
edit make that 7/20
|
|
|
|
Draax
Newbie
Offline
Activity: 21
Merit: 0
|
|
November 25, 2016, 07:40:26 PM |
|
also same guy getting 7 pos in a row within a minute? is that a possibility?
should we just declare this coin dead fart due to noone willing to address issues?
|
|
|
|
Lercker
|
|
November 25, 2016, 08:59:01 PM |
|
also same guy getting 7 pos in a row within a minute? is that a possibility?
should we just declare this coin dead fart due to noone willing to address issues?
Krile is the only current dev of this coin. He wants this to be a community coin, so if you want to try to fix the code for the POS or know someone who would be willing to try feel free to pull to code off Github, the link is on the OP. Krile's tried to fix it before but I think has taken time off this endeavor to try an produce a mobile wallet first... The POS could be worse, it works out okay most of the time.
|
|
|
|
krile (OP)
|
|
November 25, 2016, 10:16:57 PM |
|
There is something fundamentaly wrong with protocol. While running minimum of 2.5Ghz constantly (meaning that i fluctuate between 25% and 8% of total hash minimum) with average of about 14%, in 12 hours i received only 9 blocks. As for the aim time of 90 seconds fluctuations in difficulty aint that big (i mean even with spikes to 35Ghz of total network I should be able to solve at least by 10 times average slower, lets use statistics), including pos double that. Plus observing "nothing happens for 1 hour then lots of stuff happening in 5 minutes" i dont think that i can be attributed to "it has to equal out etc", the jums are to double, not to infinity, meaning blocks should be solved no?
can it have something to do that we for example find that 1/3rd of solved difficulty blocks are rejected (not orphaned, rejected) without reason? while doing well over difficulty requrements? we are running 1.2.3 client.
I am planning on a semi/pro webgame esport head to head and team based website, that we are secretly working for a long time, with adds only with crypto add site and betting and etc, and i was thinking about first coins to add in there, as a launch, so far we have 3 planned and we were searching for fourth, and were thinking to choose from "lower" ones. Can anyone explain how to include this into schema if people have to wait up for one hour for confirmations? its slower than btc...
Lots of questions, will play here for 48 more hours before deciding, but so far doesnt seem so good, without any prospective and work done from devs or opening it up for public.
Disclaimer: we are looking into coin as it had no premine and was fair start. We will not use any of that premine and secret launch coins...
No need to get so upset. There is nothin malicious in the code. I am currently addressing this problem of "nothing happening for an hour and the 10 blocks coming in" -which is also responsible for the rejected blocks. I already atempted a fix a while back but I failed and had to revert back. Another fix is on its way, still on testnet atm, its really hard to replicate this problem on testnet btw, that is why its a pain to solve. Could be out this weekend, but in any case it will be a fork months away because of yobits extremely slow wallet update response time (the last fork was set too soon and it took them more than a month to update the wallet, so this time I will give them more time). But hang in there, this coin started as a cute gift but it actually developed into something. But we all know how it is here, everybody wants 1BTC just to start talking to you if you ask for some dev help. I am still doing everything on my own. Peace!
|
|
|
|
krile (OP)
|
|
November 28, 2016, 08:59:20 PM Last edit: November 29, 2016, 09:32:26 PM by krile |
|
Nevacoin Version 1.3.1 Released Please note this version is not a fork, it is compatible with protocol version 65005 (wallet version 1.2.3). It contains some fixes that are worth the upgrade especially it you use the wallet for mining.
well it kinda was... Changes: -remove mining button from the gui (difficulty to high to be usable anymore, "setgenerate true" still works from the debug window) -disconnect from nodes older than protocol 65005 (versions older than 1.2.3 - prefork) -remove alert key functionality from the code (a feature too centralized for my taste, and not used anyway) -other minor code cleanups -add checkpoints -update existing seed nodes to new * nevacoin.net domain -add additional seeds, thanks to @staysecure ( ARCO dev) and crysx (chainworksindustries, GraniteCoin dev) -attempt a fix for the blockchain being stuck for an hour or more on occasions Downloads See below for 1.3.2 downloads On this occasion I also announce (again) that the nevacoin website, faucet and dice game have been moved from the .pw domain to nevacoin .net. Links on the website have been updated, also the paper wallet generator is available online (for extra secure paper wallets always download the zip and generate them offline). The website will see further changes and updates in the coming days/weeks.
|
|
|
|
killdemon
|
|
November 29, 2016, 11:50:00 AM Last edit: November 29, 2016, 01:35:05 PM by killdemon |
|
It looks like 1.3.1 introduced blockchain fork. 1.3.0 and 1.3.1 wallets are on side of the fork and the rest of the users are on another one!!! Please double check. Also you can see at https://chainz.cryptoid.info/neva/#!network PENDING CONNECTIONS!!! I am suggesting to all to move to 1.31 version as fast as possible.
|
|
|
|
krile (OP)
|
|
November 29, 2016, 05:50:28 PM Last edit: November 29, 2016, 06:20:26 PM by krile |
|
It looks like 1.3.1 introduced blockchain fork. 1.3.0 and 1.3.1 wallets are on side of the fork and the rest of the users are on another one!!! Please double check. Also you can see at https://chainz.cryptoid.info/neva/#!network PENDING CONNECTIONS!!! I am suggesting to all to move to 1.31 version as fast as possible. Well this one sucks. Dont update. Revert back to 1.2.3/1.3.0. Most of the network is on the old chain so lets keep it that way for now. It anyone wants to make a NevaClassic on the new fork be my guests My good friend pointed out that we are the NevaClassic chain. Screw you new NevaCoin chain! We are not forking! Downloads for 1.2.3 for those who already updated: https://github.com/Nevacoin/nevacoin/releases/tag/v1.2.3SUM: 1.2.3 = GOOD 1.3.0 = GOOD 1.3.1 = BAD 1.3.2 = GOOD
|
|
|
|
Draax
Newbie
Offline
Activity: 21
Merit: 0
|
|
November 29, 2016, 06:19:43 PM |
|
I would strongly suggest then update download links in first post.. it usually is the one which gets most clicks downloads... Lost 8 pos blocks today.. not that a single ever pos block was validated, always conflicted It looks like 1.3.1 introduced blockchain fork. 1.3.0 and 1.3.1 wallets are on side of the fork and the rest of the users are on another one!!! Please double check. Also you can see at https://chainz.cryptoid.info/neva/#!network PENDING CONNECTIONS!!! I am suggesting to all to move to 1.31 version as fast as possible. Well this one sucks. Dont update. Revert back to 1.2.3/1.3.0. Most of the network is on the old chain so lets keep it that way for now. It anyone wants to make a NevaClassic on the new fork be my guests Downloads for 1.2.3 for those who already updated: https://github.com/Nevacoin/nevacoin/releases/tag/v1.2.3SUM: 1.2.3 = GOOD 1.3.0 = GOOD 1.3.1 = BAD 1.3.2 = GOOD
|
|
|
|
killdemon
|
|
November 29, 2016, 06:21:10 PM |
|
I have updated to 1.3.1, now after the fork i have reverted back to 1.2.3 but i am at same fork. -rescan is not working. How to get back and resync?
|
|
|
|
krile (OP)
|
|
November 29, 2016, 06:23:21 PM |
|
I would strongly suggest then update download links in first post.. it usually is the one which gets most clicks downloads... Lost 8 pos blocks today.. not that a single ever pos block was validated, always conflicted It looks like 1.3.1 introduced blockchain fork. 1.3.0 and 1.3.1 wallets are on side of the fork and the rest of the users are on another one!!! Please double check. Also you can see at https://chainz.cryptoid.info/neva/#!network PENDING CONNECTIONS!!! I am suggesting to all to move to 1.31 version as fast as possible. Well this one sucks. Dont update. Revert back to 1.2.3/1.3.0. Most of the network is on the old chain so lets keep it that way for now. It anyone wants to make a NevaClassic on the new fork be my guests Downloads for 1.2.3 for those who already updated: https://github.com/Nevacoin/nevacoin/releases/tag/v1.2.3SUM: 1.2.3 = GOOD 1.3.0 = GOOD 1.3.1 = BAD 1.3.2 = GOOD Haha, good one. You cant lose what you never had. But jokes aside, we will get there, we will fix all the problems in time. This coin was a gift for my girlfriend, she is as confusing as this coin is at times.
|
|
|
|
krile (OP)
|
|
November 29, 2016, 06:24:03 PM |
|
I have updated to 1.3.1, now after the fork i have reverted back to 1.2.3 but i am at same fork. -rescan is not working. How to get back and resync?
Delete everything in nevacoin directory EXCEPT THE WALLET.DAT and restart the 1.2.3 wallet.
|
|
|
|
|