Bitcoin Forum
December 10, 2016, 01:34:49 AM *
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 ... 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 [130] 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 ... 205 »
  Print  
Author Topic: bitHopper: Python Pool Hopper Proxy  (Read 333096 times)
Litt
Sr. Member
****
Offline Offline

Activity: 350


View Profile
August 05, 2011, 09:13:49 PM
 #2581

I'm holding back on 24 and dig for a bit until they have proved themselves more. I've given them some shares for the current round as a test and that would be that. I will try all the new pools once, but after that they need to be proven worthy as Clipse is saying imo. I had similar issue with poolmunity's json, though I never sent any shares in and won't until they've paid out a couple blocks. Someone also said poolmunity wasn't good for another reason, but wasn't told what. Maybe someone can shed some light?

Trying to maximize the profit efficiency by hopping more pools is great and all, but for me it's more about the philosophy that I'm hopping and not being hopped on that matters most rather than risking too much at these new pools. Wink I say Bithasher having 8 blocks under it's belt is a sweetspot personally to be invited for a piece of my pie slice.



1481333689
Hero Member
*
Offline Offline

Posts: 1481333689

View Profile Personal Message (Offline)

Ignore
1481333689
Reply with quote  #2

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

Posts: 1481333689

View Profile Personal Message (Offline)

Ignore
1481333689
Reply with quote  #2

1481333689
Report to moderator
1481333689
Hero Member
*
Offline Offline

Posts: 1481333689

View Profile Personal Message (Offline)

Ignore
1481333689
Reply with quote  #2

1481333689
Report to moderator
c00w
Full Member
***
Offline Offline

Activity: 196


View Profile
August 05, 2011, 09:44:01 PM
 #2582

I fixed some DB problems and LP looks fixed. So I tagged v0.1.1. If you're running a version which is moderately newish this is probably what you want to use.

1HEmzeuVEKxBQkEenysV1yM8oAddQ4o2TX
paraipan
Legendary
*
Offline Offline

Activity: 924


Firstbits: 1pirata


View Profile WWW
August 05, 2011, 09:53:24 PM
 #2583

json reset again lol

fucking lovely, ill just have to use the regex stats for now assuming those are correct.

small request to you clipse: can you put a little bit more attention when it resets to see if it's a 0 or a sub 100 value ? (a predictable value), can be circumvented ignoring a reset when in that range

edit: I actually don't  monitor this pool anymore, but when did, I've seen that strange resets too

BTCitcoin: An Idea Worth Saving - Q&A with bitcoins on rugatu.com - Check my rep
simonk83
Hero Member
*****
Offline Offline

Activity: 896


View Profile
August 05, 2011, 09:57:56 PM
 #2584

Ok, here's the test to see if Slush is fixed Wink

EDIT:  All good Smiley
Clipse
Hero Member
*****
Offline Offline

Activity: 504


View Profile
August 05, 2011, 10:23:10 PM
 #2585

json reset again lol

fucking lovely, ill just have to use the regex stats for now assuming those are correct.

small request to you clipse: can you put a little bit more attention when it resets to see if it's a 0 or a sub 100 value ? (a predictable value), can be circumvented ignoring a reset when in that range

edit: I actually don't  monitor this pool anymore, but when did, I've seen that strange resets too

It resets to 0 and counts onwards then eventually corrects to the actual round shares, then it resets again(atleast it happened twice like this today on the JSON)

...In the land of the stale, the man with one share is king... >> Clipse

We pay miners at 130% PPS | Signup here : Bonus PPS Pool (Please read OP to understand the current process)
Clipse
Hero Member
*****
Offline Offline

Activity: 504


View Profile
August 05, 2011, 10:34:55 PM
 #2586

Ive wondered about the following error whenever I switch to bitclockers.

Code:
[00:33:00] LP triggered from server bitclockers
[00:33:00] Error in json decoding, Probably not a real LP response

Is this normal at all?

...In the land of the stale, the man with one share is king... >> Clipse

We pay miners at 130% PPS | Signup here : Bonus PPS Pool (Please read OP to understand the current process)
pbj sammich
Sr. Member
****
Offline Offline

Activity: 272


Fighting Liquid with Liquid


View Profile
August 05, 2011, 10:41:41 PM
 #2587

So I've been out of the loop for most of the week with work issues, and I come here and there's like 30+ new pages  Huh

Anyway just git pull and am running

Still a little confused on the slice scheduler - is it on by default now or do I need to do something different to slice?


edit: alot of work done this week geez, really appreciate it c00w et al
Clipse
Hero Member
*****
Offline Offline

Activity: 504


View Profile
August 05, 2011, 10:53:25 PM
 #2588

So I've been out of the loop for most of the week with work issues, and I come here and there's like 30+ new pages  Huh

Anyway just git pull and am running

Still a little confused on the slice scheduler - is it on by default now or do I need to do something different to slice?


edit: alot of work done this week geez, really appreciate it c00w et al

Default is normal slicescheduler, you can pass the cmd --scheduler OldDefaultScheduler or just doublecheck the spelling by launching hopper with --listschedulers

...In the land of the stale, the man with one share is king... >> Clipse

We pay miners at 130% PPS | Signup here : Bonus PPS Pool (Please read OP to understand the current process)
MaGNeT
Legendary
*
Offline Offline

Activity: 1050


Founder of Orlycoin | O RLY? YA RLY!


View Profile WWW
August 05, 2011, 11:18:29 PM
 #2589

I don't understand the "penalty" option in the user.cfg

What does it do?  Can I use it for other pools than Slush? What would be the effect of a higer or a lower value? Smiley
hawks5999
Full Member
***
Offline Offline

Activity: 168



View Profile WWW
August 05, 2011, 11:26:38 PM
 #2590

I don't understand the "penalty" option in the user.cfg

What does it do?  Can I use it for other pools than Slush? What would be the effect of a higer or a lower value? Smiley

higher penalties make the pool less likely to be chosen all other things being equal.

for example, if two pools are at 20%, the one with lower penalty will be chosen.

■ ▄▄▄
■ ███
■ ■  ■               
LEDGER  WALLET    ████
■■■ ORDER NOW! ■■■
              LEDGER WALLET
Smartcard security for your BTCitcoins
■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■
Decentralized. Open. Secure.
msb8r
Member
**
Offline Offline

Activity: 78


View Profile WWW
August 05, 2011, 11:31:08 PM
 #2591

I fixed some DB problems and LP looks fixed. So I tagged v0.1.1. If you're running a version which is moderately newish this is probably what you want to use.

I think you introduced a new one, though.

Whenever BH writes to database, no further submitted shares are updated, or if they are they're not showing up on the webpage.

Example starting with no database.
Before first "writing to database" user shares are updated for pool 1. As soon as the message shows up, user shares stay static.
Switching to pool 2, the same behaviour is evident. User shares for pool 2 updates up till the point that changes are written to the database, and then stay static.

Stales are still updating though, and as far as I can tell it has no impact on performance.

New Bitcoin directory @ http://btcdir.org/
MaGNeT
Legendary
*
Offline Offline

Activity: 1050


Founder of Orlycoin | O RLY? YA RLY!


View Profile WWW
August 05, 2011, 11:33:14 PM
 #2592

I don't understand the "penalty" option in the user.cfg

What does it do?  Can I use it for other pools than Slush? What would be the effect of a higer or a lower value? Smiley

higher penalties make the pool less likely to be chosen all other things being equal.

for example, if two pools are at 20%, the one with lower penalty will be chosen.

Thanks Smiley I'll play around with it tomorrow.
It's 1:32 AM over here... Bye!
djex
Full Member
***
Offline Offline

Activity: 196


View Profile
August 06, 2011, 12:26:01 AM
 #2593

I fixed some DB problems and LP looks fixed. So I tagged v0.1.1. If you're running a version which is moderately newish this is probably what you want to use.

I think you introduced a new one, though.

Whenever BH writes to database, no further submitted shares are updated, or if they are they're not showing up on the webpage.

Example starting with no database.
Before first "writing to database" user shares are updated for pool 1. As soon as the message shows up, user shares stay static.
Switching to pool 2, the same behaviour is evident. User shares for pool 2 updates up till the point that changes are written to the database, and then stay static.

Stales are still updating though, and as far as I can tell it has no impact on performance.

I can confirm this.

Smiley  : 1LbvSEJwtQZKLSQQVYxQJes8YneQk2yhE3
owowo
Jr. Member
*
Offline Offline

Activity: 43


View Profile
August 06, 2011, 12:40:34 AM
 #2594

just downloaded. somehow the shares count at the statspage is getting stuck, stales are ok. I stopped, bitHopper and deleted stats.db but it's stuck again... I'm on ubuntu.
Clipse
Hero Member
*****
Offline Offline

Activity: 504


View Profile
August 06, 2011, 12:50:34 AM
 #2595

Anyone figured out a way to get these 2 pools supported yet? I know Ed said he got btcmp working but still testing it, any update?

http://www.btcmp.com/

https://pool.itzod.ru/


...In the land of the stale, the man with one share is king... >> Clipse

We pay miners at 130% PPS | Signup here : Bonus PPS Pool (Please read OP to understand the current process)
gtrrkicw
Newbie
*
Offline Offline

Activity: 26



View Profile
August 06, 2011, 01:29:42 AM
 #2596

I fixed some DB problems and LP looks fixed. So I tagged v0.1.1. If you're running a version which is moderately newish this is probably what you want to use.

I think you introduced a new one, though.

Whenever BH writes to database, no further submitted shares are updated, or if they are they're not showing up on the webpage.

Example starting with no database.
Before first "writing to database" user shares are updated for pool 1. As soon as the message shows up, user shares stay static.
Switching to pool 2, the same behaviour is evident. User shares for pool 2 updates up till the point that changes are written to the database, and then stay static.

Stales are still updating though, and as far as I can tell it has no impact on performance.

I can confirm this.

I thought it was just me... I'm seeing this too

Did you find this helpful? 1PMwrmT32UGro7ufcQdsoWzZiQYq7L15sj
joulesbeef
Sr. Member
****
Offline Offline

Activity: 476


moOo


View Profile
August 06, 2011, 01:30:47 AM
 #2597

Code:
1:29:36] slush: 4817926
1:29:36] RPC request [getwork] submitted to DigBTC.net (DigBIT)
1:29:36] RPC request [getwork] submitted to DigBTC.net (DigBIT)
1:29:36] RPC request [getwork] submitted to DigBTC.net (DigBIT)
1:29:37] RPC request [getwork] submitted to DigBTC.net (DigBIT)
1:29:37] RPC request [getwork] submitted to DigBTC.net (DigBIT)
1:29:38] RPC request [getwork] submitted to DigBTC.net (DigBIT)
1:29:38] RPC request [getwork] submitted to DigBTC.net (DigBIT)
1:29:38] RPC request [getwork] submitted to DigBTC.net (DigBIT)
1:29:39] RPC request [getwork] submitted to DigBTC.net (DigBIT)
1:29:39] RPC request [getwork] submitted to DigBTC.net (DigBIT)
1:29:39] RPC request [getwork] submitted to DigBTC.net (DigBIT)
1:29:40] RPC request [getwork] submitted to DigBTC.net (DigBIT)
1:29:40] RPC request [getwork] submitted to DigBTC.net (DigBIT)
1:29:40] RPC request [getwork] submitted to DigBTC.net (DigBIT)
1:29:41] RPC request [getwork] submitted to DigBTC.net (DigBIT)
1:29:41] RPC request [getwork] submitted to DigBTC.net (DigBIT)
1:29:41] RPC request [getwork] submitted to DigBTC.net (DigBIT)
1:29:42] RPC request [getwork] submitted to DigBTC.net (DigBIT)
1:29:42] btcpool24: 977187
1:29:42] RPC request [getwork] submitted to DigBTC.net (DigBIT)
1:29:43] RPC request [getwork] submitted to DigBTC.net (DigBIT)


is the newest version supposed to do this sooo much?

mooo for rent
muyoso
Member
**
Offline Offline

Activity: 84



View Profile
August 06, 2011, 01:39:21 AM
 #2598

Code:
1:29:36] slush: 4817926
1:29:36] RPC request [getwork] submitted to DigBTC.net (DigBIT)
1:29:36] RPC request [getwork] submitted to DigBTC.net (DigBIT)
1:29:36] RPC request [getwork] submitted to DigBTC.net (DigBIT)
1:29:37] RPC request [getwork] submitted to DigBTC.net (DigBIT)
1:29:37] RPC request [getwork] submitted to DigBTC.net (DigBIT)
1:29:38] RPC request [getwork] submitted to DigBTC.net (DigBIT)
1:29:38] RPC request [getwork] submitted to DigBTC.net (DigBIT)
1:29:38] RPC request [getwork] submitted to DigBTC.net (DigBIT)
1:29:39] RPC request [getwork] submitted to DigBTC.net (DigBIT)
1:29:39] RPC request [getwork] submitted to DigBTC.net (DigBIT)
1:29:39] RPC request [getwork] submitted to DigBTC.net (DigBIT)
1:29:40] RPC request [getwork] submitted to DigBTC.net (DigBIT)
1:29:40] RPC request [getwork] submitted to DigBTC.net (DigBIT)
1:29:40] RPC request [getwork] submitted to DigBTC.net (DigBIT)
1:29:41] RPC request [getwork] submitted to DigBTC.net (DigBIT)
1:29:41] RPC request [getwork] submitted to DigBTC.net (DigBIT)
1:29:41] RPC request [getwork] submitted to DigBTC.net (DigBIT)
1:29:42] RPC request [getwork] submitted to DigBTC.net (DigBIT)
1:29:42] btcpool24: 977187
1:29:42] RPC request [getwork] submitted to DigBTC.net (DigBIT)
1:29:43] RPC request [getwork] submitted to DigBTC.net (DigBIT)


is the newest version supposed to do this sooo much?


I think that is the reason Bitclockers kills bithopper.  Too many getworks.  Switched to CherryPicker yesterday to test it out and OMFG:



Worked flawlessly.  Just need to figure out what Cherrypicker is doing differently and emulate it.  Also, I am getting .2% stales with Cherrypicker and never got below 4% stales with bithopper. . . . . .

Edit:  In fact, I am getting DRASTICALLY less stales on every pool.  Like by a factor of 10. 

I drink it up!
joulesbeef
Sr. Member
****
Offline Offline

Activity: 476


moOo


View Profile
August 06, 2011, 01:44:27 AM
 #2599

also just got my first payment with rfc pool.

their last block was invalid? how does that exactly happen? shouldnt those shares be added to the next block? in calc prop?

and bitclockers seems to be screwing with me more than ever today.


Quote
I think that is the reason Bitclockers kills bithopper.  Too many getworks.  Switched to CherryPicker yesterday to test it out and OMFG:


the massive getworks is new.

and those rejects are comparable to bithopper most of the time. but yeah we should see what is the difference between how cherry picker does bitclocker

the only thing i can see is they use a slightly different api addy..

going to try it... see if it helps

theirs http://bitclockers.com/api.json
ours api_address: https://bitclockers.com/api
and no https

hmmm

mooo for rent
Clipse
Hero Member
*****
Offline Offline

Activity: 504


View Profile
August 06, 2011, 01:47:15 AM
 #2600

also just got my first payment with rfc pool.

their last block was invalid? how does that exactly happen? shouldnt those shares be added to the next block? in calc prop?

and bitclockers seems to be screwing with me more than ever today.


Quote
I think that is the reason Bitclockers kills bithopper.  Too many getworks.  Switched to CherryPicker yesterday to test it out and OMFG:


the massive getworks is new.

and those rejects are comparable to bithopper most of the time. but yeah we should see what is the difference between how cherry picker does bitclocker

the only thing i can see is they use a slightly different api addy..

going to try it... see if it helps

theirs http://bitclockers.com/api.json
ours api_address: https://bitclockers.com/api
and no https

hmmm


I think for bitclockers we should just throttle the getworks , sure we could lose 1-2% efficiency or get a few more idle miner instances but atleast we would flood their pool with massive getworks, for some reason it seems my hopper loves to pull much more getworks than submits and only seems to happen with bitclockers.

The server timeouts isnt api/json related either, I even used my own custom json host that only pulled updates 1nc every 5mins and bitclockers still died. Its somewhere between bithopper and the way bithopper managed getworks that is stuffing with bitclockers and none of the other pools. Weird.

...In the land of the stale, the man with one share is king... >> Clipse

We pay miners at 130% PPS | Signup here : Bonus PPS Pool (Please read OP to understand the current process)
Pages: « 1 ... 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 [130] 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 ... 205 »
  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!