Quote from: ExEric3 on January 25, 2018, 06:52:26 PM

Quote from: Skyzer0 on January 16, 2018, 12:59:43 AM

why the stats on stats page show 6 gh/s but pool websites shows 15 gh/s ? which one is correct? all the 3 pools combined doesn't make up for the 6 gh/s on stats page, so there is 10 gh/s on solo mining?

6500USD on this coin today, starting to look great.

this coin supports dapps so nicely and the coin is just like ethereum and expanse, no reason not to mine this.

i expect a nice growth within 2 months, when 3 and 4gb cards starts to lose hashrate on ethereum, a whole 1 million gpu's are coming for these dagger hashimoto coins, due to many transactions on ethereum the dag is growing faster than typical.

this coin only needs 100 to 200 gh/s to hit one dollar. within 6 to 10 months the coin can be all from 1 to 10 dollars, the total network hashrate will also grow exponentally when volta from nvidia releases, if the die's are like titan volta with alot more SM's per SP and around 4600 cores+ on 2080TI the gpu might be able to run 80 to 100 mh/s, around 70 to 80 mh/s at stock speeds and overclocked possibly hitting 90-100 mh/s per gpu. hopefully they give us bios key so people can edit bios's, something they did not do with pascal series and people had to use other factory bios's and flash those, you could flash but not edit, those keys was only distributed to the AIB manufactories and kept stricly hidden from public.

there's also a new website going on http://soil.cash/

let the soil grow.

Always compare block height. Usually its all same if some node will not crash or something else will not happened.

If you compare net diff its same. Problem is network hashrate.

Net Hashrate is counted on pool side:

Quote

hashrate: Ember.computed('difficulty', {
get() {
return this.getWithDefault('difficulty', 0) / config.APP.BlockTime;
}
}),

How u can see its counted (divided by block time) which is statically configured on pool side. Thats reason why you see wrong values on most pools.

http://soil.miners-zone.net have this configured:

Quote

// For network hashrate (change for your favourite fork)
BlockTime: 13.0

https://github.com/Soilcoin/go-soil/blob/master/params/protocol_params.go#L79

Since it looks there are some miners with 10GH/s which trying mining attacks they are trying constantly mine most blocks in short time. Diff goes up and block time goes down. When they left network diff is trying go down and block time goes up. I remember times when SOIL had 12 secs block times and on network had 500MH/s.

And recognise values like real hashrate and average hashrate. On network stats that black page which Im running its counted from last 50 blocks. And if I will change that 13 secs in pool config file to actual 41 secs block time and will recompile pool pages you will see almost same hashrate (for some time until some big minner didnt comes or some didnt left) like on network stats. (you will never will get same values since again network stats are averaged).

So dear miner its all clear now? Happy mining.

i dont know, blocktime shouldn't have to be re set all the time because of more hashrate, ethereum is proof of this. keeps a 15s blocktime average regardless if its 130 th/s or 170 th/s so why shouldn't soil? instantly as hashrate goes up, blocktime goes down, http://178.62.133.174:9001/#/chain/ is what i use, right now its been a very low hashrate and therefore blocktime is around 53s last 10 blocks, which is ridicules. but instantly as hashrate goes up, blocktime goes down and difficulty up. but i dont see this as pool sided.

what i see is a Treshold that the developer wants there to be a certain amount of hashrate on the network before giving out all the coins as promised, this will keep single miners with 1-2 gh/s from scooping up all the coins if there is low hashrate, which isn't really fair in any sort of way.

i've watched expanse, ellaism, all go from 200 gh/s to 990 GH/s and blocktime is always the same average, it doesn't change based on pool and not the hashrate, for soil all i see is a treshold, once we surpass it again there will be 15s blocktime average, but right now its too low.