Bitcoin Forum

The link is wrong

Here is corrected http://bytecoin.us.to:8000/

Very nice.

I can't get any shares with reaper!
I get shares according to gui miner, but the server still won't log them.

8XSXmLJ5DB6qpdEhqv4EcfkcFUmDwa8rBA is my address

I can't get any shares with reaper!
I get shares according to gui miner, but the server still won't log them.

8XSXmLJ5DB6qpdEhqv4EcfkcFUmDwa8rBA is my address

I'm getting 130 MH/s


2013-04-04 11:55:44: Listener for "byte pool" started
2013-04-04 11:55:45: Listener for "byte pool": 04/04/2013 11:55:45, started OpenCL miner on platform 0, device 0 (Juniper)
2013-04-04 11:55:45: Listener for "byte pool": bytecoin.us.to:6327 04/04/2013 11:55:45, checking for stratum...
2013-04-04 11:55:49: Listener for "byte pool": bytecoin.us.to:6327 04/04/2013 11:55:49, diverted to stratum on bytecoin.us.to:6327
2013-04-04 11:55:52: Listener for "byte pool": bytecoin.us.to:6327 04/04/2013 11:55:52, Setting new difficulty: 0.999984741211
2013-04-04 11:55:53: Listener for "byte pool": bytecoin.us.to:6327 04/04/2013 11:55:53, Setting new difficulty: 0.999984741211
2013-04-04 11:55:53: Listener for "byte pool": bytecoin.us.to:6327 04/04/2013 11:55:53, authorization failed with 8XSXmLJ5DB6qpdEhqv4EcfkcFUmDwa8rBA:1@bytecoin.us.to:6327
2013-04-04 11:55:53: Listener for "byte pool": bytecoin.us.to:6327 04/04/2013 11:55:53, Setting new difficulty: 0.999984741211
2013-04-04 11:55:56: Listener for "byte pool": bytecoin.us.to:6327 04/04/2013 11:55:56, IO errors - 1, tolerance 2

It looks like the server isn't accepting your login details ('authorization failed'), so you aren't being registered and the server isn't accepting shares to your name :/

I'll see what I can do, this has happened to me before, as this seems to be a quite common problem with p2pool, or at least p2pool with bytecoin

Looks like I'm having the same problem:

2013-04-04 17:09:07: Listener for "Default": 04/04/2013 17:09:07, started OpenCL miner on platform 1, device 0 (Quadro K5000M)
2013-04-04 17:09:08: Listener for "Default": bytecoin.us.to:6327 04/04/2013 17:09:08, checking for stratum...
2013-04-04 17:09:08: Listener for "Default": bytecoin.us.to:6327 04/04/2013 17:09:08, diverted to stratum on bytecoin.us.to:6327
2013-04-04 17:09:08: Listener for "Default": bytecoin.us.to:6327 04/04/2013 17:09:08, Setting new difficulty: 1.29718570116
2013-04-04 17:09:09: Listener for "Default": bytecoin.us.to:6327 04/04/2013 17:09:09, authorization failed with 8VcNiDbUvSrLB8c8sdXFGWVGXzWrHbh5Dp:1@bytecoin.us.to:6327
2013-04-04 17:09:09: Listener for "Default": bytecoin.us.to:6327 04/04/2013 17:09:09, Setting new difficulty: 1.27240181007
2013-04-04 17:09:12: Listener for "Default": bytecoin.us.to:6327 04/04/2013 17:09:12, IO errors - 1, tolerance 2

Just to check, what miner are you using? GUIMiner? If so could you try mining with DiabloMiner instead and see if it works?

I'm using GUIMiner

This pool is a scam or what? I'm submitting shares, they are accepted, blocks are solved by pool but there is no payout.

8SCfz1Lg7fa3aXYsLvM2YHycQrFvyZEAoB

8XSXmLJ5DB6qpdEhqv4EcfkcFUmDwa8rBA

am I connected to your severs now?

It works now. It takes a lot of time for pool to realise miner joined, is that normal?

Great work on the faucet and pool LucasJones!

I have been using cgminer with very good success for those having issues.

I just made a donation to the faucet to help keep her topped up for ya ;)

I stopped mining like 20 minutes ago but I'm still receiving payouts. That means there is some sort of fade-in and fade-out with pool.

Whenever a block is found, payment is given to shares in a window, starting with the last share submitted and going backwards up to some number N of shares. Shares older than the window are not paid. This is essentially a 0-1 cutoff decay function. There is no concept of rounds - shares can be paid even if they were found before the previous block. This means that a given share can be paid more than once - however, the payouts are chosen so that the expected reward is equal to solo expected reward. Because the payment for a share depends only on blocks found in the future and not on shares and blocks found in the past, there is no way to hop based on the current status of the pool. However, if implemented incorrectly, it is possible to hop based on imminent difficulty changes

Percentage of rejected shares is very high, over 20% on my side. Mining with either CGMiner or BFGMiner makes no difference. Blocks are no longer
solved every few seconds so there should be less rejected shares. Any fix for the issue?

Could you check your latency to the faucet page (hosted on the same IP as the pool)?

P2Pool relies heavily on low latencies, so if your connection is slower than others to the pool, it could mean that you get a higher number of rejected shares.

EDIT: I'm going to restart the server's internet connection, just tested it and it's *very* slow. Should be better in a minute, and the number of shares that are rejected should decrease :)

over 300 BTE in the faucet, but only 0.05 released at a time, maybe increase it to 0.5 for a while ?

I might increase it to 0.1 for now, I'm just trying to find a balance between how much is donated/mined and how much is withdrawn (As there are over 300 payouts a day on average).

300 payouts * 0.5 = 150 BTE, which seems a bit much to give away in one day, and much more than what is mined for the faucet.

Understood, if 300 a day, agree 0.1 is better.

I tried mining the pool that feeds the faucet recently but got some JSON errors, will have another try later, would like to contribute to the faucet

pool down?

Add CAPTCHA to faucet, else BOTs will drain all coins in a day. Seriously.

now pointing my cgminer at it... nice to be adding to the faucet  :D