Guys, I know there is many things to improve, but I'm focused mainly to new core right now. I believe that better mining efficiency has much higher priority than stats :-).

+10 he does really nice stuff.

Exactly.


If you have some connections in your bitcoin client, don't see any errors in miner and your card is working (because you can submit shares/blocks to the pool), then everything is working fine.

It's still quite high. With the default miner ask rate (5 seconds), the normal ratio of stale shares is around ~1-3%.

I'm watching pool console right now and there are no problems, so the higher-than-expected stale rate should be something on your side.

What _exactly_ do you need? The actual BTC/USD quote is available on mtgox and if you want to cover the risk with counter trades, you can do it by few clicks. You can even counter trade the amount firstly on the mtgox and then use the final rate as input for your real-world trade.

Yes, this was an temporary issue of the pool, bitcoin client crashed for no particular reason. Now it is OK.


Yes, there is difference between those pools. My pool is analyzing every submitted share in realtime and deepbit accept all submits and analyze them later. So the fact that you see more stale shares in my pool is not a bug, it is a feature.

But yes, the thing you reported was an issue of the pool, it's without debate.

I don't think it is stability. It is just lack of interest. Look at the volume...

Price is going sideways in the channel, but it will become wild market again. It just need one large trade to make other panicking.

Please don't use unicode characters in worker name and password. I changed password for worker work46, it should work now.

Thanks, 60 trades is very nice number for such young service :-).

Btw I'd like to ask you if you're considering some better design for coinpal/coincard in the future. I think you offer great services, but many people asked me if there are some troubles with the site. Friend told me that it looks like the site has broken link to it's CSS file :-).

mndrix, I'm curious how many trades on coincard do you have daily. Can you reveal at least rough numbers? :-)

Pool experienced some troubles in last two hours, you probably hit many timeouts and stale submits in this time. Restarting bitcoin daemons helped and now I'm discussing those problems in bitcoind with Gavin.

Alternative clients strictly following official rules are wildly welcome (at least from me). Unfortunately, those rules are often badly documented, so it is pretty hard to follow them. When some alternative client with badly implemented rules takes significant part of Bitcoin network, there is a risk of blockchain split and then collapse of whole network.

This is true when those versions do something. Currently, we have many implementations where each does practically nothing. I preffer to have one alternative implementation which cover original functionality as much as possible than have many implementations where every can just connect to another node, receive a message and die. I call it "split of the effort".

I cannot say anything, because I didn't write any of those implementations, but writing YABNI from the scratch doesn't make sense for me.

There is only limited amount of free transactions every hour. As Bitcoin popularity is going up, those slots are full time to time. To speed up transaction processing, you can offer some fee in the client settings. Then the transaction will be included ASAP.

Try to search recent forum posts, yesterday somebody posted PERL code for parsing mtgox quotes...

Edit: Link to Perl module is on the wiki. Nice job, mndrix!

I think that ISTJ fits to me perfectly and I still (at least partially) understand the Bitcoin .

I can confirm, have strange issues on Ubuntu (for example, third and fourth cards are detected, but does not work). This weekend I'm going to complete reinstall to Debian, I hope it helps.

What do you exactly mean? As I understand your project correctly, you're doing (yet another) bitcoin node implementation...

Did you considered building pycoin on the top of ArtForz half-node source lying somewhere on the pastebin.com? I see that you duplicated some of his great job. I have also fork of his node running on the Twisted framework (in fact it needed only few tweaks), which is very robust and can be easily integrated with Qt, for example.

I didn't published my fork, because my job with the node isn't done yet, but if you're interested, I can send it to you right now. It would be nice to work on the same core and don't split the power between two very similar projects.

I have wet dreams about full bitcoin client implementation in python, so I appreciate any progress on it.

Edit: I'm talking about this client code written by ArtForz. There is newer version lying around, which solve storing the blockchain to the disk, but I cannot find the link.

This is little offtopic, but the right reason why I closed registration was that in the some point pool started to grow exponentially (difficulty was low, bitcoin price was high and somebody slashdotted it) and I was too slow in adding more and more bitcoinds . For current pool users, there is no reason for making pool even bigger; more ghash/s does not add any benefit for them.