Bitcoin Forum
December 10, 2016, 04:48:59 PM *
News: To be able to use the next phase of the beta forum software, please ensure that your email address is correct/functional.
 
   Home   Help Search Donate Login Register  
Pages: « 1 [2] 3 »  All
  Print  
Author Topic: New mining pool for testing (now closed)  (Read 19689 times)
slush
Legendary
*
Offline Offline

Activity: 1358



View Profile WWW
February 02, 2011, 09:06:30 PM
 #21


It would be nice to say to potential users that this version is vulnerable and may not be used in production.

Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1481388539
Hero Member
*
Offline Offline

Posts: 1481388539

View Profile Personal Message (Offline)

Ignore
1481388539
Reply with quote  #2

1481388539
Report to moderator
1481388539
Hero Member
*
Offline Offline

Posts: 1481388539

View Profile Personal Message (Offline)

Ignore
1481388539
Reply with quote  #2

1481388539
Report to moderator
1481388539
Hero Member
*
Offline Offline

Posts: 1481388539

View Profile Personal Message (Offline)

Ignore
1481388539
Reply with quote  #2

1481388539
Report to moderator
zipslack
Jr. Member
*
Offline Offline

Activity: 43


View Profile
February 03, 2011, 03:16:33 AM
 #22

It would be nice to say to potential users that this version is vulnerable and may not be used in production.

Do you care to explain that statement? It resembles a baseless accusation.  Wink
jgarzik
Legendary
*
Offline Offline

Activity: 1470


View Profile
February 03, 2011, 04:02:38 AM
 #23

It would be nice to say to potential users that this version is vulnerable and may not be used in production.

Do you care to explain that statement? It resembles a baseless accusation.  Wink

slush is right, but he's being terse because we discussed the vulnerabilities in private...  Once my further changes survive testing on this new mining pool, I'll update the code again.

Jeff Garzik, bitcoin core dev team and BitPay engineer; opinions are my own, not my employer.
Donations / tip jar: 1BrufViLKnSWtuWGkryPsKsxonV2NQ7Tcj
ColdHardMetal
Hero Member
*****
Offline Offline

Activity: 701



View Profile
February 03, 2011, 05:51:32 AM
 #24

The pool found its first block last night, block # 105839.

Now that a block is in the database, work on statistics may commence.

My miner has been connected for a few days so should have some shares in that block. It's slow so it wouldn't have been a large %. Do you have a minimum BTC level threshold before you send coins out?

jgarzik
Legendary
*
Offline Offline

Activity: 1470


View Profile
February 03, 2011, 11:11:34 PM
 #25

This mining pool test has been a smashing success.  Thanks to all who helped out with their CPU/GPU cycles.  Here's a quick briefing.


1. What was being tested?
--------------------------------------------------------------------
I'm working on a suite of bitcoin-related services.  Mining pool capability is a small part of that.  This was a live test of code that will be deployed in production later on.  We found many bugs that a static, in-house test could have never found.  slush was also very generous with advice and cautionary warnings.

To thank the community for the help, the core server source code has been GPL'd and released:  http://yyz.us/bitcoin/poold.py   However, it should be noted that that server is missing several data validations that need to occur (to prevent cheating).



2. What is the current status of the pool?
--------------------------------------------------------------------
Only one block was ever generated by the pool (which IMO is fantastic, given current difficulty, short notice and informal nature of this new pool)

You can get real-time stats at http://pool.yyz.us/stats.cgi

As I consider this a concluded test, I will be shutting down the pool next week -- hopefully enough time to generate another block for the remaining folks who contributed shares.  I have switched my own GPU miners back to slush's pool, though my CPU miners are still pointed at pool.yyz.us.



3. What is the status of the payout -- where my money?
-------------------------------------------------------------------------------------------
We have one block (50 BTC), which was confirmed 87 blocks ago as of this writing.

Based on a technical reading of slush's site, I wrote the software so that only miners who got shares in the block we generated got credit:  "When the pool mints a block, only users who worked on that block are rewarded, and only for work they did on that block."  But apparently I wrote the software incorrectly, because people expected to be rewarded based on shares contributed to all blocks up to and including the newly minted 50BTC block.

So according to my software, this is the winning distribution based on those who worked on block 105839,
     mine319.pit00     211
     mine300pit04     48
     BitCoinPurse     7
     worker102     2
     immaminer     2
     Raulo     2
     wtf     2
     test     1
     mine319.pit00     1

That excludes shares contributed on blocks prior to 105839, and some ~18 hours of shares in the current round, and those records cannot easily be recreated due to since-fixed software bugs.

So, since it's only 50 BTC and I don't want to argue endlessly about it, as a compromise I am going send 1.00 BTC to each of 41 registered users, and then divide the remaining 9 BTC up according to the distribution above.

If the mining pool mints another 50 BTC block in the next ~5 days or so, those share records are present, and I can do a real, slush-like distribution of the reward.  After that, the pool server will be shut down.



4.  What comes next?
---------------------------------------------
Here are some tantalizing hints:
  • push-based mining (current RPC miners poll for new work every few seconds)
  • geographically distributed mining servers in the US, Eur and Asia, for best possible latency
  • additional share rewards -- sometimes we might want to compensate you above the 50 BTC reward itself, because your mining increases the security and value of our network

Jeff Garzik, bitcoin core dev team and BitPay engineer; opinions are my own, not my employer.
Donations / tip jar: 1BrufViLKnSWtuWGkryPsKsxonV2NQ7Tcj
jgarzik
Legendary
*
Offline Offline

Activity: 1470


View Profile
February 04, 2011, 12:28:29 AM
 #26

So, since it's only 50 BTC and I don't want to argue endlessly about it, as a compromise I am going send 1.00 BTC to each of 41 registered users, and then divide the remaining 9 BTC up according to the distribution above.

This payout has been made.

Jeff Garzik, bitcoin core dev team and BitPay engineer; opinions are my own, not my employer.
Donations / tip jar: 1BrufViLKnSWtuWGkryPsKsxonV2NQ7Tcj
LZ
Staff
Legendary
*
Offline Offline

Activity: 1456


Satoshi everywhere!


View Profile WWW
February 04, 2011, 12:39:49 AM
 #27

Got it, thanks! By the way, what indices have I to create for users, shares and credits tables in the database?

"Never invest unless you can afford to lose your entire investment." © S3052
Anonymous
Guest

February 04, 2011, 01:12:02 AM
 #28

Added my miniscule khashes to the pool lol.


Protip - a pentium D cpu is not the best for mining  Cheesy


jgarzik
Legendary
*
Offline Offline

Activity: 1470


View Profile
February 04, 2011, 01:22:21 AM
 #29

Got it, thanks! By the way, what indices have I to create for users, shares and credits tables in the database?

Not sure I want to give out all the secret sauce Wink  Left as an exercise to the reader.

Jeff Garzik, bitcoin core dev team and BitPay engineer; opinions are my own, not my employer.
Donations / tip jar: 1BrufViLKnSWtuWGkryPsKsxonV2NQ7Tcj
slush
Legendary
*
Offline Offline

Activity: 1358



View Profile WWW
February 04, 2011, 09:26:30 AM
 #30

and those records cannot easily be recreated

So, shortly said, this is a scam. gene, where are you???

(edit: I hope it is obvious that I'm kidding.)

BitCoinPurse
Jr. Member
*
Offline Offline

Activity: 34



View Profile
February 04, 2011, 01:51:39 PM
 #31

I got my 1.23 BTC, which will be worth $2,856,092,198.89 someday! 

I enjoyed helping the experiment.

My Coin Purse is sagging!  13WXS46x634zook2MHSJbc7gwdrXK1JLq4
Raulo
Full Member
***
Offline Offline

Activity: 238


View Profile
February 04, 2011, 02:04:57 PM
 #32

Based on a technical reading of slush's site, I wrote the software so that only miners who got shares in the block we generated got credit:  "When the pool mints a block, only users who worked on that block are rewarded, and only for work they did on that block."  But apparently I wrote the software incorrectly, because people expected to be rewarded based on shares contributed to all blocks up to and including the newly minted 50BTC block.

But what you programmed is actually a perfect pool-abuse countermeasure that I realized after reading about your method:
http://bitcointalk.org/index.php?topic=3165.0

Instead of switching to slush's method, you should keep this one.

1HAoJag4C3XtAmQJAhE9FTAAJWFcrvpdLM
jgarzik
Legendary
*
Offline Offline

Activity: 1470


View Profile
February 04, 2011, 11:44:14 PM
 #33

The pool will be shut down Monday at 11:59pm EST.  Until then, I'm keeping my CPU miners going on it, at least Smiley

Jeff Garzik, bitcoin core dev team and BitPay engineer; opinions are my own, not my employer.
Donations / tip jar: 1BrufViLKnSWtuWGkryPsKsxonV2NQ7Tcj
motherhumper
Newbie
*
Offline Offline

Activity: 16


View Profile
February 05, 2011, 11:16:38 AM
 #34

 Cheesy lol $2,856,092,198.89 per bitcoin?  how did you com up with that number?  Grin
jgarzik
Legendary
*
Offline Offline

Activity: 1470


View Profile
February 08, 2011, 04:59:00 AM
 #35

The pool has been shut down.  Thanks to all who helped test!  Only one block was found during this test, from beginning to end.

Jeff Garzik, bitcoin core dev team and BitPay engineer; opinions are my own, not my employer.
Donations / tip jar: 1BrufViLKnSWtuWGkryPsKsxonV2NQ7Tcj
baitzor
Newbie
*
Offline Offline

Activity: 6


View Profile
February 10, 2011, 03:41:51 AM
 #36

I'm interested in starting my own mining server, got most of it down, all I have to implement is the getwork method, for geting new hashes, is the latest poold.py the one I should be looking at?

Where did you get starting on reading about getwork, or did you just look up the code from the bitcoin client?

Sharecoin: SRJqrhniPqytd3MovDfr5L9rr8LC9hxzJp
jgarzik
Legendary
*
Offline Offline

Activity: 1470


View Profile
February 10, 2011, 04:48:46 AM
 #37

I'm interested in starting my own mining server, got most of it down, all I have to implement is the getwork method, for geting new hashes, is the latest poold.py the one I should be looking at?

Where did you get starting on reading about getwork, or did you just look up the code from the bitcoin client?

You will need to intimately understand the mining process, notably the binary layout of the 80-byte bitcoin block headers.  The best reference is the C++ source code for the official bitcoin client.

Jeff Garzik, bitcoin core dev team and BitPay engineer; opinions are my own, not my employer.
Donations / tip jar: 1BrufViLKnSWtuWGkryPsKsxonV2NQ7Tcj
Cdecker
Hero Member
*****
Offline Offline

Activity: 487



View Profile WWW
February 10, 2011, 11:27:27 AM
 #38

The pool has been shut down.  Thanks to all who helped test!  Only one block was found during this test, from beginning to end.
I assume it didn't go all that well, I'm sorry to hear it. It's always been my opinion that if we really must have pools (instead of running hundreds of independent miners) we should have many of them to chose from, as to avoid central points of failure. Should slush turn out to be taken down or replaced by a malicious entity we'd have a problem at hand.

Meanwhile, thank you for publishing part of your code, I'll use it in my own mining rig if that's ok, and if someone can confirm that it actually works Cheesy

Want to see what developers are chatting about? http://bitcoinstats.com/irc/bitcoin-dev/logs/
Bitcoin-OTC Rating
jgarzik
Legendary
*
Offline Offline

Activity: 1470


View Profile
February 10, 2011, 07:37:44 PM
 #39

The pool has been shut down.  Thanks to all who helped test!  Only one block was found during this test, from beginning to end.
I assume it didn't go all that well, I'm sorry to hear it.

Scroll up for test results ("smashing success").

Quote
It's always been my opinion that if we really must have pools (instead of running hundreds of independent miners) we should have many of them to chose from, as to avoid central points of failure. Should slush turn out to be taken down or replaced by a malicious entity we'd have a problem at hand.

I agree, the more pools, the better for bitcoin.  That's why I published my code!

Jeff Garzik, bitcoin core dev team and BitPay engineer; opinions are my own, not my employer.
Donations / tip jar: 1BrufViLKnSWtuWGkryPsKsxonV2NQ7Tcj
dishwara
Legendary
*
Offline Offline

Activity: 1386

Truth may get delay, but NEVER fails


View Profile
February 11, 2011, 08:08:16 AM
 #40

U saying u closed the mining pool?

coz i just registered & try to run & got error

problem communicating with RPC....
Pages: « 1 [2] 3 »  All
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!