All ports are auto-forwarded, my router is UPnP ready and active... There are no port restrictions.

I'll force port forwarding, but they are already forwarding...

It is them rejecting the connection, not me.

Normally I get 8 instant connections... Now I am getting 2, and that took over an hour to sustain.

I don't need port forwarding, it does that automatically. Otherwise I wouldn't have any connections, or show on any lists. I show on the big list often, normally... (Just not after this happens.)

Port-monitor shows many open connections, but they are just waiting to die... nothing connected on them anymore.
http://technet.microsoft.com/en-us/sysinternals/bb896644.aspx
also TCPview shows about 5, and two loopbacks for bottlecaps, and 4 others, including 8 for my miners.
http://technet.microsoft.com/en-us/sysinternals/bb897437

No firewalls, other than standard ISP protection from pings and probes and ack-attacks.

Never had an issue up until last week, prior to 1.4. Actually, about 5 hours before 1.4 was released, this started happening. But the issue on 1.3 was that I was not getting any POS at all, though I had over 5000 coins ready for POS. Once 1.4 was released, I got like 40 POS per day... Then all hell broke loose.

Just had 4 again, but it dropped back down to 3, then 2...

P.S. If it is any importance, this is win-7 home-premium up to date 64-bit version

My config is setup for 30, but I never get more than 8... that is most wallets. Only a few wallets seem to ever get over 8. Normally on those I have about 20-25. I figured that was a windows wallet limitation for this wallet too. Might not be... someone said they had 12 on windows wallet, I think...

my ip 107.217.208.215

only one of my connections is in that list from the block-crawler

Here, the most I ever get is 8. Fast... unless this happens... then it takes about 10-20 min to get 1, which I assume is some new person, as they are not on the big list, and thus, not banning me or not banned themselves, which turns them into a relay for my work... then I get 1 new one again... a few minutes later.

Stuck at 2 still... if one is accused of misbehaving, I am screwed again... I have to wait for someone new to join, to piggy-back on them as a relay. Because all three of us will become isolated again, or all become isolated ourselves, as three separate chains or waiting for someone new to piggy-back on.

I am still stuck on 2 connections... I see 3 and 4 for a split second... then they instantly disappear. (All version 1.4.2/1.4.1 and all in that long list. They just refuse the connection, once connected.)

I still don't get how that issue causes all 8 of my connections to drop, and causes all 25 of the other connections to refuse my connection. Leaving me connecting to the first new people that are trying to connect, but they can't connect to them either, only me... mining on my chain, but eventually leaving to the taller chain, leaving me isolated again.

Unless the calculation for Computeminwork() is still off by a fraction of a decimal, or just too high for what is actually being submitted.

I had to manually delete the chain again, restore a backup, reconnect manually, unlock my wallet, restart my miners... then I was able to mine again. From 1AM to 3:30AM my miners were dead in the water...

I HOPE that is not "what it was supposed to do"... That is the problem we have all had. With the addition of no reconnections, which I still have. I just happened to luck out and catch 2 new connections that just joined the chain. The rest in the list are auto-killing my connection attempts to them, once they get connected. (As if I was personally responsible for the misbehaving. Guilt by association, though we were all connected to that peer. How do 20 connections stay, and five get perma-ban and isolated to mining alone, every time?)

When it says "not enough proof of stake"... is it complaining because someone created a POS block, and there was already enough "claimed"... Thus, not enough POS to accept that block? It shouldn't disconnect us for that, ever... just reject it, and update the height, as obviously, that one that submitted the block did not have the latest POS block, which was the "limit" for that minute/hour.

Unless it is complaining that someone created a POS but they didn't have enough POW blocks to convert to POS, thus, not enough POS... (That is the most uninformative warning I have ever seen. lol. Might as well say, "something didn't work right" as the warning... like javascript does! xD)

If it is bitching about someone creating a POS for a block which they don't have enough POW available... then you need to check one of two things in our wallets... or both...
1: Is there a POW block ready for POS (then mine POS, if it is accepting POS on the system)
2: Is there STILL a POW block ready for POS (then submit POS, if it has not been spent, or consumed by a prior POS solution)

Optionally 3: Reserve 10 POW for POS, prior to mining/solving the actual POS block, as "unavailable for POS"... Since I notice that POS happens first, THEN it removes the coins after submitting... at which point the coins could have been spent, or consumed by a POS that just got accepted a few seconds ago.

and on the other side...

Don't kill people because they submitted what they thought MIGHT be accepted, being unaware that the unrelayed POS block the server didn't distribute, was the last POS block that was just about to be sent to that user for building-on. Simply ignore it, since it is a POS block, that has near-zero diff, and you should be expecting a ton of invalid ones to arrive, as we all solve them real fast. (Unless you raise the diff, then they come more spaced-apart, and traverse the network to us, faster. Stopping us from submitting the POS we were just about to submit, if we thought the limit wasn't reached yet.)

If the first thing is true... about us being banned because the wallet is creating POS for POW's that we don't have available... then you might want to tell us to stop mining when there is (limit - 1), as having one less will not matter on the next cycle it will ask for one more. However, that WILL reduce the last flood of submissions, letting the ones still in transit, or ones that have not gotten the (limit value) yet... get accepted without forking and rejecting them for something the wallet did.

Also...

Instead of just "disconnecting us", under suspicion of whatever... (Which is what is creating the forks, the program isolates us as a group, through the one relaying to the one severing the connection.)

Give the program some kind of warning to let it know WHY it is being disconnected, before disconnecting. If only so you can locate the issue better, by talking to the one being disconnected. Since you have no idea who is disconnecting who, or why, unless you witness it yourself. It is easy to find those of us getting disconnected. We are the ones frequenting the forums. But it doesn't tell us why we are being rejected, it just rejects us.

The beast be forked again... dead fork, but forked... all connections being refused again. (Refusing me) Version 1.4.2

Won't even let me connect to get the chain... any chain... (From 79997 up, not from 0.)

Got one to accept my connection, back on track... but I was stuck on that dead fork that couldn't be mined. "Not enough work"... and the other connections kept refusing me, I guess, after they left and started a new branch. Left me mining with 2 connections, then one... which wasn't enough to mine...

Got only one connection here, but it is letting me mine on it, at the correct height. Hope it relays my blocks!

Also note, it was at almost 01:00 am again...8/19/2013 00:54... same time as last time... (GMT -5)

I'm never sleeping again... ever!

That I can do... There are hundreds of them all over my house... lol.

Or did you want this... http://fallout.wikia.com/wiki/Gecko_(creature)

Challenge accepted... Pack of baby-geckos, huddled around a bottlecap! (I will put my own artistic twist on them, to make them unique.)

Nice... love it...

I can attest that 1.4.1 is also running strong, attached to the 1.4.2 clients. Switching back to 1.4.2 soon, just because I would rather not be the source of future forks, running 1.4.1. (Just wanted to see if 1.4.1 would continue to operate without error, and it has for over 10 hours now.)

Off topic...

I am bored and about to begin making a clay-sculpture, to be used for molding. Anyone have any suggestions of something cool or any requests? (I prefer sci-fi and fantasy things, but that is not a limitation.)

Speak up, since you have nothing-else to do, while your miners are running without error.

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.

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

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.

Thank-you by the way...

Noticed the only connections I get are still only showing as version:70000.... are they just not updated yet, or did you not change that version number internally?

No...

lol. I had to say it... it is in my nature... hope the linux versions and server versions get posted soon... those are the ones kicking us offline and rejecting us.

But now I know who Mullick is!

Now all we need is some of the other things I mentioned, to be taken care of...
- Higher diff for POS blocks, to reduce block-flooding and collisions
- Split block-chain having an archive from 0 to last-hard-coded, and one for last-hard-coded to present-height. For the purpose of ease of "rebuilding from last-hard-coded forward", as opposed to 0 to present. (Or manually by just deleting the latter half of the DB, keeping the archive portion. Better yet, a command to dumptopdatabase, or rebuildfromarchive.)
- Ability for the program to automatically remove blocks that don't match the "tallest found chain", so the new chain can be rebuilt from that fork onward... (As opposed to staying on the small chain or just crapping out, since it can't build on the last block, which does not match, obviously, to the taller forked chain hash.)
- 1 mandatory roaming connection to traverse rooms looking for anyone reporting a taller chain, to jump on that chain and rebuild the fork, at the point of the fork.
- Ability to start wallet unlocked, via startup shortcut or bat, refusing mining until the wallet is unlocked. (Eg, not relaying block data if it is locked, so we don't start mining with invalid credentials that produce invalid blocks.)

Oh, and free cookies for every 10'th block mined...

Oh, and the POS thing fixed... POS still only gives 0.01 no matter how many coins are staked, or ready to be staked. 20, 40, 60, 80, 100... all give 0.01 reward... (only seeing 10+10 = 0.01) and instantly moving coins out of stake, and the reward, as soon as they are confirmed... after 25 blocks. (I don't think that is the way it was intended to function, as per the description of how POS works.)

One problem... there is no 1.4.2 yet... The title of the post says 1.4.2 but the program is only 1.4.1...

Who compiled that version? Where is the source? Why is it not listed on page 1?

Just asking before I download some strangers personal version of a program that might be a backdoor broadcasting my wallet or doing something that can't be monitored.

V1.4.1 listed on post 1 of this thread is still functioning at the moment... and indicates no-where, other than the title, there is a v1.4.2 made by the creator/manager "John Eden".

Excuse my paranoia... lol

The one good thing that comes from an exchange stopping all exchanges of a coin... is that we get a bunch of cheap to purchase coins after they begin accepting trades again. lol...

Cheaper to buy, than to mine.

Why would you stop someone from buying something you already have in your possession? Just because coins that are not in your possession yet, can't be confirmed? That makes no sense.

That would be like walmart closing it's doors in the TV department, because 100 new TV's didn't arrive yet so they stop selling all those TV's. Even though they have 100 of that same TV sitting on the shelves, ready to sell or put on lay-away.

An internal trade is one that someone has already sent and been confirmed as being "on the right chain".

Unless the fork is longer than the number of confirms... but by that point, it is already too late anyways, those have already been traded and would be lost at that point. If you know there is a fork, and you know where it is... roughly... you know which coins to "not trust" that came-in beyond block-x or within x-blocks...

But if someone deposited 20000 blocks at 5000-height, and the fork is 7000+... then you can safely allow those coins to move to any internal account on an exchange. Since those coins are not physically moved in a wallet, just tracked by the database as having a new owner.

When you trade CAP for BTC on an exchange, you don't get it instantly deposited into a personal wallet. It stays in the exchanges wallet, until you decide to withdraw it to your external wallet. Then it just checks that you are the owner, and if you are, they get pushed to a block for withdraw.

Internally, issues with a wallet only impede deposits, because someone may be depositing on the wrong chain, which is not detected by the other chain. (So it can't be collected, or would be erased if it came in after the fork, from another block, or didn't come in at all.)

But internally, it doesn't matter. On an exchange. (Not to a trader, who doesn't actually withdraw, but simply exchanges CAP->BTC then uses that BTC to buy WDC... from that same exchange. Not being able to remove it to your personal wallet is simply a hinderance. That can be instantly warned, prior to exchange, if the system takes that into consideration. Not everyone "cashes-out", many just keep trading from coin to coin.)

The short solution is to temporarily raise the "confirm acceptance" for the exchange to something crazy like 10,000 confirms for deposits, and stop all withdraws. Then, inform anyone making a trade, that they will not be able to withdraw that coin, only trade for another coin, which can be withdrawn. While any pending deposits will be notified on a similar level, alerting them that pending deposits will not be available for trade, until the fork has found a resolution. Asking them not to deposit, until the fork is over, and alerting them that pending deposits may not come through, and may have to be resent, if they were sent from the wrong fork. (If sent from the wrong fork, the coins would return to the wallet of the sender, once the bad fork disappears.)

You could still allow internal trades... since that doesn't use the wallet until deposit or withdraw...

Eg, Just inform them that deposits and withdraws are the only limitation for the coins. But they can still trade to any coin that you have listed, which is working, since you KNOW the coins you have already received are in your possession.

Just saying, that that might be a future upgrade to your system, if you implemented it, to reduce or alleviate some issues with coins that all eventually have a fork. Stopping all trades, internal and external is kind-of silly.

It is only the "newly minted coins", or "transfer-blocks" that are the issue with the exchanges. You could trade any coins already confirmed and in your possession, without any issues. (Just blocking withdrawals and deposits with a notice to those depositing and withdrawing. With a little baby-sitting, you know how to get on the right chain, and get accidental deposits which you can't control.)

Where are you getting 1.4.2? The links on the first post all still link to 1.4.1? I have refreshed a million times, and the only links and descriptions are for 1.4.1 still. I think he just screwed-up the title...

P.S. It's almost 01:00 here, that is when mass-genocide happens for connections... watching like a hawk again. lol. OOps... forgot it is military time 13:00 not 01:00...

I wasn't complaining, just making a joke about the lack of the actual 1.4.2 being listed before the title was changed. I am about 99% sure that the forum ate his post submission, and he is retyping it all up, as we post now. xD That, or he just assumed it was actually posted... and left to go back to other things.

Even with this issue, this is still the one-of-the-best coins to mine. (Opinion)

Crossing fingers... UPDATE, UPDATE, UPDATE!

Pfft... front page still has 1.4.1... Don't update yet... That was premature... lol.

How to update 101
1: Update and compile and test all versions
2: Upload all compiled versions and source
3: Update information and links on post
4: Check that everything is correctly listed and working as links
5: Change title of post to "Update 1.4.2"

You got 1 and 5... now try 2,3 and 4.

P.S. Potential fork detected... The block-crawler just returned 0 connections again, and 0 block-height... Last time it did that, it began killing our connections, and we forked. It was severed, and now we are about to be severed, I assume, again. (Prepare for reconnection when the big-guns get severed from that list, that is where the new tallest branch will be.)

Hmm, right at noon... 12:00... Guess it will happen within the hour, when it sees us all as "misbehaving" by about 01:00 again... Time-glitch or time-hack?

ARG... lol... I was mining the last half hour on my locked wallet... that is sooo annoying... I knew I would forget that one of these times... lol.