Neighbourhood Pool Watch: Weekly network forecast 24th June 2013

24th June, 2013

Last post

Important:
These posts are a test of the methods used to create the forecasts, and definitely do not forecast non-MTGOX US$ / BTC price related changes - for example the current massive decrease in the cost of a hash. Please do not use the forecasts here for financial forecasts - these posts might be useful in that respect.

0.Introduction

I'm in a bit of a rush this week - I lost my network blocks database (and the backup) and had to regenerate everything from scratch. I have a pile of work ahead of me, so minimal comments and analysis this week.

From a quick look it seems more of the same. Only a slight (8 Thps) increase in the weekly average network hashrate, which gives the models a chance to catch up. The method 1 difficulty forecasts are looking a bit more accurate, which I'd expect since they're more flexible than method 2, although they have a higher variance in accuracy too.

I think method 1 is better to use when the network hashrate is very peaky and method 2 more accurate when network hashrate is much smoother.

1. Models and datasets:

The model datasets have been collected into one paste to save time. Model estimates have been likewise aggregated.

Forecast and canary model analysis

All datasets

All estimates

Canary model: An estimate of the current hashrate estimate based only on current price and previous network hashrates. Used to detect changes to the network caused by agents other than the direct action the MTGOX US$ / BTC price as determined by the model.

Models f1, f2, f3 and f4: These are the one, two, three and four week forecasts of the network hashrate, based on the modelled relationship between the MTGOX US$ / BTC and the network hashrate.

Difficulty modelling: Method one calculates a difficulty estimation using the network hashrate estimation and is recalculated each week. Method 2 calculates difficulty estimation based only on previous difficulties and the MTGOX price, and is only recalculated after each difficulty retarget.

2. Results

3. Charts

Chart 1:

A graphical history of the one, two, three and four week forecasts of the weekly average network hashrate compared to the actual network weekly average hashrate.

Chart 2:

A graphical history of the Canary model estimates of the weekly average network hashrate compared to the actual network weekly average hashrate.

Chart 3:

A graphical history of the last twenty six weeks of retarget date and difficulty estimates, actual retarget dates and actual difficulties. It should be noted that each retarget will often be forecast by two consecutive weekly forecasts, hence the multiple points per retarget on the new chart.

Chart 4:

A graphical history of the one, two, and three retarget forecasts of the Difficulty, modelled directly as a function of previous Difficulties and MTGOX US$ / BTC prices.