What's in your bitcoin.conf ?
minrelaytxfee=0.0001500
blockmaxsize=919899
blockprioritysize=44308
limitfreerelay=6
I have found valid, tx containing blocks in the past.. Additionally, logs from bitcoind. The time shows in UTC here, would that matter? 2016-04-15 03:20:49 CreateNewBlock(): total size 919823 txs: 1748 fees: 35821561 sigops 3928
2016-04-15 03:21:04 CreateNewBlock(): total size 919890 txs: 1742 fees: 36105460 sigops 3945
2016-04-15 03:21:13 UpdateTip: new best=000000000000000003828fbc61ad281aa2e298ed4a299abf36209a4725d51930 height=407355 log2_work=84.488361 tx=122495866 date=2016-04-15 03:20:49 progress=1.000000 cache=287.3MiB(138792tx)
You are sure it's your miner that found the block (I'm not familiar with if that message says you found the block or someone else did)? There's something screwy going on because your bitcoind is offering transaction based work just before you found the block of 910k Perhaps for whatever reason your p2pool client kept building empty block work indefinitely after the previous block through some bug. Is your p2pool code modified in any way? |
|
|
|
No. So, Why was that block empty? I checked the node that block was mined on and it should have been completely full. What gives??? 2016-04-14 23:21:00.883567 New work for worker! Difficulty: 5346.855749 Share difficulty: 9605175.641964 Total block value: 25.358216 BTC including 1748 transactions
2016-04-14 23:21:12.763410 GOT BLOCK FROM MINER! Passing to bitcoind! https://blockchain.info/block/000000000000000003828fbc61ad281aa2e298ed4a299abf36209a4725d51930
2016-04-14 23:21:12.782751 GOT SHARE! 1DwXFhwiBGdsiqBxCYopMNkqZmZZUegnd8 25d51930 prev f4281eee age 11.90s
2016-04-14 23:21:13.353501 Skipping from block 52e336f67c1b0d339d5e7423595c60f169cd17bd24e5306 to block 3828fbc61ad281aa2e298ed4a299abf36209a4725d51930!
2016-04-14 23:21:13.403123 > Block submittal result: False (u'duplicate') Expected: True What do I have misconfigured? ._. What's in your bitcoin.conf ? |
|
|
|
[2016-04-19 06:59:37.439] Possible block solve diff 188183387504.931061 !
[2016-04-19 06:59:37.569] BLOCK ACCEPTED!
[2016-04-19 06:59:37.569] Solved and confirmed block 407987 by 1FfJWVkrF6YXyeK9KCj84WavgDJGhdtVCX
[2016-04-19 06:59:37.569] User 1FfJWVkrF6YXyeK9KCj84WavgDJGhdtVCX:{"hashrate1m": "806T", "hashrate5m": "795T", "hashrate1hr": "398T", "hashrate1d": "37.4T", "hashrate7d": "51.5T"}
[2016-04-19 06:59:37.569] Worker 1FfJWVkrF6YXyeK9KCj84WavgDJGhdtVCX:{"hashrate1m": "806T", "hashrate5m": "795T", "hashrate1hr": "398T", "hashrate1d": "37.4T", "hashrate7d": "51.5T"}
[2016-04-19 06:59:37.569] Block solved after 91607170114 shares at 51.3% diff
|
|
|
|
Priceless...
Somehow, we got way off-topic.
Not really. The point is p2pool was written in python when mining was just about building a simple shelf where it suited the job perfectly with the minimum amount of effort. Unfortunately these days building a simple shelf doesn't cut it. |
|
|
|
This never gets tired, even if it does misspell assembly  |
|
|
|
|
Nice. That just shows that antpool's various servers aren't synchronised till after the blocks are found. Their SPV mining didn't save them from themselves even on this occasion, and all the servers were within the great firewall so they can't even blame that.
I think I recall a big pool doing this to itself many years ago once before... can't remember who it was.
|
|
|
|
[2016-04-17 06:31:27.553] Possible block solve diff 372637602971.086060 !
[2016-04-17 06:31:27.691] BLOCK ACCEPTED!
[2016-04-17 06:31:27.691] Solved and confirmed block 407691 by 3JhmANFUNJkBREYYfPPy8hdJ3cnrGvWKhY.75
[2016-04-17 06:31:27.691] User 3JhmANFUNJkBREYYfPPy8hdJ3cnrGvWKhY:{"hashrate1m": "35.6T", "hashrate5m": "35.4T", "hashrate1hr": "35.8T", "hashrate1d": "49.5T", "hashrate7d": "97T"}
[2016-04-17 06:31:27.691] Worker 3JhmANFUNJkBREYYfPPy8hdJ3cnrGvWKhY.75:{"hashrate1m": "1.46T", "hashrate5m": "1.32T", "hashrate1hr": "1.17T", "hashrate1d": "1.15T", "hashrate7d": "1.15T"}
[2016-04-17 06:31:27.691] Block solved after 80152629514 shares at 44.9% diff
Note the blocktrail link shows the block as v20000000 which is due to the upgrade to bitcoin 0.12.1 for the soft fork. |
|
|
|
|
Solo pools are now running on a bitcoin 0.12.1 base ready for the next soft fork. Yes, miners wouldn't have noticed anything since bitcoind upgrades are seamless to mining on ckpool.
|
|
|
|
|
Just a thought; you're using an SSD. Are you using discard on the mount options, if supported by your distribution? If not, are you using trim on the file system at regular intervals?
|
|
|
|
Congrats! My address is in my forum profile, thanks!
Sent CK, hope it would be confirmed soon. Thank You. Your generous donation was received with many thanks!  |
|
|
|
The drought breaks! [2016-04-15 21:25:35.000] Possible block solve diff 414770411756.936035 !
[2016-04-15 21:25:35.139] BLOCK ACCEPTED!
[2016-04-15 21:25:35.139] Solved and confirmed block 407492 by 1JmnazCaLCnCSw3BZjo9NWhQGoMnp2BxPn
[2016-04-15 21:25:35.139] User 1JmnazCaLCnCSw3BZjo9NWhQGoMnp2BxPn:{"hashrate1m": "1.75P", "hashrate5m": "1.74P", "hashrate1hr": "1.77P", "hashrate1d": "308T", "hashrate7d": "50.9T"}
[2016-04-15 21:25:35.139] Worker 1JmnazCaLCnCSw3BZjo9NWhQGoMnp2BxPn:{"hashrate1m": "1.75P", "hashrate5m": "1.74P", "hashrate1hr": "1.77P", "hashrate1d": "308T", "hashrate7d": "50.9T"}
[2016-04-15 21:25:35.139] Block solved after 652938252734 shares at 365.4% diff
Holy Bit, that's my address!!!! What a day, after 6 months of doing solo  CK, please send me your btc address, will buy you a beer Thanks & Regards. Congrats! My address is in my forum profile, thanks! |
|
|
|
I use rentals from time to time on kano.is can't get it to work here any suggestions?
"...If you use an incompatible rental service that refuses to work on port 3333 try port 3334..." Refer to 1st post in this thread -- all the information you need for solo mining here. I use NiceHash, I've tried both ports with no luck 999 times out of 1000 if someone can't mine on this pool it's because they're not using a valid bitcoin address as their username. |
|
|
|
ok sorry if I judge it wrongly lol.. I thought that if a block contain no transaction, it called empty block. If its not immediately after a new block, it's not empty block? I'm really confuse lol. anyone kind enough to explain it to me No you got it right the first time. The rest of the discussion was trying to ascertain why it was an empty block. |
|
|
|
Check the times of the blocks: 2016-04-15 02:57:19.832312 UpdateTip: new best=0000000000000000052e336f67c1b0d339d5e7423595c60f169cd17bd24e5306 height=407354 log2_work=84.48832
tx=122495865 date=2016-04-15 02:57:07 progress=1.000000 cache=4.7MiB(5564tx)
2016-04-15 03:21:13.214595 UpdateTip: new best=000000000000000003828fbc61ad281aa2e298ed4a299abf36209a4725d51930 height=407355 log2_work=84.48836
1 tx=122495866 date=2016-04-15 03:20:49 progress=1.000000 cache=51.3MiB(16114tx)
Doesn't look like it was immediately after a new block... So, what do you think happened? Someone configured their coin daemon that feeds their p2pool instance to do so. |
|
|
|
When P2Pool learns that there's a new block, it mines empty blocks until bitcoind gives it a block template. The alternative to doing this would be to mine orphaned blocks rather than empty ones. :/ Check the times of the blocks: 2016-04-15 02:57:19.832312 UpdateTip: new best=0000000000000000052e336f67c1b0d339d5e7423595c60f169cd17bd24e5306 height=407354 log2_work=84.48832
tx=122495865 date=2016-04-15 02:57:07 progress=1.000000 cache=4.7MiB(5564tx)
2016-04-15 03:21:13.214595 UpdateTip: new best=000000000000000003828fbc61ad281aa2e298ed4a299abf36209a4725d51930 height=407355 log2_work=84.48836
1 tx=122495866 date=2016-04-15 03:20:49 progress=1.000000 cache=51.3MiB(16114tx)
Doesn't look like it was immediately after a new block... |
|
|
|
|
Mikestang's right. If all the posts are about non-bitcoin mining hardware I'll just close the thread. You can start one in altcoin mining.
|
|
|
|
Once the network diff jacked up over like 80G people really got turned off (no pun) from solo mining and stopped. There's not nearly as many active solo miners as there was just a while ago. I think the halving could change all of this, but we shall see...
That's not really true about people getting turned off. The average hashrate on solo pool has continued to climb consistently. The only thing really is that diff exploded for a while there proportionately more than hashrate and predicting a loss in my revenue with that diff rise, along with having invested in more infrastructure at the same time I had no choice but to increase fees. If I hadn't, this would have become a non-profit venture, only making profit from donations. That would have made it hardly worth the effort I put into code and pool maintenance. Anyway I can't see people stopping mining solo and as they fall off the profit curve, more people are throwing their straggling hardware here. The proportion that rent I cannot predict and to be honest more people rent than I ever expected would. Mine on. |
|
|
|
i coulddnt stay away i pointed back my mini farm
of 4 s1's
1 s2
4 compac sticks
and also pointed a small 5+th rental here
That's not so much a mini farm as a... veggie patch? Anyway with the other posts on this thread it is slowly turning into a combined marketplace/services thread and getting way offtopic. Can we try to keep to posts relevant to the pool only please? |
|
|
|
...There was absurdly good luck for a period before that... and it will happen again.
Can you give us a raw estimate what that will be in % luck (lets say for the last 10/25/50 blocks)?  Don't have that much data, so no sorry. |
|
|
|
|
Show Posts
