gistfile1.txt

--- Log opened Thu Jun 16 13:30:54 2011
13:30 -!- Irssi: Starting query in freenode with rikurr
13:30 <rikurr> ok, for how long do you plan to stay online? I got a distress call from a good friend of mine.
13:34 <masterkorp> i am online 24/7 buddie
13:35 <masterkorp> you can query me the problem even if i am away and i will handle it as soon as i can
13:35 <masterkorp> so no horries
13:38 <rikurr> ok, great
--- Log closed Thu Jun 16 13:43:51 2011
--- Log opened Fri Jun 17 03:44:15 2011
03:44 -!- Irssi: Starting query in freenode with rikurr
03:44 <rikurr> crashed to bed after coming to home from gym around 2am. Let's try again today.
--- Log closed Fri Jun 17 03:49:52 2011
--- Log opened Fri Jun 17 05:10:31 2011
05:10 <masterkorp> sure
--- Log closed Fri Jun 17 05:15:52 2011
--- Log opened Fri Jun 17 05:54:01 2011
05:54 <rikurr> ok do you know what this is about?
--- Log closed Fri Jun 17 05:59:52 2011
--- Log opened Fri Jun 17 06:06:17 2011
06:06 <masterkorp> no
06:06 <masterkorp> i know its about C
--- Log closed Fri Jun 17 06:11:52 2011
--- Log opened Fri Jun 17 06:37:38 2011
06:37 <rikurr> ok. The source is here: https://github.com/jgarzik/pushpool/commit/4c57a66012e9098a166843ca3427807945bbf1f5
06:37 <rikurr> err sorry here: https://github.com/jgarzik/pushpool
06:38 <rikurr> it's a pool mining component written in C for bitcoin/namecoin mining
06:41 <masterkorp> let me guess it doesn't work ? :)
--- Log closed Fri Jun 17 06:46:52 2011
--- Log opened Fri Jun 17 07:21:51 2011
07:21 <rikurr> sorry, busy at the office from time to time.
07:21 <rikurr> So..
07:24 <rikurr> pushpool has hardcoded in a shortcut to check whether the submitted hash has high enough value to be a potential solution and only submits those upstream
07:24 <rikurr> and it was written for bitcoin, which has a lot higher difficulty than namecoin has at the moment
07:24 <rikurr> https://en.bitcoin.it/wiki/Difficulty
07:25 <rikurr> It simply checks ath nth char of the hex hash is still 0. Whereas the proper way of checking whether to submit the solution to upstream would be:
07:27 <rikurr> hash < target
07:27 <rikurr> target is the negative of difficulty. So higher target means easier difficulty.
07:27 <rikurr> An example code of how that's done in a python pool is here:
07:28 <rikurr> http://yyz.us/bitcoin/poold.py - around line 204
07:29 <rikurr> and the shortcut pushpool takes is at msg.c line 304
07:30 <rikurr> Se would like to modify pushpool to to the actual hash < target checking when deciding whether to submit the solution to upstream or not
07:30 <rikurr> *so
07:30 <rikurr> s/Se/So We/
07:35 <rikurr> You would basically have to implement the calculation of difficulty -> target
07:37 <rikurr> I've read the code a lot, so please ask if there is anything unclear.
07:37 <rikurr> I just don't know C at all.
07:38 <rikurr> the data_str passed to check_hash is the hash the user has submitted.
--- Log closed Fri Jun 17 07:43:52 2011
--- Log opened Fri Jun 17 08:12:20 2011
08:12 <rikurr> https://en.bitcoin.it/wiki/Target
--- Log closed Fri Jun 17 08:17:52 2011
--- Log opened Fri Jun 17 19:49:48 2011
19:49 <masterkorp> sorry no time today, gona start it tomorrow
--- Log closed Fri Jun 17 19:54:52 2011
--- Log opened Fri Jun 17 20:16:07 2011
20:16 <rikurr> ok, let me know
--- Log closed Fri Jun 17 20:21:52 2011
--- Log opened Sat Jun 18 15:18:56 2011
15:18 <rikurr> any progress or news?
--- Log closed Sat Jun 18 15:24:53 2011
--- Log opened Sat Jun 18 15:25:22 2011
15:25 <masterkorp> sorry man
15:25 <masterkorp> i am studying the code
15:25 <masterkorp> it might take a while
15:28 <rikurr> hmm
--- Log closed Sat Jun 18 15:33:53 2011