[ANN][NKA] INCAKOIN l Perú l Launched Aug 2013

*I’m still banned from posting publicly in the IncaKoin discord channel, for expressing the concerns and issues with the project.

The first of which is the error we get when we try to stake our keys, which have inputs of fifty million coins per transfer(s) or more. I have confirmed with the other users who I am in contact with, that there are billions of coins which cannot be staked, and they as well as myself are steaming mad, and worse by the day. None of us are willing to move the coins and lose our now 14 months of staking weight; if we move them to allow them to stake; by sending smaller input transfers of say ten million. That’s a massive percentage of the network lost from us, to those of you who don’t have the same problem.
I’m guessing is any of you devs had the same problem, it would have been fixed a long time ago. Very convenient for you, not having fallen into such a trap.

If you try to change the code, so as we all lose that staking weight, while allowing yourselves to have staked your coins the whole time. IT’S CRIMINAL FRAUD, and you should be prosecuted directly by the mafia-like human-farming statists as such. Hang em high like dead ducks.

This is the error we get when we try to stake those keys;

ERROR: CTransaction::CheckTransaction() : txout.nValue too high
ERROR: CheckBlock() : CheckTransaction failed
ERROR: ProcessBlock() : CheckBlock FAILED
ERROR: IncaKoinMiner : ProcessBlock, block not accepted

Do a google search of this above error, shakezula’s name comes up (Adam McKinney?); IncaKoin, and the “shitcoin”. This is an old bug from before 2014.

I was told many months ago by Bobby (wolfie), that it was easily fixable and would be done right away. Regtable, has also repeatedly told me it was easy to fix. When I ask them privately why it has not been fixed yet. I get no response.

If the bug, only needs one value to be changed, and then recompiled, WHY HAS IT NOT BEEN FIXED YET?
You’ve ruined this project, you’ve derailed all the work I’ve personally put into this coin. You’ve destroyed our investments! The network is in ruin, and the investors/users are pissed.

Is this a matter of mere negligence? Or is it actually a malicious attack, a self destructive action, suicidal impulses being acted out by immature pathological liar con men, is what myself and the other investors want to know.
What the fuck is going on with you people? Have you lost your minds?

The Cryptopia exchange still has the wallet on maintenance, and rightfully so. Until the issues have been sorted out. This bug (which was added intentionally apparently, to speed up the blocks I was told by wolfie and Regtable). What the hell does that even mean?? It’s like dealing with some liar scam artists!

WHY HAS IT NOT BEEN FIXED YET? If it’s only one line of code that needs to be changed and recompiled into a client.

You’ve shattered any trust we had in you.

The other exchanges also have their wallets in maintenance, its been a long time now. They’re all stuck on abandoned illegitimate forks of the chain, a whole other issue to deal with. You thought you could fix the problem by adding a centralized checkpoint server, that didn’t work. Now the coin is truly centralized, into the hands of some unknown irresponsible, derelict controllers who don’t respond and silence those who bring these problems we face into the public.

The presstab block explorer has been down for ages as well. Unpaid and abandoned.

Another block explorer and mining pool I have found.
https://prohashing.com/explorer/Incakoin/

They show a block height of 2,723,883, now 140,000 blocks behind the legitimate chain. Obviously stuck on a bad fork as well. I messaged them, but got no response.

It’s time you put on your big boy pants and get the first of the issues solved, so that we can all help to get things back on track. The first of which is the “txout.nValue too high”.

We appreciate the work Regtable has done recompiling the client with updated libraries, although none of us over here are using it, after we’ve found a virus embedded into one of the earlier clients, which the type is now identifiably by virus scanners, we’re waiting to hear whats happened by the commentary of other users before we try the newish version.

I suggest you get the first issue fixed immediately, then perhaps we can find a way to take the UTXO data and add it into a fork of a protocol (a coin, not an ico token) which works properly, so we can port over the entire chain into a more updated client system, without all the bugs that have been found within the Bitcoin source code over the years.

Or what’s next???