Version 1.4.0 releasedThis update includes a FORK that will happen at block height 291111 which is approximately the 7th March 2017. Please update your wallets before that. DOWNLOADS |
|
|
|
Anyone else finding that there are very few connections on SDC network. My node (up 24/7) has 6 connections. Same server running bitcoind (average form 100 to 125 connections), blackcoin (average from 90 to 125 connections). I am not behind a NAT, direct public IP on the server. Block explorer also showing only 22 connections: https://chainz.cryptoid.info/sdc/#!network I am not saying that anything is wrong, I just find it strange that such a big market coin has so few nodes running. 16 here bro 16 is still not that much  Possible that there are plenty nodes running over tor? This is a PoS coin largely controlled by a very small number of people. It is centralized and I am not surprised to hear there are so few peers You realize there are over 250 wallets staking (accounting for 45%+ of the network)? How is that centralized.  That's not a small number of peers.. Technically those are addresses. One person could own all those addresses. You do not know who controls them. It is not 1 address = 1 peer. It can be 1 peer = 100 addresses = 10% of coins for example. But I of course do not know what is the actual distribution of SDC, I just wanted to point that out...that it is not so straightforward... |
|
|
|
Anyone else finding that there are very few connections on SDC network. My node (up 24/7) has 6 connections. Same server running bitcoind (average form 100 to 125 connections), blackcoin (average from 90 to 125 connections). I am not behind a NAT, direct public IP on the server. Block explorer also showing only 22 connections: https://chainz.cryptoid.info/sdc/#!network I am not saying that anything is wrong, I just find it strange that such a big market coin has so few nodes running. If you are behind NAT you are limited to "outbound" peers only i.e. 16 MAX on Shadow/Blk and 8 MAX on Bitcoin (unless you are using upnp) If you have public IP and correct firewall policy you will start to see "inbound" peers ... You can see from this explorer server that it is connected to over ~110 right now and can observe as much as ~200 daily ( http://explorer.shadow.cash/nodes/ ) Stopping the client, removing peers.dat and restarting should get you back into the game. Most of my nodes (and I run a dozen or so have over 70 peers). Hi, tnx for the hint. I deleted the peers.dat, shortly after restarting the daemon I am up to 17 connections and climbing fast. Strange thing though, I dont get it why that would happen. I am running shadowcash node for a year now, never had problems before. Did the peers.dat get so crowded with dead nodes over time it stopped adding new ones? Anyway, its fine now |
|
|
|
Anyone else finding that there are very few connections on SDC network. My node (up 24/7) has 6 connections. Same server running bitcoind (average form 100 to 125 connections), blackcoin (average from 90 to 125 connections). I am not behind a NAT, direct public IP on the server. Block explorer also showing only 22 connections: https://chainz.cryptoid.info/sdc/#!network I am not saying that anything is wrong, I just find it strange that such a big market coin has so few nodes running. 16 here bro 16 is still not that much Possible that there are plenty nodes running over tor? |
|
|
|
Anyone else finding that there are very few connections on SDC network. My node (up 24/7) has 6 connections. Same server running bitcoind (average form 100 to 125 connections), blackcoin (average from 90 to 125 connections). I am not behind a NAT, direct public IP on the server. Block explorer also showing only 22 connections: https://chainz.cryptoid.info/sdc/#!network I am not saying that anything is wrong, I just find it strange that such a big market coin has so few nodes running. |
|
|
|
untill POS the richest gets richier with multiple blocks by second is fixed i am dropping this from all my projects, as it seems one sided.
catch you laters i guess...
The stalls in the chain are to blame for that, the difficulty drops too fast suddenly, giving the "rich" node a chance to sign a few more blocks immediately. This will be fixed with a fork in the next release. The atempted update wanted to do that but it (I) failed miserably. You can speculate the coin will work better soon and invest now while it is still cheap  Hi dev, about the staking problem i am not sure if it can help with the POS problem but perhaps you can try. I have found stratis platform is too using blackcoin code, look what they did in the main.h for fix the drifting problem: https://github.com/stratisproject/stratisX/blob/master/src/main.hHi, thank you very much for the hint, I will look into their solution. My initial plan was to just increase it in proportion to the increased block time. Blackcoin: 64s (furure drift 5min) Nevacoin: 182s (increase from 5min to 15min) Thank you again! PM your neva address (if you have it) if you want a tip for this  |
|
|
|
untill POS the richest gets richier with multiple blocks by second is fixed i am dropping this from all my projects, as it seems one sided.
catch you laters i guess...
The stalls in the chain are to blame for that, the difficulty drops too fast suddenly, giving the "rich" node a chance to sign a few more blocks immediately. This will be fixed with a fork in the next release. The atempted update wanted to do that but it (I) failed miserably. You can speculate the coin will work better soon and invest now while it is still cheap |
|
|
|
hour and a half blocks still there...
still not getting nowhere even close to 10%...
i found its easier to mine and buy then, gets me bigger stake, meaning anyone who is mining can come to same conclusion, meaning network will go down..
not good for network (if i would be lets say 3 full gtx rigs i could already do a 51% fully).
POS not working (wallets getting multiple blocks in a row or like me getting 19/20 blocks conflicted).
These are immediate and imminent treats to the coin..
When network hash goes down, diff goes down, people start mining more, diff goes up and the story repeats. I think that is how a (free) market usually works... The value of the coin is reflected in its price, it is where it is at the moment. If the hash is so low that a 51% attack is feasable by an individual I think people will/ should wait for more confirmations. But then again, why would you 51% attack a 3000$ market cap coin if you can make more mining zec/eth/monero? What I am trying to say is, I don't quite get what you are trying to point out except the obvious We are talking about cryptocurrencyes after all, as everywhere else in life, and even more applicable here in crypto land: buyer beware. |
|
|
|
Hi!
Where it is possible to download a miner for AMD GPU?
There is no public AMD miner yet... if no mine then what is provided by their side Sorry I dont understand what you are asking :/ |
|
|
|
Nevacoin Version 1.3.2 Released 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) -remove code that caused the fork with version 1.3.1
DownloadsFor the ones that prefer updating than downgrading, version 1.3.2 is cleaned up from the fork mess and only contains the updates listed above. I apologize to everyone for the inconvenience. |
|
|
|
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. |
|
|
|
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. |
|
|
|
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 |
|
|
|
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. |
|
|
|
|
I can confirm that yobit is very very very slow with updates.
Had the same issues with Nevacoin. I submitted an update months before the fork, still the wallet was in maintenance for months after the fork.
And I also got all these generic replies.
I also sent three tickets for ARCO, same generic replies.
I dont have enough evidence to call them scammers, but I can call them extremely slow and unprofessional with client(dev) communication.
I mean seriously, we all know how long it takes to compile and update a coin daemon...its minutes. If you do it in time before the fork, there is no re-syncing necessary...
I think to be sure, you have to send them an update at least 3 months before the fork, and when you do, you still have to bug them every week of those 3 months to make sure they actually do it in time...
|
|
|
|
Looks like YoBit are now syncing their ARC wallet.
Still in maintenance atm :/ |
|
|
|
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! |
|
|
|
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... |
|
|
|
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 :/ |
|
|
|
|
Show Posts
