The ones that come to mind right now are:
getMiningInfo (no extra params)
gives info for mining. example:
{"baseTarget":"2880322","height":"13884","generationSignature":"bf903dd43395da657be20e08d8cd4c3c2aaf01610da5674983b478fe45bca3ed"}

submitNonce (secretPhrase, nonce, accountId)
for solo mining, only secretPhrase and nonce are needed.
for v2 pooling, give pool's secretPhrase with miner's nonce and accountId.
returns JSON with result and if everything good, deadline

setRewardRecipient (secretPhrase, recipient)

getRewardRecipient (account)
returns JSON {"rewardRecipient":""} showing what numeric address the reward recipient of the supplied account is set to

getAccountsWithRewardRecipient (account)
returns JSON {"accounts":[]} showing what account ids have their reward recipient set to the supplied account. This is intended for use by pools, and a user stops showing up on this list when a new assignment has been confirmed, even though it hasn't taken effect yet, to give pools sufficient time to react to the change. A pool can effectively use this list as a registered users list when the call it with their own id.

Probably will take it up to 150k tomorrow, but just stepping it up slowly.

I wrote a script that queries my local burst wallet for the baseTarget for every block. The baseTarget can be used to calculate the total network size.

It's a little but of a manual process, but here's the ruby script I run to update the data (requires the 'rest-client' gem):


Then, from an irb shell, I just run something like "print_last_blocks(13000)" (I change 13000 so that it only prints the blocks since the last time I ran it), and it spits out a bunch of comma separated values that I copy and paste into a gnumeric spreadsheet. In the spreadsheet, I have a dynamically computed column for the 360 block moving average.

Did you host a pool? There are thing you need to configure to work. And there are thing I can't notice unless there are people hashing on the pool.

Hello
It's possible to do my pads with different stagger?
I am now in 2048 and I wanted to add a HDD but I get this message:
It probably Takes too long to read the scoops! Consider stagger larger sizes
I would like to add my next hdd in 4096

Oops I forgot to change the google translation
You have a lot of merit, thank you for translating. 
And thank you for your answer 

for payment please access http://burst.cryptoport.io/acc/5846652537316771321

last 24hr not found block , but i has send my 9500 burst to pool balance and pay some account

found block  = payout
not found block = no pay out  <----  wrong ?


           

It's still a luck thing, just the pool reduces the variability, kinda makes it like blocks are 100x smaller, but 100x easier to find....

Ok, but why you did that?