haven't been around bitcoin long enough:
an odd scenario, but if difficultly manages to drop can mining pools resubmit previously close shares?

both quite helpful.   here's the remaining screenshot sneak peeks.







it's waiting on apple app review right now in basic form (just about all you see there).   
going to be a week before i get a list back from them of things to address.

then a beta round if i can work out this new testflight internal/external thing.

250THs coincidentally odds to about a month for finding a block (~23 days).    gotta make you wonder if it's a coincidence  

it will adjust itself on the next difficulty adjustment (in a few hours).   thus the cycle of of bitcoin life.

on a related topic about others having access to your keys and passwords [subtle transition].

any volunteers to pm me their kano.is username and apikey for testing.
looking for a multi worker user.

i can only get so far with my one miner and random generator.

more specifically access to private keys.   

access to your wallet (with passphrase)
access to a cached copy of your keys while moving them from a to b.
use of an online vanity address generator.

5N can only be reduced by physical increased hash rate.   This is a totally different beast.  
We are virtually hashing > a 30PH pool in the last 18Hrs, which maps to luck.    And there's six hours left for a few more.    

will officially remember this as block friday.  

malform json handled, empty json values handled.   gtg for future repeats.

thanks.   no worries here.   it's a good way to test resiliency.   
can't request these on demand for obvious reasons, so using it as opportunities.

play around with setting like doubling and halving bitcoin value.

i weakly justify my S5 with solar, fun and bitcoin support.   
 
mainly solar to bitcoin  , when dealing with WAF.

i scrambled together my own for learning purposes.   non verified, but another reference:
http://23.108.83.12/miner.html

iPhone - App Sneak Peek.

conquering APN.




 
ETA: 1-31 

to be totally transparent.   i pinged thejesterone (android app developer) to get an update.  
i will yield development if he replies and picks it up.

edit: started on it anyways, in case.

lets see if that sig comes through.

i still have an dusty apple dev license i keep around for sentimental reasons.
i'll dust it off and chuck together a prototype for the app store by end of month. 
this is a good enough cause.  esp since i would like one too.

iteration target :: exact request above + basic block notification. 

not looking for new features req yet, so don't pm me about it until then unless:

a) i'm stepping on your territory (ie: you have one in progress, brand trademark, etc)
b) you are looking for a donation address.

functionally it's a little less Bitcoins per miner, but more often.   so it balances out.   
your personal BTC/week should stay about the same all else equal.

to see a average of one block a day, the magic hash number is ~5165THs.

approaching an 2x that will mean more block parties. 

The red line is the start of the last 5Nd for the most recent block reward.   
The rewards page will have [Your N Avg] as the avg of all shifts above that line that has a reward > 0.

that block is around the corner...  waiting to be found. 

first it hits you that the good about more pool hash is you hit 100% faster.   
then the high settles down and you realize the bad is that you hit next 100% faster too.
finally you give in and check every 5Nd instead 

when your [N Average] = the rate of your miners.

each worker can have it's own stats but is summed into a shift.

two weeks here now and i'm still having trouble understanding half of the shift page info to date.  
because rewards are past tense, i can't visualize why it changes.   it's meant for some pps type comparison i think.

on the reward page you get the final important numbers.
you will see an [N average] when blocks found (independent of workers) which is your effective hash rate.

somewhere between 3-5 days you'll N average will hit your miner's speed.   just be patient for it.
you can't speed it up 5Nd without throwing in more hash than your miners can produce.

you can take "[Your BTC] x 120 / [N Range (in hours)]" to see an approximate BTC/day for the effective payout at any time.
(not the official way - you should track it yourself overtime).  
keep in mind it will be comparable only to a miner at [N Average] hash rate.

keeping separate worker names can help you identify a misbehaving worker (though your local stats are there too).  and when a block is found, the worker that finds it is advertised on the block stats page.

and welcome aboard.