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

[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.

[1714673186]

1714673186

[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

[ExEric3]

...
*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?

Problem can be we are running stats page on old fork. I need order another server machine for new stats and try it there without classical route - eth-net-api

[ExEric3]

martymcfly2015 you changed network port for SOIL? At least in help I see different port

--port value          Network listening port (default: 30403)

It shouldnt be 39420?

[ExEric3]

...
*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?

Problem can be we are running stats page on old fork. I need order another server machine for new stats and try it there without classical route - eth-net-api

Gsoil crashing on ethstats code:

WARN [05-13|07:34:00] Invalid stats history request            msg=false
panic: runtime error: slice bounds out of range

[martymcfly2015]

martymcfly2015 you changed network port for SOIL? At least in help I see different port

--port value          Network listening port (default: 30403)

It shouldnt be 39420?

Yes, I've changed the ports because it's more convenient now.
geth -> gsoil
8545 -> 39421
8546 -> 39422
30301 -> 30401
30303 -> 30403

[ExEric3]

Looks like after update node to v1.6.1 stopped works pool paments:

2017/05/14 11:44:52 Locked payment for 0x94cac9107ebf7b3ce4e3680b4ded42047318455f, 9384406500 Shannon
2017/05/14 11:44:52 Failed to send payment to 0x94cac9107ebf7b3ce4e3680b4ded42047318455f, 9384406500 Shannon: invalid argument 0: hex number has leading zero digits after 0x. Check outgoing tx for 0x94cac9107ebf7b3ce4e3680b4ded42047318455f in block explorer and docs/PAYOUTS.md
2017/05/14 11:44:52 Paid total 0 Shannon to 0 of 1 payees

[ExEric3]

Looks like after update node to v1.6.1 stopped works pool payments:

2017/05/14 11:44:52 Locked payment for 0x94cac9107ebf7b3ce4e3680b4ded42047318455f, 9384406500 Shannon
2017/05/14 11:44:52 Failed to send payment to 0x94cac9107ebf7b3ce4e3680b4ded42047318455f, 9384406500 Shannon: invalid argument 0: hex number has leading zero digits after 0x. Check outgoing tx for 0x94cac9107ebf7b3ce4e3680b4ded42047318455f in block explorer and docs/PAYOUTS.md
2017/05/14 11:44:52 Paid total 0 Shannon to 0 of 1 payees

Fixed on pool side.

2017/05/14 17:39:29 Starting payouts
2017/05/14 17:39:29 Set payouts interval to 2h0m0s
2017/05/14 17:39:29 Locked payment for 0xc1ba9076672bde89a442093be0dcc836040b322d, 433063125000 Shannon
2017/05/14 17:39:29 Paid 433063125000 Shannon to 0xc1ba9076672bde89a442093be0dcc836040b322d, TxHash: 0x0b16396cd8f27ea1a0d1b16ca6ff61a5148dfad689206a88297a43faf6d95f2c
2017/05/14 17:39:29 Waiting for tx confirmation: 0x0b16396cd8f27ea1a0d1b16ca6ff61a5148dfad689206a88297a43faf6d95f2c
2017/05/14 17:41:14 Payout tx for 0xc1ba9076672bde89a442093be0dcc836040b322d confirmed: 0x0b16396cd8f27ea1a0d1b16ca6ff61a5148dfad689206a88297a43faf6d95f2c

So Miners-Zone is on latest code base v1.6.1 with fully resynced blockchain. So happy mining on http://soil.miners-zone.net

[altsheets]

ABEESOIL is running on the new gsoil

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.

Synced, and seems to work just fine:



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

Links
* Useful manual: Cleaning old GO version, and installing new go1.8.0 and go-soil1.6.1 = msg18990348
* more about ABEE(soil) block explorer extension, screenshots of all its functions = topic 1181547

Todo:
* you have raised the block rewards again? Then I need to add that change to my mined&supply calculations.

Please donate
   [SOIL] 0x8da4fc05ca343e6a41646194e91931d9f413a40c
   BTC 1M4EaZVprZEmtrS3G78fMFy8yGVgdUJMXv  

and sell me some SOIL please, thanks.

 

[wariner]

Hi,

I have one problem with new wallet 1.6.1... wallet don't sending payment to network...to confirm my tx I need to found block with the same wallet..solutions?

[Dunkelheit667]

Hi,

I have one problem with new wallet 1.6.1... wallet don't sending payment to network...to confirm my tx I need to found block with the same wallet..solutions?

You've found a new workaround, mining a block will send the transaction as well, great! For a different approach you might check this.

[wariner]

You've found a new workaround, mining a block will send the transaction as well, great! For a different approach you might check this.

I see...but deleted soil folder and download again the blockchain ...dont solve for me

With gsoil_MMF_v1.4.4 all works fine

[Dunkelheit667]

You've found a new workaround, mining a block will send the transaction as well, great! For a different approach you might check this.

I see...but deleted soil folder and download again the blockchain ...dont solve for me

With gsoil_MMF_v1.4.4 all works fine

Sound's frustrating. Just to be sure, have you deleted the SOILsafe folder (as martymcfly2015 recommended) as well? This did the magic in my case.

[BTCbtcLOVE]

Is there anything about returning SOIL on bittrex?
Or how to save soil from bittrex?
Plz help me, a have a lot soil on bittrex...
Thanks!

[altsheets]

Is there anything about returning SOIL on bittrex?
Or how to save soil from bittrex?
Plz help me, a have a lot soil on bittrex...
Thanks!

Yes, please sell them to us, see here: https://bitcointalk.org/index.php?topic=1213614.new#new

[yaffa01]

md5sum is 3d72e043adfa2d0afc3161299e935952?

Good point:

http://178.62.133.174/soil/SOIL-chaindata-20170203-block-1808086.zip.checksums.txt

Here we go with a Blockchain Bootstrap on mega.nz:

Code:

https://mega.nz/#!BY5lEBqb!2dJpuqLOIXQ7nc-vmP_SVrp9qmSTrkViz-jBv0RbGfQ

Feel free to share this link wherever needed.

thanks for telling this truth...to us now ...i am ready to work over it...

[abvhiael]

Is there anything about returning SOIL on bittrex?
Or how to save soil from bittrex?
Plz help me, a have a lot soil on bittrex...
Thanks!

we wont know anything from bittrex until they decide one way or another. you can send a message to julian on the bittrex slack to help move things along if youd like. their SOIL wallet is up to date, theyve applied the latest patches, so you should have no problem moving SOIL off of bittrex onto a fully synced SOIL client.

ive been squirrelling away some currency from another project im working on and will be adding to our DOT balance at cryptopia, hopefully i can put enough in to help cover what we need to get listed there. im very much in pro-favour of having us listed at cryptopia, the support there is phenomenal, not only from the devs and admins that are online, but the folks in the troll box are very helpful too.

the best bet, as always, is to send a small test amount from bittrex to your wallet to be sure its synced correctly, and then send the rest over.

[altsheets]

...
http://178.62.133.174:9001/#/chain/
...
Please donate
   [SOIL] 0x8da4fc05ca343e6a41646194e91931d9f413a40c
   BTC 1M4EaZVprZEmtrS3G78fMFy8yGVgdUJMXv  

and sell me some SOIL please, thanks.

 

[martymcfly2015]

I've got a couple of requests for having SOILsafe on macOS, so I borrowed a mac from a friend. A port of gsoil for mac is already available.
Here you go!
https://github.com/Soilcoin/SOILsafe/releases/download/0.8.10/SOILsafe-macosx-0-8-10.dmg

If you like my work... tip me  
[SOIL] 0x663682fd2d96064fdb2f152a56bab75d921065c0
BTC 17vKnSGtuegVi8LsSpQbJwDsNFdgrkwuwf