I take no credit for any of the above. I just added an ID column to the miner table and a timestamp in the shares in the above post.
Which is wrong in every possible way. |
|
|
|
Sorry, I don't get what the problem is with the data provided. Can someone explain? Block 9437 was generated 2009-04-01 10:39:07 Block 9443 was generated 2009-04-01 11:56:56 Block 9446 was generated 2009-04-01 12:20:52 The number of confirmations maybe? Since in the so called 'data' they're quite high. Which back then, couldnt have been achieved. |
|
|
|
Hi,
I just fired up my bitcoin client to check my new mining payouts (from pools) and found a new entry that just says "Generated". It is about 0.44 BTC.
It appears neither in "Sent" nor in "Received", only in "All Transactions".
What is this?
This happens if you were on eligius, and werent there for a week. So you get paid whatever you had left. |
|
|
|
Yeah, sorry, but them fields are a tad bit incorrect. Flowz, before you start handing out 'templates' at least learn how the sizes work.
Mind providing a correcter version of it then? For starters, let's look at the pool_worker table. We see that the username has a max length of 255 characters. All good and everything...but The shares table's username field is capped at 120, meaning if i were to register with tgregereryt3483734u9euffjifuweu90ewur903u94u390udepojfsdifh098ur590u3ueojfpoidi ojr093ur903ejfiopjf09ur903ru03riewjijc90ru93309u3r It will get truncated to 120 characters when inserting shares in the DB. And if you decide to pull my stats from the shares table, you won't be able to, cause there is no such user that matches that username. If we look at the solution field, it's length is only 255 characters, while in truth it's 256 if i remember correctly. It's not very important, since phoenix itself ignores the last few bytes/characters of the solution so it doesnt send them, but for good practice, better set it to that amount. Also, are you seriously thinking someone is going to register with a password that is 255 characters long? Lol no, moreover it will be hashed. 64 characters for a password(max bytes for a sha256 hash), and from 60 to 80 for username is plenty. Also, not to brag, but i was the one who gave the table structure to xenland when he first started developing "miningFarm". Altho, this one, you posted differs. |
|
|
|
Now, open up msg.c and head down to the check_hash function, specifically the return of better_hash. It looks like it is checking a hard coded 40 bits of 0's. Won't I need to change this spot too? What should I change this to based on the 10, 50, 100 scenarios?
Correct. In addition to changing EASY_TARGET, you must update check_hash. IMHO the bounty should go to the person submitting a patch that makes difficulty variable, without recompiling the source code! Well no, cause then cgminer will be broken perhaps. |
|
|
|
|
Yeah, sorry, but them fields are a tad bit incorrect. Flowz, before you start handing out 'templates' at least learn how the sizes work.
|
|
|
|
Thanks xcooling, everything works now  |
|
|
|
|
You should have mentioned we need the Microsoft SDK for mstcpip.h as well as probably a few new stuff to the configure line.
|
|
|
|
@Dikidera, everyone on a forum gets pounded on every now and the - if you're as 4-channy as you seem you know that. We've all posted things on the spur of the moment we're not proud of, and we've all has people annoy us and there is always the temptation to keep the flame burning. But there is never an excuse for using all caps. So let's just pretend page 39 edit 39 and 40 didn't happen and start again.
I'm sure you could spend time 4-channing us, but this is a really good proxy once you understand how it works and why.
1. Pool hopping currently works well only on proportional pools and only when you have access to non-delayed total shares. Neither btcguild or deepbit provide usable total share stats.
2. bitHopper provides a user stats page you can access on your browser on 127.0.0.1 which shows efficiency. You'll be able to see it work and see how far ahead you are by using it.
3. Since I've been using bitHopper I've had 140% to 200% efficiency on pools we use, for a total of 160%. Multipool's efficiency is around 120%.
4. Challenges coming up: loss of usable pools stats.
If you do have real coding skills (which is what I assume you're referring to when you recommend we don't anger you, and not that you've had an accident with a radioactive substance and go green and ragey when you get cranky) then help the project! We could do with someone helping with html scraping.
Why is there a problem with delayed stats? Pool hopping is just that. You request work, send a share, switch, send a share, switch and so on....this is not how i imagine pool hopping to be. Sup Pinky, where is the Brain ? Did i give you permission to speak slave? dont't start another round of that shit, this time I will personally see that the guilty gets banned. I came here to read good stuff not the ppl's personal vendetta's btw: if a pool delays stats you cannot hopp in blindfolded, not knowing this tells us you are 1. a script kiddie jerkin' around 2. you are a pool op looking for trouble after seeing his pool hopped. In either case i recommend you reading at least some pages of this thread or go to another part of bitcoins.org forum, it' huge and you could fit perfectly in other thread  Do you...understand the meaning of what script kiddie means? I don't think you do. And no, i am not a pool operator though i did start writing my front end once only to find it a bother to maintain a pool. |
|
|
|
@Dikidera, everyone on a forum gets pounded on every now and the - if you're as 4-channy as you seem you know that. We've all posted things on the spur of the moment we're not proud of, and we've all has people annoy us and there is always the temptation to keep the flame burning. But there is never an excuse for using all caps. So let's just pretend page 39 edit 39 and 40 didn't happen and start again.
I'm sure you could spend time 4-channing us, but this is a really good proxy once you understand how it works and why.
1. Pool hopping currently works well only on proportional pools and only when you have access to non-delayed total shares. Neither btcguild or deepbit provide usable total share stats.
2. bitHopper provides a user stats page you can access on your browser on 127.0.0.1 which shows efficiency. You'll be able to see it work and see how far ahead you are by using it.
3. Since I've been using bitHopper I've had 140% to 200% efficiency on pools we use, for a total of 160%. Multipool's efficiency is around 120%.
4. Challenges coming up: loss of usable pools stats.
If you do have real coding skills (which is what I assume you're referring to when you recommend we don't anger you, and not that you've had an accident with a radioactive substance and go green and ragey when you get cranky) then help the project! We could do with someone helping with html scraping.
Why is there a problem with delayed stats? Pool hopping is just that. You request work, send a share, switch, send a share, switch and so on....this is not how i imagine pool hopping to be. Sup Pinky, where is the Brain ? Did i give you permission to speak slave? |
|
|
|
@Dikidera, everyone on a forum gets pounded on every now and the - if you're as 4-channy as you seem you know that. We've all posted things on the spur of the moment we're not proud of, and we've all has people annoy us and there is always the temptation to keep the flame burning. But there is never an excuse for using all caps. So let's just pretend page 39 edit 39 and 40 didn't happen and start again.
I'm sure you could spend time 4-channing us, but this is a really good proxy once you understand how it works and why.
1. Pool hopping currently works well only on proportional pools and only when you have access to non-delayed total shares. Neither btcguild or deepbit provide usable total share stats.
2. bitHopper provides a user stats page you can access on your browser on 127.0.0.1 which shows efficiency. You'll be able to see it work and see how far ahead you are by using it.
3. Since I've been using bitHopper I've had 140% to 200% efficiency on pools we use, for a total of 160%. Multipool's efficiency is around 120%.
4. Challenges coming up: loss of usable pools stats.
If you do have real coding skills (which is what I assume you're referring to when you recommend we don't anger you, and not that you've had an accident with a radioactive substance and go green and ragey when you get cranky) then help the project! We could do with someone helping with html scraping.
Why is there a problem with delayed stats? Pool hopping is just that. You request work, send a share, switch, send a share, switch and so on....this is not how i imagine pool hopping to be. |
|
|
|
Got a PM: Calling me a loser means insta-death. And i think my post was pretty straightforward.
Lol. Wonder if his parents know he is mining on their computer instead of doing his homework? It's not like i was hiding the PM. I just want you to learn, you don't ever fuck with diki. It's the other way around |
|
|
|
hey dikidera you just got reported to admin, watch your mouth when you go out in public. That goes to you too clipse
So? And two, it's not me that should watch it, but you. |
|
|
|
Yeah. Thats by design. btcguild lies through its api.
Eligius and arsbitcoin have fair algorithms so we use them as a backup when there is nothing to hop.
By default it hops:
mtred
rfcpool
x8s
triplemining
ozco
nofeemining
The others currently have bizarre payment algorithms or no reliable way to get share counts from.
So basically, btcguild doesnt work? |
|
|
|
1) RAWR?
Can we all calm down? Like seriously.
2) btcguild?
Yeah, I fixed that in the latest version of password.py.default. My bad.
Btcguild get's skipped and only eligius works. |
|
|
|
This hopping proxy needs A LOT OF WORK. It currently forces you to use EVERY pool specified in the password.py file. AND I DONT WANT THAT. you are smack dab in middle of an alpha development that is given freely to you. I'm not sure how to make that more clear. the Hopper does need work, it is being worked on as we speak. You dont walk up to someone with a half finished sand castle and scream "IT NEEDS WORK" and really not sure what you are doing mining bitcoins at all.. unless you came in the past month or so, it all took work just to get it to work. and you do realise that more sites = more luck = better pay? it is easy as hell to disable the sites, the people here are normally friendly as hell and put up with some noob asss shit all the time to help people. But fuck if anyone should put up with you. That is 1000% the wrong attitude and the wrong way to ask for help. You do realize how much effort is going into making the hopper? and you couldnt even make the effort to read the read me. I have to assume you are a troll cause there really arent that many people that stupid left on the net. One rule: Never, ever, ever make me angry, which you are doing right now. As for the readme, i read it...not much of an explanation there. Also, it seems it's NOT using btcguild. |
|
|
|
1) clipse?
I added the rate display to the flat version. can you confirm that the flat version shows rate as 5010 while the dynamic shows rate at 501?
Flat: localhost:8337/flat
This hopping proxy needs A LOT OF WORK. It currently forces you to use EVERY pool specified in the password.py file. AND I DONT WANT THAT. It doesnt support neither slush nor deepbit... you might want to read the thread or the files on github a little before spouting off that it needs A LOT OF WORK. you are a) wrong and b) uninformed if you DONT WANT THAT, then build your own. The only file on github is a README which says Copy password.py.default to a new file called password.py then modify the new
file to include your bitcoin addresses, and pool passwords, instead of mine. I never said i wanted to use every damn pool there is in that file. If i remove all the lines, the script dies.. |
|
|
|
1) clipse?
I added the rate display to the flat version. can you confirm that the flat version shows rate as 5010 while the dynamic shows rate at 501?
Flat: localhost:8337/flat
This hopping proxy needs A LOT OF WORK. It currently forces you to use EVERY pool specified in the password.py file. AND I DONT WANT THAT. It doesnt support neither slush nor deepbit... |
|
|
|
dikidera, many open source applications support libcurl 7.20.x and later. In 7.20 this eroor will be reprodused.
If you are using an old version of libcurl, why don't you just upgrade? I found it funny that you couldn't compile the miner with an old version...i mean, that's what it is, old. |
|
|
|
|
If you downclock the memory significantly, you will notice a drop in temps. But the main reason they have high temps in the first place is because they can't breathe in one mobo. I have two extra fans blowing at my 5850 and 5870, cause the 5850 does indeed go over 90C
|
|
|
|
|
Show Posts
