the price may pump when poloniex finish its maintenance

Yes, when the difficulty is falling a small number of the blocks come with a larger block reward.

This prevents large sources of hashrate (like nicehash) from "coin hopping".

Coin hopping is a lot like the "pool hopping" scheme that was commonplace before PPLNS, but instead of switching pools you switch coins.  It is a problem for every GPU-mined coin.  No matter how fancy and clever the difficulty-adjustment algorithm is, if there any large single source of hashpower (cough cough nicehash) they can boost their income by jumping into a coin, mining until the difficulty catches up to their added hashrate, then jumping over to another coin.  Even if the difficulty adjusts in one block, they still got mined one block of low-difficulty using their high hashrate.  As long as there are enough coins to hop between they can hop on every block, doesn't matter how fast the difficulty adjusts since it is always based on the previous block(s).  Take a look at the Monero hashrate, it's been oscillating up and down with almost exactly a 24-hour period for a few years now (their difficulty adjustment window is based on the last 24 hours worth of blocks).

By giving more reward to a randomly chosen block during dropping-difficulty periods (which is effectively taken from the reward during rising-difficulty periods) nexus thwarts this exploit.  Well, in theory.  It looks like the formula for boosting the reward is messed up, the bonus blocks seem to be larger and less frequent than they should be, but it still helps.  The other drawback is that this only works for multi-algorithm coins where the network time is based on all mining algorithms.  If a single-algorithm coin tried to do this then a nicehash-like coin hopper could defeat the mechanism by screwing with the block timestamps, and with enough hashpower the chain wouldn't know they were fudging the timestamps (by a small amount) and making the chain think the difficulty was dropping (by speeding up time) when in fact it wasn't.  Everybody would do this and pretty soon the chain timestamps would be way ahead of the actual wall-clock time on all the non-mining clients.

With two or more mining algorithms there is no incentive for the miners on the other algorithms to do the same thing at the same time, so they don't.  On the other hand nexus's "unified time" causes a lot of other headaches for people, I'm not sure it was a good idea either.

I found two blocks today but only one get credited: the other one is gone !

I found 9 blocks in total but my balance is 108,591633 (a balance of 8 blocks)

Edit : the nb of transactions was 9 and it is 8 now...

Now long takes deposit confirmation on bittrex? One hour and still 0 of 3 confirmation in local wallet.

Edit: second transaction has 50+ confirmations but still not shown on exchange even on pending. Same with Cryptopia.

I have two wallets running on two different computers and one wallet is almost always a few blocks behind with the debug.log filled with:
***** Core LLP: Unified Samples Out of Drift Scope Current (8205) Samples (8234)

Both wallets have 8 nodes connected and the time is also synchronized.

This is the part in the source for the error but it's no help to me: https://github.com/Nexusoft/Nexus/blob/master/src/core/unifiedtime.cpp#L287

What is causing this?

So I ordered both the AB350 Gaming K4 and the AB350 Pro 4.  I got the Gaming K4 in yesterday.  

In my tests; only 4x Nvidia cards worked with Ubuntu 16.04.  I tried a lot of different bios settings; there might be one I missed, or a future bios update that enables 6x Nvidia: but for now these aren't worth it IMO.  Also might work with 6x amd cards; I only have 4x 470s, so I can't test that.

I expect the Pro 4 to have similar results.

Used this CPU:

https://www.newegg.com/Product/Product.aspx?Item=N82E16819113437

and this RAM:

https://www.newegg.com/Product/Product.aspx?Item=N82E16820233982

Hi,
I think you should open the wallet first (no syncing - just for creating the Nexus folder in AppData/Roaming), close it, remove wallet.dat and insert your old one, then open the wallet again and then let it sync.
I tried to put my wallet.dat to a synced wallet and it didn't work, then it tried it like above and it worked. You can give it a try.

Assuming Nexus POS works the same way as proposed Bitcoin POS, there would be a POS mining channel with its own mining algorithm and reward.  The Nexus blockchain lists the hash and prime channels, but not the hidden POS mining channel. And there are no public POS miners available. So who is mining the POS blocks and what is their reward?

Maybe the POS miner is built into the wallet? That would explain why the wallet uses so much CPU constantly. Do open wallets sometimes get random POS mining rewards?

Is it possible each block that gets mined by the hash algorithm sends the unused prime reward to the Nexus authors, and each block that gets PRIME mined sends the unused hash reward to the them instead.  This keeps the hash and prime rewards in sync, but still rewards the miners and the Nexus guys.

You are the creator of Nexus?

it's false, that quantum can break sha 256, they are spreading misinformation in fct it's not sha256 which is in danger of quantum when they will be available, but it's a round of hash to have the private key, i think it was called ECDSA but i maybe wrong, this is vulnerable, and if nexus is using this for their private key they will be vulnerable also

I have a problem on CentOS 7.3 with Nexus Wallet.



I've tried two times and after one minute of loading it always says something about stylesheet, anyone can help me?

i think the new miners was not updated to work with the last wallet they changed something in the code maybe

You can enter mV values but they will be ignored. GPU core voltage is calculated at runtime in relative steps to its base voltage. What you will need is an offset either hardcoded into the bios using a hex editor ( complicated ) or a tool like Strixx or Watttool ( simple ) to load the core voltage offset at system startup.