bitpop
Legendary
Offline
Activity: 2912
Merit: 1060
|
|
July 10, 2013, 05:19:36 AM |
|
Why do you need a proxy?
|
|
|
|
|
|
|
Be very wary of relying on JavaScript for security on crypto sites. The site can change the JavaScript at any time unless you take unusual precautions, and browsers are not generally known for their airtight security.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
Raulnsh
Newbie
Offline
Activity: 22
Merit: 0
|
|
July 10, 2013, 05:33:16 AM |
|
Why do you need a proxy?
I have several getwork CPU miners behind stratum proxy.
|
|
|
|
|
evilpete
Member
Offline
Activity: 77
Merit: 10
|
|
July 10, 2013, 05:55:05 AM |
|
how many percent was updated? where can we see? can wait for the switch.
I'd also like to know what percentage of the network has upgraded. Based on http://p2pool-nodes.info/, its 96 nodes are still at < v13.0 and 32 at > v13.0, so around 25%. p2pool-nodes.info only shows a portion of the public nodes. A bit over a week ago it was only showing 30-40 nodes but I was able to tweak my pool to attempt to explore and it found ~260 public nodes. p2pool-nodes.info hadn't found my public node for about 5-6 weeks. It finally updated last week sometime. Treat p2pool-nodes.info as a sample, not an exhaustive list.
|
First they ignore you, then they laugh at you, then they fight you, then you win. - Mahatma Gandhi
|
|
|
forrestv (OP)
|
|
July 10, 2013, 06:05:38 AM |
|
I'm doing test mining with versions 13.0-13.1 for two days 2013-07-10 10:47:12.841000 Local: 348kH/s in last 10.0 minutes Local dead on arrival: ~3.8% (2-6%) Expected time to share: 21.4 hours 2013-07-10 10:47:12.841000 Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: 0.0000 LTC 2013-07-10 10:47:12.872000 Pool: 741MH/s Stale rate: 20.0% Expected time to block: 1.4 hours 2013-07-10 10:47:18.778000 2013-07-10 10:47:18.809000 New work for worker! Difficulty: 0.000109 Share difficulty: 6.293200 Total block value: 50.001000 LTC including 10 transact ions No shares. Expected time may be 1.6 hours then again 1 day. Is it normal? Will I get any shares with p2pool? It is normal. Expected time to share is 1 day, but expected time to block is 1.4 hours. P2Pool is increasing your share difficulty to prevent you from receiving dust payouts. You will get shares if you keep mining.
|
1J1zegkNSbwX4smvTdoHSanUfwvXFeuV23
|
|
|
Raulnsh
Newbie
Offline
Activity: 22
Merit: 0
|
|
July 10, 2013, 06:30:40 AM |
|
Yes, yes! It is just dec 2012 version 1.3.0 which works with ltcmine but does not work with p2pool 2013-07-10 12:25:23: Running command: C:\guiminer\stratumproxy\mining_proxy.exe -pa scrypt -o ***.***.***.*** -p **** 2013-07-10 12:25:23: Listener for "Stratum" started 2013-07-10 12:25:24: Listener for "Stratum": 2013-07-10 12:25:24,437 WARNING proxy jobs.<module> # C extension for midstate not available. Using default implementation instead. 2013-07-10 12:25:24: Listener for "Stratum": 2013-07-10 12:25:24,457 ERROR proxy mining_proxy.main # Stratum host/port autodetection failed 2013-07-10 12:25:24: Listener for "Stratum": Traceback (most recent call last): 2013-07-10 12:25:24: Listener for "Stratum": File "mining_proxy.py", line 155, in main 2013-07-10 12:25:24: Listener for "Stratum": File "twisted\internet\defer.pyo", line 1045, in _inlineCallbacks 2013-07-10 12:25:24: Listener for "Stratum": File "mining_libs\utils.pyo", line 106, in detect_stratum 2013-07-10 12:25:24: Listener for "Stratum": TypeError: 'NoneType' object has no attribute '__getitem__' 2013-07-10 12:25:24: Listener for "Stratum": 2013-07-10 12:25:24,457 INFO proxy mining_proxy.main # Stratum proxy version: 1.3.0 2013-07-10 12:25:24: Listener for "Stratum": 2013-07-10 12:25:24,457 INFO proxy mining_proxy.main # Trying to connect to Stratum pool at ***.***.***.***:**** 2013-07-10 12:25:24: Listener for "Stratum": 2013-07-10 12:25:24,457 INFO proxy mining_proxy.main # Setting PoW algo: scrypt 2013-07-10 12:25:24: Listener for "Stratum": 2013-07-10 12:25:24,460 INFO stats stats.print_stats # 1 peers connected, state changed 1 times 2013-07-10 12:25:24: Listener for "Stratum": 2013-07-10 12:25:24,460 INFO proxy mining_proxy.on_connect # Connected to Stratum pool at ***.***.***.***:**** 2013-07-10 12:25:24: Listener for "Stratum": 2013-07-10 12:25:24,460 INFO proxy mining_proxy.on_connect # Subscribing for mining jobs 2013-07-10 12:25:24: Listener for "Stratum": 2013-07-10 12:25:24,466 INFO proxy mining_proxy.main # ----------------------------------------------------------------------- 2013-07-10 12:25:24: Listener for "Stratum": 2013-07-10 12:25:24,466 INFO proxy mining_proxy.main # ----------------------------------------------------------------------- 2013-07-10 12:25:24: Listener for "Stratum": 2013-07-10 12:25:24,466 INFO proxy client_service.handle_event # Setting new difficulty: 5.38747577579 2013-07-10 12:25:24: Listener for "Stratum": 2013-07-10 12:25:24,493 INFO proxy mining_proxy.on_disconnect # Disconnected from Stratum pool at ***.***.***.***:**** 2013-07-10 12:25:24: Listener for "Stratum": 2013-07-10 12:25:24,494 INFO stats stats.print_stats # 0 peers connected, state changed 1 times 2013-07-10 12:25:26: Listener for "Stratum": 2013-07-10 12:25:26,707 INFO stats stats.print_stats # 1 peers connected, state changed 1 times 2013-07-10 12:25:26: Listener for "Stratum": 2013-07-10 12:25:26,707 INFO proxy mining_proxy.on_connect # Connected to Stratum pool at ***.***.***.***:**** 2013-07-10 12:25:26: Listener for "Stratum": 2013-07-10 12:25:26,707 INFO proxy mining_proxy.on_connect # Subscribing for mining jobs 2013-07-10 12:25:26: Listener for "Stratum": 2013-07-10 12:25:26,720 INFO proxy client_service.handle_event # Setting new difficulty: 5.38747577579 2013-07-10 12:25:26: Listener for "Stratum": 2013-07-10 12:25:26,727 INFO proxy mining_proxy.on_disconnect # Disconnected from Stratum pool at ***.***.***.***:**** 2013-07-10 12:25:26: Listener for "Stratum": 2013-07-10 12:25:26,727 INFO stats stats.print_stats # 0 peers connected, state changed 1 times 2013-07-10 12:25:29: Listener for "Stratum": 2013-07-10 12:25:29,194 INFO stats stats.print_stats # 1 peers connected, state changed 1 times 2013-07-10 12:25:29: Listener for "Stratum": 2013-07-10 12:25:29,194 INFO proxy mining_proxy.on_connect # Connected to Stratum pool at ***.***.***.***:**** 2013-07-10 12:25:29: Listener for "Stratum": 2013-07-10 12:25:29,194 INFO proxy mining_proxy.on_connect # Subscribing for mining jobs 2013-07-10 12:25:29: Listener for "Stratum": 2013-07-10 12:25:29,198 INFO proxy client_service.handle_event # Setting new difficulty: 6.32609060383 2013-07-10 12:25:29: Listener for "Stratum": 2013-07-10 12:25:29,213 INFO proxy mining_proxy.on_disconnect # Disconnected from Stratum pool at ***.***.***.***:**** 2013-07-10 12:25:29: Listener for "Stratum": 2013-07-10 12:25:29,213 INFO stats stats.print_stats # 0 peers connected, state changed 1 times 2013-07-10 12:25:31: Listener for "Stratum": 2013-07-10 12:25:31,836 INFO stats stats.print_stats # 1 peers connected, state changed 1 times 2013-07-10 12:25:31: Listener for "Stratum": 2013-07-10 12:25:31,836 INFO proxy mining_proxy.on_connect # Connected to Stratum pool at ***.***.***.***:**** 2013-07-10 12:25:31: Listener for "Stratum": 2013-07-10 12:25:31,836 INFO proxy mining_proxy.on_connect # Subscribing for mining jobs 2013-07-10 12:25:31: Listener for "Stratum": 2013-07-10 12:25:31,839 INFO proxy client_service.handle_event # Setting new difficulty: 6.32609060383 2013-07-10 12:25:31: Listener for "Stratum": 2013-07-10 12:25:31,861 INFO proxy mining_proxy.on_disconnect # Disconnected from Stratum pool at ***.***.***.***:**** 2013-07-10 12:25:31: Listener for "Stratum": 2013-07-10 12:25:31,861 INFO stats stats.print_stats # 0 peers connected, state changed 1 times 2013-07-10 12:25:34: Listener for "Stratum": 2013-07-10 12:25:34,713 INFO stats stats.print_stats # 1 peers connected, state changed 1 times 2013-07-10 12:25:34: Listener for "Stratum": 2013-07-10 12:25:34,713 INFO proxy mining_proxy.on_connect # Connected to Stratum pool at ***.***.***.***:**** 2013-07-10 12:25:34: Listener for "Stratum": 2013-07-10 12:25:34,713 INFO proxy mining_proxy.on_connect # Subscribing for mining jobs 2013-07-10 12:25:34: Listener for "Stratum": 2013-07-10 12:25:34,743 INFO proxy client_service.handle_event # Setting new difficulty: 6.32609060383 2013-07-10 12:25:34: Listener for "Stratum": 2013-07-10 12:25:34,834 INFO proxy mining_proxy.on_disconnect # Disconnected from Stratum pool at ***.***.***.***:**** 2013-07-10 12:25:34: Listener for "Stratum": 2013-07-10 12:25:34,834 INFO stats stats.print_stats # 0 peers connected, state changed 1 times 2013-07-10 12:25:37: Listener for "Stratum": 2013-07-10 12:25:37,507 INFO stats stats.print_stats # 1 peers connected, state changed 1 times 2013-07-10 12:25:37: Listener for "Stratum": 2013-07-10 12:25:37,507 INFO proxy mining_proxy.on_connect # Connected to Stratum pool at ***.***.***.***:**** 2013-07-10 12:25:37: Listener for "Stratum": 2013-07-10 12:25:37,509 INFO proxy mining_proxy.on_connect # Subscribing for mining jobs 2013-07-10 12:25:37: Listener for "Stratum": 2013-07-10 12:25:37,552 INFO proxy client_service.handle_event # Setting new difficulty: 6.32609060383 2013-07-10 12:25:37: Listener for "Stratum": 2013-07-10 12:25:37,671 INFO proxy mining_proxy.on_disconnect # Disconnected from Stratum pool at ***.***.***.***:**** 2013-07-10 12:25:37: Listener for "Stratum": 2013-07-10 12:25:37,671 INFO stats stats.print_stats # 0 peers connected, state changed 1 times 2013-07-10 12:25:39: Listener for "Stratum": Unhandled error in Deferred: 2013-07-10 12:25:39: Listener for "Stratum": Unhandled Error 2013-07-10 12:25:39: Listener for "Stratum": Traceback (most recent call last): 2013-07-10 12:25:39: Listener for "Stratum": File "twisted\web\server.pyo", line 156, in process 2013-07-10 12:25:39: Listener for "Stratum": File "twisted\web\server.pyo", line 191, in render 2013-07-10 12:25:39: Listener for "Stratum": File "twisted\web\resource.pyo", line 216, in render 2013-07-10 12:25:39: Listener for "Stratum": File "mining_libs\getwork_listener.pyo", line 165, in render_POST 2013-07-10 12:25:39: Listener for "Stratum": --- <exception caught here> --- 2013-07-10 12:25:39: Listener for "Stratum": File "twisted\internet\defer.pyo", line 134, in maybeDeferred 2013-07-10 12:25:39: Listener for "Stratum": File "mining_libs\worker_registry.pyo", line 37, in authorize 2013-07-10 12:25:39: Listener for "Stratum": File "stratum\socket_transport.pyo", line 89, in rpc 2013-07-10 12:25:39: Listener for "Stratum": stratum.custom_exceptions.TransportException: Not connected
|
|
|
|
bitpop
Legendary
Offline
Activity: 2912
Merit: 1060
|
|
July 10, 2013, 06:34:12 AM |
|
Get a new cpu miner?
|
|
|
|
Raulnsh
Newbie
Offline
Activity: 22
Merit: 0
|
|
July 10, 2013, 07:12:40 AM |
|
Get a new cpu miner?
OK to get new CPU miner .
|
|
|
|
lenny_
Legendary
Offline
Activity: 1036
Merit: 1000
DARKNETMARKETS.COM
|
|
July 10, 2013, 07:55:34 AM |
|
I'm doing test mining with versions 13.0-13.1 for two days 2013-07-10 10:47:12.841000 Local: 348kH/s in last 10.0 minutes Local dead on arrival: ~3.8% (2-6%) Expected time to share: 21.4 hours 2013-07-10 10:47:12.841000 Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: 0.0000 LTC 2013-07-10 10:47:12.872000 Pool: 741MH/s Stale rate: 20.0% Expected time to block: 1.4 hours 2013-07-10 10:47:18.778000 2013-07-10 10:47:18.809000 New work for worker! Difficulty: 0.000109 Share difficulty: 6.293200 Total block value: 50.001000 LTC including 10 transact ions No shares. Expected time may be 1.6 hours then again 1 day. Is it normal? Will I get any shares with p2pool? As you see: Expected time to share: 21.4 hours Variance make this number 5x bigger or smaller, depend on your luck. Wait a bit longer
|
|
|
|
asyring
Newbie
Offline
Activity: 29
Merit: 0
|
|
July 10, 2013, 09:59:27 AM |
|
It is possible to implement that the namecoin mining is not soloming? Is there a chance to poolmine namecoins?
|
|
|
|
mdude77
Legendary
Offline
Activity: 1540
Merit: 1001
|
|
July 10, 2013, 10:12:47 AM |
|
I'm doing test mining with versions 13.0-13.1 for two days 2013-07-10 10:47:12.841000 Local: 348kH/s in last 10.0 minutes Local dead on arrival: ~3.8% (2-6%) Expected time to share: 21.4 hours 2013-07-10 10:47:12.841000 Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: 0.0000 LTC 2013-07-10 10:47:12.872000 Pool: 741MH/s Stale rate: 20.0% Expected time to block: 1.4 hours 2013-07-10 10:47:18.778000 2013-07-10 10:47:18.809000 New work for worker! Difficulty: 0.000109 Share difficulty: 6.293200 Total block value: 50.001000 LTC including 10 transact ions No shares. Expected time may be 1.6 hours then again 1 day. Is it normal? Will I get any shares with p2pool? As you see: Expected time to share: 21.4 hours Variance make this number 5x bigger or smaller, depend on your luck. Wait a bit longer 348kh/s is miniscule. M
|
I mine at Kano's Pool because it pays the best and is completely transparent! Come join me!
|
|
|
bitpop
Legendary
Offline
Activity: 2912
Merit: 1060
|
|
July 10, 2013, 10:21:25 AM |
|
Use bitparking It is possible to implement that the namecoin mining is not soloming? Is there a chance to poolmine namecoins?
|
|
|
|
kano
Legendary
Offline
Activity: 4480
Merit: 1800
Linux since 1997 RedHat 4
|
|
July 10, 2013, 01:20:45 PM |
|
I'm doing test mining with versions 13.0-13.1 for two days 2013-07-10 10:47:12.841000 Local: 348kH/s in last 10.0 minutes Local dead on arrival: ~3.8% (2-6%) Expected time to share: 21.4 hours 2013-07-10 10:47:12.841000 Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: 0.0000 LTC 2013-07-10 10:47:12.872000 Pool: 741MH/s Stale rate: 20.0% Expected time to block: 1.4 hours 2013-07-10 10:47:18.778000 2013-07-10 10:47:18.809000 New work for worker! Difficulty: 0.000109 Share difficulty: 6.293200 Total block value: 50.001000 LTC including 10 transact ions No shares. Expected time may be 1.6 hours then again 1 day. Is it normal? Will I get any shares with p2pool? As you see: Expected time to share: 21.4 hours Variance make this number 5x bigger or smaller, depend on your luck. Wait a bit longer Actually 8x isn't that rare either ...
|
|
|
|
baloo_kiev
|
|
July 10, 2013, 01:59:03 PM |
|
I'm doing test mining with versions 13.0-13.1 for two days 2013-07-10 10:47:12.841000 Local: 348kH/s in last 10.0 minutes Local dead on arrival: ~3.8% (2-6%) Expected time to share: 21.4 hours 2013-07-10 10:47:12.841000 Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: 0.0000 LTC 2013-07-10 10:47:12.872000 Pool: 741MH/s Stale rate: 20.0% Expected time to block: 1.4 hours 2013-07-10 10:47:18.778000 2013-07-10 10:47:18.809000 New work for worker! Difficulty: 0.000109 Share difficulty: 6.293200 Total block value: 50.001000 LTC including 10 transact ions No shares. Expected time may be 1.6 hours then again 1 day. Is it normal? Will I get any shares with p2pool? As you see: Expected time to share: 21.4 hours Variance make this number 5x bigger or smaller, depend on your luck. Wait a bit longer Actually 8x isn't that rare either ... 3% probability for x5 and 0.4% for x8 to be exact...
|
|
|
|
dc81
Member
Offline
Activity: 108
Merit: 100
|
|
July 10, 2013, 04:22:47 PM |
|
how many percent was updated? where can we see? can wait for the switch.
I'd also like to know what percentage of the network has upgraded. Based on http://p2pool-nodes.info/, its 96 nodes are still at < v13.0 and 32 at > v13.0, so around 25%. p2pool-nodes.info only shows a portion of the public nodes. A bit over a week ago it was only showing 30-40 nodes but I was able to tweak my pool to attempt to explore and it found ~260 public nodes. p2pool-nodes.info hadn't found my public node for about 5-6 weeks. It finally updated last week sometime. Treat p2pool-nodes.info as a sample, not an exhaustive list. i switched my node host to another machine and it just took some time to rebuild the list of p2pool nodes. i plan on adding the ability to manually adding a node and possibly custom hostnames instead of just the ip. but it may be a few weeks before i have time to incorporate it. however, i was able to add the bitcoind latency and hash rate of the node to the list.
|
|
|
|
maqifrnswa
|
|
July 10, 2013, 05:10:56 PM |
|
how many percent was updated? where can we see? can wait for the switch.
I'd also like to know what percentage of the network has upgraded. Based on http://p2pool-nodes.info/, its 96 nodes are still at < v13.0 and 32 at > v13.0, so around 25%. I don't think number of nodes is the metric for cross-over, I think it's percentage of hashrate. Right now it is: 13: 36% 360 GH/s 11: 64% 640 GH/s I'm doing test mining with versions 13.0-13.1 for two days 2013-07-10 10:47:12.841000 Local: 348kH/s in last 10.0 minutes Local dead on arrival: ~3.8% (2-6%) Expected time to share: 21.4 hours 2013-07-10 10:47:12.841000 Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: 0.0000 LTC 2013-07-10 10:47:12.872000 Pool: 741MH/s Stale rate: 20.0% Expected time to block: 1.4 hours 2013-07-10 10:47:18.778000 2013-07-10 10:47:18.809000 New work for worker! Difficulty: 0.000109 Share difficulty: 6.293200 Total block value: 50.001000 LTC including 10 transact ions No shares. Expected time may be 1.6 hours then again 1 day. Is it normal? Will I get any shares with p2pool? As you see: Expected time to share: 21.4 hours Variance make this number 5x bigger or smaller, depend on your luck. Wait a bit longer 348kh/s is miniscule. M for LTC it's respectable, equivalent to ~500MH/s on BTC's network.
|
|
|
|
wtogami
|
|
July 10, 2013, 06:10:23 PM |
|
The Litecoin Project is proud to release the source of p2pool-scanner, an node.js app that scans the entire p2pool network and generates a page listing known public pools. The main benefit in releasing this source is to allow BTC p2pool to use it. https://github.com/litecoin-project/p2pool-scannerSource http://p2pool.litecointools.com/The p2pool LTC network is listed here. Yes, the current ordering is not ideal. Ordering by uptime isn't the greatest idea. It should be smarter in excluding old, known buggy versions of p2pool and when the daemon is warning. Please send pull requests to the above github project with general improvements to the code. Someone else should run the official BTC p2pool-scanner. Keep it stable and contribute improvements to the source project, and we can ask forrestv to link to your p2pool scanner from the OP.
|
If you appreciate my work please consider making a small donation. BTC: 1LkYiL3RaouKXTUhGcE84XLece31JjnLc3 LTC: LYtrtYZsVSn5ymhPepcJMo4HnBeeXXVKW9 GPG: AEC1884398647C47413C1C3FB1179EB7347DC10D
|
|
|
dc81
Member
Offline
Activity: 108
Merit: 100
|
|
July 10, 2013, 06:31:53 PM |
|
The Litecoin Project is proud to release the source of p2pool-scanner, an node.js app that scans the entire p2pool network and generates a page listing known public pools. The main benefit in releasing this source is to allow BTC p2pool to use it. https://github.com/litecoin-project/p2pool-scannerSource http://p2pool.litecointools.com/The p2pool LTC network is listed here. Yes, the current ordering is not ideal. Ordering by uptime isn't the greatest idea. It should be smarter in excluding old, known buggy versions of p2pool and when the daemon is warning. Please send pull requests to the above github project with general improvements to the code. Someone else should run the official BTC p2pool-scanner. Keep it stable and contribute improvements to the source project, and we can ask forrestv to link to your p2pool scanner from the OP. i have been maintaining one for btc at http://p2pool-nodes.info/i noticed you hard coded the port number, but there are nodes that don't use the default port. i have filtered out p2pool versions that aren't on 11.x or 13.x right now and those that are disconnected from bitcoind.
|
|
|
|
wtogami
|
|
July 10, 2013, 07:08:22 PM |
|
i have been maintaining one for btc at http://p2pool-nodes.info/i noticed you hard coded the port number, but there are nodes that don't use the default port. i have filtered out p2pool versions that aren't on 11.x or 13.x right now and those that are disconnected from bitcoind. Did you base it on p2pool-scanner or wrote your own?
|
If you appreciate my work please consider making a small donation. BTC: 1LkYiL3RaouKXTUhGcE84XLece31JjnLc3 LTC: LYtrtYZsVSn5ymhPepcJMo4HnBeeXXVKW9 GPG: AEC1884398647C47413C1C3FB1179EB7347DC10D
|
|
|
dc81
Member
Offline
Activity: 108
Merit: 100
|
|
July 10, 2013, 07:21:24 PM |
|
i have been maintaining one for btc at http://p2pool-nodes.info/i noticed you hard coded the port number, but there are nodes that don't use the default port. i have filtered out p2pool versions that aren't on 11.x or 13.x right now and those that are disconnected from bitcoind. Did you base it on p2pool-scanner or wrote your own? wrote it myself
|
|
|
|
|