[NEW POOL & MINER] - BitcoinPool.com - Jump In! ~NO FEES~ :)

[FairUser]

Well, it is worth what it is worth. I'm now using your miner exclusively, so there you go

Don't let my word be taken the wrong way, you've done an amazing work. Not only did you get the miner to search the full key space, which is the way I like it, you also give out very helpful information while mining, something that was really lacking. Kudos to you, and btc's too once this miner renders me some

Thank you very much!

[1714265982]

1714265982

[1714265982]

1714265982

[1714265982]

1714265982

[1714265982]

1714265982

[geebus]

This efficiency number is a bit misleading, IMO.

There is no guarantee that a solution exists in a 'getwork' data unit.

Better to rename "efficiency" as "luck."  It is more clear.

It's "efficiency" in the sense that it's the percentage of how close you are to a 1:1 ratio of getworks asked to answers submitted. It's more "efficient" in regards to a pool because it causes less traffic on the server, and allows for more users to connect and participate, thus increasing the potential for blocks to be solved at a faster rate.

The miner itself yields results at the same speed as the core version of m0mchill's miner, but with a greatly reduced network load.

ef·fi·cien·cy [ih-fish-uhn-see]
–noun, plural -cies.

1) the ratio of the work done or energy developed by a machine, engine, etc., to the energy supplied to it, usually expressed as a percentage.

By dictionary definition, our miner fork is more efficient if you're looking at the getworks as "energy" and answers as "work done".

[FairUser]

By asking a CPU Miner (or any miner that isn't at least some X% of the network's total power) to process the entire getwork solution space before performing another GetWork, you are dooming that Miner to a very significant percentage of Stale shares.

Yup, you're right.  CPU miners are doomed either way.  Either they ask for new work so fast that they don't even have a chance at getting through 1% of a single getwork request, or they risk working too long on a getwork and the network's block count increases by one making their work stale.  CPU miner's are simply too slow to be able to run at a high efficiency against any pool, or even the bitcoin network at this point.  Because the average block is solved in less time than it takes on a average CPU to process even 1 getwork all the way through, it's really not worth using a CPU to mine for bitcoins at this point.

When taking GPU's vs CPU's, it's truly a night and day difference.  You could take the most powerful DUAL CPU/QUAD CORE Intel server (~12,700 khash/s) and run it against a ATI 5750 card (~150,000 khash/s) and the ATI card will smoke that server hands down...we've tried.  

We built and tested this the Pool with GPU's.  
Could you imagine us trying to build and test a pool with CPU's?! ROFL  

[TinkerToyTech]

Think of it as printing lottery tickets instead of money, you printing outthe chance for a chacne at some real money,


and if someone can go through the paces for gpu mining for throttable minimg for meand can perhaps help me set it up
I would arrange payment in a say, tv card for the US, I have a couple AVERMEDIA ATSC cards around and I'll mail you
one in payment if you can help me get setup mining wiht my cpu and dual gpu on a single card.  Please.  email
kc0edo@yahoo.com or @tinkerToyTech on the twitter and that facebook thing

This efficiency number is a bit misleading, IMO.

There is no guarantee that a solution exists in a 'getwork' data unit.

Better to rename "efficiency" as "luck."  It is more clear.

It's "efficiency" in the sense that it's the percentage of how close you are to a 1:1 ratio of getworks asked to answers submitted. It's more "efficient" in regards to a pool because it causes less traffic on the server, and allows for more users to connect and participate, thus increasing the potential for blocks to be solved at a faster rate.

The miner itself yields results at the same speed as the core version of m0mchill's miner, but with a greatly reduced network load.

ef·fi·cien·cy [ih-fish-uhn-see]
–noun, plural -cies.

1) the ratio of the work done or energy developed by a machine, engine, etc., to the energy supplied to it, usually expressed as a percentage.

By dictionary definition, our miner fork is more efficient if you're looking at the getworks as "energy" and answers as "work done".

[FairUser]

Think of it as printing lottery tickets instead of money, you printing outthe chance for a chacne at some real money,

and if someone can go through the paces for gpu mining for throttable minimg for me and can perhaps help me set it up
I would arrange payment in a say, tv card for the US, I have a couple AVERMEDIA ATSC cards around and I'll mail you
one in payment if you can help me get setup mining wiht my cpu and dual gpu on a single card.  Please.  email
kc0edo@yahoo.com or @tinkerToyTech on the twitter and that facebook thing

I'll be happy to help you out, no payment is necessary.  Maybe a donation once we get you up and you've been able to mine for awhile.

PM me the following information:
- What type of video card do you currently have
- What the driver version is for your video card
 

[M4v3R]

What about payouts? When are you paying the BTC and how can I change the threshold?

[geebus]

What about payouts? When are you paying the BTC and how can I change the threshold?

We pay as soon as the block is confirmed, and currently, it will pay whatever you've earned, rounded to the 8th digit after the decimal for compatibility with bitcoind. We explain it in our FAQ.

We'll be adding payment thresholds later.

[FairUser]

I just tested ufasoft's CPU miner.

I was unable to connect to our pool.
I used wireshark to take a closer look at what is going on.  Here is what I found:


POST / HTTP/1.1
Content-Length: 43
Host: bitcoinpool.com:8334
Cache-Control: no-cache

{"method": "getwork", "params": [], "id":0}HTTP/1.0 401 not authorized


The red text is the response from our server.
The blue test is the request to our server.
It appears that this CPU miner is somehow missing the "Authorization" in the HTTP headers when making the request. 
I haven't used this client before, so I attempted to use it on slush's pool too.  It didn't work their either.

So how many people have gotten this miner to work??
I would also be curious to know how you got it working...because I can't see how it's Authenticating to the pool servers. 
I did enter my login and password on the command line, but it doesn't look like it's sending that information to the server in anyway....which would be the a very good reason why it is not working for some of you! 

Hopefully ufasoft will fix this issue soon.

(This was tested on a Win7 x64 w/ Intel I7 quad core.)

[nster]

I just tested ufasoft's CPU miner.

I was unable to connect to our pool.
I used wireshark to take a closer look at what is going on.  Here is what I found:


POST / HTTP/1.1
Content-Length: 43
Host: bitcoinpool.com:8334
Cache-Control: no-cache

{"method": "getwork", "params": [], "id":0}HTTP/1.0 401 not authorized


The red text is the response from our server.
The blue test is the request to our server.
It appears that this CPU miner is somehow missing the "Authorization" in the HTTP headers when making the request. 
I haven't used this client before, so I attempted to use it on slush's pool too.  It didn't work their either.

So how many people have gotten this miner to work??
I would also be curious to know how you got it working...because I can't see how it's Authenticating to the pool servers. 
I did enter my login and password on the command line, but it doesn't look like it's sending that information to the server in anyway....which would be the a very good reason why it is not working for some of you! 

Hopefully ufasoft will fix this issue soon.

(This was tested on a Win7 x64 w/ Intel I7 quad core.)

-a 5 -t 8 -o host@host.com:#### -u XXXXXXXX -p XXXXXXXXX is how you are supposed to set it up

I'm using it with deepbit's pool (deepbit.net) it also works with btcmine.com's miner

[kseistrup]

OK, we made a change.  Auto-banning is turned off for now.  CPU miners are safe.

Thanks, mate(s)! 

[FairUser]

-a 5 -t 8 -o host@host.com:#### -u XXXXXXXX -p XXXXXXXXX is how you are supposed to set it up

I'm using it with deepbit's pool (deepbit.net) it also works with btcmine.com's miner

Here's what I'm trying:

C:\Users\User>C:\Users\User\Downloads\bitcoin-miner.exe -a 60 -t 4 -o http://bitcoinpool.com:8334/ -u MYusername -p MYpassword
bitcoin-miner 0.3.2  Copyright (c) 2011 Ufasoft  http://ufasoft.com/open/bitcoin

4 threads       Using SSE2
0 MHash/s

It just sits their @ 0 MHash/s.  I also looked under wireshark, and it's still not passing the "Authorization" header.
I don't see how a pool could track this miner's answer without using the Authorization header to know which worker is who's....

<very confused>    

Please correct me if I'm running the command incorrectly.  I don't see much documentation on it.

[M4v3R]

Hm... at current rate, it seems to pay moreless on my 5850 than other pools. But I'll have to mine longer to be sure.

Edit: I did the calculations wrong. It actually paid less, approx. 0.1 BTC per hour.

[kseistrup]

Enhancement request:  Please show datetimes in UTC (seems to be PST for now?).

Rationale:  Once I have figured out the time difference between the pool server and me, it'as easy to convert the timestamps on the website to localtime.  However, countries switch to and from daylight saving time using different rules, and so each user has to take into account the DST rules that prevail at the pool server.  It would be somewhat safe to say that most users can convert from UTC to his own timezone on the fly, hence my request.

Cheers,

[geebus]

Hm... at current rate, it seems to pay moreless on my 5850 than other pools. But I'll have to mine longer to be sure.

Edit: I did the calculations wrong. It actually paid less, approx. 0.1 BTC per hour.

We pay based on the amount you're contributing vs what the whole group has contributed. If you're getting paid less, you're contributing a smaller portion of the whole.

[geebus]

-a 5 -t 8 -o host@host.com:#### -u XXXXXXXX -p XXXXXXXXX is how you are supposed to set it up

I'm using it with deepbit's pool (deepbit.net) it also works with btcmine.com's miner

I dug through the source code of Ufasoft's miner.

Basically, most miners (poclbm, diablominer, rpc-miner, jgarzik's cpu miner) work like this:

Client (Request for Getwork w/ Authorization Headers included) --> Server
Server (Respond with Getwork) --> Client
Client (Send Hash from Getwork) --> Server
Server (Respond with Accepted, or Invalid/Stale) --> Client

Ufasoft's Miner works like this:
Client (Request Getwork) --> Server
Server (Prompt for Authorization) --> Client
Client (Respond with Credentials) --> Server
Server (Respond with Getwork) --> Client
Client (Send Hash from Getwork) --> Server
Server (Prompt for Authorization) --> Client
Client (Respond with Credentials) --> Server
Server (Respond with Accepted, or Invalid/Stale) --> Client

Twice as much network traffic, and incompatible with our pool simply because they don't include the credentials in the headers on every request.

Maybe you can email ufasoft about it and see if they can modify the way their miner works.

[LMGTFY]

I dug through the source code of Ufasoft's miner.
...
Twice as much network traffic, and incompatible with our pool simply because they don't include the credentials in the headers on every request.

Maybe you can email ufasoft about it and see if they can modify the way their miner works.

[Tycho] (deepbit) has already raised this with ufasoft. Apparently it's because of the HTTP library ufasoft is using. I don't know if ufasoft is planning to remedy that - it kind of sounds like [Tycho] added a workaround to deepbit.

[geebus]

Enhancement request:  Please show datetimes in UTC (seems to be PST for now?).

Rationale:  Once I have figured out the time difference between the pool server and me, it'as easy to convert the timestamps on the website to localtime.  However, countries switch to and from daylight saving time using different rules, and so each user has to take into account the DST rules that prevail at the pool server.  It would be somewhat safe to say that most users can convert from UTC to his own timezone on the fly, hence my request.

Cheers,

I changed all dates to show GMT/UTC instead of server timezone (GMT-8).

[kseistrup]

I changed all dates to show GMT/UTC instead of server timezone (GMT-8).

Cool, thanks! 

[xenon481]

By asking a CPU Miner (or any miner that isn't at least some X% of the network's total power) to process the entire getwork solution space before performing another GetWork, you are dooming that Miner to a very significant percentage of Stale shares.

Yup, you're right.  CPU miners are doomed either way.  Either they ask for new work so fast that they don't even have a chance at getting through 1% of a single getwork request, or they risk working too long on a getwork and the network's block count increases by one making their work stale.  CPU miner's are simply too slow to be able to run at a high efficiency against any pool, or even the bitcoin network at this point.  Because the average block is solved in less time than it takes on a average CPU to process even 1 getwork all the way through, it's really not worth using a CPU to mine for bitcoins at this point.

When taking GPU's vs CPU's, it's truly a night and day difference.  You could take the most powerful DUAL CPU/QUAD CORE Intel server (~12,700 khash/s) and run it against a ATI 5750 card (~150,000 khash/s) and the ATI card will smoke that server hands down...we've tried.  

We built and tested this the Pool with GPU's.  
Could you imagine us trying to build and test a pool with CPU's?! ROFL  

So you admit that your pool too favors faster miners when you specifically (incorrectly in every way except your one shortsighted emotions over statistics way) chided Slush's pool for doing so in your OP.

[...] or “weight based shares" (slush's pool) which favors faster cards [...]

And only getting ~12,700khash/s is ridiculously low for a high end Intel CPU. People are reporting upwards of ~24,000khash/s when mining with their CPUs.

[shackleford]

Thanks for the pool guys. Slush's pool is closed and it looks like you are trying to make it more efficient to allow more people in.

To spite the thread being peppered with ^prick remarks it is appreciated.  Hope we get a block soon.