Cockeyed
Member
 Offline
Activity: 73
Merit: 10
|
 |
August 20, 2013, 12:21:40 PM |
|
Damn, I wanted to sell some IFC on eBay, and I wrote "InfiniteCoin - not BitCoin" to make clear what it is. eBay got somehow crazy now. They erased my offer because it´s "Abue of Trademarks". So BitCoin is a Trademark now on ebay... Really crazy gus, but never mind.
What I wanted to say: Some hours ago IFC went time 18 (from 5 to 90)! But now dropped back to 8. (on Coins-E).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
You can see the statistics of your reports to moderators on the "Report to moderator" pages.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
|
|
sololoop
Member
Offline
Activity: 123
Merit: 10
|
|
August 20, 2013, 01:00:21 PM |
|
Damn, I wanted to sell some IFC on eBay, and I wrote "InfiniteCoin - not BitCoin" to make clear what it is. eBay got somehow crazy now. They erased my offer because it´s "Abue of Trademarks". So BitCoin is a Trademark now on ebay... Really crazy gus, but never mind.
What I wanted to say: Some hours ago IFC went time 18 (from 5 to 90)! But now dropped back to 8. (on Coins-E).
probably ebay has no ideal how to handle hundred million / billion  amount...that's why your offer being erased |
|
|
|
|
sololoop
Member
Offline
Activity: 123
Merit: 10
|
|
August 20, 2013, 02:00:02 PM |
|
Pleased to help, c1010010. sololoop, thanks for pointing this out - you're right, the pool difficulty isn't showing correctly on the stats page. Both the pool difficulty and the time to share are underreporting by a factor of about 10 on the stats page but P2Pool's logs show higher difficulty. At the moment, for example, the logs show Share difficulty: 0.516141 whereas the share difficulty shown on the stats page is 0.0513. Similarly the logs show Expected time to share: 27.3 seconds (equivalent to 0.455 minutes) whereas the stats page shows 0.0459 minutes. The logs seem to be correct and the pool seems to be behaving in accordance with the logs. No idea at the moment why the stats page is showing the incorrect figures. A similar situation has also been reported by another p2pool user at https://bitcointalk.org/index.php?topic=18313.msg2961120#msg2961120 . I'll post a message in that thread and see tomorrow if the ratios remain the same. thanks for clarify. It is exactly what you said. Tested on 350k miner today, cost it 2 hours to get a real shares  . Once the address in, the miner got its deserved reward. |
|
|
|
|
|
TreasureSeeker (OP)
|
|
August 21, 2013, 01:36:36 AM |
|
I've compared the figures in the logs for "share difficulty" and the "Expected time to share" with the figures displayed on the stats page again tonight and they're still differing by about the same ratios. The stats page when I checked was page showing a "Share difficulty" of 0.0617 whereas the log was showing difficulty of 0.621079 . Therefore the stats page is displaying a share difficulty of 1/10.066110 of the log's share difficulty. For the "Expected time to share" the stats page was showing 0.0461 minutes whereas the share log was showing 27.3 seconds (0.455 minutes) . Therefore the stats page is displaying a share difficulty of 1/9.869848 of the log's share difficulty. I'm still waiting for an answer to this problem from the thread I mentioned in my previous post. Meanwhile if you're looking at the stats page, just multiply the "Share difficulty" and the "Expected time to share" by 10 and you should be about right. Apologies meanwhile for any confusion this may cause. (At 350 kh/s and a share difficulty of around 0.6 which, based on the logs being right, we would have had during today, it would take just under 2 hours on average between finding shares, so based on your experience sololoop, I think we're on the right track in assuming the logs are showing the right share difficulty  ). |
|
|
|
Hippie Tech
aka Amenstop
Legendary
Offline
Activity: 1624
Merit: 1001
All cryptos are FIAT digital currency. Do not use.
|
|
August 21, 2013, 01:55:30 PM |
|
While some of the reward drops are explainable, the ones seen below are not. Notice how the pool's hashrate is fairly constant.  TODAY'S VICTIMS. 1.29 mhash IS NOT 'DUST'.  960 khash RIPPED OFF !  910 khash PWN'D ! Stay tuned ! Let see how long it takes this one to recover.  |
|
|
|
sololoop
Member
Offline
Activity: 123
Merit: 10
|
|
August 21, 2013, 03:13:43 PM |
|
While some of the reward drops are explainable, the ones seen below are not.
Notice how the pool's hashrate is fairly constant.
TODAY'S VICTIMS.
1.29 mhash IS NOT 'DUST'.
960 khash RIPPED OFF !
910 khash PWN'D ! Stay tuned ! Let see how long it takes this one to recover.
Vicims? or simple math on your prove : local rate: mean 101MH/s total payout 131072 1.29 mhash IS NOT 'DUST'. 1.29m / 101m = 0.01277 * 131072 = 1674 coins but he got 2.12k 2120 coins <--- victim ??  446 more than expert 960 khash RIPPED OFF ! 0.96m / 101m = 0.00950495 * 131072 = 1245 coins he got 1.12k 1120 coins <---oh my god.......125 coins less = victim  910 khash PWN'D ! Stay tuned ! Let see how long it takes this one to recover. 0.91m / 101m = 0.0090099 * 131072 = 1180 coins he got 1.07k 1070 coins <----oh ....scam ? victim !?  110coins less ....... Actually, do you means address : iRG4LA with 1.29m earned more point than iGZzG 960k and iBubSS 910k ?? |
|
|
|
|
Hippie Tech
aka Amenstop
Legendary
Offline
Activity: 1624
Merit: 1001
All cryptos are FIAT digital currency. Do not use.
|
|
August 21, 2013, 06:26:46 PM |
|
I'm not worried about the one day averages because of the way the miners come and go with this site. Explain the parts where no IFC is being paid and the steep steady declines. Do you not see how those averages should have been much higher ? |
|
|
|
|
TreasureSeeker (OP)
|
|
August 21, 2013, 08:07:23 PM |
|
This is all "as far as I understand it".... Directly from the Bitcoin wiki entry on p2pool at https://en.bitcoin.it/wiki/P2PoolPayout logic
Each share contains a generation transaction that pays to the previous n shares, where n is the number of shares whose total work is equal to 3 times the average work required to solve a block, or 8640 (= 24 hours of shares), whichever is smaller. Payouts are weighted based on the amount of work each share took to solve, which is proportional to the p2pool difficulty at that time.
Where it says 24 hours of shares, read this as 72 hours in the case of TreasureQuarry as TreasureQuarry's share target is 30 seconds (rather than 10 seconds which used to be the case for Bitcoin p2pools when that wiki entry was written. Bitcoin now also uses 30 second share targets in the latest p2pool release). It's worth reading the entire wiki entry by the way to see the complexity of p2pool's share chain etc. A very important part of the entry is the "whichever is smaller". When you find a share, payments start in the next block found by the pool. Payments don't necessarily continue for 72 hours based on that one share though because of the "whichever is smaller" part of the wiki entry. Over the 2 or 3 days I've had a look at a relatively low hashrate miner and this has basically meant that payments for one share have continued for between 25 to 38 blocks roughly (it varies). At that point you've been paid the correct amount for that share. If you've not found a share again, payments will stop (the gaps you see) until another share is found. Rises and dips, or higher or lower than expected averages over a relatively small period of time would be due to the miner's success or failure ("luck" if you like) in actually finding shares. |
|
|
|
Hippie Tech
aka Amenstop
Legendary
Offline
Activity: 1624
Merit: 1001
All cryptos are FIAT digital currency. Do not use.
|
|
August 21, 2013, 08:38:12 PM |
|
The truth is .. there is NO EXPLANATION because these are not just slight variations.
+/- 5-10% swings in hashrate or pay on any type of pool is normal.
In case you didn't know.. when the miner isn't plagued by "worker restart" messeges,
600 - 1600 khash DOES NOT HAVE A PROBLEM FINDING SHARES !!
STOP PLAYING STUPID !! PAY THE MINER'S WHAT YOU OWE THEM !!
|
|
|
|
|
TreasureSeeker (OP)
|
|
August 21, 2013, 09:06:27 PM
Last edit: August 21, 2013, 09:27:56 PM by TreasureSeeker |
|
# grep iBub log
2013-08-20 05:16:07.495854 GOT SHARE! iBubSS8GgNf1ci6BjQV7xe5qtLwkkuK1gV c84087c7 prev a7d635b3 age 4.89s
2013-08-20 06:41:23.795408 GOT SHARE! iBubSS8GgNf1ci6BjQV7xe5qtLwkkuK1gV b886c8fa prev 0657ed82 age 6.15s DEAD ON ARRIVAL
2013-08-20 12:20:01.970409 GOT SHARE! iBubSS8GgNf1ci6BjQV7xe5qtLwkkuK1gV a89f14a2 prev 8253530e age 16.24s DEAD ON ARRIVAL
2013-08-20 12:25:31.580541 GOT SHARE! iBubSS8GgNf1ci6BjQV7xe5qtLwkkuK1gV efb4c9cf prev 93142eae age 52.08s
2013-08-20 13:08:59.453283 GOT SHARE! iBubSS8GgNf1ci6BjQV7xe5qtLwkkuK1gV 71caacf9 prev 202e88fe age 6.11s
2013-08-20 14:13:02.597145 GOT SHARE! iBubSS8GgNf1ci6BjQV7xe5qtLwkkuK1gV d126ced3 prev bd656547 age 47.52s DEAD ON ARRIVAL
2013-08-20 15:23:18.621038 GOT SHARE! iBubSS8GgNf1ci6BjQV7xe5qtLwkkuK1gV 2b734c0d prev 2b12a041 age 3.42s
2013-08-20 17:12:51.843618 GOT SHARE! iBubSS8GgNf1ci6BjQV7xe5qtLwkkuK1gV 461e05e2 prev 576f7b7f age 5.33s
2013-08-20 19:17:15.054809 > Worker iBubSS8GgNf1ci6BjQV7xe5qtLwkkuK1gV submitted share more than once!
2013-08-20 19:27:41.871266 GOT SHARE! iBubSS8GgNf1ci6BjQV7xe5qtLwkkuK1gV 20349911 prev 7508dde0 age 3.43s
2013-08-20 19:31:55.252850 GOT SHARE! iBubSS8GgNf1ci6BjQV7xe5qtLwkkuK1gV 925159da prev b8dd32d3 age 10.78s
2013-08-20 19:56:43.928146 GOT SHARE! iBubSS8GgNf1ci6BjQV7xe5qtLwkkuK1gV 3e903d26 prev 64249405 age 3.67s
2013-08-20 20:19:23.721426 GOT SHARE! iBubSS8GgNf1ci6BjQV7xe5qtLwkkuK1gV ca9ab383 prev dc0f8cb5 age 2.24s
2013-08-20 21:33:53.029647 GOT SHARE! iBubSS8GgNf1ci6BjQV7xe5qtLwkkuK1gV 3afaedd8 prev 61e6fabf age 22.25s
2013-08-20 22:31:08.293278 GOT SHARE! iBubSS8GgNf1ci6BjQV7xe5qtLwkkuK1gV ec6b1d4e prev 758c5050 age 4.30s
2013-08-20 22:49:37.715850 > Worker iBubSS8GgNf1ci6BjQV7xe5qtLwkkuK1gV submitted share more than once!
2013-08-21 00:07:38.549587 GOT SHARE! iBubSS8GgNf1ci6BjQV7xe5qtLwkkuK1gV 9caf9252 prev 5401aa7f age 9.38s
2013-08-21 00:17:14.858363 GOT SHARE! iBubSS8GgNf1ci6BjQV7xe5qtLwkkuK1gV 161be422 prev b04dea64 age 9.44s
2013-08-21 01:45:37.632737 GOT SHARE! iBubSS8GgNf1ci6BjQV7xe5qtLwkkuK1gV a39daf35 prev 1d331779 age 10.40s
2013-08-21 01:45:47.729197 GOT SHARE! iBubSS8GgNf1ci6BjQV7xe5qtLwkkuK1gV 82f254ac prev a39daf35 age 9.84s
2013-08-21 01:46:10.365619 GOT SHARE! iBubSS8GgNf1ci6BjQV7xe5qtLwkkuK1gV d70f0c81 prev 82f254ac age 22.37s
2013-08-21 02:38:37.997384 GOT SHARE! iBubSS8GgNf1ci6BjQV7xe5qtLwkkuK1gV e8a0ad35 prev 422a7a84 age 2.03s
2013-08-21 02:42:57.411146 GOT SHARE! iBubSS8GgNf1ci6BjQV7xe5qtLwkkuK1gV df666a9d prev b39ce221 age 18.03s
2013-08-21 04:45:44.814539 GOT SHARE! iBubSS8GgNf1ci6BjQV7xe5qtLwkkuK1gV 29945ec2 prev 2f488278 age 20.92s
2013-08-21 04:57:33.594080 GOT SHARE! iBubSS8GgNf1ci6BjQV7xe5qtLwkkuK1gV 14ffc0c0 prev 5f578950 age 25.99s
2013-08-21 05:09:41.341555 GOT SHARE! iBubSS8GgNf1ci6BjQV7xe5qtLwkkuK1gV eb722afa prev 725196f4 age 8.52s
2013-08-21 06:47:38.267201 GOT SHARE! iBubSS8GgNf1ci6BjQV7xe5qtLwkkuK1gV efdd6f81 prev 20091296 age 3.32s
2013-08-21 07:53:01.037272 GOT SHARE! iBubSS8GgNf1ci6BjQV7xe5qtLwkkuK1gV ce586c63 prev 9d83e953 age 23.84s
2013-08-21 09:06:22.909099 GOT SHARE! iBubSS8GgNf1ci6BjQV7xe5qtLwkkuK1gV b32cea58 prev 44b633cb age 15.04s
2013-08-21 11:25:30.903626 GOT SHARE! iBubSS8GgNf1ci6BjQV7xe5qtLwkkuK1gV a48b9595 prev 0d9a482a age 22.63s
2013-08-21 13:24:36.583842 GOT SHARE! iBubSS8GgNf1ci6BjQV7xe5qtLwkkuK1gV d0d49288 prev afc4d138 age 34.55s
2013-08-21 13:38:35.562768 GOT SHARE! iBubSS8GgNf1ci6BjQV7xe5qtLwkkuK1gV 4270c16b prev b129f441 age 3.06s
2013-08-21 13:39:49.454854 GOT SHARE! iBubSS8GgNf1ci6BjQV7xe5qtLwkkuK1gV 6e6a9713 prev fea9a986 age 37.09s
2013-08-21 13:52:05.684458 GOT SHARE! iBubSS8GgNf1ci6BjQV7xe5qtLwkkuK1gV e1ba54cc prev bca34871 age 10.44s
2013-08-21 14:02:59.349550 GOT SHARE! iBubSS8GgNf1ci6BjQV7xe5qtLwkkuK1gV 9401dee0 prev f56abe1f age 2.43s
2013-08-21 14:23:43.746906 GOT SHARE! iBubSS8GgNf1ci6BjQV7xe5qtLwkkuK1gV e91e448c prev 88eb515d age 5.14s DEAD ON ARRIVAL
2013-08-21 14:27:05.035738 GOT SHARE! iBubSS8GgNf1ci6BjQV7xe5qtLwkkuK1gV cf478d6b prev d5b55f48 age 7.85s
2013-08-21 15:46:18.715602 GOT SHARE! iBubSS8GgNf1ci6BjQV7xe5qtLwkkuK1gV 9683ba12 prev cf6255c4 age 23.40s
2013-08-21 16:43:19.979706 GOT SHARE! iBubSS8GgNf1ci6BjQV7xe5qtLwkkuK1gV f5aca897 prev 08b68dda age 6.48s
2013-08-21 18:39:08.509063 GOT SHARE! iBubSS8GgNf1ci6BjQV7xe5qtLwkkuK1gV ae369767 prev 0f8663f1 age 9.14s DEAD ON ARRIVAL
See how shares become more spread out after 5.09 on 21 august (Times are UTC) until 13.24.
Does everyone see the graphs in their own local timezones by the way?
|
|
|
|
Cockeyed
Member
Offline
Activity: 73
Merit: 10
|
|
August 21, 2013, 10:11:54 PM |
|
Whatever. I did not get anything since days. I guess it´s because the overall hashrate is exploded and my 1.5 kH is kinda homeopathic. By tomorrow or friday I will upgrade a bit.
|
|
|
|
|
|
TreasureSeeker (OP)
|
|
August 21, 2013, 10:40:12 PM
Last edit: August 21, 2013, 11:22:22 PM by TreasureSeeker |
|
Yes, at 1.5 Kh/s and the current share difficulty of about 1.3, it's likely to take about 43 days to find a share, interpreting the results from burnside's calculator. Good luck with the upgrade, Cockeyed Edited...just noticed that the log is now showing share difficulty of around 2.8 (which would mean even longer for you, Cockeyed). Seems it's not as simple as just multiplying what's shown on the stats page by 10. I'm still waiting for a reply in the other thread about the underreporting of share difficulty on the stats page. |
|
|
|
Cockeyed
Member
Offline
Activity: 73
Merit: 10
|
|
August 22, 2013, 12:46:49 PM |
|
OK, thanks.
Is there any webpage where we can see the ovarall hashrate, difficulty, blockchainsize, etc.?
|
|
|
|
|
|
TreasureSeeker (OP)
|
|
August 22, 2013, 09:15:29 PM |
|
For the entire Infinitecoin network as a whole you can view the current difficulty on the uppermost (ie the most recent) block on the block explorer at http://exploretheblocks.com:2750/chain/Infinitecoin . The "Block" number on that page will show you how many blocks have been found so far in total by the entire Infinitecoin network. You can also view the current difficulty and number of blocks using your Infinitecoin wallet program on your pc. Start the Infinitecoin program, and wait for it to synchronise and download any blocks it needs to get itself up to date. Then from the top menu go to "Help", select "Debug Window" from the drop-down menu and the click the "Console" Tab. Then where you see the ">" sign at the bottom, type getinfo Press enter and you 'll see "difficulty" of the entire Infinitecoin network and "blocks" which is the total number of Infinitecoin blocks that have been found by the entire infinitecoin network until now. You'll also see some other information too. If, at the ">" sign you enter getmininginfo You'll get some more interesting stuff including "networkhashps" which is the total hashes per second if the whole Infinitecoin network (divide by 1,000 to get Kh/s or by 1,000,000 to get Mh/s). For the pool, the "Local rate" figure on the stats page at http://treasurequarry.com:9844/static/ will give you the total pool hashrate. The "Share difficulty" figure is still displaying incorrectly (I'm still waiting for a reply from the other thread about this). Currently it's showing a 0.56 according to the p2pool log (this seems to be wobbling much more than I'd expect but whatever it's doing it's the difficulty for all miners so everyone should be on an equally fair footing when it comes to finding shares). If there's not a fix to this difficulty oddness posted by tomorrow I'll roll back to the previous stable version of p2pool that we were using before this weekend until another upgrade comes along. |
|
|
|
|
killdemon
|
|
August 24, 2013, 11:42:23 AM
Last edit: August 24, 2013, 11:53:51 AM by killdemon |
|
Blocks are found and block explorer is showing amounts which i should receive in my wallet but i am not getting anything!?!
|
|
|
|
|
TreasureSeeker (OP)
|
|
August 24, 2013, 01:24:45 PM |
|
If the block explorer shows amounts going to you, they should be showing in your wallet. Is your wallet synchronised up-to-date with all current blocks?
|
|
|
|
|
killdemon
|
|
August 24, 2013, 02:42:12 PM |
|
False alarm.  I did not have conf file. It worked before, anyway i have added nodes and now it is ok. My wallet is synchronised. |
|
|
|
|
TreasureSeeker (OP)
|
|
August 24, 2013, 03:27:24 PM
Last edit: August 24, 2013, 04:34:28 PM by TreasureSeeker |
|
Great news, killdemon. I've been thinking that somehow the incorrect displaying of the share difficulty on the stats page may be related to the way I downloaded the new upgraded software from github to my pc then uploaded it to my server. I think I may have needed to git-clone directly on the server. I'll be trying to move the existing sharechain to a newly git-cloned version of the pool in the next hour or so. There will probable a few bits of downtime whilst I'm giving this a go. Apologies in advance. |
|
|
|
|
TreasureSeeker (OP)
|
|
August 24, 2013, 03:52:06 PM |
|
The git-cloned copy isn't accepting the existing sharechain. It looks like I'm going to need to scrub the existiing sharechain and start a new one. Effectively this will restart the pool completely from scratch. I'll do this on Monday. That'll give anyone who is currently mining enough warning.
|
|
|
|
Cockeyed
Member
Offline
Activity: 73
Merit: 10
|
|
August 24, 2013, 07:45:02 PM |
|
Is there anything which it means us to do?
I think for history purpose the old stats should remain somehow accessible.
PS: I had no chance fto take the task for my planned upgrade session. I will try to speed up my mining on monday. Beside of all the quarrel here in the quarry, it´s a really cool pool I must say.
|
|
|
|
|
|
