Bitcoin Forum

I asked this in one of the miner threads but dont see much hope for an answer, likely it will just get buried by posts made with new accounts.

can anyone shed some light on calculating proper rewards?


http://s017.radikal.ru/i402/1611/0c/b5c67c6d200c.png

these calculators don't seem accurate.

current network hashrate is just under 5MH/s (or 500,000H/s).. a 500 H/s contribution nets .5% of all blocks mined after variance.

block reward still being 2 ZEC every 2.5 minutes average, 20% scam fee to filthy rich bitcoin pumpers so lets round down to 1.6 ZEC reward until it ramps up to next increment before settling on 12.5 ZEC total.

0.5% chance of solving each block means estimated time to block is 200 blocks or 500 minutes?

getting 1.6 ZEC every 500 minutes means a full reward of 1.6 ZEC every 8.3 hours.. minus pool fee.

that's 0.2 ZEC an hour, what am i missing?

Go have a coffee and then re-check your math.
500/5,000,000 = ?
Hint: it's not 0.5%

You can compare your results to my python calculator

https://gist.github.com/nerdralph/dc4b6ad4f0f8f58098187be2f6debd5f

I think you didn't get the memo? zec is a centralized altcoin and the company launched it is in control of the system, meaning after 6 years they can destroy the coin or  fork it and dump on market if it gets big as bitcoin.

oops.. 0.1% yes lets blame the coffee  (or lack there of)

1/5'th of the estimated conclusion i came to is still .04 ZEC per hour which after like a buck and 44 cents for electricity still amounts to heaps more than these calculators are professing.

You're still off by an order of magnitude.  Maybe you grabbed a decaf by mistake? :-)

i just doubled H/s to get Sol/s but output is :  IndexError: list index out of range

block = int(sys.argv[3320]) # arg1 = current block number

net_rate_k = int(sys.argv[1000000])# arg2 = current network rate in thousands of solutions per second

your_rate = int(sys.argv[1000])# arg3 = your solution rate


okay this is better.. .01%, speeding to conclusions my bad.

.004 ZEC per hour.. *24 is like .096 which since i rounded in a bunch of places is about accurate with this calculator.

thanks much! oh and will be grinding my own coffee from here on.!

You somehow have the code messed up.  If you look at the gist, you'll see:

Or if you are a vegetarian, that could explain the brain fog.
https://www.psychologytoday.com/blog/evolutionary-psychiatry/201211/youre-vegetarian-have-you-lost-your-mind

too many big words in that article.

can you offer anything with pictures by chance?

Though everything seems mixed up here,
lets first of all talk about the units we use here.

Equihash is an (anon) algorythm stated in SOL/s,
I do not know any way, 2 compare that
2 hash/s used in other algorythms.

Bench what you have against all that you "can do".

But do not mix Apples and Grapes.


;) (just my 2 cents)

P.S. await some surprises according 2 the devices :P

One issue with trying to write a calculator for ZCash (ZEC) right now is the "block reward ramp up period" has almost a month left to go.

 Sol(utions)/s pretty much *IS* the same as hash/sec for other algorythms.

 May I offer some Navy Sludge? 9-)

some of the early calculators were way off because of the slow start reward. and i think pool administrators lack of communicating payout schemes hurt a lot too.

looking forward to the block reward rising :) i dont think anyone would mind an estimated reward based on time (2.5 minute blocks) rather than actual reward on their calculators.

its pretty easy to create a formula to guess what the reward will be for a block at noon on monday.