You're doing it wrong. Simply run the script and then open data file in sierrachart.

What is login refresh?

Try latest version, it fixes issues like this.

I must say that I never used Sierrachart DOM, it's pretty new feature. I also failed in finding API documentation and doubt that it will work on expired trial .

Of course. This is absolutely independent on any external subject. Actually script is downloading data from mtgox (using web services) and storing them to Sierrachart's proprietary dataformat to local disk. SierraChart then update graph (in realtime) from this file...

I have no idea how many people is using this stuff - please let me know!

Thanks for making this clear. Yes, this mtgox plugin and realtime charting work even with expired trial of SierraChart.

Version 0.2 is out. It uses another, more stable websocket library. Feed should be more stable and much faster now.

Btw - do you know any good service like github, but for mercurial? I like social layer of github, but prefer hg...

Is there anybody willing to sell 1oz gold bars (with certificate) for bitcoins, delivery in Europe?

Soon.


Fortunately no

To be correct - yes, this is possible. There can be more valid responses for one getwork request.

Yes, everything is going fine, 600k shares (block #4417) isn't anything abnormal with current difficulty.

yes

Today I found similar abnormal activity on bitcoin p2p port like during weekend. I have no idea what was going on, because bitcoin logs say nothing. I decided to limit bitcoin p2p connections only to some range of IPs to eliminate chance that somebody is trying to do something nasty. Unfortunately it looks like those I/O problems caused two invalid blocks (#4371 and #4360). After limiting p2p only to several IPs, p2p and I/O activity stopped. I'll be watching this in following days even more.

Yes, I know about that. Unfortunately last troubles were not about freeze/crash. Bitcoind was up and running, but was just crazy slow because of I/O storm for some unknown reason.

Nice to know .


Well, will be enough coloring the workers (on profile page) in red when there is no share in last minute?


I have absolutely no idea. There is API on mtgox which give you bitcoin address for sending funds, but have no idea about LR api.

Working on new pool core, current one has some limitations. Working LP will be ready in following two weeks.


Last attack was not related to getwork layer, so IP graylisting won't help anyhow. But good idea for next DDoS issue .


There are newly some pool users who has phone contact to me for case of some troubles. I also trust one man enough that I'm considering to give him ssh access to pool machines so they will be able to repair stuff when I will be on summer holiday...

It won't be necessary to register separate worker for every miner instance very soon, I'm working on core improvements...


Actually this is already presented on account page, just commented out for some reasons. Try to use greasemonkey script, which enable this in GUI for you...


Actually you have time of last submit here already, but agree that some visual thing would be nice.


Well, it is so 'cheap' to copy this feature from deepbit and I don't think it is really *needed* .


Long polling is planned (it is related to 'more miner on one account' stuff). I'm not sure if instant payout is so necessary, because you can set threshold to something low and pool will send you money in nearest payout, which is every hour... I don't like 'instant payout' because it is mostly spamming the network; mass payouts every hour are much better from this point.

There is a huge difference - closed source pool cannot access your computer. As you're sending every small bit of earned bitcoins to your wallet from the pool, there is no chance how I can steal your coins.

Usually I'm not paranoid (I'm using Windows, Skype etc), but realistic, because there was malicious software stealing wallets before some time already.

No, it is a bug in library which the script use. Will be solved in following bugfix release...