Bitcoin Forum
December 07, 2016, 12:33:02 PM *
News: Latest stable version of Bitcoin Core: 0.13.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 [24] 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 ... 205 »
  Print  
Author Topic: bitHopper: Python Pool Hopper Proxy  (Read 332856 times)
Clipse
Hero Member
*****
Offline Offline

Activity: 504


View Profile
July 18, 2011, 09:05:37 AM
 #461

The triplemining code worked except it spaz out api errors

I did add triplemining_user_apikey to password.py

...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)
1481113982
Hero Member
*
Offline Offline

Posts: 1481113982

View Profile Personal Message (Offline)

Ignore
1481113982
Reply with quote  #2

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

Posts: 1481113982

View Profile Personal Message (Offline)

Ignore
1481113982
Reply with quote  #2

1481113982
Report to moderator
1481113982
Hero Member
*
Offline Offline

Posts: 1481113982

View Profile Personal Message (Offline)

Ignore
1481113982
Reply with quote  #2

1481113982
Report to moderator
1481113982
Hero Member
*
Offline Offline

Posts: 1481113982

View Profile Personal Message (Offline)

Ignore
1481113982
Reply with quote  #2

1481113982
Report to moderator
Sukrim
Legendary
*
Offline Offline

Activity: 1848


View Profile
July 18, 2011, 09:10:22 AM
 #462

The triplemining code worked except it spaz out api errors

I did add triplemining_user_apikey to password.py

...and why? I don't see this being used anywhere in the code!

https://bitfinex.com <-- leveraged trading of BTCUSD, LTCUSD and LTCBTC (long and short) - 10% discount on fees for the first 30 days with this refcode: x5K9YtL3Zb
Mail me at Bitmessage: BM-BbiHiVv5qh858ULsyRDtpRrG9WjXN3xf
Clipse
Hero Member
*****
Offline Offline

Activity: 504


View Profile
July 18, 2011, 09:14:22 AM
 #463

The triplemining code worked except it spaz out api errors

I did add triplemining_user_apikey to password.py

...and why? I don't see this being used anywhere in the code!

hmmm good point Wink I got confused with the api inclusion in the first part of the code, my bad.

...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
July 18, 2011, 09:40:13 AM
 #464

I removed that api part from password.py and still get triplemining api error.

...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)
nob
Newbie
*
Offline Offline

Activity: 23


View Profile
July 18, 2011, 09:45:35 AM
 #465

i just pasted the code mentioned above into pool.py and everything was fine.

Have you imported re ?
Clipse
Hero Member
*****
Offline Offline

Activity: 504


View Profile
July 18, 2011, 09:59:34 AM
 #466

yeh I did, but quite possibly in the wrong file, should it be in pool.py or bithopper.py ? I put it in pool.py.

...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)
nob
Newbie
*
Offline Offline

Activity: 23


View Profile
July 18, 2011, 10:04:40 AM
 #467

uhm.. pool.py is correct
Clipse
Hero Member
*****
Offline Offline

Activity: 504


View Profile
July 18, 2011, 10:05:37 AM
 #468

yeh so my settings do check out however api doesnt meh

...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)
organofcorti
Donator
Legendary
*
Offline Offline

Activity: 1960


Poor impulse control.


View Profile WWW
July 18, 2011, 10:11:22 AM
 #469

ok seems to be working for me. Thanks again Sukrim!

OK, Clipse, if you are going to use the code as given with c00w's bitHopper, you'll need to remove the
Code:
'slice':-1, 'slicedShares':0,
from the code.

Bitcoin network and pool analysis 12QxPHEuxDrs7mCyGSx1iVSozTwtquDB3r
follow @oocBlog for new post notifications
Clipse
Hero Member
*****
Offline Offline

Activity: 504


View Profile
July 18, 2011, 10:16:21 AM
 #470

yeh I did remove the slice part since first tried with default c00w bithopper.

Will try now as is with slice bithopper.

...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)
organofcorti
Donator
Legendary
*
Offline Offline

Activity: 1960


Poor impulse control.


View Profile WWW
July 18, 2011, 10:33:19 AM
 #471

Sorry that didn't help. I have no idea what I did differently this time, but it's working with c00w's bithopper. Previously I got the same error as you.

On a different but related note, anyone tell me how to parse the following simple but nested json feed? looking for 'round_shares' doesn't work.

Code:
{"poolstats":{"hashrate_unit":"GH/s","hashrate":25.02,"workers":81,"round_time_unit":"seconds","round_time":177163,"round_shares":1120942}}


Bitcoin network and pool analysis 12QxPHEuxDrs7mCyGSx1iVSozTwtquDB3r
follow @oocBlog for new post notifications
Clipse
Hero Member
*****
Offline Offline

Activity: 504


View Profile
July 18, 2011, 10:35:14 AM
 #472

Sorry that didn't help. I have no idea what I did differently this time, but it's working with c00w's bithopper. Previously I got the same error as you.

On a different but related note, anyone tell me how to parse the following simple but nested json feed? looking for 'round_shares' doesn't work.

Code:
{"poolstats":{"hashrate_unit":"GH/s","hashrate":25.02,"workers":81,"round_time_unit":"seconds","round_time":177163,"round_shares":1120942}}



Weird yeh, seems to work with slice bithopper version, I double checked and compared with default bithopper version and except for removing sliced parts it checked out.

Anyhow, im test running sliced version now.

Btw, any reason bitpit is still enabled to mine with the slice bithopper version?

...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)
zybron
Member
**
Offline Offline

Activity: 66



View Profile
July 18, 2011, 10:52:12 AM
 #473

On a different but related note, anyone tell me how to parse the following simple but nested json feed? looking for 'round_shares' doesn't work.

Code:
{"poolstats":{"hashrate_unit":"GH/s","hashrate":25.02,"workers":81,"round_time_unit":"seconds","round_time":177163,"round_shares":1120942}}
Here's the line you'll need:
Code:
round_shares = int(info['poolstats']['round_shares'])

Clipse
Hero Member
*****
Offline Offline

Activity: 504


View Profile
July 18, 2011, 10:52:25 AM
 #474

Wow, this really feels like we're on a war footing.

The difference being that every strategy session from the PoolHopper side of the war takes place in a public forum. A public forum that is likely monitored by the PoolOperator side of the war.
i can set a private forum if needed Smiley

Would be handy for some counter measures, I think its good idea that pools change but we are helping them way to much without them having to do much work right now Wink

...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)
organofcorti
Donator
Legendary
*
Offline Offline

Activity: 1960


Poor impulse control.


View Profile WWW
July 18, 2011, 10:54:01 AM
 #475

Wow, this really feels like we're on a war footing.

The difference being that every strategy session from the PoolHopper side of the war takes place in a public forum. A public forum that is likely monitored by the PoolOperator side of the war.
i can set a private forum if needed Smiley

I dunno. The whole point is to be open and help the pool operators 'hop' to a better system. We're aiming to put ourselves out of business! By not hopping on a prop pool, miners are cheating themselves.

Bitcoin network and pool analysis 12QxPHEuxDrs7mCyGSx1iVSozTwtquDB3r
follow @oocBlog for new post notifications
Clipse
Hero Member
*****
Offline Offline

Activity: 504


View Profile
July 18, 2011, 10:54:27 AM
 #476

Mmm just started to get a ton of this.

Code:
12:53:38] OK NOT slicing because of arsbitcoin
[12:53:38] reslice 1: -1 677034 677034
[12:53:38] reslice 1: 63.9894742825 1094840.21559 1094840.21559
[12:53:38] OK NOT slicing because of eligius
[12:53:38] reslice 1: 183.360485614 730747 730307
[12:53:38] OK NOT slicing because of triplemining
[12:53:38] reslice 1: 95.5366532248 938434.470503 938434.470503
[12:53:38] OK NOT slicing because of multiclone
[12:53:38] reslice 1: -1 5977429 5977429
[12:53:38] reslice 1: -1 1295915 1295915
[12:53:38] reslice 1: -1 2939783 2939783
[12:53:38] reslice 1: -1 0 0
[12:53:38] slicing False
Caught, jsonrpc_call insides
Connection was refused by other side: 111: Connection refused.
Caught, jsonrpc_call insides
Connection was refused by other side: 111: Connection refused.
Caught, jsonrpc_call insides
Connection was refused by other side: 111: Connection refused.
Caught, jsonrpc_call insides
Connection was refused by other side: 111: Connection refused.
Caught, jsonrpc_call insides
Connection was refused by other side: 111: Connection refused.
Caught, jsonrpc_call insides
Connection was refused by other side: 111: Connection refused.
Caught, jsonrpc_call insides
Connection was refused by other side: 111: Connection refused.


This seems to happen when connecting to eligius and not ozcoin.

...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)
organofcorti
Donator
Legendary
*
Offline Offline

Activity: 1960


Poor impulse control.


View Profile WWW
July 18, 2011, 10:59:57 AM
 #477

On a different but related note, anyone tell me how to parse the following simple but nested json feed? looking for 'round_shares' doesn't work.

Code:
{"poolstats":{"hashrate_unit":"GH/s","hashrate":25.02,"workers":81,"round_time_unit":"seconds","round_time":177163,"round_shares":1120942}}
Here's the line you'll need:
Code:
round_shares = int(info['poolstats']['round_shares'])

Thank mate!

Bitcoin network and pool analysis 12QxPHEuxDrs7mCyGSx1iVSozTwtquDB3r
follow @oocBlog for new post notifications
organofcorti
Donator
Legendary
*
Offline Offline

Activity: 1960


Poor impulse control.


View Profile WWW
July 18, 2011, 11:13:03 AM
 #478

Mmm just started to get a ton of this.


Dude, you are having a crappy night! Hope you get it sorted. Maybe for the time being you should revert back to an earlier git clone that worked for you?

Bitcoin network and pool analysis 12QxPHEuxDrs7mCyGSx1iVSozTwtquDB3r
follow @oocBlog for new post notifications
Clipse
Hero Member
*****
Offline Offline

Activity: 504


View Profile
July 18, 2011, 11:22:10 AM
 #479

So heres a thought, anyone here consider putting together a theoretical luckbased approach ?

I know its been discussed here but I think it would still be interesting to actually do it.

Pull the last 2 or 3 blocks and see how far out of the difficulty range the avg is ie. 3blocks(just a number i like) combined gives 6million, that avg out at 2million per block so not terrible unlucky, however a different pool have their last 3 blocks at combined of 10million, thats > double avg difficulty per block thus we work a formula into the duration hopper should stay at this pool for this new block which would be the 1st block after the last 3blocks used for sample.

My rough approach would assume the following:

Right now we seem to use a 40% of diff approach, now if we use that as our base value and apply the difference of the last 3 blocks in example above we will get the following.

10million shares across 3blocks = 3333333.33 shares per block
This means the last 3 blocks lasted on avg 213% longer

We will then calculate our 40% into current difficulty which would be 625211.2 and add 213% which gives 1331699.85 difficulty thus the new difficulty for the selected pool to stay on for the 4th block(block just after the previous 3)

Now the reverse would be implied when a pool got really lucky in last 3blocks, thus we would be avoiding them or leave them far earlier than 40% of difficulty.

I hope this makes somewhat sense Wink it does in my twisted mind.

please note: This is some hectic thumbsucking, would be nice to check it out in practice.

...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
July 18, 2011, 11:24:26 AM
 #480

Mmm just started to get a ton of this.


Dude, you are having a crappy night! Hope you get it sorted. Maybe for the time being you should revert back to an earlier git clone that worked for you?

Those json errors only happen with eligius , bithopper or slice bithopper version. I wonder if they somehow banned my IP from connecting to their pool.

Anyhow no biggy, just removed them and its gone Wink

...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 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 [24] 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 ... 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!