ccminer-1-7-6-r10-neoscrypt

Here is an updated ccMiner 1.7.6-r10 Widows binary of the Nanashi Meiyo-Meijin fork (source) with optimized Lyra2RE and Lyra2REv2 performance. The latest r10 update fixes the hashrate issues that were present with other versions of ccMiner on the latest Nvidia Pascal GPUs such as GTX 1080 and GTX 1070. You can see a brief test of the performance of the new 32-bit Windows binary of the miner compiled with VS2013 and CUDA 8.0 below.

ccMiner 1.7.6-r10 Neoscrypt performance:
– GTX 1080 – 985 KHS
– GTX 1070 – 889 KHS
– GTX 980 Ti – 840 KHS

Just as a reference the latest ccMiner fork by SP has managed to provide just about 365 KHS on GTX 1080 and 668 KHS on GTX 1070, so now you can fully utilize the performance of the new Nvidia Pascal GPUs for mining NeoScrypt-based crypto coins. Do note that the results quoted above are with

To download the latest ccMiner 1.7.6-r10 with fixed Neoscrypt on Pascal for Windows OS…

geth-hard-fork-support

The latest Ethereum Go client Geth version 1.4.10 named “Return of the ETH” has been just made available for download as the go-ethereum team’s DAO hard-fork implementation. It enables anyone to choose whether they would like to support the DAO hard-fork or oppose it, and take them to their blockchain of choice. On startup (on the main network) Geth will print the currently configured choice, which you can freely change with the appropriate flag at any time. If no flag is specified, the previous configuration is used. If no fork choice was ever provided, Geth will default to supporting the fork per the majority vote.

How to make your choice:
– To support the DAO hard-fork, start Geth with --support-dao-fork
– To oppose the DAO hard-fork, start Geth with --oppose-dao-fork

To download the latest Ethereum Geth client 1.4.10 with the Hard Fork support…

ethereum-hard-fork

The plans for the upcoming Ethereum hard fork that is designed to fix the issues around the DAO situation have been published, with the hard fork planne to take place at block number 1922000 that should hit around 20th of July though it may depend on your time zone. The idea is to have the hard fork take place shortly before the 21.07, which is the date in which the DAO attacker can split. Some of the Ethereum clients such as Parity and the most widely used Geth have a hard-fork implementation for The DAO now, though they have not released updates for the hard fork yet. Other clients like pyethereum, or libethereum already started their implementations of the hard-fork, so it is certain that they will release a new version including the hard fork with the same date. Do note that you will need to update your local Ethereum client before the planned block in order to ensure that you will be able to continue using it after block 1922000. With hard forks you need to update your client in order for it to continue operating properly on the network as it includes mandatory changes making older releases incompatible.

Ethereum is also extending their bounty program to include vulnerabilities found in the hard fork specification. This includes the specification itself, the associated smart contract code that is defined in the specification, and the implementations in geth, cpp-ethereum, parity, and pyethapp clients. So people that find issues in the code and report them can be rewarded for their efforts and at the same time they will be making Ethereum safer and more problem free for use in the future.

To read more details about the upcoming hard fork of Ethereum intended to resolve the DAO situation…

top