Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 111. (Read 2591920 times)

well a bit of advert would go a long way
just posted a thing on twitter maybe you could do the same do boost just to get us to the moon
because this concept is way better then what i have seen so far

people don't believe in P2Pool.
but the example of 7PH/s is good ... 2-3 block per day with this PooooOOOOooower !

mm i see still no block whatup

Iv'e got /8096+8096 on 2 S7s still low hash rate ?

What options did you append to your BTC user name?

So I created a mining pool using p2pool. Works good with my little bit of hash on but would be interested how it reacts to other miners. There are 5 coins to choose from at the moment- Bitcoin, Joulecoin, Mazacoin, Terracoin, and Titcoin.

SiteUrl= www.hashingbros.com

If you try it out I would be interested in getting some input on it.

Thanks.

Using two different minera boxes. One is running minerd with gridseed black blades and the other is
running cgminer running a pair of Zeus miner boxes. Both exhibit the same behavior. I am using the
http:// prefix rather than the stratum+tcp://


They work perfectly when attached to other pools running standard stratum.

any news on s7 firmware for p2pools also i'm running a old coincraft A1 2th miner with same probs with low hash on p2poo with cgminer 3.9 is there a poss upgrade for this

where did all the hash went to ?

not looking good. i hope the GL luck maintains.

time for block

What miner are you attaching to your litecoin node?

Really? the statement "mining altcoins" is not helpful.
some of us do both bitcoin and litecoin.

Mining altcoins.

When I attach a miner to the p2pool litecoin version, I get nothing but hash > target errors.

Things are set up according to instructions. Any idea what I am doing wrong?

It could be that the target vs. _target issue interferes with additionally mining the 611coin. For merged-mining NMC this has been solved by https://github.com/p2pool/p2pool/commit/a6f3f9259a5ea4975e961946b7ad7fe941ac76be

If you are talking about sharechains/Merged-Mining-2 then the anwers is: not yet. I hope lots of people pester forrestv or any other p2pool dev about MM2: https://github.com/p2pool/p2pool/issues/265 

Maybe cloudmining with P2Pool? 

definitely!
I've had about 33% better revenue using P2Pool than using ghash.io during the last days. Furthermore the P2Pool.611.to has already merge mined more than 200 SIL.


NMC merge mining works on my P2Pool only, if I deactivate the other sha256 coins for merge mining.
At the moment I'm merge mining 611 (SixEleven) which should offer a better profit

Hi,

[/size]

Is BIP65 causing any trouble in regards to merged mining Bitcoin together with Namecoin and other sha256 coins like 611 (SixEleven)?
Using the latest release v15 I'm only able to merge mine one additional coin. As soon as I add a second coin the workers get flooded by messages like these and the DOA rate approachs 100%:

Shutting down namecoind resolves the issue.
You may check the stats on http://p2pool.611.to for details.

Btw.: Is it possible to payout merge mined coins? It would be cool if it would be possible to append the additional coins address to the username like the options for difficulty and packet size.

Same problem for me, my 5 x S7`s were also hashing at 15-20TH instead of about 24TH on Cadence`s  p2ppool, ping was 35, took them off in the end due to poor performance and now one of the S7`s is not hashing at full speed on antpool whereas it was, currently its hashing at 3TH instead of around 4.73TH, firmware has been updated and miner power cycled numerous times, need to actually check with hosting if a full re-boot can be done, but still not back to full speed  .

Was looking forward to mining on p2ppool but after whats happened to my 1 S7 I going to avoid p2ppool unfortunately.

I emailed Bitmain with the below from the system log so will update this post if anybody wants to know the outcome, hoping a RMA is not required.
  559.496729] chain2 reg crc_r{0x16}crc{0x13} Err ret{0x80d1c2ff}
[  559.502998] asic cmd return 80d1c2ff
[  559.506741] chain2 reg crc_r{0x16}crc{0x13} Err ret{0x80d1c2ff}
[  559.512931] asic cmd return 80d1c2ff
[  559.516676] chain2 reg crc_r{0x16}crc{0x13} Err ret{0x80d1c2ff}
[  559.522862] asic cmd return 80d1c2ff
[  559.526609] chain2 reg crc_r{0x16}crc{0x13} Err ret{0x80d1c2ff}
[  559.532804] asic cmd return 80d1d189
[  559.536555] chain2 reg crc_r{0x1f}crc{0x64} Err ret{0x80d1d189}
[  559.542742] asic cmd return 80d1d189
[  559.546489] chain2 reg crc_r{0x1f}crc{0x64} Err ret{0x80d1d189}
[  559.553708] asic cmd return 80d1d189
[  559.557496] chain2 reg crc_r{0x1f}crc{0x64} Err ret{0x80d1d189}
[  559.563686] asic cmd return 80d1d189
[  559.567433] chain2 reg crc_r{0x1f}crc{0x64} Err ret{0x80d1d189}
[  559.573610] asic cmd return 80d1d189
[  559.577351] chain2 reg crc_r{0x1f}crc{0x6c} Err ret{0x80d1d189}
[  559.583550] ch2-as33: dev->task_buffer_wr{0x00000923}rd{0x00000d23}ret
work_id{0x8d11} don't match task_buffer_match{0x0d11}
[  559.596043] ch2-as33: dev->task_buffer_wr{0x00000923}rd{0x00000d23}ret
work_id{0x8d14} don't match task_buffer_match{0x0d14}
[  559.607863] ch2-as8: dev->task_buffer_wr{0x00000923}rd{0x00000d23}ret
work_id{0x8cf3} don't match task_buffer_match{0x0cf3}
[  559.619713] asic cmd return 80117e0f
[  559.623482] chain2 reg crc_r{0x1d}crc{0x2b} Err ret{0x80117e0f}

[off topic]
My alarm is set to 21:00 hrs every day on my android phone.

Mon. 23:08 hrs, I wake up look at my phone; the alarm says "Mon 21:00" on the lock screen, "oh shit WTF I say"; I call work to tell them I'm late will be there ASAP, hang up and look at the lock screen again and now the alarm says "Tue 21:00".
[/off topic]

23:55 hrs, at work and check my p2pool stats page; since the last restart; 7 shares (1 orphan, 0 dead).

00:39 hrs, return to the office after doing shit and check the stays page again; 7 shares (1 orphan, 1 dead).

Really, WTF is going on here?

my 5,2 ths S7 mine only with 4,6 ths @p2pool
try 4 different nodes (ping 16-25 ms)

I have just sent them an e-mail about this issue. Who knows, may be it will lead us to renewed driver code.