Bitcoin Forum
December 05, 2016, 08:32:28 AM *
News: Latest stable version of Bitcoin Core: 0.13.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 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 181 182 183 184 185 186 187 188 189 [190] 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 »
  Print  
Author Topic: bitHopper: Python Pool Hopper Proxy  (Read 332687 times)
ewibit
Legendary
*
Offline Offline

Activity: 1744


View Profile
August 23, 2011, 05:49:47 PM
 #3781

I got the same problem as @kbsbtc, BH just freeze the stats page and keep showing "writing to database", miner dies and have to close and run it again.. (v0.2.2.4-68 with --auth --p2pLP and OldDefaultScheduler)

Also getting a lots of "Not enough votes in one direction to make a decision"

and also I send my firsts shares to BtcGuild Smiley
exactly the same here...
1480926748
Hero Member
*
Offline Offline

Posts: 1480926748

View Profile Personal Message (Offline)

Ignore
1480926748
Reply with quote  #2

1480926748
Report to moderator
There are several different types of Bitcoin clients. Header-only clients like MultiBit trust that the majority of mining power is honest for the purposes of enforcing network rules such as the 21 million BTC limit. Full clients do not trust miners in this way.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1480926748
Hero Member
*
Offline Offline

Posts: 1480926748

View Profile Personal Message (Offline)

Ignore
1480926748
Reply with quote  #2

1480926748
Report to moderator
1480926748
Hero Member
*
Offline Offline

Posts: 1480926748

View Profile Personal Message (Offline)

Ignore
1480926748
Reply with quote  #2

1480926748
Report to moderator
r2edu
Member
**
Offline Offline

Activity: 68


View Profile
August 23, 2011, 05:58:04 PM
 #3782

https://bitcointalk.org/index.php?topic=32921.200

 Poll 
Question: do you think pool hopping is ethical? YES  2 (50%)
NO  2 (50%)
 
Total Voters: 4
 


The real poll must be: "do you think BMU pool ops are ethical?" :p

LOTS of problems with that pool since ever... close it down, is a fail after fail after fail heheh
ewibit
Legendary
*
Offline Offline

Activity: 1744


View Profile
August 23, 2011, 06:24:31 PM
 #3783

The real poll must be: "do you think BMU pool ops are ethical?" :p
all my shares from the _old_ pool are away  Shocked
hawks5999
Full Member
***
Offline Offline

Activity: 168



View Profile WWW
August 23, 2011, 06:30:30 PM
 #3784

The poll is pointless. If enough people say it's ethical does BMU turn off their hopper-cheating mechanism or if enough people say hopping is unethical will he just keep cheating hoppers?

I doubt the former will happen and the latter will happen regardless. When you have an unethical pool operator who has no qualms with cheating a portion of his clients, there is really no limit to how unethical he'll be.

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

Activity: 126


View Profile
August 23, 2011, 06:54:24 PM
 #3785

Anyone else getting an error where BitHopper stops after a period of time?

It just gets stuck...

[14:16:38] writing to database
[14:17:38] writing to database
[14:18:38] writing to database
[14:19:38] writing to database
[14:20:38] writing to database
[14:21:38] writing to database
[14:22:38] writing to database
[14:23:38] writing to database
r2edu
Member
**
Offline Offline

Activity: 68


View Profile
August 23, 2011, 07:11:17 PM
 #3786

mines always stuck after an "LP Call" to btcserv... 0.2.2.4-68

now I will try with 0.2.2.4-83
norulezapply
Sr. Member
****
Offline Offline

Activity: 475


View Profile
August 23, 2011, 08:15:31 PM
 #3787

Anyone else getting an error where BitHopper stops after a period of time?

It just gets stuck...

[14:16:38] writing to database
[14:17:38] writing to database
[14:18:38] writing to database
[14:19:38] writing to database
[14:20:38] writing to database
[14:21:38] writing to database
[14:22:38] writing to database
[14:23:38] writing to database


+1 for this since i got the latest version

EDIT: this still isn't fixed in the latest version... just a heads up.

I get an LP call then constant "writing to database" messages.
renders my miner useless until i restart bithopper Sad
occurs every 30 minutes approximately for me.

If my post helped, I'll happily accept a few bitmills!   15rGg6A1JFZV3b7TTbtpAaiYGdUD1e1oAm
Atroxes
Full Member
***
Offline Offline

Activity: 120



View Profile
August 23, 2011, 10:49:41 PM
 #3788

Regarding this issue: https://github.com/c00w/bitHopper/issues/177#issue_comment_form

Manual triggers for mine_deepbit pools

If a feature like this was added, being also able to execute this function through win/*nix commandline, would allow for extremely easy writing of tcl/mirc scripts that could catch blockannounces in certain IRC channels and do manual triggers. This would effectively enable hopping on pools like deepbit, btcguild etc.
user7516
Jr. Member
*
Offline Offline

Activity: 41


View Profile
August 23, 2011, 10:53:26 PM
 #3789

 Shocked OMG, look at slush's block #7543:
lucita777
Jr. Member
*
Offline Offline

Activity: 39


View Profile
August 23, 2011, 11:05:18 PM
 #3790

Shocked OMG, look at slush's block #7543:


Lots of BTC for anyone who was able to squeeze a share in. To bad I didn't  Cry
organofcorti
Donator
Legendary
*
Offline Offline

Activity: 1946


Poor impulse control.


View Profile WWW
August 23, 2011, 11:11:44 PM
 #3791

@deepceleron: how are you getting on with LP penalty - Did you end up with a significant increase in accuracy?

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

Activity: 1848


View Profile
August 24, 2011, 12:34:51 AM
 #3792

I still have a problem with p2pLP - My router seems to drop connections (like LP connections...) quite fast, so I rarely actually get Longpolls. I hoped p2pLP would still notify me of found blocks (didn't yet look deeply into the code to find out what's going on) but this doesn't seem to be the case.

Would it be possible to just set up an IRC bot that announces each block on the network and the (either confirmed or guessed) pool that owns it for people like me? The input could still come from bitHopper users via this ranking mechanism or whatever you actually use...

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
deepceleron
Legendary
*
Offline Offline

Activity: 1470



View Profile WWW
August 24, 2011, 12:48:56 AM
 #3793

@deepceleron: how are you getting on with LP penalty - Did you end up with a significant increase in accuracy?
I kinda gave up on it for a while. As you saw from my post like five pages back, I put in the delays to the results I had already gotten and analyzed that. The conclusion was that even after inputting (or auto-learning) and even hand-tuning the average delay for each pool, the current 'first pool wins' method is suboptimal. A better algorithm, that in my limited sample gave no false positives, is to take the average delay of all pools after correction, and then analyze each pool against this average to determine if one stands out above the standard deviation expected if no polled pools were the finding pool. This improves results, since you aren't merely comparing the winning pool against the second-fastest, you are averaging out the LP delay capriciousness of your baseline over 15 pools.

Secondly, I propose a better p2p-IRC result sharing format, where all pool new block LP receive times (and the getwork timestamp) are published raw to IRC by each miner, perhaps after gathering LPs for a 10 second period after the first response. This would be better than the current "I think this pool won" publishing method, as then similar averaging can be done by the bithopper software independently, but with everybody's data, which, if we continue with the premise that the block-finding pool responds faster, should make identification clear.

This also will only last as long as pools don't take countermeasures, such as modifying bitcoind to randomly delay the RPC change to a new block if the local bitcoin found it, or by simply disabling long polling, like slush's pool.

As I would have to learn python, some database libs, and the current codebase before making improvements (and since improving hopping software was labeled as equivalent to "making poison gas for the Nazis" by hoppers themselves), I will leave it to someone else to implement this.

organofcorti
Donator
Legendary
*
Offline Offline

Activity: 1946


Poor impulse control.


View Profile WWW
August 24, 2011, 01:16:53 AM
 #3794

Thanks for that - I just wanted to make sure you hadn't gotten any new results that invalidated your post. I was planning on trying out LP penalty and wanted to make sure you were still seeing a significant improvement since it seems like a lot of work to do.

Edit: let me clarify - I wanted to make sure that you still thought any analysis of LP arrival times was useful.

I'll try and write a script to do a daily summary from the console output - think that daily Lp penalty would be granular enough?

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

Activity: 1946


Poor impulse control.


View Profile WWW
August 24, 2011, 01:19:27 AM
 #3795

For those of you who cant get to Hoppersden to read the "How to hop slush" post, if you want to play with the simulator yourself, it's posted here:

https://github.com/organofcorti/byteHopper-s

It requires you to have latest R installed, and editable variables are only accessible from the code. It's also not very well commented, sorry. On the other hand it's small enough and simple enough that you should be able to follow it.

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

Activity: 1848


View Profile
August 24, 2011, 01:30:00 AM
 #3796

If everyone publishes just raw data, it might be hard to eliminate fakers effectively... Maybe have it as an option + ask for/publish specific data only from the top 10(?) pool guessers.

If pools delay longpolls (they are already on a relatively long random delay), this would directly hurt their miners. Just delaying it for (potential) pool hoppers also won't work, as you can always easily fake a 24/7 CPU miner.

Also most pool operators seem to not be able to modify bitcoind on their own at all, if you just take a look at transaction policies or the lack of these... ironically the only one definitely able to really hack bitcoind seems to be a bit of a religious nutjob, including payers in the blockchain and flaming/preaching away on IRC! Cheesy

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
deepceleron
Legendary
*
Offline Offline

Activity: 1470



View Profile WWW
August 24, 2011, 02:08:44 AM
 #3797

Thanks for that - I just wanted to make sure you hadn't gotten any new results that invalidated your post. I was planning on trying out LP penalty and wanted to make sure you were still seeing a significant improvement since it seems like a lot of work to do.

Edit: let me clarify - I wanted to make sure that you still thought any analysis of LP arrival times was useful.

I'll try and write a script to do a daily summary from the console output - think that daily Lp penalty would be granular enough?

If you want extreme time logging that is easier to process, replace instances of
print time.strftime("[%H:%M:%S] ")

in bithopper.py with:
print str(time.clock()) + ": "

Then you get:
258.662399982: LP Call http://ozco.in:8332/LP
260.253839675: LP Call http://eu1.triplemining.com:8344/LP
261.29642532: LP Call http://pool.bitclockers.com:8332/LP


or you can save to a log file if the message is "LP Call", etc.

deepceleron
Legendary
*
Offline Offline

Activity: 1470



View Profile WWW
August 24, 2011, 02:29:07 AM
 #3798

If everyone publishes just raw data, it might be hard to eliminate fakers effectively... Maybe have it as an option + ask for/publish specific data only from the top 10(?) pool guessers.

Making realistic data for a dozen pools for each block with valid getwork timestamps is a higher barrier to entry than the current attack, which would be simply sending "Best Guess: {bitclockers} with 1 of 1 votes" over 9000 times. It's open source, so unless you want to only accept signed messages from a public key list of known-good users, there is always an attack.

lucita777
Jr. Member
*
Offline Offline

Activity: 39


View Profile
August 24, 2011, 04:09:41 AM
 #3799

Anyone else getting an error where BitHopper stops after a period of time?

It just gets stuck...

[14:16:38] writing to database
[14:17:38] writing to database
[14:18:38] writing to database
[14:19:38] writing to database
[14:20:38] writing to database
[14:21:38] writing to database
[14:22:38] writing to database
[14:23:38] writing to database


+1 for this since i got the latest version

EDIT: this still isn't fixed in the latest version... just a heads up.

I get an LP call then constant "writing to database" messages.
renders my miner useless until i restart bithopper Sad
occurs every 30 minutes approximately for me.

+1

occurs on BH 0.2.2.4-68.

As a workaround I wrote a very simple windows console script which restarts the BH about every 30 minutes. It assumes that there is only a single python.exe process running and that it is a BH.
Code:
@echo off
set DELAY=1800
set PYTHON_IM=python.exe
set PYTHON_PATH=c:\Python27\python.exe
set BH_PATH=d:\c00w-bitHopper\bitHopper.py

:loop
echo Restarting BitHopper....
taskkill /T /IM %PYTHON_IM%
start %PYTHON_PATH% %BH_PATH%
echo Waiting %DELAY% sec...
ping 127.0.0.1 -n %DELAY% >nul
goto :loop
Atroxes
Full Member
***
Offline Offline

Activity: 120



View Profile
August 24, 2011, 10:36:21 AM
 #3800

For some reason, with --p2pLP enabled, the pool that gets voted, doesn't reset round share count for me. Is this normal?
Pages: « 1 ... 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 181 182 183 184 185 186 187 188 189 [190] 191 192 193 194 195 196 197 198 199 200 201 202 203 204 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!