Ninjastic
Search content
Sort by
Showing 20 of 21 results by holgerkpedersen
Post
Topic
Board Announcements (Altcoins)
Re: Bug in the SuperCoin wallet
by
holgerkpedersen
on 02/02/2020, 08:30:24 UTC
Hi.

checkwallet found the error.

{
"mismatched spent coins" : 3,
"amount in question" : 1567.09944619
}

I tried the repairwallet, too, getting the same result.

Restarted the wallet. The error was corrected.

Thank you for your clarifications, Gerry.

Br, Holger
Post
Topic
Board Announcements (Altcoins)
Bug in the SuperCoin wallet
by
holgerkpedersen
on 30/01/2020, 19:40:02 UTC
Hi.

I have noticed a change in my wallet amount in the SuperCoin Wallet. Earlier this year there was about 9600 SUPER. Now it reports about 8100 SUPER. The SuperCoin Explorer reports the correct amount, so I think there is a bug in the Super Coin Wallet v4.0.1.0

Any ideas, what to do about this?

Btw, we need more nodes.

BR, Holger
Post
Topic
Board Announcements (Altcoins)
Re: 🌱[ANN] SOIL | Environmental | Agriculture | Smart Contracts | Sustainable
by
holgerkpedersen
on 28/08/2018, 18:28:11 UTC
Quote from: jdaz on July 06, 2018, 02:32:14 PM
Quote from: somanyroads on July 06, 2018, 06:19:39 AM

Are these peers no longer working for you?

http://178.62.133.174:9001/#/util/peers

nope :| no luck.

I use "gsoil-windows-amd64-1.6.7". It works for me.

https://github.com/Soilcoin/go-soil/releases/download/v1.7.7/gsoil-windows-amd64-1.6.7.zip
Post
Topic
Board Announcements (Altcoins)
Re: [$XVG] VERGE [POW][MultiAlgo][BLACKHOLE][Entire Line of TOR/i2P Resources]
by
holgerkpedersen
on 05/07/2018, 12:03:20 UTC
Quote from: nicklello on July 05, 2018, 11:01:00 AM
I think it would be great if the roadmap were updated more often and communication about development were more open.

Still, you are welcome to contribute to the solutions. The Roadmap is here https://vergecurrency.com/roadmap/ in case it's not known by the reader.
Post
Topic
Board Announcements (Altcoins)
Re: BITSOAR, the Korean company made coin.
by
holgerkpedersen
on 17/02/2018, 15:31:00 UTC
Quote from: markhuang on February 05, 2018, 01:52:34 PM
Quote from: BITSOAR on February 05, 2018, 08:33:24 AM
Bitsoar is scheduled to enter Vietnam, Singapore, Malaysia and Indonesia market. The ico of each country is completed or in progress, and there will be a large-scale investment attraction. Just wait and see what happens.

http://bitsoar.com
i cant understand how mine this coin?no windows wallet?
 Or your wallet hasn't been released yet? and you must give us more info about your coin ,create a discord channel or telegram will be better!

You can't mine this shitcoin. However, you can acquire some coins, and start staking to earn up to 1% compound interest per X timeframe. Amateur-ish information. Don't waste your time on this scam.
Post
Topic
Board Announcements (Altcoins)
Re: [ANN] SOIL | Environmental | Agriculture | Quixotic | Hackathon | Contracts
by
holgerkpedersen
on 06/03/2017, 20:06:29 UTC
Quote from: martymcfly2015 on March 06, 2017, 03:48:56 PM
Quote from: holgerkpedersen on March 06, 2017, 01:53:11 PM
Quote from: martymcfly2015 on March 06, 2017, 11:02:55 AM
I think there's no need to have two ANN threads. I've asked abvhiael to share the account of this thread with me. We would have another person with access to the OP.
I'm not a dev and it's hard to find altruistic people to get in. I'm happy for the moment to help with the technical aspects of soil but if we want to continue here, we need more people in.


I'm a C# developer, but I guess , I could learn to develop on the blockchain as well. I'll be your apprentice @abvhiael.

I think it's good fun to try and understand the ideas driving a blockchain towards common goals in benefit of the community.

So, to be able to compile the currently available source code into a gsoil.exe for Windows might be one of my first goals in this group. I just need some help in doing it. Later, I think; i can be able to do it on my own.

How to compile gsoil under windows
Code:
Get Git from http://git-scm.com/downloads
Get go windows https://golang.org/dl/
Get http://win-builds.org/doku.php
Set Environment paths
Add GOROOT pointed to c:\go and GOPATH to c:\godev
Set PATH to %PATH%;%GOROOT%\bin;%GOPATH%\bin;c:\winbuilds\bin
Install godep: "go get -u github.com/tools/godep"
go get -d -u github.com/Soilcoin/go-soil.git
go to c:\godev\src\github.com\Soilcoin\gsoil\cmd\gsoil and run "godep go install"
Find the binary in c:\godev\bin

Thanks, I'll try it out Wink
Post
Topic
Board Announcements (Altcoins)
Re: [ANN] SOIL | Environmental | Agriculture | Quixotic | Hackathon | Contracts
by
holgerkpedersen
on 06/03/2017, 13:53:11 UTC
Quote from: martymcfly2015 on March 06, 2017, 11:02:55 AM
I think there's no need to have two ANN threads. I've asked abvhiael to share the account of this thread with me. We would have another person with access to the OP.
I'm not a dev and it's hard to find altruistic people to get in. I'm happy for the moment to help with the technical aspects of soil but if we want to continue here, we need more people in.


I'm a C# developer, but I guess , I could learn to develop on the blockchain as well. I'll be your apprentice @abvhiael.

I think it's good fun to try and understand the ideas driving a blockchain towards common goals in benefit of the community.

So, to be able to compile the currently available source code into a gsoil.exe for Windows might be one of my first goals in this group. I just need some help in doing it. Later, I think; i can be able to do it on my own.

Post
Topic
Board Altcoin Discussion
Re: [POLL] Soilcoin [SOIL] revive?
by
holgerkpedersen
on 26/02/2017, 14:49:43 UTC
I can't vote, but the answer is yes.
Post
Topic
Board Announcements (Altcoins)
Re: [ANN] SOIL | Environmental | Agriculture | Quixotic | Hackathon | Contracts
by
holgerkpedersen
on 10/02/2017, 20:57:35 UTC
When mining with ethminer.exe I get a lot of blocks very quickly, and then I get this message; which I don't understand: We are too far in the future. Waiting for 5s

I0210 21:55:34.816257    4972 worker.go:447]    Mined 5 blocks back: block #460911
I0210 21:55:34.817259    4972 worker.go:569] commit new work on block 460917 with 0 txs & 0 uncles. Took 501.5µs
I0210 21:55:35.340652    4972 worker.go:348]   Mined block (#460917 / 37856e1b). Wait 5 blocks for confirmation
I0210 21:55:35.341655    4972 worker.go:569] commit new work on block 460918 with 0 txs & 0 uncles. Took 0
I0210 21:55:35.342154    4972 worker.go:447]    Mined 5 blocks back: block #460912
I0210 21:55:35.343659    4972 worker.go:569] commit new work on block 460918 with 0 txs & 0 uncles. Took 500.3µs
I0210 21:55:35.881088    4972 worker.go:348]   Mined block (#460918 / 780d16ba). Wait 5 blocks for confirmation
I0210 21:55:35.881088    4972 worker.go:470] We are too far in the future. Waiting for 5s

Also the miner comes up like, but I'm not sure why:

  i  21:55:41|main    Nonce: 2d82a72d51b105b8
  i  21:55:41|main  B-) Submitted and accepted.
  m  21:55:41|main  Getting work package...
  m  21:55:41|main  Got work package: #e2399bba
  i  21:55:41|cudaminer0  set work; seed: #3db89d40, target: #0000042f1a11
  i  21:55:41|main  Solution found; Submitting to 127.0.0.1:39342 ...
  i  21:55:41|main    Nonce: 2d82a72d51f57ee4
JSON-RPC problem. Probably couldn't connect. Retrying in 1...
  m  21:55:53|main  Mining on PoWhash #e2399bba : 0.335=0.335MH/s A338+0:R0+0
JSON-RPC problem. Probably couldn't connect. Retrying in 1...
  m  21:56:05|main  Mining on PoWhash #e2399bba : 0=0MH/s A338+0:R0+0
JSON-RPC problem. Probably couldn't connect. Retrying in 1...
  m  21:56:17|main  Mining on PoWhash #e2399bba : 0=0MH/s A338+0:R0+0
JSON-RPC problem. Probably couldn't connect. Retrying in 1...
  m  21:56:29|main  Mining on PoWhash #e2399bba : 0=0MH/s A338+0:R0+0
JSON-RPC problem. Probably couldn't connect. Retrying in 1...
  m  21:56:41|main  Mining on PoWhash #e2399bba : 0=0MH/s A338+0:R0+0
JSON-RPC problem. Probably couldn't connect. Retrying in 1...
  m  21:56:53|main  Mining on PoWhash #e2399bba : 0=0MH/s A338+0:R0+0
JSON-RPC problem. Probably couldn't connect. Retrying in 1...
  m  21:57:05|main  Mining on PoWhash #e2399bba : 0=0MH/s A338+0:R0+0
JSON-RPC problem. Probably couldn't connect. Retrying in 1...
  m  21:57:17|main  Mining on PoWhash #e2399bba : 0=0MH/s A338+0:R0+0
JSON-RPC problem. Probably couldn't connect. Retrying in 1...
  m  21:57:29|main  Mining on PoWhash #e2399bba : 0=0MH/s A338+0:R0+0
JSON-RPC problem. Probably couldn't connect. Retrying in 1...
  m  21:57:41|main  Mining on PoWhash #e2399bba : 0=0MH/s A338+0:R0+0
JSON-RPC problem. Probably couldn't connect. Retrying in 1...
  m  21:57:54|main  Mining on PoWhash #e2399bba : 0=0MH/s A338+0:R0+0


Post
Topic
Board Announcements (Altcoins)
Re: [ANN] SOIL | Environmental | Agriculture | Quixotic | Hackathon | Contracts
by
holgerkpedersen
on 10/02/2017, 20:48:22 UTC
Quote from: Dunkelheit667 on February 10, 2017, 08:19:06 PM
Quote from: holgerkpedersen on February 10, 2017, 07:47:51 PM
It is moving, but try to start mining. I even get blocks, so I am not alone anymore Smiley
...
I've tried, but unfortunately mining will crash the node instantly on my raspberry for any reason without throwing an error message. Even with a 4GB swap file. Sooo... thanks for keeping the chain going! Smiley

Okay, small isn't always beautiful. Especially, when it crashes.
Post
Topic
Board Announcements (Altcoins)
Re: [ANN] SOIL | Environmental | Agriculture | Quixotic | Hackathon | Contracts
by
holgerkpedersen
on 10/02/2017, 19:47:51 UTC
It is moving, but try to start mining. I even get blocks, so I am not alone anymore Smiley

I0210 20:28:05.562993    4972 worker.go:447]    Mined 5 blocks back: block #460550
I0210 20:28:05.564504    4972 worker.go:569] commit new work on block 460556 with 0 txs & 0 uncles. Took 517.1µs
I0210 20:28:18.399951    4972 blockchain.go:1251] imported 1 block(s) (0 queued 0 ignored) including 0 txs in 4.0112ms. #460556 [adb3db4a / adb3db4a]
I0210 20:28:18.400429    4972 worker.go:569] commit new work on block 460557 with 0 txs & 0 uncles. Took 477.5µs
I0210 20:28:18.400929    4972 worker.go:447]    Mined 5 blocks back: block #460551
I0210 20:28:53.702442    4972 blockchain.go:1251] imported 1 block(s) (0 queued 0 ignored) including 0 txs in 3.517ms. #460557 [567f43c4 / 567f43c4]
I0210 20:28:53.702936    4972 worker.go:569] commit new work on block 460558 with 0 txs & 0 uncles. Took 0
I0210 20:30:09.724233    4972 worker.go:348]   Mined block (#460558 / ff1d7346). Wait 5 blocks for confirmation
I0210 20:30:09.725768    4972 worker.go:569] commit new work on block 460559 with 0 txs & 0 uncles. Took 1.5345ms
I0210 20:30:09.725768    4972 worker.go:447]    Mined 5 blocks back: block #460553
I0210 20:30:09.726239    4972 worker.go:569] commit new work on block 460559 with 0 txs & 0 uncles. Took 471.5µs
I0210 20:31:50.042980    4972 worker.go:348]   Mined block (#460559 / add1cb55). Wait 5 blocks for confirmation
I0210 20:31:50.043451    4972 worker.go:569] commit new work on block 460560 with 0 txs & 0 uncles. Took 471.2µs
I0210 20:31:50.043451    4972 worker.go:447]    Mined 5 blocks back: block #460554
I0210 20:31:50.044455    4972 worker.go:569] commit new work on block 460560 with 0 txs & 0 uncles. Took 0
I0210 20:32:02.218211    4972 worker.go:348]   Mined block (#460560 / be63621c). Wait 5 blocks for confirmation
I0210 20:32:02.218713    4972 worker.go:569] commit new work on block 460561 with 0 txs & 0 uncles. Took 501.5µs
I0210 20:32:02.219750    4972 worker.go:447]    Mined 5 blocks back: block #460555
I0210 20:32:02.220440    4972 worker.go:569] commit new work on block 460561 with 0 txs & 0 uncles. Took 0
I0210 20:32:52.201073    4972 blockchain.go:1251] imported 1 block(s) (0 queued 0 ignored) including 0 txs in 3.0083ms. #460561 [24b739b5 / 24b739b5]
I0210 20:32:52.201575    4972 worker.go:569] commit new work on block 460562 with 0 txs & 0 uncles. Took 502.7µs
I0210 20:32:55.645297    4972 worker.go:348]   Mined block (#460562 / e7632c10). Wait 5 blocks for confirmation
I0210 20:32:55.645802    4972 worker.go:569] commit new work on block 460563 with 0 txs & 0 uncles. Took 505.7µs
I0210 20:32:55.646810    4972 worker.go:569] commit new work on block 460563 with 0 txs & 0 uncles. Took 0
I0210 20:33:38.127977    4972 worker.go:348]   Mined block (#460563 / a14412c9). Wait 5 blocks for confirmation
I0210 20:33:38.128952    4972 worker.go:569] commit new work on block 460564 with 0 txs & 0 uncles. Took 0
I0210 20:33:38.129473    4972 worker.go:447]    Mined 5 blocks back: block #460558
I0210 20:33:38.130457    4972 worker.go:569] commit new work on block 460564 with 0 txs & 0 uncles. Took 491.3µs
I0210 20:33:59.003788    4972 worker.go:348]   Mined block (#460564 / ce0e1bcf). Wait 5 blocks for confirmation
I0210 20:33:59.004289    4972 worker.go:569] commit new work on block 460565 with 0 txs & 0 uncles. Took 0
I0210 20:33:59.005291    4972 worker.go:447]    Mined 5 blocks back: block #460559
I0210 20:33:59.006298    4972 worker.go:569] commit new work on block 460565 with 0 txs & 0 uncles. Took 497µs
I0210 20:34:30.187160    4972 worker.go:348]   Mined block (#460565 / 392a4d14). Wait 5 blocks for confirmation
I0210 20:34:30.187663    4972 worker.go:569] commit new work on block 460566 with 0 txs & 0 uncles. Took 0
I0210 20:34:30.188730    4972 worker.go:447]    Mined 5 blocks back: block #460560
I0210 20:34:30.189735    4972 worker.go:569] commit new work on block 460566 with 0 txs & 0 uncles. Took 502.1µs
I0210 20:35:38.571857    4972 worker.go:348]   Mined block (#460566 / 855b71cf). Wait 5 blocks for confirmation
I0210 20:35:38.572332    4972 worker.go:569] commit new work on block 460567 with 0 txs & 0 uncles. Took 474.7µs
I0210 20:35:38.573334    4972 worker.go:569] commit new work on block 460567 with 0 txs & 0 uncles. Took 0
I0210 20:36:03.552134    4972 blockchain.go:1251] imported 1 block(s) (0 queued 0 ignored) including 0 txs in 3.5086ms. #460567 [eff6e521 / eff6e521]
I0210 20:36:03.552607    4972 worker.go:569] commit new work on block 460568 with 0 txs & 0 uncles. Took 473.5µs
I0210 20:36:03.553656    4972 worker.go:447]    Mined 5 blocks back: block #460562
I0210 20:36:08.219405    4972 blockchain.go:1251] imported 1 block(s) (0 queued 0 ignored) including 0 txs in 3.5095ms. #460568 [d57de49a / d57de49a]
I0210 20:36:08.220408    4972 worker.go:569] commit new work on block 460569 with 0 txs & 0 uncles. Took 501.4µs
I0210 20:36:08.220408    4972 worker.go:447]    Mined 5 blocks back: block #460563
I0210 20:36:19.500856    4972 worker.go:348]   Mined block (#460569 / 57cdfdaf). Wait 5 blocks for confirmation
I0210 20:36:19.501382    4972 worker.go:569] commit new work on block 460570 with 0 txs & 0 uncles. Took 0
I0210 20:36:19.502404    4972 worker.go:447]    Mined 5 blocks back: block #460564
I0210 20:36:19.502898    4972 worker.go:569] commit new work on block 460570 with 0 txs & 0 uncles. Took 0
I0210 20:36:32.566713    4972 worker.go:348]   Mined block (#460570 / dc6cf3b8). Wait 5 blocks for confirmation
I0210 20:36:32.567186    4972 worker.go:569] commit new work on block 460571 with 0 txs & 0 uncles. Took 473.5µs
I0210 20:36:32.567688    4972 worker.go:447]    Mined 5 blocks back: block #460565
I0210 20:36:32.568691    4972 worker.go:569] commit new work on block 460571 with 0 txs & 0 uncles. Took 501.1µs
I0210 20:37:31.435356    4972 worker.go:348]   Mined block (#460571 / 9d20b8e2). Wait 5 blocks for confirmation
I0210 20:37:31.435826    4972 worker.go:569] commit new work on block 460572 with 0 txs & 0 uncles. Took 469.6µs
I0210 20:37:31.436327    4972 worker.go:447]    Mined 5 blocks back: block #460566
I0210 20:37:31.437331    4972 worker.go:569] commit new work on block 460572 with 0 txs & 0 uncles. Took 492.2µs
I0210 20:38:27.147922    4972 worker.go:348]   Mined block (#460572 / ba62b87e). Wait 5 blocks for confirmation
I0210 20:38:27.148397    4972 worker.go:569] commit new work on block 460573 with 0 txs & 0 uncles. Took 475.4µs
I0210 20:38:27.149898    4972 worker.go:569] commit new work on block 460573 with 0 txs & 0 uncles. Took 500µs
I0210 20:38:29.277110    4972 blockchain.go:1251] imported 1 block(s) (0 queued 0 ignored) including 0 txs in 2.9777ms. #460573 [2c19f24a / 2c19f24a]
I0210 20:38:29.277617    4972 worker.go:569] commit new work on block 460574 with 0 txs & 0 uncles. Took 506.6µs
I0210 20:39:32.786290    4972 worker.go:348]   Mined block (#460574 / 332801c0). Wait 5 blocks for confirmation
I0210 20:39:32.786792    4972 worker.go:569] commit new work on block 460575 with 0 txs & 0 uncles. Took 501.5µs
I0210 20:39:32.787795    4972 worker.go:447]    Mined 5 blocks back: block #460569
I0210 20:39:32.788769    4972 worker.go:569] commit new work on block 460575 with 0 txs & 0 uncles. Took 0
I0210 20:39:50.108510    4972 worker.go:348]   Mined block (#460575 / f61a9bee). Wait 5 blocks for confirmation
I0210 20:39:50.108985    4972 worker.go:569] commit new work on block 460576 with 0 txs & 0 uncles. Took 0
I0210 20:39:50.110001    4972 worker.go:447]    Mined 5 blocks back: block #460570
I0210 20:39:50.110489    4972 worker.go:569] commit new work on block 460576 with 0 txs & 0 uncles. Took 0
I0210 20:40:38.703360    4972 blockchain.go:1251] imported 1 block(s) (0 queued 0 ignored) including 0 txs in 2.9762ms. #460576 [6e291944 / 6e291944]
I0210 20:40:38.703871    4972 worker.go:569] commit new work on block 460577 with 0 txs & 0 uncles. Took 510.8µs
I0210 20:40:38.704864    4972 worker.go:447]    Mined 5 blocks back: block #460571
I0210 20:41:15.733660    4972 worker.go:348]   Mined block (#460577 / 53c06a5b). Wait 5 blocks for confirmation
I0210 20:41:15.734129    4972 worker.go:569] commit new work on block 460578 with 0 txs & 0 uncles. Took 0
I0210 20:41:15.735133    4972 worker.go:447]    Mined 5 blocks back: block #460572
I0210 20:41:15.736134    4972 worker.go:569] commit new work on block 460578 with 0 txs & 0 uncles. Took 500.6µs
I0210 20:41:16.276103    4972 blockchain.go:1251] imported 1 block(s) (0 queued 0 ignored) including 0 txs in 3.5095ms. #460578 [eb7e9b91 / eb7e9b91]
I0210 20:41:16.277172    4972 worker.go:569] commit new work on block 460579 with 0 txs & 0 uncles. Took 568.2µs
I0210 20:41:31.213287    4972 worker.go:348]   Mined block (#460579 / 88c89cf3). Wait 5 blocks for confirmation
I0210 20:41:31.213790    4972 worker.go:569] commit new work on block 460580 with 0 txs & 0 uncles. Took 503µs
I0210 20:41:31.214291    4972 worker.go:447]    Mined 5 blocks back: block #460574
I0210 20:41:31.215293    4972 worker.go:569] commit new work on block 460580 with 0 txs & 0 uncles. Took 500.2µs
I0210 20:41:36.706483    4972 worker.go:348]   Mined block (#460580 / 5edc615c). Wait 5 blocks for confirmation
I0210 20:41:36.706984    4972 worker.go:569] commit new work on block 460581 with 0 txs & 0 uncles. Took 501.2µs
I0210 20:41:36.707485    4972 worker.go:447]    Mined 5 blocks back: block #460575
I0210 20:41:36.708489    4972 worker.go:569] commit new work on block 460581 with 0 txs & 0 uncles. Took 503µs
I0210 20:42:28.475823    4972 blockchain.go:1251] imported 1 block(s) (0 queued 0 ignored) including 0 txs in 3.039ms. #460581 [5313061e / 5313061e]
I0210 20:42:28.476307    4972 worker.go:569] commit new work on block 460582 with 0 txs & 0 uncles. Took 484.3µs
I0210 20:42:35.095066    4972 blockchain.go:1251] imported 1 block(s) (0 queued 0 ignored) including 0 txs in 3.0077ms. #460582 [5fd01cd2 / 5fd01cd2]
I0210 20:42:35.095567    4972 worker.go:569] commit new work on block 460583 with 0 txs & 0 uncles. Took 501.5µs
I0210 20:42:35.096069    4972 worker.go:447]    Mined 5 blocks back: block #460577
I0210 20:42:43.569056    4972 blockchain.go:1251] imported 1 block(s) (0 queued 0 ignored) including 0 txs in 3.5137ms. #460583 [2996ecbb / 2996ecbb]
I0210 20:42:43.569553    4972 worker.go:569] commit new work on block 460584 with 0 txs & 0 uncles. Took 497µs
I0210 20:42:45.680098    4972 blockchain.go:1251] imported 1 block(s) (0 queued 0 ignored) including 0 txs in 3.0383ms. #460584 [e38298bf / e38298bf]
I0210 20:42:45.680571    4972 worker.go:569] commit new work on block 460585 with 0 txs & 0 uncles. Took 472.4µs
I0210 20:42:45.681581    4972 worker.go:447]    Mined 5 blocks back: block #460579
I0210 20:42:48.626785    4972 worker.go:348]   Mined block (#460585 / 9fb68535). Wait 5 blocks for confirmation
I0210 20:42:48.627261    4972 worker.go:569] commit new work on block 460586 with 0 txs & 0 uncles. Took 0
I0210 20:42:48.628262    4972 worker.go:447]    Mined 5 blocks back: block #460580
I0210 20:42:48.628763    4972 worker.go:569] commit new work on block 460586 with 0 txs & 0 uncles. Took 501.5µs
I0210 20:42:57.169952    4972 blockchain.go:1251] imported 1 block(s) (0 queued 0 ignored) including 0 txs in 3.5405ms. #460586 [3452e42a / 3452e42a]
I0210 20:42:57.170423    4972 worker.go:569] commit new work on block 460587 with 0 txs & 0 uncles. Took 470.2µs
I0210 20:43:11.245575    4972 worker.go:348]   Mined block (#460587 / eeeeadd7). Wait 5 blocks for confirmation
I0210 20:43:11.246050    4972 worker.go:569] commit new work on block 460588 with 0 txs & 0 uncles. Took 474.7µs
I0210 20:43:11.247053    4972 worker.go:569] commit new work on block 460588 with 0 txs & 0 uncles. Took 501.2µs
I0210 20:43:14.748040    4972 worker.go:348]   Mined block (#460588 / 18a510f9). Wait 5 blocks for confirmation
I0210 20:43:14.748533    4972 worker.go:569] commit new work on block 460589 with 0 txs & 0 uncles. Took 0
I0210 20:43:14.750025    4972 worker.go:569] commit new work on block 460589 with 0 txs & 0 uncles. Took 505.6µs
I0210 20:43:24.068162    4972 worker.go:348]   Mined block (#460589 / 90f7f5bf). Wait 5 blocks for confirmation
I0210 20:43:24.068632    4972 worker.go:569] commit new work on block 460590 with 0 txs & 0 uncles. Took 470µs
I0210 20:43:24.070136    4972 worker.go:569] commit new work on block 460590 with 0 txs & 0 uncles. Took 489.5µs
I0210 20:43:46.582646    4972 worker.go:348]   Mined block (#460590 / a6860e2e). Wait 5 blocks for confirmation
I0210 20:43:46.583115    4972 worker.go:569] commit new work on block 460591 with 0 txs & 0 uncles. Took 469.6µs
I0210 20:43:46.584621    4972 worker.go:447]    Mined 5 blocks back: block #460585
I0210 20:43:46.585121    4972 worker.go:569] commit new work on block 460591 with 0 txs & 0 uncles. Took 500µs
I0210 20:44:16.008364    4972 worker.go:348]   Mined block (#460591 / 6d539f9b). Wait 5 blocks for confirmation
I0210 20:44:16.008867    4972 worker.go:569] commit new work on block 460592 with 0 txs & 0 uncles. Took 502.7µs
I0210 20:44:16.010379    4972 worker.go:569] commit new work on block 460592 with 0 txs & 0 uncles. Took 501.5µs

Post
Topic
Board Announcements (Altcoins)
Re: [ANN] SOIL | Environmental | Agriculture | Quixotic | Hackathon | Contracts
by
holgerkpedersen
on 10/02/2017, 18:57:12 UTC
Quote from: martymcfly2015 on February 10, 2017, 05:50:35 PM
Quote from: Dunkelheit667 on February 10, 2017, 04:47:44 PM
I'm getting this on testnet, any hints?

Code:
E0210 17:45:00.776716    3691 blockchain.go:1384] Bad block #460001 (0x5edaeaebdf53887e1c93cccbb9115680b8991b416b0ce7216bfd3bc29eac22b6)
E0210 17:45:00.776844    3691 blockchain.go:1385] Difficulty check failed for header 5697432, 5151670
I0210 17:45:00.805252    3691 downloader.go:267] Synchronisation failed: Difficulty check failed for header 5697432, 5151670

Code:
instance: Gsoil_TNET/v1.4.3-f0475b8f/linux/go1.7.5
 datadir: /root/.soiltnet
coinbase: 0x5d575c05ab6462b0ff748a2f4e5cd4b0a0306e7c
at block: 460000 (Thu, 09 Feb 2017 21:14:41 CET)
modules: admin:1.0 db:1.0 debug:1.0 eth:1.0 miner:1.0 net:1.0 personal:1.0 shh:1.0 txpool:1.0 web3:1.0

Yes, the problem is that you have no peers - other connected clients - which are on the right chain.
We had a fork to homestead on block #460000 on the testnet with client version "Gsoil_TNET/v1.4.3" and I we have old testnet clients online (TNET_v1.4.1) which are on it's on chain now.

Maybe this node is on the right chain:
admin.addPeer("enode://45ec3e9efbe74e7b6a4accd04ea003fca120e4fd812c6dba6a194e657a1060d0134e9b46462207b52e3ca9a796626fef127f26432f837964b5945f9581744e58@62.227.107.119:39340")

Restart soil and add the node. If this wont help - maybe holgerkpedersen can help with his node when he's back online.


I have same problem as you guys.

I've started my node just a few minutes ago.

My node has the following properties:

admin.addPeer("enode://a623eadd411ab6d612e091716706a22de86a9d01e932bcd170463e46920073be04e0c9263a3c2720bb18a446d1a95d39e9a90f903e954514ea530296a462d637@2.105.196.29:39340")


> admin.peers
[{
    caps: ["eth/61", "eth/62", "eth/63"],
    id: "45ec3e9efbe74e7b6a4accd04ea003fca120e4fd812c6dba6a194e657a1060d0134e9b46462207b 52e3ca9a796626fef127f26432f837964b5945f9581744e58",
    name: "Gsoil_TNET/v1.4.3-f0475b8f/linux/go1.7.5",
    network: {
      localAddress: "192.168.0.16:39340",
      remoteAddress: "62.227.107.119:54268"
    },
    protocols: {
      eth: {
        difficulty: 174846653126,
        head: "f870969d8d16b7b7b3188b637ea3cfe680b17bdab85d2c691e77a318c7f8bb2e",
        version: 63
      }
    }
}, {
    caps: ["eth/61", "eth/62", "eth/63"],
    id: "e042fbe55beaff48ffbb0c1caabd224267260b660c738f2fd33e53d3b18ef984734323fe7be5be2 3e3faa3d9358aa32c8d02337bfb921fc4abd2fac36e041b4a",
    name: "Gsoil_TNET/v1.4.3/windows/go1.5.4",
    network: {
      localAddress: "192.168.0.16:39340",
      remoteAddress: "77.78.26.74:50353"
    },
    protocols: {
      eth: {
        difficulty: 174856467025,
        head: "ea301f1bfd2b167a597824fb15f8bd8c7d3b17376023884a5d3aaee1a55be348",
        version: 63
      }
    }
}]

I am also cpu mining, therefore I use  ">miner.start(1)", to keep things moving. If nobody is mining; we won't get far, and it explains, the missing blocks to be imported.
Post
Topic
Board Announcements (Altcoins)
Re: [ANN] SOIL | Environmental | Agriculture | Quixotic | Hackathon | Contracts
by
holgerkpedersen
on 09/02/2017, 19:08:25 UTC
Quote from: altsheets on February 09, 2017, 06:25:18 PM
I happened again. It had actually only survived for half an hour, then the blockexplorer node was offline again, because it had crashed again with a "panic: runtime error: index out of range":

Code:
I0208 22:18:58.707726   10883 downloader.go:288] Block synchronisation started
I0208 22:19:20.323027   10883 blockchain.go:1230] imported 87 block(s) (0 queued 0 ignored) including 0 txs in 8.65759476s. #1822401 [e022f6b1 / 2848295b]
I0208 22:19:26.974903   10883 blockchain.go:1230] imported 256 block(s) (0 queued 0 ignored) including 0 txs in 6.51036203s. #1822657 [9b38bfc6 / 6d5506a7]
I0208 22:19:32.260438   10883 blockchain.go:1230] imported 256 block(s) (0 queued 0 ignored) including 0 txs in 5.280125215s. #1822913 [0d3f1d6d / 79be460a]
...
I0208 22:53:03.373333   10883 blockchain.go:1230] imported 1 block(s) (0 queued 0 ignored) including 0 txs in 6.292147ms. #1825228 [dc2d8a82 / dc2d8a82]
I0208 22:53:41.866656   10883 blockchain.go:1230] imported 1 block(s) (0 queued 0 ignored) including 0 txs in 37.473429ms. #1825229 [aff98a9f / aff98a9f]
I0208 22:53:48.124703   10883 blockchain.go:1230] imported 1 block(s) (0 queued 0 ignored) including 0 txs in 15.644022ms. #1825230 [85e4e08a / 85e4e08a]
I0208 22:53:52.288943   10883 blockchain.go:1230] imported 1 block(s) (0 queued 0 ignored) including 0 txs in 14.348147ms. #1825231 [d32527f6 / d32527f6]
panic: runtime error: index out of range

Anyone understands possible reasons for this? http://pastebin.com/xSMWS7wx


Thanks for switching off the new-code nodes for now.  I only see these here, all with older versions:

Code:
cat peers-20170209.txt | grep "name\|peers"
 admin.peers
    name: "Gsoil/v1.3.3-b62bb712/linux/go1.5",
    name: "Gsoil/v1.4.0/windows/go1.6",
    name: "Gsoil/v1.4.0/windows/go1.6",
    name: "Gsoil/v1.4.0-9174da70/linux/go1.7.1",
   
Please keep the new-code nodes off the mainchain, at least until this weekend. Thanks.


I restarted the node. When the blockexplorer chain page does not show numbers but a pop up notification instead, the gsoil node has crashed again.


I have no clue; why you get an error, but something is indexing into an illegal location in some sort of collection. There could be some misunderstandings related to intermixing of testnet and mainnet addressing. IMO; it's likely causing trouble.

Are you preparing the homestead explorer?
Post
Topic
Board Announcements (Altcoins)
Re: [ANN] SOIL | Environmental | Agriculture | Quixotic | Hackathon | Contracts
by
holgerkpedersen
on 09/02/2017, 17:54:18 UTC
I am in now

admin.addNode("enode://a623eadd411ab6d612e091716706a22de86a9d01e932bcd170463e46920073be04e0c9263a3c2720bb18a446d1a95d39e9a90f903e954514ea530296a462d637@2.105.196.29:39340");

Post
Topic
Board Announcements (Altcoins)
Re: [ANN] SOIL | Environmental | Agriculture | Quixotic | Hackathon | Contracts
by
holgerkpedersen
on 08/02/2017, 15:48:11 UTC
Quote from: Dubrovin on February 08, 2017, 01:09:31 PM
Hello! I have left the coins on the old wallet! What will happen to them? how to get them back?


I guess, you just let the coins be where they are, until we go live with the homestead version of gsoil.exe. They will reappear when the network returns to normal mining on the main net.

Always make a copy of your gsoil/keystore folder to a safe place; if you want to be able to keep the existing wallet.
Post
Topic
Board Announcements (Altcoins)
Re: [ANN] SOIL | Environmental | Agriculture | Quixotic | Hackathon | Contracts
by
holgerkpedersen
on 07/02/2017, 23:23:06 UTC
Is this one working on the testnet? I am not sure.

admin.addPeer("enode://a623eadd411ab6d612e091716706a22de86a9d01e932bcd170463e46920073be04e0c9263a3c2720bb18a446d1a95d39e9a90f903e954514ea530296a462d637@2.105.196.29:39340"")

my testnode address: "0xc3807abee52c39b9a3bdd682602eb5f36c5adee8"

However, this IP Address is unfortunately not static. But, I'll check it out now and then; correcting the node.
Post
Topic
Board Digital goods
Re: 1 Ticket to Consensus 2017 Conference in NYC May 22-24, 2017
by
holgerkpedersen
on 01/02/2017, 21:20:21 UTC
Quote from: covertress on January 30, 2017, 11:59:34 PM
Still available.

I guess, you'll find someone, before it's too late, young lady Wink

Hope, you're good. Smiley
Post
Topic
Board Announcements (Altcoins)
Re: [ANN] SOIL | Environmental | Agriculture | Quixotic | Hackathon | Contracts
by
holgerkpedersen
on 18/01/2017, 21:18:50 UTC
Quote from: RKS on January 18, 2017, 03:57:26 PM
With no other exchange, another coin bites the dust Cry
Dead coin?

The coin might be dead for now, but we are waiting for the developer to push it forward. The reason it's dead is, the lack of activity in the development of the project. As I understand, the only true developer of soilcoin is in deep economic trouble. So how can this coin evolve?

The coin can be reintroduced on an exchange; when the developer has assembled a team to drive the project forward.
Post
Topic
Board Announcements (Altcoins)
Re: [ANN] SOIL | Environmental | Agriculture | Quixotic | Hackathon | Contracts
by
holgerkpedersen
on 30/09/2016, 20:12:40 UTC
Quote from: abvhiael on September 28, 2016, 05:06:58 PM
Quote from: holgerkpedersen on September 26, 2016, 08:15:38 AM
@abvhiael: Thanks for the info update of your thoughts about the attacks on ETH based blockchains.  Wink

I understand your concerns about the centralization of knowledge about locking blocks, and the chance of corruption amongst insiders. I agree, it's not better. But, the bigger the number of nodes, the harder it is to take over with 51% attacks. Probably, it could be a solution until the network has matured.


ive been giving this a lot of thought, and tearing thru google like a madman, about this problem thats faced Krypton and Shift. and the idea presented, hardcoded blocks, seems like the best scenario, assuming a trustworthy currency developer. Ive never veiwed SOIL as a financial engine... hell, theres more than enough blockchains out there that are hyperobsessed with fintech, and yeah, thats where the money is. but SOIL isnt about that, its always been about the technology, how it can change EVERY sector of industry. and to make that technology available, globally. its always been about building the dApps for distributed climate prediction, and microgrid systems, and food provenance and livestock lineage, its been about making this sort of technology, these smart contracts, available to anyone, with operating costs a fraction of what corporate interests use to line their pockets with. i think its sad to see Krypton abandon the EVM, and its sad to see Shift migrate to LISK, but thats the reality of the cryptopolitical landscape. to accomplish wwhat SOIL is to become, we need the EVM. and no, not Ethereum's blockchain or Expanse's blockchains, because those currencies are very good at being what they are building themselves into. SOIL should always be something different, and it should always be independent, and as open to its users as it is NOW. anyone can build on SOIL, anything. gas costs, comparatively, for computational intesive work, SOIL is gonna be the place to go. and i want SOIL to be a.. well.. a "humanitarian blockchain" or maybe the first truly GREEN one. ive said from the beginning that this project is going to something that takes YEARS to mature. what i WANT to build with it, technology has to catch up with. its a committment, and its been hard to really focus on it over the last few months, while finances were tighter than theyve ever been. but i weathered thru, and SOIL did too. i hope, if the 51Crew guys are monitoring these smaller EVM blockchains, and if theyre reading this, please dont attack SOIL. theres no money to pay off your ransom. for me, keeping my family fed is a near day to day proposition. i have NO cryptocurrency reserves. but SOIL is something different. we're under the radar, quietly building something that will benefit humanity in the end. its not about money, its about leaving something more and better behind than what we found this world when we were born.

that being said,hard coded benchmarks on the blockchain should be easy enough to fit into our protocols, and have those run by a smart contract. theres quite a lot of smart contract blockchain administrative stuff that i want to get set up under an umbrella SOILdev account, things already running on the SOILnet as contracts. this should be one of those sorts of things. at least, although the SOILcoin Foundation might maintain the keys to those contracts, the whole of it can be automated, and protected by a 2-of-3 multisig wallet, with at least one unaffiliated but active community member as a signatory.

this post really went sideways from where id planned, but lack of coffee in my system toay is likely the culprit. trying to catch up on these nodes, and cloud servers. to whom offered up a vultr server instance, id check the message list, but ive got KITTENS roaming across my mousepad right nw, and one wrong move... (sighs) will post again later if i can. i have a massive TO-DO list involved to get SOILnet back up and healthier than ever. then i can get back to building the neat stuff for it.

Coffee beats it all Cheesy

Lots of thoughts. The weak spot is the trustworthyness of the developers involved with setting the benchmarks on the nodes. They are very important central players. If one of them turns evil; trouble will start spinning.

It might still be possible to take over the best chain with less nodes than 51% - The 51Crew DDoS attacks will be able to take down the majority of nodes; except those controlled by the attackers. Safety of the blockchain is the key to success. If you can't trust it; you can't risk it.

Just a thought: If the software, somehow could detect a major fallout of the peers; the software could be able to alert the other nodes; and set the network to a halt; preventing the attackers from doing anything, because of suspension, until a routine investigation has been done by blockchain surveiling software. A certain percentage of nodes must send a "go" signal; before the suspension of the network will be reverted to normal state.

Post
Topic
Board Announcements (Altcoins)
Re: [ANN] SOIL | Environmental | Agriculture | Quixotic | Hackathon | Contracts
by
holgerkpedersen
on 26/09/2016, 08:15:38 UTC
@abvhiael: Thanks for the info update of your thoughts about the attacks on ETH based blockchains.  Wink

I understand your concerns about the centralization of knowledge about locking blocks, and the chance of corruption amongst insiders. I agree, it's not better. But, the bigger the number of nodes, the harder it is to take over with 51% attacks. Probably, it could be a solution until the network has matured.