Bitcoin Forum
March 19, 2024, 03:00:25 AM *
News: Latest Bitcoin Core release: 26.0 [Torrent]
 
   Home   Help Search Login Register More  
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 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 ... 205 »
  Print  
Author Topic: bitHopper: Python Pool Hopper Proxy  (Read 355541 times)
hawks5999
Full Member
***
Offline Offline

Activity: 168
Merit: 100



View Profile WWW
July 24, 2011, 06:10:53 PM
 #941

I agree with joules. Pool op's and 24/7 miners get so self righteous about hopping. Yet as we've seen, when pools are hopper friendly they solve blocks faster than comparable size pools who try to block hoppers. Exhibit A: bitp.it. When they were hop friendly they were scoring several blocks. Then they started faking and blocking and got stuck on a 6 day round.
Exhibit B: mtred. They have yet to implement anti pool hopping techniques and are consistently pulling in blocks. Their 24/7 miners whine about hoppers but don't realize the benefit they receive from hoppers. So if they start to mess with stats or otherwise go anti-hopper then we should all just turn them off and let them flail.

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

Posts: 1710817225

View Profile Personal Message (Offline)

Ignore
1710817225
Reply with quote  #2

1710817225
Report to moderator
1710817225
Hero Member
*
Offline Offline

Posts: 1710817225

View Profile Personal Message (Offline)

Ignore
1710817225
Reply with quote  #2

1710817225
Report to moderator
BitcoinCleanup.com: Learn why Bitcoin isn't bad for the environment
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1710817225
Hero Member
*
Offline Offline

Posts: 1710817225

View Profile Personal Message (Offline)

Ignore
1710817225
Reply with quote  #2

1710817225
Report to moderator
bb
Member
**
Offline Offline

Activity: 84
Merit: 10


View Profile
July 24, 2011, 06:15:07 PM
 #942

[ ] You understand this.
MaGNeT
Legendary
*
Offline Offline

Activity: 1526
Merit: 1002


Waves | 3PHMaGNeTJfqFfD4xuctgKdoxLX188QM8na


View Profile WWW
July 24, 2011, 06:20:54 PM
 #943

I agree with joules. Pool op's and 24/7 miners get so self righteous about hopping. Yet as we've seen, when pools are hopper friendly they solve blocks faster than comparable size pools who try to block hoppers. Exhibit A: bitp.it. When they were hop friendly they were scoring several blocks. Then they started faking and blocking and got stuck on a 6 day round.
Exhibit B: mtred. They have yet to implement anti pool hopping techniques and are consistently pulling in blocks. Their 24/7 miners whine about hoppers but don't realize the benefit they receive from hoppers. So if they start to mess with stats or otherwise go anti-hopper then we should all just turn them off and let them flail.


There is no benefit from hoppers.
Only the hoppers benefit.

Finding blocks faster doesn't help anyone mining in a pool, it only makes the share of hoppers bigger and the ones of the non-hoppers smaller.
If you can't calculate that, don't blame me...
relm9
Hero Member
*****
Offline Offline

Activity: 840
Merit: 1000



View Profile
July 24, 2011, 06:30:32 PM
 #944

Something up with btcmonkey?

Getting error in pool api for it in the latest release, all other pools work fine
zybron
Member
**
Offline Offline

Activity: 66
Merit: 10



View Profile
July 24, 2011, 06:34:35 PM
 #945

Got this for poolmunity from the latest from c00w:

Code:
[14:26:10] LP Call poolmunity.com:8332/LP
[Failure instance: Traceback (failure with no frames): <class 'twisted.internet.
error.ConnectError'>: An error occurred while connecting: 10013: An attempt was
made to access a socket in a way forbidden by its access permissions..
]

Any ideas?

anty
Newbie
*
Offline Offline

Activity: 40
Merit: 0



View Profile WWW
July 24, 2011, 06:41:39 PM
 #946

Code:
[btcworld]
name: BTC World
mine_address: btcworld.de:8332
api_address:http://btcworld.de/statistics
role:info
api_method:re
api_key:Valid\s+shares\s+for\s+current\s+round:</th><td>([0-9]+(,[0-9]+)*)
api_strip:','
#CHANGE THIS
#http://btcworld.de/signup
user: user
pass: x

This works just fine when I run it through the steps (selectSharesResponse) in python cmd line, but not when I run it "live".
Try this regex:
Code:
api_key:Valid\s+shares\s+for\s+current\s+round:</th><td>([0-9]+(?:,[0-9]+)*)
This is untested, but the (?:[your RegEx here]) syntax is used if you want to group something but not generate a group in the output.
BitHopper now takes output.group(1) to get the difficulty from regex. That means the first string that you surround with parentheses. I don't know how nested groups are named, but when you use the (?:[your RegEx here]) syntax it shouldn't matter.
hawks5999
Full Member
***
Offline Offline

Activity: 168
Merit: 100



View Profile WWW
July 24, 2011, 06:43:20 PM
 #947

I agree with joules. Pool op's and 24/7 miners get so self righteous about hopping. Yet as we've seen, when pools are hopper friendly they solve blocks faster than comparable size pools who try to block hoppers. Exhibit A: bitp.it. When they were hop friendly they were scoring several blocks. Then they started faking and blocking and got stuck on a 6 day round.
Exhibit B: mtred. They have yet to implement anti pool hopping techniques and are consistently pulling in blocks. Their 24/7 miners whine about hoppers but don't realize the benefit they receive from hoppers. So if they start to mess with stats or otherwise go anti-hopper then we should all just turn them off and let them flail.


There is no benefit from hoppers.
Only the hoppers benefit.

Finding blocks faster doesn't help anyone mining in a pool, it only makes the share of hoppers bigger and the ones of the non-hoppers smaller.
If you can't calculate that, don't blame me...

What's more beneficial to 24/7 miners? Getting 1% of 4 blocks per day or getting 4% of 1 block every 4 days? If you can't calculate that, don't blame me.
Ask bitp.it miners if they preferred the time from July 13th to 18th or the time from the 18th to the 23rd. They may have gotten a smaller share but they got nothing for 6 days and when they finally got it, it didn't make up the lost coins.
And pool operators benefit from being able to advertise higher Gh/s rates in the forum. Nothing draws a crowd like a crowd. If you don't already have >1Th/s you are benefitted by hoppers.
In the end, non-hoppers will be viewed as solo miners and CPU miners. Nonhoppers are buggy whip manufacturers and we are in the automobile era.

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

Activity: 40
Merit: 0


View Profile
July 24, 2011, 07:21:10 PM
 #948

I agree with joules. Pool op's and 24/7 miners get so self righteous about hopping. Yet as we've seen, when pools are hopper friendly they solve blocks faster than comparable size pools who try to block hoppers. Exhibit A: bitp.it. When they were hop friendly they were scoring several blocks. Then they started faking and blocking and got stuck on a 6 day round.
Exhibit B: mtred. They have yet to implement anti pool hopping techniques and are consistently pulling in blocks. Their 24/7 miners whine about hoppers but don't realize the benefit they receive from hoppers. So if they start to mess with stats or otherwise go anti-hopper then we should all just turn them off and let them flail.


There is no benefit from hoppers.
Only the hoppers benefit.

Finding blocks faster doesn't help anyone mining in a pool, it only makes the share of hoppers bigger and the ones of the non-hoppers smaller.
If you can't calculate that, don't blame me...

What's more beneficial to 24/7 miners? Getting 1% of 4 blocks per day or getting 4% of 1 block every 4 days? If you can't calculate that, don't blame me.
Ask bitp.it miners if they preferred the time from July 13th to 18th or the time from the 18th to the 23rd. They may have gotten a smaller share but they got nothing for 6 days and when they finally got it, it didn't make up the lost coins.
And pool operators benefit from being able to advertise higher Gh/s rates in the forum. Nothing draws a crowd like a crowd. If you don't already have >1Th/s you are benefitted by hoppers.
In the end, non-hoppers will be viewed as solo miners and CPU miners. Nonhoppers are buggy whip manufacturers and we are in the automobile era.

Except it was more like this:  100% 50 coins of one block that may be found in 6 - 7 years.  The 300mhs that the pool was running at prior to the pool being hopped.

To a smaller amount of actual coins that were produced when the block was found because the hoppers.

Yes they are advertising 50Ghs now.
shotgun
Member
**
Offline Offline

Activity: 98
Merit: 11



View Profile
July 24, 2011, 07:25:19 PM
 #949

How does this proxy differ from the Flexible Mining Proxy: https://forum.bitcoin.org/index.php?topic=5506.0

I'm currently using that one and it works well. Not sure if they are for the exact same purpose though. Could I run both to get pool H/A and pool hopping? Hmmm... sort of not sure what the differences are between the two apps.

<luke-jr> Catholics do not believe in freedom of religion.
c00w (OP)
Full Member
***
Offline Offline

Activity: 196
Merit: 100


View Profile
July 24, 2011, 08:14:35 PM
 #950

1) Pool API Errors?
Well I think we crashed poolmonkey or triggered DDOS protections. I'm going to raise the lower limit from once every 10 seconds to once every 30.

2)Btcworld is added for hopping. bitp.it is added as a backup.

I can't get a translation of the x8s thread to work.

3)differences between this and flexible miner proxy?
This one hops. Oh and it changes servers in the case of server death etc... We also have LP support
I know they have support for individual worker statistics which we don't have yet.

1HEmzeuVEKxBQkEenysV1yM8oAddQ4o2TX
Rino
Newbie
*
Offline Offline

Activity: 38
Merit: 0


View Profile
July 24, 2011, 08:27:17 PM
 #951

triplemining just went nuts for me
api_key:-->([ 0-9]+)</td>
api_strip:' '
doesnt work for it anymore.
EskimoBob
Legendary
*
Offline Offline

Activity: 910
Merit: 1000


Quality Printing Services by Federal Reserve Bank


View Profile
July 24, 2011, 08:29:23 PM
 #952

did Triplemining managed to kick poolhoppers in the nuts?
Code:
[23:10:52] triple: 2,444,511
[23:11:14] triple: 600
[23:11:19] nofeemining: 6,849
[23:11:26] triple: 682
Caught, jsonrpc_call insides
'user'
[23:11:37] triple: 508
[23:11:46] triple: 1,387
[23:11:56] triple: 1,360
[23:12:06] triple: 811
[23:12:16] triple: 1,747
[23:12:17] nofeemining: 7,685
[23:12:26] triple: 988
[23:12:35] Error in pool api for triple
[23:12:46] triple: 1,393
[23:12:56] triple: 1,729
[23:13:06] triple: 537
[23:13:15] nofeemining: 8,591
[23:13:16] triple: 271
[23:13:26] triple: 881
 

I restarted the bitHopper and:

Code:
[23:23:49] Updating Difficulty
[23:23:49] 1690906.2047244
[23:23:49] Checking Database
[23:23:49] DB Verson: 0.1
[23:23:49] Database Setup
[23:23:50] triple: 1,474
[23:23:50] Server change to triple, telling client with LP
[23:23:50] mtred: 4,480,869
[23:23:50] nofeemining: 18,380
[23:23:50] RPC request [e83d3000] submitted to triplemining.com
Caught, jsonrpc_call insides
'user'
Caught, jsonrpc_call insides
'user'
...
and so on


While reading what I wrote, use the most friendliest and relaxing voice in your head.
BTW, Things in BTC bubble universes are getting ugly....
c00w (OP)
Full Member
***
Offline Offline

Activity: 196
Merit: 100


View Profile
July 24, 2011, 08:36:29 PM
 #953

1) Triple?
Yeah its down. They're doing some fancy lieing I can't figure out.
Its disabled in pool.cfg.default.

2) Being to sensitive with jumps?
If you are just doing a getwork we fail servers quickly because its easy to change servers. And otherwise miners will starve. Especially miners which give up quickly like poclbm.

If you are trying to submit work we won't change that requests server on you.

1HEmzeuVEKxBQkEenysV1yM8oAddQ4o2TX
Clipse
Hero Member
*****
Offline Offline

Activity: 504
Merit: 502


View Profile
July 24, 2011, 09:04:14 PM
 #954

dont bother, they are changing to PPLNS soon.

Rather get away from them now, let them see how hoppers revolting isnt a good thing 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)
MrSam
Member
**
Offline Offline

Activity: 112
Merit: 10



View Profile WWW
July 24, 2011, 09:10:53 PM
 #955

dont bother, they are changing to PPLNS soon.

Rather get away from them now, let them see how hoppers revolting isnt a good thing Wink

While i have no real problem with poolhoppers, but what disturbs me is that i (triplemining) get now like 10 /stats url requests every second and that starts to put a way to heavy load on my servers.

I would recommend a central database that is beeing polled by all users ..

Either way, Clipse is right and we will switch to PPLNS soon.
flower1024
Legendary
*
Offline Offline

Activity: 1428
Merit: 1000


View Profile
July 24, 2011, 09:15:28 PM
 #956

dont bother, they are changing to PPLNS soon.

Rather get away from them now, let them see how hoppers revolting isnt a good thing Wink

While i have no real problem with poolhoppers, but what disturbs me is that i (triplemining) get now like 10 /stats url requests every second and that starts to put a way to heavy load on my servers.

I would recommend a central database that is beeing polled by all users ..

Either way, Clipse is right and we will switch to PPLNS soon.


you could have placed a json file on your server which updates thrrough a cron-job.

buty anyway: good look with pplns Smiley

would be glad if you tell us before you'll switch.

to get triple working again:
open work.py
function: get
    header = {'User-Agent': ['Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20100101 Firefox/5.0'],'Content-Type': ['application/x-www-form-urlencoded'] }
    d = agent.request('GET', url, Headers(header), None)

(this is from an old version, but should not be very hard to adapt)
ahitman
Sr. Member
****
Offline Offline

Activity: 302
Merit: 250


View Profile
July 24, 2011, 09:16:57 PM
 #957

I agree, there must be a big load on servers due to all the hoppers polling, is it possible to use something like: http://btc-poolwatch.com/ to do a central stats poll and let the clients use that instead of pools directly?
MrSam
Member
**
Offline Offline

Activity: 112
Merit: 10



View Profile WWW
July 24, 2011, 09:19:56 PM
 #958

dont bother, they are changing to PPLNS soon.

Rather get away from them now, let them see how hoppers revolting isnt a good thing Wink

While i have no real problem with poolhoppers, but what disturbs me is that i (triplemining) get now like 10 /stats url requests every second and that starts to put a way to heavy load on my servers.

I would recommend a central database that is beeing polled by all users ..

Either way, Clipse is right and we will switch to PPLNS soon.


you could have placed a json file on your server which updates thrrough a cron-job.

buty anyway: good look with pplns Smiley

would be glad if you tell us before you'll switch.

Okay, i re-enabled the default so triplemining should work for everyone again now.
I will post a message here before we make the switch to pplns... In the meantime: Happy Mining
flower1024
Legendary
*
Offline Offline

Activity: 1428
Merit: 1000


View Profile
July 24, 2011, 09:20:25 PM
 #959

I agree, there must be a big load on servers due to all the hoppers polling, is it possible to use something like: http://btc-poolwatch.com/ to do a central stats poll and let the clients use that instead of pools directly?

i was already thinking about that.

the problem is this site is big target. it could easily be put offline.
atm i have my poolhopper running at a vserver and its publishing its stats per json.

but i am afraid of publishing this address.

also it would be easier for pools to fake stats explicity for that service.

i would do it for btc. but this could get into a fulltime job very fast.
EskimoBob
Legendary
*
Offline Offline

Activity: 910
Merit: 1000


Quality Printing Services by Federal Reserve Bank


View Profile
July 24, 2011, 09:24:29 PM
 #960

after last pull:

Code:
--- <exception caught here> ---
  File "/usr/lib/python2.7/site-packages/twisted/internet/base.py", line 793, in runUntilCurrent
    call.func(*call.args, **call.kw)
  File "/blah/MINER/bitHopper/pool.py", line 144, in update_api_server
    d = work.get(self.bitHopper.json_agent,info['api_address'],Headers({'User-Agent':'Mozilla/5.0 (X11; Linux i686) AppleWebKit/535.1 (KHTML, like Gecko) Ubuntu/11.04 Chromium/14.0.825.0 Chrome/14.0.825.0 Safari/535.1'}),None)
  File "/usr/lib/python2.7/site-packages/twisted/web/http_headers.py", line 141, in __init__
    self.setRawHeaders(name, values)
  File "/usr/lib/python2.7/site-packages/twisted/web/http_headers.py", line 201, in setRawHeaders
    "instance of %r instead" % (name, type(values)))
exceptions.TypeError: Header entry 'User-Agent' should be list but found instance of <type 'str'> instead

While reading what I wrote, use the most friendliest and relaxing voice in your head.
BTW, Things in BTC bubble universes are getting ugly....
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 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 ... 205 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!