[ANN][NKA] INCAKOIN l Perú l Launched Aug 2013 | update v.1.5.2.0 released

[TeslaFreeEnergy]

Guys, why NKA not on C-CEX?

NKA was listed on c-cex for well over a year but we got delisted this year due to low trading volume over a 30 day period
which was a shame as i had almost finished setting up the new slots casino i was working on that required c-cex merchant services to handle the deposits

that's sad...

hope we can get back soon.

Is c-cex the only one with merchant sevices?

[Yannic]

Heya

For those who get stake, after how many days you got stake of your coins ?

I have 3 addy aged 43 days, 43 days and 40 days , my wallet is open 24h/24h encrypted but unlocked

Thanks

http://www.zupimages.net/viewer.php?id=16/25/3v8w.png

[Blockhunter]

I will check my wallet and the community wallet.

[kelsey]

mine doesn't seem to want to stake, coins are mature and network weight many many times that of the network with client saying expected time to next reward 0 secs  

[Yannic]

yes there is a problem with Stake, i wached yesterday and see stake are less than 1 NKA per days for the whole community

[Blockhunter]

Not many coins are being minted anymore.

http://crypto.life/nka/stats.php

[Blockhunter]

Not many coins are being minted anymore.

http://crypto.life/nka/stats.php

Note: Madross transferred .22BTC to me to promote on Facebook. Hopefully soon I will come up with something for that.

[Yannic]

Thanks madross for your quick reply and the quick update to solve the problem

[Fuzzbawls]

There was an issue in the reward calculation, it was divided by the COIN value (1000000) twice, once inside the function and once outside the function, leading to very small values. Here is a fixed version

lock your wallets untill the below date if your coins haven't staked yet sorry for any trouble this has caused people

github has been updated exchanges and other services will be contacted
windows wallet https://mega.nz/#!hkwFGJgT!gDFxXzoaB6I1qGvky4tufQFkZAlhhYRAgLd5XGAOmPw
all other wallets will be compiled shortly


Reward correctly changes to 9% every 35 days after July 9 00:00:00 GMT

Just wondering...

did you remove miniupnpc 1.9 compatibility, reintroduce the antiquated and generally insecure irc based peer fetching, remove the more up-to-date pnSeed nodes, revert to a non-standard difficulty RPC return, and revert the signature verification patches on purpose?

[madross]

There was an issue in the reward calculation, it was divided by the COIN value (1000000) twice, once inside the function and once outside the function, leading to very small values. Here is a fixed version

lock your wallets untill the below date if your coins haven't staked yet sorry for any trouble this has caused people

github has been updated exchanges and other services will be contacted
windows wallet https://mega.nz/#!hkwFGJgT!gDFxXzoaB6I1qGvky4tufQFkZAlhhYRAgLd5XGAOmPw
all other wallets will be compiled shortly


Reward correctly changes to 9% every 35 days after July 9 00:00:00 GMT

Just wondering...

did you remove miniupnpc 1.9 compatibility, reintroduce the antiquated and generally insecure irc based peer fetching, remove the more up-to-date pnSeed nodes, revert to a non-standard difficulty RPC return, and revert the signature verification patches on purpose?

no that was an accident on my end i did assume that the coder pulled from the latest github but it seems he didn't

[Fuzzbawls]

There was an issue in the reward calculation, it was divided by the COIN value (1000000) twice, once inside the function and once outside the function, leading to very small values. Here is a fixed version

lock your wallets untill the below date if your coins haven't staked yet sorry for any trouble this has caused people

github has been updated exchanges and other services will be contacted
windows wallet https://mega.nz/#!hkwFGJgT!gDFxXzoaB6I1qGvky4tufQFkZAlhhYRAgLd5XGAOmPw
all other wallets will be compiled shortly


Reward correctly changes to 9% every 35 days after July 9 00:00:00 GMT

Just wondering...

did you remove miniupnpc 1.9 compatibility, reintroduce the antiquated and generally insecure irc based peer fetching, remove the more up-to-date pnSeed nodes, revert to a non-standard difficulty RPC return, and revert the signature verification patches on purpose?

no that was an accident on my end i did assume that the coder pulled from the latest github but it seems he didn't

thought so...wise to never give work to coders that only offer files in a zip/tarball for FOSS projects that already have a public git repository. A pull request from a forked repo would have shown this and no assumptions would needed to be made.

[madross]

There was an issue in the reward calculation, it was divided by the COIN value (1000000) twice, once inside the function and once outside the function, leading to very small values. Here is a fixed version

lock your wallets untill the below date if your coins haven't staked yet sorry for any trouble this has caused people

github has been updated exchanges and other services will be contacted
windows wallet https://mega.nz/#!hkwFGJgT!gDFxXzoaB6I1qGvky4tufQFkZAlhhYRAgLd5XGAOmPw
all other wallets will be compiled shortly


Reward correctly changes to 9% every 35 days after July 9 00:00:00 GMT

Just wondering...

did you remove miniupnpc 1.9 compatibility, reintroduce the antiquated and generally insecure irc based peer fetching, remove the more up-to-date pnSeed nodes, revert to a non-standard difficulty RPC return, and revert the signature verification patches on purpose?

no that was an accident on my end i did assume that the coder pulled from the latest github but it seems he didn't

thought so...wise to never give work to coders that only offer files in a zip/tarball for FOSS projects that already have a public git repository. A pull request from a forked repo would have shown this and no assumptions would needed to be made.

 

wise advice i will use this in the future he was the original coder who applied the pos changes first and once i realized of the rewards calculation issue i promtly contacted him since it was his work that created the issue

[Yannic]

github has been updated exchanges and other services will be contacted
windows wallet https://mega.nz/#!hkwFGJgT!gDFxXzoaB6I1qGvky4tufQFkZAlhhYRAgLd5XGAOmPw
all other wallets will be compiled shortly


Reward correctly changes to 9% every 35 days after July 9 00:00:00 GMT

Just wondering...

did you remove miniupnpc 1.9 compatibility, reintroduce the antiquated and generally insecure irc based peer fetching, remove the more up-to-date pnSeed nodes, revert to a non-standard difficulty RPC return, and revert the signature verification patches on purpose?

This wallet linked is correct ?

[Fuzzbawls]

github has been updated exchanges and other services will be contacted
windows wallet https://mega.nz/#!hkwFGJgT!gDFxXzoaB6I1qGvky4tufQFkZAlhhYRAgLd5XGAOmPw
all other wallets will be compiled shortly


Reward correctly changes to 9% every 35 days after July 9 00:00:00 GMT

Just wondering...

did you remove miniupnpc 1.9 compatibility, reintroduce the antiquated and generally insecure irc based peer fetching, remove the more up-to-date pnSeed nodes, revert to a non-standard difficulty RPC return, and revert the signature verification patches on purpose?

This wallet linked is correct ?

if the linked windows wallet is built from the current git commit (dff4131) then it does have the correct subsity, but it also contains a number of regressions. Also worth mentioning that the linked wallet will force disconnect any client with a protocol version below it, including the current v1.3.0.0 clients (which are still valid until July 9th)

[Yannic]

github has been updated exchanges and other services will be contacted
windows wallet https://mega.nz/#!hkwFGJgT!gDFxXzoaB6I1qGvky4tufQFkZAlhhYRAgLd5XGAOmPw
all other wallets will be compiled shortly


Reward correctly changes to 9% every 35 days after July 9 00:00:00 GMT

Just wondering...

did you remove miniupnpc 1.9 compatibility, reintroduce the antiquated and generally insecure irc based peer fetching, remove the more up-to-date pnSeed nodes, revert to a non-standard difficulty RPC return, and revert the signature verification patches on purpose?

This wallet linked is correct ?

if the linked windows wallet is built from the current git commit (dff4131) then it does have the correct subsity, but it also contains a number of regressions. Also worth mentioning that the linked wallet will force disconnect any client with a protocol version below it, including the current v1.3.0.0 clients (which are still valid until July 9th)

Thanks Fuzzbawls, i will wait a little before to update then.

[kelsey]

There was an issue in the reward calculation, it was divided by the COIN value (1000000) twice, once inside the function and once outside the function, leading to very small values. Here is a fixed version

lock your wallets untill the below date if your coins haven't staked yet sorry for any trouble this has caused people

github has been updated exchanges and other services will be contacted
windows wallet https://mega.nz/#!hkwFGJgT!gDFxXzoaB6I1qGvky4tufQFkZAlhhYRAgLd5XGAOmPw
all other wallets will be compiled shortly


Reward correctly changes to 9% every 35 days after July 9 00:00:00 GMT

seems now the new client wants to dl the whole chain again  previous bootstrap doesn't seem to work with it either. any new bootstrap?

[madross]

There was an issue in the reward calculation, it was divided by the COIN value (1000000) twice, once inside the function and once outside the function, leading to very small values. Here is a fixed version

lock your wallets untill the below date if your coins haven't staked yet sorry for any trouble this has caused people

github https://github.com/madross/incakoin-new

please recompile using the new above source

windows wallet https://mega.nz/#!45w0yZSY!uWhrudngcZKyG20Y-W9TXisEH5RMxSeeU2uA8HUtbQs
bootstrap https://mega.nz/#!I4YEmZZa!-uFaLS4RUMe8EZphl06MiErqipWfd73XL4nwUgroF_k
Android update pushed to playstore should be available in the next 24-48 hours
all other wallets will be available once completed



Reward correctly changes to 9% every 35 days after July 9 00:00:00 GMT

[Yannic]

There was an issue in the reward calculation, it was divided by the COIN value (1000000) twice, once inside the function and once outside the function, leading to very small values. Here is a fixed version

lock your wallets untill the below date if your coins haven't staked yet sorry for any trouble this has caused people

github https://github.com/madross/incakoin-new

please recompile using the new above source

windows wallet https://mega.nz/#!45w0yZSY!uWhrudngcZKyG20Y-W9TXisEH5RMxSeeU2uA8HUtbQs
bootstrap https://mega.nz/#!I4YEmZZa!-uFaLS4RUMe8EZphl06MiErqipWfd73XL4nwUgroF_k
all other wallets will be available once completed



Reward correctly changes to 9% every 35 days after July 9 00:00:00 GMT

windows wallet https://mega.nz/#!45w0yZSY!uWhrudngcZKyG20Y-W9TXisEH5RMxSeeU2uA8HUtbQs

bootstrap https://mega.nz/#!I4YEmZZa!-uFaLS4RUMe8EZphl06MiErqipWfd73XL4nwUgroF_k

Thanks Madross
Everyone update your wallet as soon as possible today or this week before the July 9

[ice00]

Did other have compilation problem on linux?

Code:

make -f makefile.unix USE_UPNP=-
/bin/sh ../share/genbuild.sh obj/build.h
g++ -c -O2  -pthread -Wall -Wextra -Wformat -Wformat-security -Wno-unused-parameter -g -DBOOST_SPIRIT_THREADSAFE -I/opt/multi-pool/src/IncaKoin/src -I/opt/multi-pool/src/IncaKoin/src/obj -DUSE_IPV6=1 -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2  -MMD -MF obj/rpcwallet.d -o obj/rpcwallet.o rpcwallet.cpp
In file included from IncaKoinrpc.h:16:0,
                 from rpcwallet.cpp:8:
json/json_spirit_writer_template.h: In function ‘String_type json_spirit::non_printable_to_string(unsigned int)’:
json/json_spirit_writer_template.h:31:50: warning: typedef ‘Char_type’ locally defined but not used [-Wunused-local-typedefs]
         typedef typename String_type::value_type Char_type;
                                                  ^
rpcwallet.cpp: In function ‘json_spirit::Value checkwallet(const Array&, bool)’:
rpcwallet.cpp:1698:50: warning: the address of ‘nOrphansFound’ will never be NULL [-Waddress]
     if (nMismatchSpent == 0) && nOrphansFound == 0);
                                                  ^
rpcwallet.cpp:1698:51: error: expected ‘;’ before ‘)’ token
     if (nMismatchSpent == 0) && nOrphansFound == 0);
                                                   ^
rpcwallet.cpp:1698:52: warning: statement has no effect [-Wunused-value]
     if (nMismatchSpent == 0) && nOrphansFound == 0);
                                                    ^
rpcwallet.cpp:1700:5: error: expected ‘;’ before ‘else’
     else
     ^
rpcwallet.cpp:1698:33: error: label ‘nOrphansFound’ used but not defined
     if (nMismatchSpent == 0) && nOrphansFound == 0);
                                 ^
rpcwallet.cpp: In function ‘json_spirit::Value repairwallet(const Array&, bool)’:
rpcwallet.cpp:1720:68: error: ‘nOrphansFound’ was not declared in this scope
     pwalletMain->FixSpentCoins(nMismatchSpent, nBalanceInQuestion, nOrphansFound);
                                                                    ^
rpcwallet.cpp:1722:50: warning: the address of ‘nOrphansFound’ will never be NULL [-Waddress]
     if (nMismatchSpent == 0) && nOrphansFound == 0)
                                                  ^
rpcwallet.cpp:1722:51: error: expected ‘;’ before ‘)’ token
     if (nMismatchSpent == 0) && nOrphansFound == 0)
                                                   ^
rpcwallet.cpp:1723:57: warning: statement has no effect [-Wunused-value]
      result.push_back(Pair("wallet check passed", true));
                                                         ^
rpcwallet.cpp:1722:33: error: label ‘nOrphansFound’ used but not defined
     if (nMismatchSpent == 0) && nOrphansFound == 0)
                                 ^
makefile.unix:148: set di istruzioni per l'obiettivo "obj/rpcwallet.o" non riuscito
make: *** [obj/rpcwallet.o] Errore 1

[ice00]

I installed the new Windows Wallet onto Pc, but it not generate POS.

I have:

your weight is 20277856928
network weight is 2184
expected time is 0 seconds

normally it catches POS