expanse-org / go-expanse

Jeffrey Wilcke's Go implementation of the Ethereum y/w paper

Expanse Go

Official golang implementation of the Expanse protocol. 🍰

Automated builds are available for stable releases and the unstable master branch. Binary archives are published at https://gexp.expanse.tech/downloads/.

Building the source

For prerequisites and detailed build instructions please read the Installation Instructions on the wiki.

Building gexp requires both a Go (version 1.13 or later) and a C compiler. You can install them using your favorite package manager. Once the dependencies are installed, run

make gexp

or, to build the full suite of utilities:

make all

Executables

The go-expanse project comes with several wrappers/executables found in the cmd directory.

Command	Description
gexp	Our main Expanse CLI client. It is the entry point into the Expanse network (main-, test- or private net), capable of running as a full node (default), archive node (retaining all historical state) or a light node (retrieving data live). It can be used by other processes as a gateway into the Expanse network via JSON RPC endpoints exposed on top of HTTP, WebSocket and/or IPC transports. gexp --help and the CLI Wiki page for command line options.
abigen	Source code generator to convert Expanse contract definitions into easy to use, compile-time type-safe Go packages. It operates on plain Expanse contract ABIs with expanded functionality if the contract bytecode is also available. However, it also accepts Solidity source files, making development much more streamlined. Please see our Native DApps wiki page for details.
bootnode	Stripped down version of our Expanse client implementation that only takes part in the network node discovery protocol, but does not run any of the higher level application protocols. It can be used as a lightweight bootstrap node to aid in finding peers in private networks.
evm	Developer utility version of the EVM (Expanse Virtual Machine) that is capable of running bytecode snippets within a configurable environment and execution mode. Its purpose is to allow isolated, fine-grained debugging of EVM opcodes (e.g. evm --code 60ff60ff --debug run).
gexprpctest	Developer utility tool to support our expanse/rpc-test test suite which validates baseline conformity to the Expanse JSON RPC specs. Please see the test suite's readme for details.
rlpdump	Developer utility tool to convert binary RLP (Recursive Length Prefix) dumps (data encoding used by the Expanse protocol both network as well as consensus wise) to user-friendlier hierarchical representation (e.g. rlpdump --hex CE0183FFFFFFC4C304050583616263).
puppeth	a CLI wizard that aids in creating a new Expanse network.

Running gexp

Going through all the possible command line flags is out of scope here (please consult our CLI Wiki page), but we've enumerated a few common parameter combos to get you up to speed quickly on how you can run your own Gexp instance.

Full node on the main Expanse network

By far the most common scenario is people wanting to simply interact with the Expanse network: create accounts; transfer funds; deploy and interact with contracts. For this particular use-case the user doesn't care about years-old historical data, so we can fast-sync quickly to the current state of the network. To do so:

$ gexp --fast --cache=512 console

This command will:

• Start gexp in fast sync mode (default, can be changed with the --syncmode flag), causing it to download more data in exchange for avoiding processing the entire history of the Expanse network, which is very CPU intensive.
• Start up gexp's built-in interactive JavaScript console, (via the trailing console subcommand) through which you can invoke all official web3 methods as well as gexp's own management APIs. This tool is optional and if you leave it out you can always attach to an already running gexp instance with gexp attach.

A Full node on the Görli test network

Transitioning towards developers, if you'd like to play around with creating Ethereum contracts, you almost certainly would like to do that without any real money involved until you get the hang of the entire system. In other words, instead of attaching to the main network, you want to join the test network with your node, which is fully equivalent to the main network, but with play-Ether only.

$ gexp --goerli console

The console subcommand has the exact same meaning as above and they are equally useful on the testnet too. Please, see above for their explanations if you've skipped here.

Specifying the --goerli flag, however, will reconfigure your gexp instance a bit:

• Instead of connecting the main Expanse network, the client will connect to the Görli test network, which uses different P2P bootnodes, different network IDs and genesis states.

• Instead of using the default data directory (~/.expanse on Linux for example), gexp will nest itself one level deeper into a goerli subfolder (~/.expanse/goerli on Linux). Note, on OSX and Linux this also means that attaching to a running testnet node requires the use of a custom endpoint since gexp attach will try to attach to a production node endpoint by default, e.g., gexp attach <datadir>/goerli/gexp.ipc. Windows users are not affected by this.

• Instead of using the default data directory (~/.expanse on Linux for example), Gexp will nest itself one level deeper into a testnet subfolder (~/.expanse/testnet on Linux). Note, on OSX and Linux this also means that attaching to a running testnet node requires the use of a custom endpoint since gexp attach will try to attach to a production node endpoint by default. E.g. gexp attach <datadir>/testnet/gexp.ipc. Windows users are not affected by this.

• Instead of connecting the main Expanse network, the client will connect to the test network, which uses different P2P bootnodes, different network IDs and genesis states.

Note: Although there are some internal protective measures to prevent transactions from crossing over between the main network and test network, you should make sure to always use separate accounts for play-money and real-money. Unless you manually move accounts, Gexp will by default correctly separate the two networks and will not make any accounts available between them.

Full node on the Rinkeby test network

Go Expanse also supports connecting to the older proof-of-authority based test network called Rinkeby which is operated by members of the community.

$ gexp --rinkeby console

Full node on the Ropsten test network

In addition to Görli and Rinkeby, Geth also supports the ancient Ropsten testnet. The Ropsten test network is based on the Ethash proof-of-work consensus algorithm. As such, it has certain extra overhead and is more susceptible to reorganization attacks due to the network's low difficulty/security.

$ gexp --ropsten console

Note: Older Geth configurations store the Ropsten database in the testnet subdirectory.

Configuration

As an alternative to passing the numerous flags to the gexp binary, you can also pass a configuration file via:

$ gexp --config /path/to/your_config.toml

To get an idea how the file should look like you can use the dumpconfig subcommand to export your existing configuration:

$ gexp --your-favourite-flags dumpconfig

Note: This works only with gexp v1.6.0 and above.

Docker quick start

One of the quickest ways to get Expanse up and running on your machine is by using Docker:

docker run -d --name expanse-node -v /Users/alice/expanse:/root \
           -p 9656:9656 -p 42786:42786 \
           expanse/client-go --fast --cache=512

This will start gexp in fast sync mode with a DB memory allowance of 512MB just as the above command does. It will also create a persistent volume in your home directory for saving your blockchain as well as map the default ports. There is also an alpine tag available for a slim version of the image.

Do not forget --http.addr 0.0.0.0, if you want to access RPC from other containers and/or hosts. By default, gexp binds to the local interface and RPC endpoints is not accessible from the outside.

As a developer, sooner rather than later you'll want to start interacting with Gexp and the Expanse network via your own programs and not manually through the console. To aid this, Gexp has built in support for a JSON-RPC based APIs (standard APIs and Gexp specific APIs). These can be exposed via HTTP, WebSockets and IPC (unix sockets on unix based platroms, and named pipes on Windows).

The IPC interface is enabled by default and exposes all the APIs supported by Gexp, whereas the HTTP and WS interfaces need to manually be enabled and only expose a subset of APIs due to security reasons. These can be turned on/off and configured as you'd expect.

HTTP based JSON-RPC API options:

• --http Enable the HTTP-RPC server
• --http.addr HTTP-RPC server listening interface (default: localhost)
• --http.port HTTP-RPC server listening port (default: 8545)
• --http.api API's offered over the HTTP-RPC interface (default: eth,net,web3)
• --http.corsdomain Comma separated list of domains from which to accept cross origin requests (browser enforced)
• --ws Enable the WS-RPC server
• --ws.addr WS-RPC server listening interface (default: localhost)
• --ws.port WS-RPC server listening port (default: 8546)
• --ws.api API's offered over the WS-RPC interface (default: eth,net,web3)
• --ws.origins Origins from which to accept websockets requests
• --ipcdisable Disable the IPC-RPC server
• --ipcapi API's offered over the IPC-RPC interface (default: admin,debug,eth,miner,net,personal,shh,txpool,web3)
• --ipcpath Filename for IPC socket/pipe within the datadir (explicit paths escape it)

You'll need to use your own programming environments' capabilities (libraries, tools, etc) to connect via HTTP, WS or IPC to a Gexp node configured with the above flags and you'll need to speak JSON-RPC on all transports. You can reuse the same connection for multiple requests!

Note: Please understand the security implications of opening up an HTTP/WS based transport before doing so! Hackers on the internet are actively trying to subvert Expanse nodes with exposed APIs! Further, all browser tabs can access locally running webservers, so malicious webpages could try to subvert locally available APIs!

Operating a private network

Maintaining your own private network is more involved as a lot of configurations taken for granted in the official networks need to be manually set up.

Defining the private genesis state

First, you'll need to create the genesis state of your networks, which all nodes need to be aware of and agree upon. This consists of a small JSON file (e.g. call it genesis.json):

{
  "config": {
    "chainId": <arbitrary positive integer>,
    "homesteadBlock": 0,
    "eip150Block": 0,
    "eip155Block": 0,
    "eip158Block": 0,
    "byzantiumBlock": 0,
    "constantinopleBlock": 0,
    "petersburgBlock": 0,
    "istanbulBlock": 0,
    "berlinBlock": 0
  },
  "alloc": {},
  "coinbase": "0x0000000000000000000000000000000000000000",
  "difficulty": "0x20000",
  "extraData": "",
  "gasLimit": "0x2fefd8",
  "nonce": "0x0000000000000042",
  "mixhash": "0x0000000000000000000000000000000000000000000000000000000000000000",
  "parentHash": "0x0000000000000000000000000000000000000000000000000000000000000000",
  "timestamp": "0x00"
}

The above fields should be fine for most purposes, although we'd recommend changing the nonce to some random value so you prevent unknown remote nodes from being able to connect to you. If you'd like to pre-fund some accounts for easier testing, create the accounts and populate the alloc field with their addresses.

"alloc": {
  "0x0000000000000000000000000000000000000001": {
    "balance": "111111111"
  },
  "0x0000000000000000000000000000000000000002": {
    "balance": "222222222"
  }
}

With the genesis state defined in the above JSON file, you'll need to initialize every Gexp node with it prior to starting it up to ensure all blockchain parameters are correctly set:

$ gexp init path/to/genesis.json

Creating the rendezvous point

With all nodes that you want to run initialized to the desired genesis state, you'll need to start a bootstrap node that others can use to find each other in your network and/or over the internet. The clean way is to configure and run a dedicated bootnode:

$ bootnode --genkey=boot.key
$ bootnode --nodekey=boot.key

With the bootnode online, it will display an enode URL that other nodes can use to connect to it and exchange peer information. Make sure to replace the displayed IP address information (most probably [::]) with your externally accessible IP to get the actual enode URL.

Note: You could also use a full fledged Gexp node as a bootnode, but it's the less recommended way.

Starting up your member nodes

With the bootnode operational and externally reachable (you can try telnet <ip> <port> to ensure it's indeed reachable), start every subsequent Gexp node pointed to the bootnode for peer discovery via the --bootnodes flag. It will probably also be desirable to keep the data directory of your private network separated, so do also specify a custom --datadir flag.

$ gexp --datadir=path/to/custom/data/folder --bootnodes=<bootnode-enode-url-from-above>

Note: Since your network will be completely cut off from the main and test networks, you'll also need to configure a miner to process transactions and create new blocks for you.

Running a private miner

Mining on the public Expanse network is a complex task as it's only feasible using GPUs, requiring an OpenCL or CUDA enabled ethminer instance. For information on such a setup, please consult the EtherMining subreddit and the Genoil miner repository.

In a private network setting however, a single CPU miner instance is more than enough for practical purposes as it can produce a stable stream of blocks at the correct intervals without needing heavy resources (consider running on a single thread, no need for multiple ones either). To start a Gexp instance for mining, run it with all your usual flags, extended by:

$ gexp <usual-flags> --mine --miner.threads=1 --miner.etherbase=0x0000000000000000000000000000000000000000

Which will start mining blocks and transactions on a single CPU thread, crediting all proceedings to the account specified by --miner.etherbase. You can further tune the mining by changing the default gas limit blocks converge to (--miner.targetgaslimit) and the price transactions are accepted at (--miner.gasprice).

Contribution

Thank you for considering to help out with the source code! We welcome contributions from anyone on the internet, and are grateful for even the smallest of fixes!

If you'd like to contribute to go-expanse, please fork, fix, commit and send a pull request for the maintainers to review and merge into the main code base. If you wish to submit more complex changes though, please check up with the core devs first on our gitter channel to ensure those changes are in line with the general philosophy of the project and/or get some early feedback which can make both your efforts much lighter as well as our review and merge procedures quick and simple.

Please make sure your contributions adhere to our coding guidelines:

• Code must adhere to the official Go formatting guidelines (i.e. uses gofmt).
• Code must be documented adhering to the official Go commentary guidelines.
• Pull requests need to be based on and opened against the master branch.
• Commit messages should be prefixed with the package(s) they modify.
  • E.g. "eth, rpc: make trace configs optional"

Please see the Developers' Guide for more details on configuring your environment, managing project dependencies and testing procedures.

License

The go-expanse library (i.e. all code outside of the cmd directory) is licensed under the GNU Lesser General Public License v3.0, also included in our repository in the COPYING.LESSER file.

The go-expanse binaries (i.e. all code inside of the cmd directory) is licensed under the GNU General Public License v3.0, also included in our repository in the COPYING file.

go-expanse's Issues

"The method exp_syncing does not exist/is not available"

System information

Gexp version: gexp version
VERSION:
1.6.6-beta-5757b6f7

OS & Version: Windows/Linux/OSX
Windows
Commit hash : (if develop)
5757b6f ?

Expected behaviour

Actual behaviour

"The method exp_syncing does not exist/is not available"

Steps to reproduce the behaviour

start gexp.exe --datadir "..\Expanse" --syncmode "full" --rpc --rpcapi "admin,eth,exp,miner,personal,rpc,txpool,web3"

erroor:
"The method exp_syncing does not exist/is not available"

Backtrace

[backtrace]

No discv4 seed nodes found

System information

Gexp version: gexp version latest
OS & Version: Linux
Commit hash : (if develop)

i am using ubuntu 16 (digitalocean vps) i can sync. full chain but after that it says No discv4 seed nodes found and problem begins.
I have checked everying. Time system is ok , When i check gexp attach
net.peerCount =1

admin.peers
[{
caps: ["exp/62", "exp/63"],
id: "d33a8d4c2c38a08971ed975b750f21d54c927c0bf7415931e214465a8d01651ecffe4401e1db913f398383381413c78105656d665d83f385244ab302d6138414",
name: "Gexp/v1.7.2-stable-9c901caa/linux-amd64/go1.7.5",
network: {
localAddress: "167.xx.253.xxx:52692",
remoteAddress: "1xx.199.xxx.48:42786"
},
protocols: {
exp: {
difficulty: 11234333021058860000,
head: "0x71724511012e77de0f8f1c93434a9d5f93fc2478015b771fe3a9255c96fe29d2",
version: 63
}
}
}]

reward

System information

Version: 1.7.2-stable
Git Commit: 9c901ca
Architecture: amd64
Protocol Versions: [63 62]
Network Id: 1
Go Version: go1.7.5
Operating System: linux

Expected behaviour

Actual behaviour

Steps to reproduce the behaviour

Backtrace

[backtrace]

I updated my expnase pool, but the rewards is worng always is 8 exp.. i changed payouts/unlocker.go

var constReward = math.MustParseBig256("8000000000000000000")

to

var constReward = math.MustParseBig256("4000000000000000000")

but always show 8 exp.. what i can do?

Compile error with Go 1.10

Can not compile with Go version 1.10 as it says I have old version and need atleast 1.7 (but I think 1.10 is newer than 1.7).

Actually if I will change 'if' in build/ci.go to something match my version, compilation is success. But I think this should be solved somehow other proper way and commited to GIT.

System information

Go Version: go version go1.10.2 linux/amd64
OS & Version: Arch Linux
Commit hash : 8e6f461

$ make
build/env.sh go run build/ci.go install ./cmd/gexp
ci.go:180: You have Go version go1.10.2
ci.go:181: go-expanse requires at least Go version 1.7 and cannot
ci.go:182: be compiled with an earlier version. Please upgrade your Go installation.
exit status 1
make: *** [Makefile:15: gexp] Error 1

Regards
Petr

wrong error message:

System information

Gexp version: gexp version
OS & Version: Windows/Linux/OSX
Commit hash : (if develop)

Expected behaviour

Actual behaviour

Steps to reproduce the behaviour

wrong error message:
\rpc\server.go:441
requests[i] = &serverRequest{id: r.id, err: &methodNotFoundError{r.method, r.method}}
must be
requests[i] = &serverRequest{id: r.id, err: &methodNotFoundError{r.service, r.method}}

Backtrace

[backtrace]

The partner instant exchange SimpleSwap.io

Hi,

I am Nicolas, the manager at SimpleSwap.io, an instant cryptocurrency exchange.

We present a simple and easy-to-use platform that works without registration and limits and allows users to make swaps in just two clicks.

We successfully support EXP on our service for a long time and we have been exchanging EXP for more than 200 coins to our customers. I tried to find contact with your team but without results.

I'm sorry that I invaded here, but maybe you can tell me where I can turn. I would like to make contact so we can have an interaction.

The darwin downloads for gexp 1.7.2 do not have an executable file in them.

System information

Gexp version: 1.7.2
OS & Version: OSX El Capitan
Commit hash : (if develop)

Expected behaviour

Should have executable file for gexp in the darwin downloads.

Actual behaviour

It's not there

Steps to reproduce the behaviour

Backtrace

[backtrace]

Advice needed

What is the current recommended version to use now?

I see that it's hard to understand from the branches

Byzantium?

Do we need to upgrade to a new client at the same time as the ETH Byzantium fork? I don't know how closely the Expanse network follows ETH anymore. The downloads page seems to be down:

https://gexp.expanse.tech/downloads/

Full syncmode error

There is problem with full sync mode. Fast works, but I am worried about blockchain consintency when full sync makes problems.

System information

Gexp
Version: 1.7.2-stable
Git Commit: 8e6f4610c4330aa72b5f98b131c944be257f3d0d
Architecture: amd64
Protocol Versions: [63 62]
Network Id: 1
Go Version: go1.10.2
Operating System: linux

Expected behaviour

Sync complete

Actual behaviour

Sync stops at block 200155

> eth.blockNumber
200154

Steps to reproduce the behaviour

run gexp with --syncmode full

Backtrace

WARN [05-23|13:20:47] Synchronisation failed, dropping peer    peer=d33a8d4c2c38a089 err="retrieved hash chain is invalid"
ERROR[05-23|13:20:55] 
########## BAD BLOCK #########
Chain config: {ChainID: 2 Homestead: 200000 DAO: <nil> DAOSupport: true EIP150: 200000 EIP155: 600000 EIP158: 600000 Byzantium: 800000 Engine: ethash}

Number: 200155
Hash: 0x3e83f2d695bccc6de2833b44993be8b8230b2a59d9b6f0c39dc19121ac5ac9a3
        receipt{med=a1b551d438c721d97dd3ef2e7590daf2c4de176efbd629c92e9a3b8b49266258 cgas=21000 bloom=00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 logs=[]}
        receipt{med=49c0842deb6b8564926edc3297ff50cb133dd0187c2680f609e87564e7674579 cgas=42000 bloom=00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 logs=[]}
        receipt{med=de032321bb8efdd9d12515277e13c9fbea9eae41f951c68305ac59171d54e8d0 cgas=63000 bloom=00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 logs=[]}
        receipt{med=404430ca728dd0a996db8732387bdbcedc9126d87bdacb08ab6b9d233eb1cee1 cgas=84000 bloom=00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 logs=[]}
        receipt{med=b6ee6ff9c34d8299f915b1517bd9cbd8eb9a0d35d1fe57d0db8b2abcdbe00043 cgas=105000 bloom=00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 logs=[]}
        receipt{med=de46122a37caf324ee8fa2c0e25423e3d1c38e96727daf8e87d1f9e042f87c93 cgas=126000 bloom=00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 logs=[]}
        receipt{med=b6a0c7b919e50ff0836ae638141087710afd63c71916cce9b8e78016ed1382a1 cgas=177168 bloom=02000000000000000000000000000000000000000000000000000000000000000000000400000000000000000000000000000000000000000000000000000000000000000000020000000008000000000000000000000000000000000000000000000000000000000000000000000200000000000000000000000010000000000000000000000000000000000000000000200000000000000000000000000010000000000000000000000000000000000000004000000000000000020000000000000002000000000000000000000000000000000000000000000000000000000000000000000000000000000000800000000000000000000000000000000000 logs=[log: c2be9f4c1657c63c856be47f3972ccb0cb0df125 [ddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef 0000000000000000000000003a6379cc9e216c062fd0e63d267d5fd62a75f061 000000000000000000000000663b8db322bb9b3fef0299a60004acf60078803d] 0000000000000000000000000000000000000000000000000000000005f5e100 7a32043d96dffd5fd473c1b5f24cee44beec3ffae62be38153260cd97670fe38 6 3e83f2d695bccc6de2833b44993be8b8230b2a59d9b6f0c39dc19121ac5ac9a3 0]}

Error: invalid gas used (remote: 176718 local: 177168)
##############################

Merge upstream changes to 1.6.5

Ethereum derivation path is used instead of Expanse, when launch Mist wallet with connected Trezor

When I launch Mist Wallet with connected Trezor wallet, it loads the first address from Trezor, but with Ethereum derivation path m/44'/60'/0'/0.
It must be m/44'/40'/0'/0 for Expanse.
If I'm right, here is where the fix must be done https://github.com/expanse-org/go-expanse/blob/v1.9.x/accounts/hd.go

System information

Gexp version: v1.9.10-stable
OS & Version: Windows 10
Commit hash : d57c0cd

Expected behaviour

The first Expanse address from derivation path m/44'/40'/0'/0 is loaded

Actual behaviour

The first Ethereum address from derivation path m/44'/60'/0'/0 is loaded

Steps to reproduce the behavior

1. Connect and unlock Trezor Model T wallet.
2. Launch Mist Wallet.
3. See the log file %AppData%\Expanse Wallet\node.log

node.log

nonce in genesis block

Why are you saying that setting nonce to a random value will prevent other nodes connecting to your private net? According to the docs, nonce is 64bit hash that proves that sufficient amount of computation has been done to comply with proof of work algorithm. Genesis block does not have prof of work because it is the first block. Logic suggest this statement is incorrect, because, to read the genesis block, anyone would need to connect to your node first. So, why are you saying that changing nonce will prevent other nodes to connect?

1.6.6 isnt mining!?

System information

Gexp version: 1.6.6
OS & Version: Ubuntu 16.04 LTS

Expected behaviour

Claymore Output ... ETH: job is the same

Actual behaviour

Claymore Output ... Received error: {"jsonrpc":"2.0","id":0,"error":{"code":-32601,"message":"The method eth_getWork does not exist/is not available"}}

Steps to reproduce the behaviour

just start gexp in rpc mode and point a miner to it.

Output: "Starting mining operation (CPU=0 TOT=2)"
is also missing after you start gexp 1.6.6

1.6.1 is working