too many big words in that article.

can you offer anything with pictures by chance?

No, any block explorer discloses rewards have been 2 ZEC since the beginning

https://explorer.zcha.in/transactions/15eba1605cb9296de2619a4f03c50fa266a74556d4868209871f32937ed60a8a

t1SaATQbzURpG1qU3vz9Wfn3pwXoTqFtTq2   1.6935 ZEC
t3Vz22vK5z2LcKEdg16Yv4FFneEL1zg9ojd      0.423375 ZEC

but the most recent blocks mining reward seems unchanged from genesis specifications

https://explorer.zcha.in/transactions/128b7cc734221a881abbcbfda36578086d1f545747f3d5039a9dd13f07814c2b

t1SaATQbzURpG1qU3vz9Wfn3pwXoTqFtTq2   1.684 ZEC
t3Vz22vK5z2LcKEdg16Yv4FFneEL1zg9ojd      0.421 ZEC

when does the reward ramping start to take effect?

So there is a slow start, from 2 ZEC to 12.5 at block 20,000.

At block 10,000 the reward should be like 6 ZEC but we're at block like 3000 now and reward is showing 2 ZEC still right?

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

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.

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?




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?

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?

so now you all can get paid pennies on the dollar with software that has updated nuggets inside!

thanks admin for adding the request payment button.. i make up that fraction of the time i wasted mining to the sad, sad joke that is this pool.

other pool admins should really take note and work against it when this sort of thing happens. it tarnishes their reputation in the community as a whole although it may not be immediately realized.

you actually got paid way too much for that cpu mining.. are you sure it was not 17H/s?

.004 in the last 27 hours sounds about right for that Sol/s rate. there has only recently been a drop in difficulty on zcash network so current calculator estimates will be inflated.

out of curiosity are all your crashing miners running windows?

linux does occasionally report gpu's gone bad.. and also occasionally get constant stale shares, but just crtl-z or ctrl-c'ing out and restarting fixes everything.

Ubuntu 16.04 and debian so far.

while you got your wallets open:

t1QEEtzeuZoUNMGUq44GGs6ZBsE7xiLyQFh

KARMA

the newer RX cards are gangbuster for this.. cant believe you let the cat out of the bag. so lucrative right now

this threads lulz.. all the new accounts giving props to thief admin..and then some people that should really know better.

i came back to test the theory that blocks maturing add to the ZEC count..

another hour mining at 100sol and the balance did not budge during mining, or 4 hours later.

just fyi, mine at your peril.

crappy payouts are not a result of blockchain issues.

i threw 100sol at this pool for 2 hours and got less than a fifth the expected returns. somewhere between 15%-20% payout here.

should have gotten about 0.00073029ZEC per hour and ended up with 0.0000539ZEC.. consider it the price of a lesson learned "admin"..enjoy your spoils

you would do better at nicehash getting paid in bitcoin and then buying ZEC back.

anyone have a seednode list for those of us supporting network through running nodes?

addnode=mainnet.z.cash does not seem to be cutting mustard.

just torify your pool miner in command line.

just open another window and start another miner at the same time.

this pools pretty suspect though ppls.. email admin@coinsforall.io bounces, stats on front end are below what diff and work should be netting, or at least severely lagged. high payout threashold and you're using t addresses when nobody knows if this is even acceptable.. stop mining here till the admin chimes in would be my advice.

well it varies depending if you use parity or geth, also whether you are running windows or a unix based OS like MacOS or Linux.

basically you add "--fast" to the command line of geth or "--pruning fast" tag in parity command line after deleting the chaindata folder/directory in your miners drive.

it will sync from genesis block to current very quickly at first.. then slow down to complete a full sync likely in about 5 or 6 hours.

by doing this you're saving only the headers on every block upto 1500 before current in geth. parity is a bit more complex (optimized) and if you use it your should look into which pruning method best suits you.

parity may even have pruning on by default now.. not sure i dont use it.

mine works, even my rigs powered with conventional disks.

try nuking your chaindata and resync with --fast.

some of the block with malicious calculations refer back to previous blocks to crunch more data. limiting the bulk of old blocks to headers only curbs the amount of erroneous calculations needed to process (and sync) a block.