Topic: Bottlecaps 2.1 UPDATE REQUIRED - HARDFORK JULY 4 2014 to 200% Annual PoS - page 173. (Read 388610 times)

Hmmmm, I am showing 80165 right now and the block crawler shows the same. Hopefully we don't have an issue.

Edit: typo

Trust me, I've done the same. Glad you got it figured out.

Block crawler is currently at 80137, so the above worries me.

Thanks I have the * and tried specifying as well....Maybe i'm missing something...I'll figure it out.

Your using V1.4.2
Windows?

Edit: Okay i was being dumb...I specified 127.0.0.1 at all the remote rigs and not the network address of the client rig.

I have multiple rigs running with no issues

Edit: I do have rcpallowip=* (or something like that, can't look right now)

Okay is it just me or if when solo mining from more than one rig to a single client using rpcallowip=

Do the remote rigs all not connect....I haven't changed anything and have mined solo many times.

I would try -repairwallet and see where that gets you. Hopefully it will fix it

cap.coinmine.pl is approaching 24 hours on the correct chain. Difficulty is under one so solo mining is a great option as well

Its sad when thats an accomplishment but hopefully its a sign of progress

Are there any pools working properly and on the correct chain now?  I am in the mood to mine me some Bottlecaps 

I have an odd problem with the 1.4.2 wallet.  Most of my coins are no longer in my balance, but I can still see them in my transaction logs, and they all have green "confirmed" checkmarks beside the transactions.  Anyone else have this problem?  I never had this problem until I changed to the 1.4.2 wallet.  The 1.4.1 still had me at the proper amount.  


Edit:  nvm - repairwallet fixed me up

My wallet was generating PoS on the correct chain fine, but I have now put in reservebalance to stop that and using the latest client.

The problem is I still have coins "missing" from my wallet where PoS blocks were generated on the wrong chain and not confirmed. How do I get these back? I have started the client with -rescan but they're still there.

Things are starting to look good.

Never admit that to me... It encourages me to keep talking...

lol.

Seriously though, thanks for all your persistent hard work and COMMUNICATION. That is more than most coins offer. Even under these trying times.

WooHoo 80,000 blocks and still going. Left the house for a few hours and came back and all is well. I think we are healing.

Thanks again Mullick.

When do you think we would be safe to reactivate the POS on our clients?

Yep if your on the right chain with 1.4.1 no reason to update just checkpoints. If you get off the chain it will be much easier to get back with 1.4.2

I have listened to all of your valuable inputs in the thread they are more than helpfull thank you

So is 1.4.1 still OK to connect with, and run if it connects for us?

I really wish the POS blocks were on a separate chain. Every time a POS is found, it forces all our half-finished work to stop, and get a new hash, essentially starting the hunt for a normal POW block, which has to be built off that POS block, which is not circulating through the net fast enough.

If it was a separate chain, built off the same seed, running along side of the POW chain... except POS only having to match the hash of the "seed" and the "last hard-coded POW block"... (In addition to being valid with your signature and valid block that was staked...) Then it wouldn't matter if they were out of order, as long as they were valid, until the point where they had to move back to the POW chain as a normal TX. But that would not interfere with the POW chain that does require successive building, to prevent tampering.

Though, because POS moves too fast, with low diff... it is inevitable that many POS that are honestly earned, will be rejected due to slow distribution through the net. (Might be a little faster if it was a separate chain also, with a variable diff too.)

But that is not a tiny thing that can be changed by adjusting a setting. It would require a lot more programming to make it reality. (Just thinking out loud here, not demanding anything. )

So here is where it stands.

I have done a side by side comparison of Caps and CGB code.

The only difference is the obvious chain start time ect. There are no stake changes that would cause any issues in caps that would be prevented in CGB. The amount of changes are extremely small.

I have implemented the fix Sunny King thought could be causing the issue. Compute minwork not being adjusted for ntargettimespan which has not been done in CGB or any other caps fork

Therfore it must be an issue with a previous client. 1.3 or earlier and 1.3 only contained checkpoint updates.

So I have disconnected all previous client ensured all clients were compiled from the same source ect.

Now it should only be an issue of weeding out the old clients creating the problem. The changes took effect yesterday but they are not disconnected immediately. If you had a peer running an obsolete version and on the right chain it would keep connection until you either restarted or it went off on a bad chain and got banned. If you were connected to an old client or even a new client still connected to an obsolete client when they generate a bad block it will still cause an issue

It will take time but We have been having a good streak since last night. Hopefully 1.4.2 will get everyone synced and stay on the right chain since there are no old clients generating the PoS blocks that were causing the problems left on the network really. The issue is PoS blocks are being generated and clients are giving this error "Contains too little proof of stake" some clients get past this others do not and create a seperate chain

updated on http://cap.coinmine.pl

Gotcha...

While you are here... can you update the 1st post...

Still says version 1.4.1 release notes... and there are two IP's mentioned... one for regular wallet setup and one for solo setup. I believe the solo setup has an old IP that is not responding... It is more near the bottom of the post. (Well, it never responds to me.)

That is my OCD kicking-in... Might want to just remove that part, about solo mining, mention it once above with the other settings, which work for solo or normal wallet operation. (Or just remember to change that, if your trusted nodes changes on a fork again. With all the connections, nodes should not need to be listed anyways. Since they are just a suggestion, and the program connects to anything that it finds in the rooms anyways.)

P.S. I noticed this version is like version 1.3... Generating a lot less POS blocks again. Did you increase the diff, and if so... is the reward or coins going to be compensated, since the diff is higher, and thus, less frequently found by all? Or is this just going to auto-balance and distribute more evenly now, as opposed to one person getting tons of POS and others getting none, due to slower connections (net lag causing stale POS submissions and rejects of POS)?

Eg, the blocks are climbing a lot slower on the chain than before. There were soooo many POS created, like 20x more than normal blocks.

Version 7000 is the protocol version not the wallet version. Its what is used to classify older peers before the protocol switch. There is no need to up protocol version in this release