🌱[ANN] SOIL | Environmental | Agriculture | Smart Contracts | Sustainable

[martymcfly2015]

Soil Windows Mining Guide

Download the mining package and extract it
https://github.com/Soilcoin/Soilcoin-Windows-mining/releases/download/0.1/soil-mining-windows.zip
Download ethminer and extract the files to soil-mining-windows/ethminer
https://github.com/Genoil/cpp-ethereum/raw/master/releases/ethminer-0.9.41-genoil-1.1.7.zip

If you don't have already a soil address - generate one
gsoil/gsoil-new-account.bat

Solo mining
soil-mining-windows/gsoil-solomine.bat
+
For nvidia gpus
ethminer/solo-mining-cuda.bat
For amd gpus
ethminer/solo-mining-ocl.bat

Pool mining
ethminer/miners-zone-cuda.bat
ethminer/miners-zone-ocl.bat
ethminer/pool.sexy-cuda.bat
ethminer/pool.sexy-ocl.bat

Choose cuda for nvidia gpus and ocl for amd gpus and the pool of your choice.
Open the bat file with an editor and enter your address and rig name.
http://pool:port/0x663682fd2d96064fdb2f152a56bab75d921065c0/marty

Happy mining!

[altsheets]

... documenting ...

wow, great stuff.

Really looking forward to reading all this.

[altsheets]

altsheets will you update your explorer node? Since stats and pool is linked on yours?

I can try today. IF the codebase is 100% reliable. Which one do I choose?

Was busy before. Sorry again.


Anyone's gonna SELL me some coins?
--> msg18798676
--> msg18695602

--> WTB/WTS thread

?

Thx.

[frostminer]

altsheets will you update your explorer node? Since stats and pool is linked on yours?

I can try today. IF the codebase is 100% reliable. Which one do I choose?

Was busy before. Sorry again.


Anyone's gonna SELL me some coins?
--> msg18798676
--> msg18695602

--> WTB/WTS thread

?

Thx.

I wanna buy more too... but ill wait until we have an exchange to trade on.
Should we wait pushing exchange until you are done testing all the code?

Great job btw, guys.

[altsheets]

altsheets will you update your explorer node? Since stats and pool is linked on yours?

I can try today. IF the codebase is 100% reliable. Which one do I choose?

[altsheets]

altsheets will you update your explorer node? Since stats and pool is linked on yours?

I can try today. IF the codebase is 100% reliable. Which one do I choose?

I have started:

Code:

cd ~/go
wget https://storage.googleapis.com/golang/go1.8.1.linux-amd64.tar.gz
tar -C /usr/local -xzf go1.8.1.linux-amd64.tar.gz
export PATH=$PATH:/usr/local/go/bin
go version

cd ~/soil/
git clone https://github.com/Soilcoin/go-soil
cd go-soil
make gsoil

but soon ran into problems:

Code:

make gsoil
build/env.sh go run build/ci.go install ./cmd/gsoil
# runtime
/usr/local/go/src/runtime/signal_unix.go:27: _SIG_DFL redeclared in this block
        previous declaration at /usr/local/go/src/runtime/signal1_unix.go:15
/usr/local/go/src/runtime/signal_unix.go:28: _SIG_IGN redeclared in this block
        previous declaration at /usr/local/go/src/runtime/signal1_unix.go:16
/usr/local/go/src/runtime/signal_unix.go:37: fwdSig redeclared in this block
        previous declaration at /usr/local/go/src/runtime/signal1_unix.go:25
/usr/local/go/src/runtime/signal_unix.go:42: disableSigChan redeclared in this block
        previous declaration at /usr/local/go/src/runtime/signal1_unix.go:35
/usr/local/go/src/runtime/signal_unix.go:43: enableSigChan redeclared in this block
        previous declaration at /usr/local/go/src/runtime/signal1_unix.go:36
/usr/local/go/src/runtime/signal_unix.go:44: maskUpdatedChan redeclared in this block
        previous declaration at /usr/local/go/src/runtime/signal1_unix.go:37
/usr/local/go/src/runtime/signal_unix.go:56: signalsOK redeclared in this block
        previous declaration at /usr/local/go/src/runtime/signal1_unix.go:49
/usr/local/go/src/runtime/signal_unix.go:62: initsig redeclared in this block
        previous declaration at /usr/local/go/src/runtime/signal1_unix.go:55
/usr/local/go/src/runtime/signal_unix.go:97: sigInstallGoHandler redeclared in this block
        previous declaration at /usr/local/go/src/runtime/signal1_unix.go:90
/usr/local/go/src/runtime/signal_unix.go:122: sigenable redeclared in this block
        previous declaration at /usr/local/go/src/runtime/signal1_unix.go:115
/usr/local/go/src/runtime/signal_unix.go:122: too many errors
Makefile:15: recipe for target 'gsoil' failed
make: *** [gsoil] Error 2

Please advise, thanks.

EDIT: Also tried with go1.7.5 = identical problem

The machine is updated

Code:

apt update && apt upgrade
uname -a
Linux ....... 3.16.0-4-amd64 #1 SMP Debian 3.16.39-1 (2016-12-30) x86_64 GNU/Linux

P.S.: The old blockexplorer is offline for now. Please help me update to the newest node code, then it should probably continue to work. Thanks

[abvhiael]

...hopefully this is the last of the update documentation for a little bit. (laughs) so many new implementations, so much more we're going to have to test going forward... this post should cover the last of the upgrades to the SOIL, as pushed in by the 1.6.0 (Puppeth Master) code updates to Ethereum, and which brings SOILcoin to simple parity with their codebase....

*puppeth* : a new CLI interface which assists building new Ethereum-level blockchain networks down to the genesis, bootnodes, signers, ethstats, faucet, dashboard, etc , eliminating the need configure all these services one by one. Puppeth uses ssh to dial into remote servers, and builds its network components out of docker containers using docker-compose. The user is guided through the process via a command line wizard which handles the background configurations. This will help build test-nets for dApp development or private blockchains for DAOs, and should be an integral part of the system building a cross-chain linked blockchain network in the future.

Alongside Puppeth, a consensus engine interface will be built into the network level protocols of go-soil. It will permit the usage of alternatives to POW block verification schemes for smaller networks, where a different security model may be required. With this release, two consensus models are supported in the production of private chains: the currently used POW model, ethash; and a new "Proof of Authority" model called clique.

Clique, the POA protocol works by allowing authorized signatories to create new blocks at their own discretion, with the ability to control minting frequency, minting distribution load between the full list of signatories, and to dynamically adjust the list of trusted signers as needed. This protocol would require for a predetermined number of signatories have active nodes at any one time, to ensure minting diversity.

As far as I understand it, from researching the consensus engine idea, these sorts of entities could be deployed as sub-chains and mineable tokens on the EVM, and as Casper (the Ethereum Core's Proof of Stake model) comes closer to implementation, its methods are likely to be included within this interface as well. Ethereum has released a testnet (Rinkeby) that is running the PoA consensus engine, https://www.rinkeby.io/ which features netstats, a github linked faucet, block explorer, etc. if you want to poke around an iteration of what Puppeth can build out from SOILcoin as well.

*smaller changes

The gsoil console command evm can be used to disassemble contracts, as well as to create contracts written in teh EVM assembly language.

The swarm implementation is expanded to also permit users to upload and download entire directories via tarball streams in the HTTP interface, as well as mount an entire folder structure into their local filesystem via FUSE.

RPC compiler calls (eth_compileSolidity, eth_compileSerpent, and eth_compileLLL) are deprecated, and dApp developers are urged to use "proper development tools" instead. (truffle, embark, dapple) [i honestly had nothing but grief using eth_compile* with any dApp development work ive done, and while theres a learning curve to the CLI development tools mentioned, user-friendliness is improving exponentially.

thats pretty much it for the updates to potentiality with the SOILcoin blockchain. there are a ton of adjunct dApps and contracts that have to be deployed in support of these changes, and over the next few weeks ill be deploying and documenting these as well. a great deal of testing and screwing about with Swarm and Whisper is going to be needed to be done, in order to present the most friendly and understandable guides to using these technologies.

The first suite that i have to look at implementing is our own SOILcoin Name Service, which will be an integral part of the swarm funtionality on the SOILnet. The SNS will eliminate the need to copy long hexadecimal addresses (0xa1b2C3d4Ef67aA...), allowing users to claim .soil addresses, so that a transaction can be sent to somebody.soil instead of '0xa1b2C3d4Ef67aA...', or interact with 'mycontract.soil', or visit a Swarm-hosted site at 'swarmsite.soil'. will, naturally, document the heck out of it to encourage usability.

[altsheets]

...

but soon ran into problems:

Code:

make gsoil
build/env.sh go run build/ci.go install ./cmd/gsoil
# runtime
/usr/local/go/src/runtime/signal_unix.go:27: _SIG_DFL redeclared in this block
        previous declaration at /usr/local/go/src/runtime/signal1_unix.go:15
/usr/local/go/src/runtime/signal_unix.go:28: _SIG_IGN redeclared in this block
        previous declaration at /usr/local/go/src/runtime/signal1_unix.go:16
...
/usr/local/go/src/runtime/signal_unix.go:122: sigenable redeclared in this block
        previous declaration at /usr/local/go/src/runtime/signal1_unix.go:115
/usr/local/go/src/runtime/signal_unix.go:122: too many errors
Makefile:15: recipe for target 'gsoil' failed
make: *** [gsoil] Error 2

Please advise, thanks.

...

[martymcfly2015]

...

but soon ran into problems:

Code:

make gsoil
build/env.sh go run build/ci.go install ./cmd/gsoil
# runtime
/usr/local/go/src/runtime/signal_unix.go:27: _SIG_DFL redeclared in this block
        previous declaration at /usr/local/go/src/runtime/signal1_unix.go:15
/usr/local/go/src/runtime/signal_unix.go:28: _SIG_IGN redeclared in this block
        previous declaration at /usr/local/go/src/runtime/signal1_unix.go:16
...
/usr/local/go/src/runtime/signal_unix.go:122: sigenable redeclared in this block
        previous declaration at /usr/local/go/src/runtime/signal1_unix.go:115
/usr/local/go/src/runtime/signal_unix.go:122: too many errors
Makefile:15: recipe for target 'gsoil' failed
make: *** [gsoil] Error 2

Please advise, thanks.

...

I think the problem is your go installation. Try to reinstall go. Delete your current go installation and all paths settings to your current go. Remove also any previous go installations via package manager.

Code:

sudo curl -O https://storage.googleapis.com/golang/go1.8.linux-amd64.tar.gz

Code:

sudo tar -xvf go1.8.linux-amd64.tar.gz

Code:

sudo mv go /usr/local

Code:

sudo nano /root/.profile

or

Code:

nano ~/.bashrc

add this to the file

Code:

export PATH=$PATH:/usr/local/go/bin

Code:

sudo source /root/.profile

or

Code:

source ~/.bashrc

That worked for me. I know, this is in principle what you did already - but maybe worth to try it...

[altsheets]

Thanks a lot MMF

... but soon ran into problems: ... Please advise, thanks.

I think the problem is your go installation. Try to reinstall go. Delete your current go installation and all paths settings to your current go. Remove also any previous go installations via package manager....

Done:

Cleaning old GO version, and installing new go1.8.0 and go-soil1.6.1

Code:

apt update
apt remove golang
   Package 'golang' is not installed, so not removed
   
echo $PATH

I cleaned:

Code:

rm -rf /usr/local/go

Search ... there were no other mentionings of 'golang' left. (To search for 'go' is futile, what a stupid naming idea for a language.)

Code:

updatedb
locate golang | grep -v go-ethereum | grep -v go-soil

following your suggestion for go1.8.0

Code:

cd ~/go/
sudo curl -O https://storage.googleapis.com/golang/go1.8.linux-amd64.tar.gz
sudo tar -xvf go1.8.linux-amd64.tar.gz
sudo mv go /usr/local
nano ~/.bashrc
    export PATH=$PATH:/usr/local/go/bin
source ~/.bashrc
go version
    go version go1.8 linux/amd64

now trying again:

Code:

cd ~/soil/
rm go-soil -rf
git clone https://github.com/Soilcoin/go-soil
cd go-soil
make gsoil

   
no error message, great.

Code:

build/bin/gsoil version
Gsoil
Version: 1.6.1-MMF
Git Commit: 6ccff9a9a330755bdb7dcbb22eba58353cbb1d2d
Architecture: amd64
Protocol Versions: [63 62]
Network Id: 42
Go Version: go1.8
Operating System: linux

Shortcut into path, and ... we'll see how this syncs now.

Code:

ln -sf ~/soil/go-soil/build/bin/gsoil ~/go/bin/
gsoil

Thanks!

[altsheets]

Syncing on top of old chain ... works:

Code:

gsoil
INFO [05-12|15:42:48] Starting peer-to-peer node               instance=Gsoil/v1.6.1-MMF-6ccff9a9/linux-amd64/go1.8
INFO [05-12|15:42:48] Allocated cache and file handles         database=~/.soil/chaindata cache=128 handles=1024
WARN [05-12|15:42:49] Upgrading chain database to use sequential keys
WARN [05-12|15:42:49] Found genesis block without chain config
INFO [05-12|15:42:49] Initialised chain configuration          config="{ChainID: 1337 Homestead: 0 EIP150: 0 EIP155:                                                                    0 EIP158: 0 Engine: ethash}"
INFO [05-12|15:42:49] Disk storage enabled for ethash caches   dir=~/.soil/gsoil/ethash count=3
INFO [05-12|15:42:49] Disk storage enabled for ethash DAGs     dir=~/.ethash            count=2
INFO [05-12|15:42:49] Initialising Soil protocol               versions="[63 62]" network=42
INFO [05-12|15:42:49] Loaded most recent local header          number=2000267 hash=8b4f6b…2881fd td=32538335992977008
INFO [05-12|15:42:49] Loaded most recent local full block      number=2000267 hash=8b4f6b…2881fd td=32538335992977008
INFO [05-12|15:42:49] Loaded most recent local fast block      number=2000267 hash=8b4f6b…2881fd td=32538335992977008
WARN [05-12|15:42:49] Blockchain not empty, fast sync disabled
INFO [05-12|15:42:49] Starting P2P networking
INFO [05-12|15:42:51] RLPx listener up                         self=enode://46fce6fdc328596df97c8c2e4d1744b9bf5bfd540                                                                   ff8cf95e4880d797bd92e2cb52a81f38a9a49e51079f875c1adbdc2d4d6f503253e2d7188a494d421bd968b@[::]:30403
INFO [05-12|15:42:51] IPC endpoint opened: ~/.soil/gsoil.ipc

Code:

INFO [05-12|15:43:21] Block synchronisation started
INFO [05-12|15:43:25] Generating ethash verification cache     epoch=66 percentage=29 elapsed=3.079s
INFO [05-12|15:43:28] Generating ethash verification cache     epoch=66 percentage=79 elapsed=6.119s
INFO [05-12|15:43:29] Generated ethash verification cache      epoch=66 elapsed=7.729s
INFO [05-12|15:43:30] Imported new chain segment               blocks=5 txs=0 mgas=0.000 elapsed=7.933s mgasps=0.000 number=2000005 hash=39d755…b0b10d
INFO [05-12|15:43:32] Generating ethash verification cache     epoch=67 percentage=19 elapsed=3.125s
INFO [05-12|15:43:36] Generating ethash verification cache     epoch=67 percentage=29 elapsed=6.199s
INFO [05-12|15:43:38] Imported new chain segment               blocks=179 txs=5 mgas=0.105 elapsed=8.100s mgasps=0.013 number=2000184 hash=e07fc0…ae2fa4
INFO [05-12|15:43:39] Generating ethash verification cache     epoch=67 percentage=41 elapsed=9.274s
INFO [05-12|15:43:42] Generating ethash verification cache     epoch=67 percentage=49 elapsed=12.640s

The interesting bit happens here:
WARN [05-12|15:43:42] Chain split detected                     number=2000000 hash=7b1028…4dbb4f drop=267 dropfrom=8b4f6b…2881fd add=244 addfrom=52e99f…68f5cd

Code:

WARN [05-12|15:43:42] Chain split detected                     number=2000000 hash=7b1028…4dbb4f drop=267 dropfrom=8b4f6b…2881fd add=244 addfrom=52e99f…68f5cd
INFO [05-12|15:43:45] Generating ethash verification cache     epoch=67 percentage=54 elapsed=15.725s
INFO [05-12|15:43:46] Imported new chain segment               blocks=130 txs=0 mgas=0.000 elapsed=8.010s  mgasps=0.000 number=2000314 hash=685315…68a11a
INFO [05-12|15:43:48] Generating ethash verification cache     epoch=67 percentage=66 elapsed=18.894s
INFO [05-12|15:43:51] Generating ethash verification cache     epoch=67 percentage=77 elapsed=21.919s
INFO [05-12|15:43:54] Imported new chain segment               blocks=200 txs=0 mgas=0.000 elapsed=8.172s  mgasps=0.000 number=2000514 hash=b76104…a2fa2e
INFO [05-12|15:43:54] Generating ethash verification cache     epoch=67 percentage=90 elapsed=24.985s
INFO [05-12|15:43:57] Generated ethash verification cache      epoch=67 elapsed=27.472s
INFO [05-12|15:44:02] Imported new chain segment               blocks=248 txs=0 mgas=0.000 elapsed=8.036s  mgasps=0.000 number=2000762 hash=6870f3…c0e3dd
INFO [05-12|15:44:10] Imported new chain segment               blocks=198 txs=5 mgas=0.105 elapsed=8.029s  mgasps=0.013 number=2000960 hash=875652…775d02
INFO [05-12|15:44:18] Imported new chain segment               blocks=180 txs=0 mgas=0.000 elapsed=8.016s  mgasps=0.000 number=2001140 hash=5b4646…254732
INFO [05-12|15:44:26] Imported new chain segment               blocks=194 txs=0 mgas=0.000 elapsed=8.029s  mgasps=0.000 number=2001334 hash=ffe879…be08d6
INFO [05-12|15:44:34] Imported new chain segment               blocks=226 txs=7 mgas=0.147 elapsed=8.081s  mgasps=0.018 number=2001560 hash=0c4cf1…49cebd
INFO [05-12|15:44:42] Imported new chain segment               blocks=219 txs=0 mgas=0.000 elapsed=8.064s  mgasps=0.000 number=2001779 hash=7448ae…de21e9
INFO [05-12|15:44:50] Imported new chain segment               blocks=272 txs=6 mgas=0.126 elapsed=8.024s  mgasps=0.016 number=2002051 hash=789e1e…7c3dc1
...

So ... looks like updating AFTER a new version has already passed the fork-block ... is unproblematic.

[altsheets]

Done. Now it only needs patience.

You can see it syncing, by reloading:

http://178.62.133.174:9001/#/chain/

Thanks for your help!

[martymcfly2015]

Syncing on top of old chain ... works:

Code:

gsoil
INFO [05-12|15:42:48] Starting peer-to-peer node               instance=Gsoil/v1.6.1-MMF-6ccff9a9/linux-amd64/go1.8
INFO [05-12|15:42:48] Allocated cache and file handles         database=~/.soil/chaindata cache=128 handles=1024
WARN [05-12|15:42:49] Upgrading chain database to use sequential keys
WARN [05-12|15:42:49] Found genesis block without chain config
INFO [05-12|15:42:49] Initialised chain configuration          config="{ChainID: 1337 Homestead: 0 EIP150: 0 EIP155:                                                                    0 EIP158: 0 Engine: ethash}"
INFO [05-12|15:42:49] Disk storage enabled for ethash caches   dir=~/.soil/gsoil/ethash count=3
INFO [05-12|15:42:49] Disk storage enabled for ethash DAGs     dir=~/.ethash            count=2
INFO [05-12|15:42:49] Initialising Soil protocol               versions="[63 62]" network=42
INFO [05-12|15:42:49] Loaded most recent local header          number=2000267 hash=8b4f6b…2881fd td=32538335992977008
INFO [05-12|15:42:49] Loaded most recent local full block      number=2000267 hash=8b4f6b…2881fd td=32538335992977008
INFO [05-12|15:42:49] Loaded most recent local fast block      number=2000267 hash=8b4f6b…2881fd td=32538335992977008
WARN [05-12|15:42:49] Blockchain not empty, fast sync disabled
INFO [05-12|15:42:49] Starting P2P networking
INFO [05-12|15:42:51] RLPx listener up                         self=enode://46fce6fdc328596df97c8c2e4d1744b9bf5bfd540                                                                   ff8cf95e4880d797bd92e2cb52a81f38a9a49e51079f875c1adbdc2d4d6f503253e2d7188a494d421bd968b@[::]:30403
INFO [05-12|15:42:51] IPC endpoint opened: ~/.soil/gsoil.ipc

...

So ... looks like updating AFTER a new version has already passed the fork-block ... is unproblematic.

config="{ChainID: 1337 Homestead: 0 EIP150: 0 EIP155: 0 EIP158: 0 Engine: ethash}"

Please make a full resync to load the new config. By default fast sync is enabled - so it will take you only a couple of minutes.

Code:

config="{ChainID: 42 Homestead: 2000000 EIP150: 2463000 EIP155: 2675000 EIP158: 2675000 Engine: ethash}"

[altsheets]

...
*gsoil will include a built-in netstats reporter with the ability to register a user node on the service simply thru the console. The ultimate goal would be to have the SOILcoin network intelligence tool return its report via a swarm-hosted page on the SOILnet, presently we will be able to take advantage of the service offered by miners-zone in correlation to their SOILcoin mining pool accessible at http://soil.miners-zone.net:9090/.  

Usage:

Code:

--ethstats "<nodename>:<secret>@soil.miners-zone.net:9090"

...

Have tried

Code:

 gsoil --ethstats "ABEESOIL:<same-password-as-before>@soil.miners-zone.net:9090"

but I get a

Code:

WARN [05-12|16:14:21] Stats login failed                       err=unauthorized

EDIT: I have now tried via the classical route (with eth-net-intelligence-api ...  pm2 start app.json), and it works. You see my node here: http://soil.miners-zone.net:9090/  ... using that same password. So ... where's my misunderstanding?

[altsheets]

Syncing on top of old chain ... works:
...
So ... looks like updating AFTER a new version has already passed the fork-block ... is unproblematic.

config="{ChainID: 1337 Homestead: 0 EIP150: 0 EIP155: 0 EIP158: 0 Engine: ethash}"

Please make a full resync to load the new config. By default fast sync is enabled - so it will take you only a couple of minutes.

Code:

config="{ChainID: 42 Homestead: 2000000 EIP150: 2463000 EIP155: 2675000 EIP158: 2675000 Engine: ethash}"

Why is that necessary?

The first 2000000 blocks were correct in any client version, were they not?

Only at 20000001 your new code started to do stuff differently - right?

[martymcfly2015]

Syncing on top of old chain ... works:
...
So ... looks like updating AFTER a new version has already passed the fork-block ... is unproblematic.

config="{ChainID: 1337 Homestead: 0 EIP150: 0 EIP155: 0 EIP158: 0 Engine: ethash}"

Please make a full resync to load the new config. By default fast sync is enabled - so it will take you only a couple of minutes.

Code:

config="{ChainID: 42 Homestead: 2000000 EIP150: 2463000 EIP155: 2675000 EIP158: 2675000 Engine: ethash}"

Why is that necessary?

The first 2000000 blocks were correct in any client version, were they not?

Only at 20000001 your new code started to do stuff differently - right?

Because of the ChainID. If you don't plan to do any transactions from this client - then it should work without a full recync, but you might stuck again on the upcoming forks (EIP150: 2463000 EIP155: 2675000 EIP158:2675000).

[altsheets]

Syncing on top of old chain ... works:
...
So ... looks like updating AFTER a new version has already passed the fork-block ... is unproblematic.

config="{ChainID: 1337 Homestead: 0 EIP150: 0 EIP155: 0 EIP158: 0 Engine: ethash}"

Please make a full resync to load the new config. By default fast sync is enabled - so it will take you only a couple of minutes.

Code:

config="{ChainID: 42 Homestead: 2000000 EIP150: 2463000 EIP155: 2675000 EIP158: 2675000 Engine: ethash}"

Why is that necessary?

The first 2000000 blocks were correct in any client version, were they not?

Only at 20000001 your new code started to do stuff differently - right?

Because of the ChainID. If you don't plan to do any transactions from this client - then it should work without a full recync, but you might stuck again on the upcoming forks (EIP150: 2463000 EIP155: 2675000 EIP158:2675000).

I see.

I don't remember this (having to resync from block 0) from any other hardfork.

[altsheets]

Syncing on top of old chain ... works:
...
So ... looks like updating AFTER a new version has already passed the fork-block ... is unproblematic.

config="{ChainID: 1337 Homestead: 0 EIP150: 0 EIP155: 0 EIP158: 0 Engine: ethash}"

Please make a full resync to load the new config. By default fast sync is enabled - so it will take you only a couple of minutes.

Code:

config="{ChainID: 42 Homestead: 2000000 EIP150: 2463000 EIP155: 2675000 EIP158: 2675000 Engine: ethash}"

Why is that necessary?
The first 2000000 blocks were correct in any client version, were they not?
Only at 20000001 your new code started to do stuff differently - right?

Because of the ChainID. If you don't plan to do any transactions from this client - then it should work without a full recync, but you might stuck again on the upcoming forks (EIP150: 2463000 EIP155: 2675000 EIP158:2675000).

I see.
I don't remember this (having to resync from block 0) from any other hardfork.

Done:

Code:

pkill gsoil
rm ~/.soil/chaindata/*

cd ~/soil/gsoil-logs
mv nohup.out nohup.out_20170512b.txt

nohup ABEESOIL_gsoil &
    nohup: ignoring input and appending output to ‘nohup.out’

Code:

tail -f nohup.out

INFO [05-12|16:38:53] Starting peer-to-peer node               instance=Gsoil/v1.6.1-MMF-6ccff9a9/linux-amd64/go1.8
INFO [05-12|16:38:53] Allocated cache and file handles         database=~/.soil/chaindata cache=128 handles=1024
INFO [05-12|16:38:53] Writing default main-net genesis block
INFO [05-12|16:38:53] Initialised chain configuration          config="{ChainID: 42 Homestead: 2000000 EIP150: 2463000 EIP155: 2675000 EIP158: 2675000 Engine: ethash}"
INFO [05-12|16:38:53] Disk storage enabled for ethash caches   dir=~/.soil/gsoil/ethash count=3
INFO [05-12|16:38:53] Disk storage enabled for ethash DAGs     dir=~/.ethash            count=2
WARN [05-12|16:38:53] Upgrading db log bloom bins
INFO [05-12|16:38:53] Bloom-bin upgrade completed              elapsed=86.168µs
INFO [05-12|16:38:53] Initialising Soil protocol               versions="[63 62]" network=42
INFO [05-12|16:38:53] Loaded most recent local header          number=0 hash=40cb5b…63a001 td=1073741824
INFO [05-12|16:38:53] Loaded most recent local full block      number=0 hash=40cb5b…63a001 td=1073741824
INFO [05-12|16:38:53] Loaded most recent local fast block      number=0 hash=40cb5b…63a001 td=1073741824
INFO [05-12|16:38:53] Starting P2P networking
INFO [05-12|16:38:55] HTTP endpoint opened: http://178.62.133.174:9123
INFO [05-12|16:38:55] RLPx listener up                         self=enode://46fce6fdc328596df97c8c2e4d1744b9bf5bfd540ff8cf95e4880d797bd92e2cb52a81f38a9a49e51079f875c1adbdc2d4d6f503253e2d7188a494d421bd968b@[::]:30403
INFO [05-12|16:38:55] IPC endpoint opened: ~/.soil/gsoil.ipc
INFO [05-12|16:39:25] Block synchronisation started
INFO [05-12|16:39:25] Imported new state entries               count=1 elapsed=1.156ms  processed=1 pending=17
INFO [05-12|16:39:25] Imported new state entries               count=16 elapsed=5.269ms  processed=17 pending=269
INFO [05-12|16:39:25] Imported new state entries               count=252 elapsed=15.279ms processed=269 pending=1372
INFO [05-12|16:39:26] Imported new state entries               count=2   elapsed=23.723ms processed=271 pending=1372
...
INFO [05-12|16:42:06] Imported new block receipts              count=2005 elapsed=1.192s    number=106496 hash=6fb8ab…76a557 ignored=0
...
INFO [05-12|16:48:41] Imported new block receipts              count=56   elapsed=111.272ms number=329784 hash=3dade7…160916 ignored=0
...
INFO [05-12|16:53:35] Imported new block receipts              count=1466 elapsed=1.613s    number=501180 hash=42e290…ddd27e ignored=0
...

So ... http://178.62.133.174:9001/#/chain/ should be available again ... in approx an hour or so.

Thanks.


So ... who is selling some SOIL to me, finally?

Thanks.

[ExEric3]

Because of the ChainID. If you don't plan to do any transactions from this client - then it should work without a full recync, but you might stuck again on the upcoming forks (EIP150: 2463000 EIP155: 2675000 EIP158:2675000).

So you wanna tell me I must full resync blockchain on pool side with latest release?

[martymcfly2015]

Avoiding the need for a full blockchain resync if you update gsoil1.4.4 to gsoil1.6.1

linux:

Code:

git clone https://github.com/Soilcoin/go-soil.git
cd go-soil
make
build/bin/gsoil init genesis.json

windows:
download
https://github.com/Soilcoin/go-soil/releases/download/v1.6.1/gsoil-windows-amd64-1.6.1_upgrade.zip
Extract it
run upgrade.bat