Roll up your machines and join the fun mining some Infinitecoins at http://treasurequarry.com:9844 . This is a new p2pool. Everything seems to be working well, including payments. It would be great if you could give it a try - and hopefully stay if you like it

I'm hoping it should have a high efficiency to ensure your valuable hashes aren't wasted (please see "Choosing your pseudo-share difficulty" below to maximise your efficiency).

To get a good representation of your hashrate on the pool's graphs, and also to possibly improve your efficiency, you may find that adding the following to the end of your Infinitecoin address (including the + sign) will help. Just find your nearest hashrate from the table below:

This will make your miner report when it finds "pseudo-shares" of a certain difficulty (you'll still need to find real shares for payments to start, which may take anything between a few seconds to a half a day or so, depending on your hashrate). Once you do find a share, payments will start going straight to your wallet as soon as the p2pool finds blocks. Due to the way p2pool's PPLNS (pay per last N shares) works, the payments may seem to start slow but will reach a peak and reasonably steady rate after a couple of days or so.

If you have any questions about your mining, it would be appreciated if you would post your IFC address that you're mining with, the hashrate your miner is reporting and the number of hours continuous mining that you are querying. This will help me to give more specific replies.

Happy mining and enjoy chipping away to get that treasure at the quarry!

Updated 4jan 13:

I've been thinking about reducing the time between shares to a lower timescale. This would have the effect of reducing the share difficulty, which would make it easier for everyone to find shares, and would mean fewer and smaller gaps between payments. I've posted a poll today at http://infinitecointalk.org/index.php/topic,1083.0.html and would be grateful if all current TreasureQuarry miners would vote on what they would prefer.

Second block found this afternoon! The server clock is fine, and Infinitecoind and p2pool's logs are recording the correct time of events, but The Timestamp that p2pool is showing for the blocks is still off for some reason. I'm wondering if it's anything to do with the slow speed of the pool currently, or the fact that only two of us are mining here at the moment, so if anyone can throw some hashes at it, it would be really appreciated and may hopefully help to sort this Timestamp puzzle out....please, please.

Yay, thanks, folks!!! The extra miners and hashpower has brought the timestamp for blocks found up to the correct time. The big increase in speed caused a temporary decrease in efficiency for a short while, but the pool has now compensated by increasing the difficulty of shares which has reduced the DOA rate.

Things are looking good...let's keep those machines digging at the quarry.

I've changed the text "Payout if block found NOW " to "Pool fee if a block were found NOW" on the front statistics page at http://treasurequarry.com:9844/static/ as I think that's what it's showing there...it's what it's showing me anyway . Can anyone check to make sure it's showing them around 1.5% of the 524288 block reward (the pool's fee) under ""Pool fee if a block were found NOW" " when they view the page and it's not somehow showing your own expected payouts (your own expected payouts will be under the " Expected Payouts if Block Found Now" tab). The figure seems to wobble a bit but I guess it'll average out at the 1.5% fee amount.

I've just created a block explorer at http://exploretheblocks.com so that we can view full details of blocks found by the pool now . I had to restart p2pool to get it to pick up the correct address to use on the links on the last blocks tab and other pages...apologies for a minute or two's downtime there.

Exploretheblocks.com is on a different server to TreasureQuarry.com, to ensure the block explorer doesn't use any resources of the pool server.

Hi, I'm trying to introduce my kids to mining some alt coins and it was suggested that infinitecoin would be good for them to start with (to see results coming in). However I have some questions starting up and would appreciate some advice for a noob! In the instructions I have it says to put in the config file:

rpcuser=**Yourusername**rpcpassword=**Yourpassword**

My question is what is this 'rpcuser' and 'rpcpassword'? Where do I get them from?

You could have young millionaires there, SlobBastard! (depending on hashrates). Don't forget the block reward halves in about 9 days - best for them, and anyone reading this, to start as soon as they can.

I've updated TreasureQuarry (and ExploreTheBlocks) to fisheater's new version1.1 of Infinitecoin to help protect the network by the way.

"Houston, we are secure and ready for the next stage of our journey...Onwards into the Infinite!"

I've just upgraded TreasureQuarry and ExploreTheBlocks to the new version 1.2 of infinitecoin, released by fisheater earlier today.

TreasureQuarry is finding blocks at fast and regular rates, with efficiency running at 105% at the moment, and the coins are pouring into happy miners' machines. If your computermachine isn't mining at the quarry yet, come join the infinite fun.

If I understand correctly, you're using your Cryptsy exchange address as a payment address for your pool earnings? The general advice for P2Pool is not to use an exchange address. It's best to use an address from your own computer's wallet for your pool payments. You may want to check with Cryptsy regarding the payment(s) as hopefully they may be able to trace things.

Tell me how it goes, xyzwarrior. I've just checked the Cryptsy chatbox and it looks like other people are mentioning problems with IFC deposits currently so you're probably not alone - guess they may have some temporary teething troubles seeing as they only introduced IFC yesterday.

Seems like I'm getting way too many restarts on my two workers. Is the pool having issues?

Just been checking for you, Swimmer63. There have been a few peaks in latency but nothing major. Are you using cgminer? I've been reading about odd disconnects recently at https://bitcointalk.org/index.php?topic=188533.0 . Not sure if anything in that thread relates to your problem. What message are you getting when it disconnects, how long are they for and does it reconnect automatically after? Can you give me the command that you're using to mine too.

Is anyone else experiencing this? If so, can you give the same details?

They've got the transaction but may not know that it should be allocated to you. Find the transaction ID (or IDs if there are multiple payments) from the block explorer and give these to Cryptsy. They should be able to confirm they've got the transaction by running

Code:

infinitecoind gettransaction **TRANSACTION ID HERE**

Checking a block explorer in conjuction with the amount of the transaction(s) will confirm it should be allocated to your address.

Yes, that's the correct column. There are indeed a lot!...seems to be about 150 transactions to you there. Try giving Cryptsy the link and see what they say. Unless they can think of another way to find the transactions then they may need to pick each one out to allocate it to you.

I'm getting a wicked low hash rate. Is this common with scrypt mining? When I was mining bitcoin with guiminer the hash rate was 600 mega hash now I'm getting about 240-290 killo hash with guiminer for scrypt. If it helps the video card is a Radeon 6870 Sapphire edition.

Welcome to the Treasure Quarry, BitCoinPokerBro. Yes, as you've found there's a big difference between the fast sha256 type of hashing that Bitcoin uses and the scrypt hashing used by Infinitecoin. Everyone hashing Infinitecoins experiences this difference compared to Bitcoin.

I switched to cgminer 3.3.0 from reaper and seeing alot of these "stratum from pool 0 requested work restart" messeges.

Help meee ..

HT xD

Hio Hippie Tech, hope you're having a profitably fun time mining at the TreasureQuarry

From what I've been able to gather, the "stratum from pool 0 requested work restart" messages are normal and occur when someone in the pool finds a share. P2Pool uses a sharechain in a similar way that Bitcoin and Infinitecoin have a blockchain (more info about the sharechain is in the Bitcoin wiki entry on P2Pool).

I've set the share target time to 30 seconds for the Infinitecoin pool, so you should probably find these messages occur around every 30 secs on average (shorter if there has just been a big increase in hashrate at the pool whilst the share difficulty adjusts, or longer if there has just been a big decrease in hashrate) .

c1010010, I'm hoping for exactly that! The thing is, I really do think it's possible in the medium to long term, especially when you think that in 2 years time there will only be 0.015625 coins produced per block, and continuing to half each month.

I switched to cgminer 3.3.0 from reaper and seeing alot of these "stratum from pool 0 requested work restart" messeges.

Help meee ..

HT xD

Hio Hippie Tech, hope you're having a profitably fun time mining at the TreasureQuarry

From what I've been able to gather, the "stratum from pool 0 requested work restart" messages are normal and occur when someone in the pool finds a share. P2Pool uses a sharechain in a similar way that Bitcoin and Infinitecoin have a blockchain (more info about the sharechain is in the Bitcoin wiki entry on P2Pool).

I've set the share target time to 30 seconds for the Infinitecoin pool, so you should probably find these messages occur around every 30 secs on average (shorter if there has just been a big increase in hashrate at the pool whilst the share difficulty adjusts, or longer if there has just been a big decrease in hashrate) .

c1010010, I'm hoping for exactly that! The thing is, I really do think it's possible in the medium to long term, especially when you think that in 2 years time there will only be 0.015625 coins produced per block, and continuing to half each month.

Thanks for the input but it still seems odd that it happens so frequently and randomly.

Did you mean the network ? The pool is definitely not finding that many shares/blocks. lol

Other than that all seems fine with the graphs and payouts. A top 10-20 block finders list would be nice.

And of course I'm having fun... missing blocks by 1-3K. Stay tuned for more high risk var-diff maddess !!

Thanks for the input but it still seems odd that it happens so frequently and randomly.

Did you mean the network ? The pool is definitely not finding that many shares/blocks. lol

I can see what you mean from your screenshot. I did mean that apparently the messages should happen each time someone on the pool itself solves a share, but they do appear to be happening faster than the average expected time between shares, although the time between shares can vary a bit temporarily before retargeting itself back (to 30 seconds for the Infinitecoin pool at TreasureQuarry) if there has been a recent change in total hashpower being directed at the pool.

I'll do a few checks in the next day or so - will try mining with Stratum whilst checking the logs to see if the messages coincide with shares being found or anything else.

Other than that all seems fine with the graphs and payouts. A top 10-20 block finders list would be nice.

That's good to have confirmed. I took a quick look in the P2Pool logs last night and couldn't see it recording who had found blocks. A block finders list may need to involve hacking around in the main p2pool python source (eek). I'll do some more investigating regarding that.

I've been looking a bit more into those "stratum from pool 0 requested work restart" messages. I haven't had much luck running cgminer on my home computer so have used bfgminer to check things instead. bfgminer actually gives a bit more of a friendly looking message of "stratum from pool 0 requested work update". On checking the P2Pool logs these messages do coincide much of the time with the times when someone in the pool finds a share. It's doesn't coincide all of the time with a share being found but it's basically a message telling you that your computer has received new work from the pool to work on.

No block found only for me? When i look at the other miner´s stats in this pool I clearly see that they got transactions. If you look at my stat you can see that there are no transactions for all the time. Maybe it´s because of my low hashing power? Strange thing.

But anyways, I will continue for a week or two, and if there is still no transaction I will engage in solo mining. Only bad thing is: With solo mining I have only 1,9 KH, while with Pool mining I get out about 3KH...

Cockeyed, you're in the same boat as me with a very low hashrate (I run at about 4kh/s). You're right in thinking that this is the reason for the breaks in payments that you're experiencing, as I experience a similar thing. At the current share difficulty of the pool of 0.0588, you're only likely to hit roughly one share a day at 3kh/s...in fact looking at your daily speed graph at http://treasurequarry.com:9844/static/graphs.html?Day, your average today is about 2.39kh/s , with a current rate as I'm writing this of about 1kh/s so it could be even longer than that between shares. You're probably doing the right thing by giving it a week or two of mining to see how things turn out, because with a low hashrate you will end up with some variance, so you'll need this type of longer term period of mining to give you a better overall averagey picture of everything.

Spoetnik, good to know that those transactions arrived after updating your wallet - I bet that was nice to see all those lovely Infinitecoins flooding in.

BitCoinPokerBro, Great to hear you're enjoying mining at TreasureQuarry What you've mentioned about ease of mining is one of things I love about P2Pool - you can just start immediately with no need for signing up or anything, and the transactions will go straight to your wallet once you've started to find shares....no risk of leaving your earnings in an online pool wallet. Your experiences with breaks in payouts for an hour or 2 every now and then may be a less severe version of Cockeyed's situation - even with a your hashrate of 240 to 290 kh/s that you mentioned previously it's possible that there may be unlucky times when you don't find a share for a good while (maybe when there is a high overall hashrate on the pool and therefore a high difficulty), and the payouts that you've been getting use up all of the share credit that you've built up. If you want me to look into anything in a bit more detail now or at any time, please feel free to give me your Infinitecoin address that you're using to mine at the Quarry and I'll be happy to delve a bit more.

TreasureSeeker, thanks a lot for your reply! Because I am just a beginning miner I need to collect some experiences. Last week I actually started with mining BTCs by using two "BFL Jalapeno". That are two black boxes, and they require my PC to be turned on all the time. So I use the CPU - which is working anyways - for creating some InfiniteCoins. Thats about me.

If the low hashing power the reason for my problem, then I am cool with it. I just will continue and see how it comes out for me.

We seem to have had a bit of a drop in mining at the Quarry so blocks are coming a bit slow tonight. A low pool hashrate relative to the global Infinitecoin hashrate may actually be more likely to be the reason why BitCoinPokerBro had noticed a few gaps of an hour or two in getting payouts every now and then. Oh...we've just found a block as I'm writing this, that's good - I was about to say we're approaching an hour and a half since our last block and one is solved...yay!

I've not seen any true merged mining with Scrypt coins. I've read different things about it - some people seem to think that it's possible to be done at the pool end somehow, whereas others say it would need a complete change to coins' blockchain and code. I'd hazard a guess that the latter is probably correct.

To get a good representation of your hashrate on the pool's graphs, and also to possibly improve your efficiency, you may find that adding the following to the end of your Infinitecoin address (including the + sign) will help. Just find your nearest hashrate from the table below:

This will make your miner report when it finds "pseudo-shares" of a certain difficulty (you'll still need to find real shares for payments to start, which may take anything between a few seconds to a half a day or so, depending on your hashrate). Once you do find a share, payments will start going straight to your wallet as soon as the p2pool finds blocks. Due to the way p2pool's PPLNS (pay per last N shares) works, the payments may seem to start slow but will reach a peak and reasonably steady rate after a couple of days or so.

I've been playing with the site for some time, and lending all my my hashpower at times (10Mh/s). How far can I push your + notation?

You could set all your machines to +0.1, but you would end up with extremely spiky looking statistics on the graphs page. The suggested pseudo share difficulties based on your hashrate give a good balance between being small enough to allow p2pool to identify and graph your ongoing hashrate, whilst being not too short which would cause excessive traffic (reporting of lots of small pseudo-shares found) between your miner and the pool, which seems to increase your reported DOA/efficiency rate.

Apart from that, the actual size of the pseudo-shares isn't vital, as pseudo-shares themselves aren't used by p2pool in calculation of your earnings. It's only when the real shares are found that you'll get credit toward the block shareouts. You can see the difficulty of the real shares on the front statistics page at http://treasurequarry.com:9844/static/ . This real-share difficulty will vary depending on the pool's total hashrate.

Good questions, Hippie Tech and powpow. You had me worried there for a while, but after looking into it, these are orphaned blocks.

Generally with found blocks, if you go to the search box on the block explorer at http://exploretheblocks.com:2750/chain/Infinitecoin and type in the block number you'll get just one infinitecoin block displayed on the results. For example if you input block 123456 you 'll get:

However, if you go to the search box on the block explorer at http://exploretheblocks.com:2750/chain/Infinitecoin and type any of the block numbers that you've mentioned, you'll get two results - our orphaned block which doesn't have the block number beside it (but has just a block hash instead) and the the "real block" (booo!) which has the block number beside it, for example using block 196495 the results are

The payout addresses listed in our orphaned blocks are actually some kind of alternative version of your own addresses. For example, Hippie Tech's address iC6Yr743UWVzt3vtYWBXGxPsZNBmUzjgNB has its alternative version of 19d2R2ef47EdTqi43iD1pAddMuuYuAsYqU displayed in the orphaned blocks. This can be confirmed by putting each of those two versions of the address into the block explorer search - you'll see that all of the transactions are identical.

i keep noticing weird behavior with the IFC wallet and the best response i can get so far isIFC's wallet is randomly getting info from the LTC wallet, hence why i randomly get out of sync and the wallet's blocks double..its always somewhere around 198,151 blocks, but then out of no where it doubles and saying syncing (half way done)and i mine on your p2pool and run my wallet 24/7 with out ever turning it off, but restarting the block count goes back how it was an i'm synced instantly.anyway i'm told this is normal and was actually laughed at more than once for bringing it and when i tried to get any details about thisi was raged on by one guy who said he already explained it and that i should stfu.. (on cryptsy's chat box)what that guy told me was something like it's picking up data from the wrong chain which is pretty much what i already had heard previously lol

big deal or not i figured it was worth mentioning and curious if others have had this..and aside from when the pool gets popular and my payments slow down i think its all working just fine.good pool and solid up time.. thanks for sharing your pool with us your doing a good job i think with it

in case anyone is curious what one i am in the stats i amiG1DGcwK5Fzva9UihBWcfKxQufFGmjB1Ludoing avg 80kh/s on my nvidia 550Ti and occasionally restarting with a 9400GT for 2 running (gives me a total of 85kh/s)

i use the wallet for testing connections to a Cudaminer mod i am codingwhich is why the conf is like that, BUT i have not had any issues with anything anywhere near doing some test connections to my wallet..i mentioned that to show everyone i don't have any nodes added manually

oh yeah and i have gotten sporadic and stratum random receive line errors from Cudaminer and other people have too but i don't know if its related to this pool.hadn't seen it in week or two then yesterday it happened like 3 times fairly quick (when hashing was at around 30 MH/s)

disclaimer:this is not a request for an angry flame war ..i'm stating strange behavior i have noticed and the context it was in, nothing more.people can take what they will with this info.

seems you word something wrong its go time for a fight at the drop of a hat.. lot of attitude in the Altcoin scene (too many experts with pissy attitudes)

by the way i did some digging just now and i am getting a lot of blocks where i am not paid or listed toonot sure if that is because my hash power is low or what but i figure i should get something right ? even if its a small amount ?

Thanks for the positive comments about the pool, Spoetnik. Looking at the graphs I can see a short period of about an hour or so when you wouldn't have received a payment this morning. This is around the time that the total pool hashrate was quite high. If your own hashrate is small in relative terms to the total pool hashrate, you will find that p2pool starts creating gaps in your actual payments (in a similar way as Cockeyed has experienced, but to a lesser degree in your case as your hashrate is higher). Overrall in the longer term it should work out that your paid the correct amount though.

Regarding the resynching of the IFC wallet , I've noticed that happening every now and then on my home computer. I noticed tonight that I hadn't added the port number in my infinitecoin.conf file on my home PC so I've now added

port=9321

Time will tell over the next few days if this will stop the resynching I guess.

If you can tell me the exact cudaminer messages and the times they happen I may be able to look into that for you.

Ha ha - I did warn you (or at least c1010010) that things would look spikey if you used those much higher pseudo shares

Bit of a shock to see the massive bee when I visited the thread (apologies to the bee for calling it a fly). At that size it's really impressive though how much detail you got there from such a small scale - can see it has what almost looks like feathery toes on its feet. Can I ask what camera you used?

Hello there, I've been mining a lot on your pool recently with no problems, but I switched my rig on last night and no payments so far at 120kh (for at least a couple hours of mining, last night and this morning included). Is this to be expected?

Ah, now I see what you mean when you said the bee landed on your coffee cup, Hippe Tech - the cup is upside-down. Good old Olympus - they certainly make great quality cameras. Just found a picture of the FE-110 5mp online. One day when IFC is a dollar per coin I'll get a camera like that.

Thanks for mining at the Quarry, Roddy5690. Yes, now that the pook is hashing along at a higher total hashrate than recently, the pool share difficulty has increased. The share difficulty is automatically adjusted by p2pool as the total pool hashrate changes, with the aim of keeping the time between shares at around 30 seconds here at TreasureQuarry. With the higher share difficulty, you will find that it takes longer to generate enough share for payouts, and there may indeed be times when you don't actually get a payout. If you keep hashing along steadily the payouts you receive should work out right in the long term.

Welcome to the Treasure Quarry CaptChadd and thanks for the compliment. Wishing us all the best of luck in our mining!

Ok, thanks, I'll keep at it. Just in case there's an issue, my graph is all wrong - At the hour scale, Im bouncing up and down from 0 to 200khashes, and on the day and week scales, my miner may as well be inactive.

My shares are registering but not being paid. It started about the time that 50 mhash jumped in.

update..

The problem fixed itself and I noticed that the default address suffered the same fate. Sounds like the pool had issues with the 150%ish jump in hashpower.

Now we're over 200 m's. I smell ASIC.

Just a little hashrate switched from somewhere (LTC , FTC, FST ,DGC..etc) and found that this is the pool doesn't downed within 24 hours (i tested 3 IFC within 24 hours .. all went down ) ASIC..... far from that.

My shares are registering but not being paid. It started about the time that 50 mhash jumped in.

update..

The problem fixed itself and I noticed that the default address suffered the same fate. Sounds like the pool had issues with the 150%ish jump in hashpower.

Now we're over 200 m's. I smell ASIC.

Just a little hashrate switched from somewhere (LTC , FTC, FST ,DGC..etc) and found that this is the pool doesn't downed within 24 hours (i tested 3 IFC within 24 hours .. all went down ) ASIC..... far from that.

Those spikes are too steep for it to be that. Looks like one user per spike to me.

Welcome to TreasureQuarry, sololoop. Happy to confirm that the server seems to be handling the two big increases today very comfortably.

Checking the graphs it seems there were indeed two big users join today, Hippie Tech. One who joined about 3.45AM with about 50Mh/s (I guess that's you, sololoop) and another with about 80Mh/s who started at about 4PM. I think what sololoop is saying as that he has switched his mining from other coins to the pool - may have lots of GPUs. Very nice hashrate whatever it is.

Whilst I'm writing, can everyone check that they're including their IFC wallet address in their commandline (or GUIminer) correctly (see the first post in this thread for details). I've noticed today that on the bottom of the graphs page, someone is showing a mining under "null". Whoever this is, I don't want you to miss out on getting your Infinitecoins.

Welcome to TreasureQuarry, sololoop. Happy to confirm that the server seems to be handling the two big increases today very comfortably.

Checking the graphs it seems there were indeed two big users join today, Hippie Tech. One who joined about 3.45AM with about 50Mh/s (I guess that's you, sololoop) and another with about 80Mh/s who started at about 4PM. I think what sololoop is saying as that he has switched his mining from other coins to the pool - may have lots of GPUs. Very nice hashrate whatever it is.

Whilst I'm writing, can everyone check that they're including their IFC wallet address in their commandline (or GUIminer) correctly (see the first post in this thread for details). I've noticed today that on the bottom of the graphs page, someone is showing a mining under "null". Whoever this is, I don't want you to miss out on getting your Infinitecoins.

I haven't received any IFC since 15:54(whatever timezone exploretheblocks.com uses), or, according to my wallet, for about an hour as of writing this. I haven't changed anything in my .bat file, so I'm certain the problem isn't on my side. The graph for my address seems to be quite inaccurate, too - is that normal?

Hello hpski, thanks for mining at TreasureQuarry. The server uses UTC, but P2Pool itself is using UTC+1, equivalent to Central European Time or British Summer time. 15:54 is just before the big 80Mh/s jump in hashrate, so the share difficulty would have also jumped up at that time. This can increase variance if you have a low hashrate relative to the total pool hashrate. If you can give me your IFC address that you're using to mine at TreasureQuarry I can give you more info if you like.

I'm intending to upgrade to the latest p2pool software later tonight or tomorrow. I'm not sure about this but I'm hoping that this *may* help reduce variance for miners with a lower hashrate relative to the total pool hashrate.

Hello hpski, thanks for mining at TreasureQuarry. The server uses UTC, but P2Pool itself is using UTC+1, equivalent to Central European Time or British Summer time. 15:54 is just before the big 80Mh/s jump in hashrate, so the share difficulty would have also jumped up at that time. This can increase variance if you have a low hashrate relative to the total pool hashrate. If you can give me your IFC address that you're using to mine at TreasureQuarry I can give you more info if you like.

I'm intending to upgrade to the latest p2pool software later tonight or tomorrow. I'm not sure about this but I'm hoping that this *may* help reduce variance for miners with a lower hashrate relative to the total pool hashrate.

Hippie Tech and hpski: The pool's total hashrate has increased so your shareout per block will decrease. Usually an increase in the pool's total shareout would also mean that the pool finds proportionally more blocks but bear in mind the whole Infinitecoin network hashrate has also increased a lot in the last day or so.

Instead of sending you lots of small "dust" (ie very tiny) transactions each block, p2pool seems to wait until you've found a share of enough difficulty to start non-dust payouts. Therefore you may not get a payout every time a block is found. Cockeyed and myself had experienced this since a long time ago as we have small hashrates, but now this is now starting to happen to more people because of the larger total pool hashrate (more people now have a smallish relative hashrate compared to the total pool hashrate)

If I can get the new version working, it seems to have a tweakable dust level which we'll all have to decide upon...once I figure out exactly how it works.

Cockeyed, my own mining graph looks as scarey as yours on the daily views for some reason. If you look at the hourly graphs though, it looks much more normal. As long as your accepted pseudo-share rate on your miner on your computer is looking OK, you should be fine.

The payouts wobble - sometimes severely and sometimes down to zero but in the longer term (not just looking at a few blocks) you'll get the right total payout.

I think the only way to explain this is to look at how much you've received. Lets look at the last 24 hours as an example.

Looking at the block explorer (which uses UTC) for the last 24 hours, from 1AM yesterday 1AM today, you've received a total of 1974568.17745222 IFC at your iC6Yr743UWVzt3vtYWBXGxPsZNBmUzjgNB address . 706000 IFC of this was a big lump-sum so we'll deduct that as it wouldn't have come from the pool (it's a good idea to use a unique address for the pool to make checking like this easier). Anyway, that leaves 1268568.17745222 that you have received from the pool on your iC6Yr743UWVzt3vtYWBXGxPsZNBmUzjgNB address over the last 24 hours.

The average (mean) hashing speed of your iC6Yr743UWVzt3vtYWBXGxPsZNBmUzjgNB address over the last 24 hours, as shown on the graph below was 991kh/s.

The average network difficulty of Infinitecoin from 1AM UTC yesterday to 1AM UTC today was 2.925633059 (average of infinitecoin blocks 206911 to 209826 which you can confirm by the block explorer and a spreadsheet).

So, at an average difficulty of 2.925633059 and an average hashrate of 991 kh/s, how much should you have earned?

According to burnside's LTC calculator you would expect to earn 340.7044 LTC per day on average. At Litecoin's rate of 50 LTC per block, that's 6.814088 blocks (ie 340.7044 / 50 ) of difficulty 2.925633059 that you'd expect to find on average. At Infinitecoin's 131072 IFC per block, 6.814088 blocksworth = 893136.142336 IFC that you'd be expected to mine at your average hashrate of 991 kh/s.

Seeing as you've actually received 1268568.17745222 IFC from the pool, you've received 142% of what would be expected.

I am not the only one suffering these losses. All of the addresses show the same hashrate but the reward drops significantly.

Don't let him confuse you with those formulas, sololoop. That has nothing to do with what is going on here.

What is your mining address ?

what confuse.... it is p2pool share diff. on the pool that we should know.The target share diff is 0.581 (38k) < ------ miner get share above this get real shares.The Block diff. is 3.7505 (246k) <---- miner get share above this . we found a block.

Every single share we submit(accept by pool) on dynamic diff. (32, 64, 128, 1k , 2k , 3k) show on cgminer "Connected to treasurequarry.com diff 1.3k" is not a real share....This is the share used to report your hash rate,.

Herewith is P2Pool FAQ about share : from bitcoin wiki : https://en.bitcoin.it/wiki/P2PoolQ: Why am I not getting very many shares?!A: The P2Pool difficulty is hundreds of times higher than on other pools. It can take time to get a share. P2Pool displays an estimate of how long you have to wait in the console output.

Q: Why does my miner say it has found a lot of shares but p2pool say I have only found a few?!A: The real P2Pool difficulty is hundreds of times higher than on normal pools, but p2pool essentially lies to your miner and tells it to work on relatively easy shares so that it submits shares every few seconds instead of every few hours. P2Pool then ignores any submitted shares that don't match the real share difficulty. By doing this, P2Pool can more accurately report your local hash rate and you can see if you are having problems with too many stale shares quickly

This started happening to me a couple days ago (i left a message here but wad left with the same rubbish you are getting). My solution has been to move pools (ifc.epools.com) and that pool (with a much higher castrate) is paying out fine. Good luck.

I don't know how much clearer I can say it. Depending on your hashrate relative to the pool you will not necessarily get paid for every block found by the pool. However in the long term you should get the correct total payout.

This started happening to me a couple days ago (i left a message here but wad left with the same rubbish you are getting). My solution has been to move pools (ifc.epools.com) and that pool (with a much higher castrate) is paying out fine. Good luck.

Thank you Roddy. I will try epools right after I'm done with my scammer accusation thread.

I don't know how much clearer I can say it. Depending on your hashrate relative to the pool you will not necessarily get paid for every block found by the pool. However in the long term you should get the correct total payout.

I'm about to upgrade the pool to the newest version of the p2pool software. There is a new feature on this version - a tweakable DUST_THRESHOLD setting. I'll be setting this to 0.01e8 which I believe is measured in Satoshis (or Infinitoshis), so should be equivalent to 0.01 IFC . This should help reduce the payout variance for relatively lower hashrate miners.

I'm hoping to get the upgrade done without any noticeable downtime or miner disconnects. Apologies if you hear any explosions in the quarry whilst this is happening.

Thanks for upgrading. Can you tell what are the exact +points of the new pool software´s update? I hope we will not have any open fire or something in the quarry...Yesterday I bought another used laptop for my work, it has an "NVIDIA Quadro FX 770M" which should give me some more speed than now (maybe 6-7 kH/s). Surely, not comparable with recent ATIs, but I did not buy it for mining, so what.

Any hints, which miner and which settings I should use with that? So far I use bfgMiner for BitCoins and cpuMiner for IFCs.

By the way: I observe that the TreasureQuarry slowly gets crowded... When I started, there were only 5 miners or so, now there are many more.

MANY OF YOU ARE REPORTING SHARES/ HASHPOWER AND ARE NOT BEING PAID ! PLEASE CHECK YOUR HOURLY, DAILY AND WEEKLY GRAPHS !

ALSO BE ON THE LOOK OUT FOR UNEXPLAINED DROPS IN YOUR IFC REWARD. IF YOUR HASHRATE AND THE POOL'S HASHRATE ARE CONSTANT, THERE SHOULD NOT BE ANY SIGNIFICANT DECLINE.

I HAVE LOST MANY THOUSANDS IFC DURING THE LAST FEW DAYS MINING FOR THIS POOL.

WE DEMAND PAYMENT.

You ignore my previous post that asking your 2nd (600k/hs)'s best share. It could help figure out what is the problem (bugs/scam) on the pool. Then, I started a fresh 350k/hs miner for testing: As you can see 350k/hs miner got an real shares 0.62 / 40.9k (above 0.224 / 14.6k) but still not in payout group. I also checked on blockchain, but no payment. 350k /hs address : i5Yr98JM8G3RXPQcozYx5nTb2enEE9cdK4

The bug here is that in many cases the hashpower is not being rewarded.

Get it through to your head. THE HASHRATES ARE PRESENT AND CONTANT. THE REWARD IS NOT !!

WTF ? lolDo you know what mining do ? you need found a block (every block got a diff.) (found a shares)However, p2pool need miner get a pool diff. share to enter their pay list party. This is P2pool pplns not PPS payout system . (not paying for your hashpower ) Hashpower is useless, it should used to find block.

But yes, the pool seem bugged / scam with real share... we are not in payout party although our miner got a real shares.

More test here : Best shares means miner get at least one share that above pool diff. but still not in payout party.

I don't know how much clearer I can say it. Depending on your hashrate relative to the pool you will not necessarily get paid for every block found by the pool. However in the long term you should get the correct total payout.

This will make your miner report when it finds "pseudo-shares" of a certain difficulty (you'll still need to find real shares for payments to start, which may take anything between a few seconds to a half a day or so, depending on your hashrate). Once you do find a share, payments will start going straight to your wallet as soon as the p2pool finds blocks. Due to the way p2pool's PPLNS (pay per last N shares) works, the payments may seem to start slow but will reach a peak and reasonably steady rate after a couple of days or so.

I know what you concern about is getting less payment and i agree that "Treasurequarry" is strange. We should get share more often.But you ignore everything importance about mining : shares, diff. PPLNS (p2pool) , and complaint less payment isn't helpful. No pools will pay you for hashrate, even PPS require miner get their target diff. to receive payment.

Is there a simple explanation for the average payout dropping so far? It looks to be about 30% of what I was seeing the other... and it appears to be declining.

Thanks.

i am not going to explanation why the average payout dropping. should i ?i am listing out the problem i found.It is curious why Treasure is different from other P2Pool PPLNS system. As every PPLNS have their pool diff. for payment target. But pool diff. for Treasure seem broken.

I fully get your point, and I agree to you that something appears somehow strange with how the payments come off. But we should be fair. Honestly, I don´t feel that anybody is scamming here; maybe it´s kind of bug in the pool´s software or it´s like TreasureSeeker said: In the long run it will be just. As I am not an expert, I can not know more. For myself it looks somehow fine: I don´t get any amount for days, then I get some quite big numbers of coins for a short period. Take a look at iNY....QF1 at full track: 2.93 GH. For that I ceceived until now 115893 IFC which looks about reasonable for me. Like many here I also wonder how the payments are exactly calculated - I have no clue.

Anyways, like in real life we should not say:"This is scam", because it´s not proven. There is no point in stating something we just think of as a fact. Other people may read it and take it for proven.

Is there a simple explanation for the average payout dropping so far? It looks to be about 30% of what I was seeing the other... and it appears to be declining.

Thanks.

The simple explanation is... we have been SCAMMED.

While I do have to admit that your conclusion is a POSSIBILITY, I don't think it is probable. Here's why.

I've been with this, and other PPLNS P2P pools for some time. The gradual ramp up behavior is very common.. It does not surprise me at all.

Now, something does appear to have changed... The results with identical input is different. There was some discussion about pool changes, and, to me at least, it seems something is not right.

I would like to get some explanation from the pool OPs, so I can understand what is going on and to either correct the issue, or reset expectations, or make an informed decision and get out of the pool myself.

That brings up my final point... You. You appear to be paranoid. (It still is called paranoia even when they ARE watching you for real, right . My suggestion would be that you take your own advice and move to a different pool just to be safe. There are only a few options then:

1). You are right, and the move made your results better, safer, more predictable. 2). You are wrong, and you moved without any reason. No real loss there, you just tried something new.

Regarding blocks 196495 and 196471, if you don't believe that they were orphaned, ask jtobey (creator of the abe block explorer software) what is indicated by the block explorer for those blocks.

P2Pool is complex and often confusing but I can assure you that the standard p2pool software has been used on TreaureQuarry throughout. I have virtually no control over what it does. The only things I've added are appropriate settings to get it to work with Infinitecoin. For those who may know about p2pool, these settings are in networks.py and /bitcoin/networks.py . There was also an addition to helper.py that used to be required in the version of the pool software that I was using before last night.

I updated to the latest p2pool software from https://github.com/forrestv/p2pool last night. In fact I did 2 upgrades - on Saturday I had noticed that there was a new official p2pool version available so had downloaded that in readiness to upgrade. I then upgraded to this on Sunday before then noticing that another new version had been released on Sunday. The second upgrade was done an hour later last night. Apparently the version that I had downloaded on Saturday and was running on the server for about an hour on Sunday did have some bugs. Whether this latest version contains any bugs I don't know. I'm not knowledgeable in python and wouldn't know how to check, or certainly not modify the code. I hope there are no bugs although it currently looks like the "Expected time to share" is showing a bit of a low value currently.

Mining here is your choice. There are no guarantees on anything because, as I have stated, I have virtually no control over what the software does.

c1010010 can you give me your IFC address so that I can look at things for you about your reduced payments. If things are not right we may need to rollback to the previous version but I'd like to avoid that if possible so I'd like to see what's happening with you.

sololoop, what timezone is your miner displaying? I want to check the logs for the same time.

I pulled all the rigs off for a while - testing out a pool for shits-n-giggles. If you need them online for any reason, I'm happy to move them back for live tests.

The oddity that I'm seeding is shown below.

My rigs are pretty consistent. I am generally a solid 8-10Mh/s with those 16 cards, but I have been having a rig acting up so there is a definite possibility that the average hashrate over the past week is closer to 7.5Mh/s.

What I saw was that when running full force, you see an average payout at point-a. But, afterwards, point-b shows a drastically different number.

Aha, I see what you mean. The reason for the drop in your expected payout is that although your own hashrate has remained steady at around the 8 mh/s, the total hashrate of the pool has increased.

I've copied a graph of the pool's total hashrate (local rate) covering the periods you've mentioned below, with the same (or thereabouts... as close as I could estimate) point A and point B.

The calculations below are very rough and don't fully take into consideration the nature of p2pool's PPLNS system which is very dynamic, but they'll give an idea of the reason for the drop in your expected payout per block...

Point A on the local rate graph is around a third up between 0 and 50 Mh/s....lets call it 17 mh's. At that point you were hashing along at your 8 mh/s compared to the pool's total 17 mh/s. Assuming an average luck of finding shares, that would mean that your expected payout for a block found would be around 8/17*131072 (ie your hashrate divided by the total pool's hashrate multiplied by the block value). This equals 61680 (close to what is showing on your graph's point A....bear in mind there seems to have been a period before point A that you were hashing at about 5mh/s which may have caused a bit of a hangover effect on point A which is why your actual expected payout figure is showing as more like 50000 at point A).

Point B on the local rate graph is about two-thirds between 50 and 100mh/s. Let's call this 83 mh/s. At that point you were still hashing along at your 8 mh/s but now compared to the pool's total 83 mh/s. Assuming an average luck of finding shares, that would mean that your expected payout for a block found would be around 8/83*131072 (ie your hashrate divided by the total pool's hashrate multiplied by the block value). This equals 12633 (close to what is showing on your graph's point B).

Now that the whole pool is hashing along faster, then assuming the total global Infinitecoin network's difficulty remained the same, the pool would find blocks faster, resulting in you getting smaller payouts at a faster rate and no major change in your total payouts over time......However, the total global Infinitecoin network's difficulty has also increased. The difficulty at 23:57 on 13aug (around the time of point A) was 1.756 (block 197153) whereas the difficulty at 23:48 on 18 august was 4.437 (block 212399)...reducing to a difficulty of 1.956 at 23:49 on 18 august which was still above the 1.756 of 13th August's block 198306. As a result your actual payouts over a period of time would be less.

c1010010 can you give me your IFC address so that I can look at things for you about your reduced payments. If things are not right we may need to rollback to the previous version but I'd like to avoid that if possible so I'd like to see what's happening with you.

sololoop, what timezone is your miner displaying? I want to check the logs for the same time.

my timezone is UTC/GMT +8 hoursActually, the reward for mining (3days) on Treasure is reasonable. My IFC coins payment is fine with capricious network diff. (1.2 raise to 8.2 within hour and drop back to 2.4 on next hour).

But there is one thing i am confused, the pool diff.(displayed on Treasure's stats page) seem not working/broken?For the low hashrate miner, it is doubtful whether his miner is mining correctly.For example : my previous 350k miner get a share above pool diff. , i suppose this address will enter the payout list but no... until the miner got a block then the address in.

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.

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).

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, 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.

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 ).

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.

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.

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).

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.

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.

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.

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.

You won't need to do anything, but if you have any shares immediately before the upgrade you'll lose them when the upgrade is done. Everyone will then begin to earn shares from a fresh start. There will be temporary winners and losers from this immediately after the upgrade...and some people will hardly be affected - your luck in how fast you find a share in the new sharechain immediately after the upgrade will determine whether you're a temporary winner, loser or relatively unaffected.

I'll do html downloads of the graphs pages to my computer before the upgrade. There's a possibility the "live" graphs may be able to be imported into the upgrade, but if not, I'll re-upload the downloaded graphs as archived html pages.

Really glad you like the quarry, Cockeyed. What do you have planned for your computer upgrade?

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.

Well, even trying to run the upgrade completely fresh from the git-cloned download with a brand new empty sharechain failed with lots of errors, so I've gone back to the old faithful version of p2pool that we were using prior to 18th August.

The "Share difficulty" on the Stats page and the "Expected time to share" are now displaying correctly again. The good news with this is that we've been able to keep all of the graphs live.

Really glad you like the quarry, Cockeyed. What do you have planned for your computer upgrade?

Right now I plan to do just an little upgrade by using another laptop with an nvidia quattro fx 770m graphics card in it. I think this should be at least a little bit more hashing rate.

But as I´m not an expert in configuring mining programs, I have no clue how I can tell to the bfgminer that there is an opengl card now. Maybe tomorrow I will do some hours of google research for that. For tonight I have to continue with CPU-miner as I did not get bfgminer running. Maybe I have to enable opengl somewhere in the cards driver, or installing some additional driver or something...

Edit after one Day: I managed to get BFGminer work with my card. I tried to mine, but it did not appear on the stat. My miner line is:

If your main miner crashes sometimes like mine, then its strongly recommended to have some kind of backup miner to save your high payments. If no miner at all serves your account, you will have a big gap. Just my 2cent worth of experiences which I have. Look at my stat (iNYf2CfdzeMcpinuC3jxWAhXD79PXC3QF1) of this hour, then you know what I mean. By the way: It seems a bit vacated here. Everybody on hollidays? Best mining...

You can confirm that the true block "Infinitecoin 246054" is the one that made it into the blockchain. Clicking on that block shows its hash is 31e5ab9ff60936a3a2634fac3d2ef71cbb8bb37199a992e9acdc322de641a76e . If you then look at block 246055 you 'll see the "Previous Block: 31e5ab9ff60936a3a2634fac3d2ef71cbb8bb37199a992e9acdc322de641a76e" shown (ie not our block hash 1bef1a24d3e87b220eec4d89e5d8ccc5b2195c476640b131c86aadd74a8da5b7).

Unfortunately there seem to be lots of orphaning going on in the Infinitecoin network due to the crazy difficulty swings in the Infinitecoin 1.6 update. During the really low difficulty periods, blocks are being found across the network in sometimes a second or less, causing the orphaning.

Good questions, Hippie Tech and powpow. You had me worried there for a while, but after looking into it, these are orphaned blocks.

Generally with found blocks, if you go to the search box on the block explorer at http://exploretheblocks.com:2750/chain/Infinitecoin and type in the block number you'll get just one infinitecoin block displayed on the results. For example if you input block 123456 you 'll get:

However, if you go to the search box on the block explorer at http://exploretheblocks.com:2750/chain/Infinitecoin and type any of the block numbers that you've mentioned, you'll get two results - our orphaned block which doesn't have the block number beside it (but has just a block hash instead) and the the "real block" (booo!) which has the block number beside it, for example using block 196495 the results are

The payout addresses listed in our orphaned blocks are actually some kind of alternative version of your own addresses. For example, Hippie Tech's address iC6Yr743UWVzt3vtYWBXGxPsZNBmUzjgNB has its alternative version of 19d2R2ef47EdTqi43iD1pAddMuuYuAsYqU displayed in the orphaned blocks. This can be confirmed by putting each of those two versions of the address into the block explorer search - you'll see that all of the transactions are identical.

LOL Whatever makes you happy, c1010010. I'm sure the next one won't cost you anything either.

Serious warning to everyone before reading this...please back up your wallet.dat file - if you lose this you'll lose all of your Infinitecoins.

OK...following the discussion in the main Infinitecoin thread at https://bitcointalk.org/index.php?topic=225891.1340 about to fork or not to fork - that is the question. I was initially thinking that going with the new blockchain fork was not a good idea, but everything seems to be pointing to the new fork winning the day. Although the block explorer has confirmed that block 246954 was found today, my home PC has still been showing only 246953 blocks . Shutting down and restarting Infinitecoin has given a message that I've never seen before "Exception11DBException DB::put:Cannot allocate memory infinitecoin in ProcessMessages(). All in all, the old blockchain isn't looking very healthy from what I can see.

I've just tried backing up, then deleting the contents of the .infinitecoin directory on my home PC, to see what blockchain it would naturally sync to. It has ended up downloading and synching to what seems to be the monocolor fork. Blocks seem to be passing by at a reasonable rate on this fork.

As far as I understand, bitcoin conventions say the longest chain wins, which again favours the monocolor fork.

As far as I understand, posters in the main Infinitecoin thread are correct in saying that (apart from mined generation rewards), no transactions should be lost if we switch chains, even transactions between blocks 246948 and 248954 .

There is however a small "double spend" risk whilst 2 forks exist as far as I've read.

updated: I'm currently downloading what seems to now known as the "correct blockchain" to TreasureQuarry. Mining will probably stop or be at 100% rejects whilst the blockchain is being downloaded. We should then be mining the "correct" (monocolor) blockchain. There is no need to adjust your miner.

Sorry about the downtime earlier today everyone. The server company that hosts the cloud server had to do some "firmware upgrades to several routers" due to some kind of issue with the routers.

The graph history seems to have restarted from new when the server started which is a bit sad as the graphs showed the history of the pool itself since it started in June, just a few days after Infinitecoin itself was launched. I've got an old copy of the graph database from around 18th August so may try to restore this in the next few days. If successful it'll mean a gap in the graphs between 18th August and the time I restore it, but I think that gap is better than having no history at all.

The graph database backup from 26th August has now been successfully restored so we can now see the history of TreasureQuarry from its very start on the yearly graphs view (except the gap between the 26th August and now).

There's no need to sign up. Just point your miner at the pool following the instructions in the first post in this thread. Be sure to use your IFC address as your username to ensure your coins are sent to you. It's a good idea to create a new unique IFC address in your wallet for mining at the pool so that you can identify the payments coming in.

If you're still unsure, please tell me what miner you're using and your IFC address and I'll be pleased to help more.

So I'm having a bit of an issue. I've been mining at TreasureQuarry for a considerable amount of time and haven't seen a single payout in my wallet. Can you speculate as to what might be happening? Stats are as follows:

When I take a look at the transactions for my address, I can clearly see that I'm owed a balance for a load of solved blocks, but every transaction states "Not yet redeemed" under the "Redeemed at input" category. What gives?

Finally figured out what the hell is going on. Your client refuses to update to the current number of blocks. It detects an estimated 433570 (at the time of this post) compared to my current 274323 blocks, seemingly starts to update, but then the client "forgets" how many block it finds on the blockchain, and leaves me about 200,000 blocks off! I'm not getting paid my share because my client is stuck in the past! What gives!?

I've tried to force a rescan. I've deleted blk0001.dat and blkindex.dat to give it a chance to rebuild. Nothing doing. Someone needs to fix this client, and in the meantime, I need an updated snapshot. TreasureSeeker, assistance please.

Thanks for the assistance TreasureSeeker, the temporary fix is working. Please keep us updated on any updates, it's still borked and reporting that my current number of blocks is higher than the estimated total blocks. Do you guys have any idea why this might have happened?

Thanks for the assistance TreasureSeeker, the temporary fix is working. Please keep us updated on any updates, it's still borked and reporting that my current number of blocks is higher than the estimated total blocks. Do you guys have any idea why this might have happened?

The number is way off because of rejects and/or orphans. And/or a whole bunch of these ones which were paid to alternate addys..

The debug window for the Infinitecoin wallet app compares current number of blocks to estimated total blocks. The fix you suggested brought "Current number of blocks" to the number of blocks represented on the block chain, but "Estimated total blocks" is still roughly 170,000 blocks off. The funds are now sitting in my wallet, but aren't tied to an address (the value there is n/a, which I find very peculiar). I also noticed that in the block explorer, the "Redeemed at input" value is still listed as "Not yet redeemed" for all of my transactions, which is even stranger still. It's almost as if it's suggesting that the coins I'm seeing in my wallet are ephemeral.

With all that said, I'm now seeing a steady stream of deposits to my wallet, but please elaborate on what's going on. How soon until we see a permanent fix for this?

I decided to test my suspicions, since the block explorer telling me that the balance hasn't been redeemed is concerning. Sure enough, I tried to test send the funds elsewhere, and I'm (not) surprised to find that I can't send my "balance" anywhere.

I understand that AlexBoyle stated that they're working on a fix just yesterday. I understand that there should be a reasonable amount of time one should expect to lapse before a fix is release. However that doesn't make this any less horrifying, and it would probably be best if someone would provide regular updates as they arise.

Just started mining with minred. Everything is going fine in CMD finding a lot of blocks, but after about an hr or so I still have not received anything in my wallet. My wallet will sync and then 5 minutes later say out of sync and sync again. Is this causing this issue?. My .bat file is below

Without the +0.00001164 your miner won't report any pseudo-shares and your graph won't display your hashrate with any accuracy at all.Just an idea but in your particular case it may actually help your graph to display better if you try reducing the +0.00001164 number. Try something quite low like +0.00000250 .

Without the +0.00001164 your miner won't report any pseudo-shares and your graph won't display your hashrate with any accuracy at all.Just an idea but in your particular case it may actually help your graph to display better if you try reducing the +0.00001164 number. Try something quite low like +0.00000250 .

Appreciate the help. I made the change, and I am getting a lot more accepted, but still don't no if they are orphans or not. Is there a way I can tell? How often is the rewards paid out? Appreciate your time, and help.

If the fix is working and addressing the sync issues, I would recommend making it available as a beta and compiling it for others rather than having others try to figure it out on their own. I'm sure that I (as well as a few others) would appreciate an easier process.

Also, is there a reason why your client is only offered as a download from http://infinitecoin.wordpress.com/? I'm wondering why it isn't available and/or being supported on Github.

boodaddy, you'll be getting more "accepted" messages from your miner with the +0.00000250 but bear in mind these are just pseudo-shares, not real shares. It's only once you find a real share that you'll start getting payouts. Then you'll get a payout each time a block is found by the pool until your share "runs out" (see http://infinitecointalk.org/index.php/topic,325.msg1228.html#msg1228)

minerman1234, Infinitecoin itself is not my client The Infinitecoin client was created by fisheater and is being upgraded by other people including AlexBoyle at the moment. The source for Version 1.8, the latest official version, is available on github at https://github.com/infinitecoin/infinitecoin .

[Updated - please ignore the rest of this post - on further testing this is not currently reliably working. Please use the conf file method posted ny TECSHARE for now until the dev team release a permanent fix.I've uploaded a precompiled linux qt executable which has my checkpoints fix . Just unzip, do the stuff I mentioned in the other thread to clear out your old block details, in other words:

Quote

IMPORTANTLY BACK UP YOUR wallet.dat FILE (just in case you accidentally deleteit in the next step). In fact, back it up twice, just to be sure.

Is this mining pool still working? I mined all last night at 680 KH/s with my IFC address as my username, but I never received any IFC. My client keeps iterating over different blocks and then it says it's up to date, but then the block checking starts again at 16920. (It varies slightly, though.) Infinitecoin seems to be unstable as there appears to be a fork in the block chain where the client can't figure out which path to take. Is IFC flawed with it's initial easy mining? I'm new to infinitecoin, so I have no idea what to expect from it. I decided to mine one night and see if I got anything from it and if so how much, but nothing happened. Unless I can find out what's going on, I'll be mining LTC again tonight instead since it seems more stable.

Is this mining pool still working? I mined all last night at 680 KH/s with my IFC address as my username, but I never received any IFC. My client keeps iterating over different blocks and then it says it's up to date, but then the block checking starts again at 16920. (It varies slightly, though.) Infinitecoin seems to be unstable as there appears to be a fork in the block chain where the client can't figure out which path to take. Is IFC flawed with it's initial easy mining? I'm new to infinitecoin, so I have no idea what to expect from it. I decided to mine one night and see if I got anything from it and if so how much, but nothing happened. Unless I can find out what's going on, I'll be mining LTC again tonight instead since it seems more stable.

If your Infinitecoin client on your home computer (or wherever you have the wallet whose address you're using to mine with) is currently on a forked chain, you won't see the IFC that you've mined at TreasureQuarry in your wallet until you sync your client to the correct chain.

If you can tell me the IFC addresses you're using to mine with, I can check the block explorer to see if it's showing IFC waiting for you when you sync.

If your Infinitecoin client on your home computer (or wherever you have the wallet whose address you're using to mine with) is currently on a forked chain, you won't see the IFC that you've mined at TreasureQuarry in your wallet until you sync your client to the correct chain.

If you can tell me the IFC addresses you're using to mine with, I can check the block explorer to see if it's showing IFC waiting for you when you sync.

I've also done some refining of my checkpoint fix (needs more checking before I post it). AlexBoyle and others are also working on the wallet for a permanent fix and other updates.

Stay with Infinitecoin. From what I've been able to find, the problems have come from past issues when difficulty was rocketing up and own due to large coin-hopping pools. A past fix to the difficulty algorithm made things arguably worse at that time for a short while, and forks have occurred relating to that time. The difficulty algorithm is now fixed but we're now needing to ensure that clients follow the right path to the correct blockchain and avoid the past forks. I'm 100% sure that this will be fully fixed shortly.

I've also done some refining of my checkpoint fix (needs more checking before I post it). AlexBoyle and others are also working on the wallet for a permanent fix and other updates.

Stay with Infinitecoin. From what I've been able to find, the problems have come from past issues when difficulty was rocketing up and own due to large coin-hopping pools. A past fix to the difficulty algorithm made things arguably worse at that time for a short while, and forks have occurred relating to that time. The difficulty algorithm is now fixed but we're now needing to ensure that clients follow the right path to the correct blockchain and avoid the past forks. I'm 100% sure that this will be fully fixed shortly.

Oooh! Awesome it's working now. On page 6 of that thread you linked to, there's a "true chain" file to download from Mega. I downloaded that and replaced the old data while keeping my wallet.dat and everything went well. I have my IFC now. Hopefully others find this thread for the Infinitecoin fix for it not syncing. Thanks again! =)

Thanks TreasureSeeker. Last night I ran this fix from http://infinitecointalk.org/index.php/topic,315.90.html...user Makabress....https://mega.co.nz/#!wERQESKT!VjDLhD51Tscp0YGUuLLGHXCu29dtxDuaabk0F7csQgIWallet synced and showed your 12 ifc depsoit (thank you!) and the deposit from my mining a few days ago.I ran the getblockhash - ddd2f46f72092cb1e06973c068ce2b304936df9ed32ff246804c5dec9b0a424e.I started mining with minerd from cmd last night and seem to have had success but I'm unable to connect to exploretheblocks. Nothing new is showing up in my wallet.It seems I'm synced to the right block now.

d7o1n4 ,are you using the +number after your Infinitecoin address when mining? It's recommended to do this to tell your miner to report psuedoshares, which helps things display well your graphs page. I'm asking as your mining graph doesn't appear to be showing very well on the graphs page...as I speak there's just a peak at around just 85H/s just before 6PM UTC last night. Going by this if you're mining at 80H/s you will have long delays between finding shares and therefore getting a run of payouts.

The block explorer at Exploretheblocks is having intermittent problems with abe block explorer freezing up. This has no connection to the sync issues. I'll be working on trying to get a more stable explorer working this weekend.

d7o1n4 ,are you using the +number after your Infinitecoin address when mining? It's recommended to do this to tell your miner to report psuedoshares, which helps things display well your graphs page. I'm asking as your mining graph doesn't appear to be showing very well on the graphs page...as I speak there's just a peak at around just 85H/s just before 6PM UTC last night. Going by this if you're mining at 80H/s you will have long delays between finding shares and therefore getting a run of payouts.

The block explorer at Exploretheblocks is having intermittent problems with abe block explorer freezing up. This has no connection to the sync issues. I'll be working on trying to get a more stable explorer working this weekend.

I've been using +0.00000116...I mined all night from cmd....then switched back to mining from the wallet today....the IFC I earned a few days ago had the +0.00000116 attached as did todays mining...my system froze after about 18000 accepted...exploretheblocks doesnt show anything new...

You can't go by the "accepted" figures on your miner. These are pseudo shares (if you're using a +number after your ICF address as recommended), not real shares. You only get credited when you find a real share.

From the bitcoin p2pool wiki

Quote

Q: Why does my miner say it has found a lot of shares but p2pool say I have only found a few?!A: The real P2Pool difficulty is hundreds of times higher than on normal pools, but p2pool essentially lies to your miner and tells it to work on relatively easy shares so that it submits shares every few seconds instead of every few hours. P2Pool then ignores any submitted shares that don't match the real share difficulty. By doing this, P2Pool can more accurately report your local hash rate and you can see if you are having problems with too many stale shares quickly

d7o1n4, how fast is your miner reporting it's mining at and what percentage efficiency is it showing? The graphs seem to indicate your mining around 1kh/s to 3 kh/s. At a rate of 2kh/s and with a share difficulty at the pool of 0.255 as I write this, it will take around 6.34 days between you finding each share and therefore getting each run of payments for a share.