Any updates on coinexchange.io?   Still in maintenance

-JK

What do I need to do to get the coins back for my masternode address?   It was the masternode that received half the payout on that 110k stake.   Should be at least 1100 coins in that address not counting the 55k from the bogus stake.

-JK

I went ahead and built from source and got this code running on linux (mns and controlling wallet).    Looks good so far, 1 VGS for POS split evenly between staker and mn.    Only thing I'm missing is the coins from one of my masternodes.   It wasn't credited in this blockchain.

-JK

Wow, thats fucked.   I can't believe this has been allowed to continue for so long after tkari's initial report.    Sad, pathetic, etc...  Time to shut down my 5 masternodes and move on.   Too bad.

This miner is back generating 10 VGS and 0 split with masternodes.    VBMuSRNVYSDGNEcHSkoCPCWJL1Hs48gyZt     
This coin is in major need of an emergency fix, of course if the dev is the one doing the stealing???

Fatal flaw?  Time to shutdown my masternodes and dedicate the resources elsewhere?    Vegas, need a status update on the big ripoff soon or its time to cut my losses and move on.

Still going to want stakers out there especially if POW is removed.   Maybe a jackpot split between the staker and masternode would be more attractive and easier to implement??

I think the AMS wallet had a similar problem a while back??   Since @keesdewit works on both wallets, he should have a good idea how to fix it.

Linux build package isn't right.   Looks like its an ARM build instead of x86_64.

Does yobit have an API that can tell you when a wallet is no longer in "maintenance"?   It would be very useful to get an alert on that since it seems like I am always battling that issue.

Already have one running on my android phone,  its called bitcoin checker,  only does price but works very well and its free (donation if you like).

-JK

bummer,  my first decent superblock in over a year and now it gets wiped due to a roll back of the chain.   If this coin was used for something real, I think there would be quite a bit more of an uproar, but since we can't do anything with it including transfer to an exchange, wgaf.    Another triumphant success story for that garbage platform otherwise known as Windows....

Anyway,  are we clear to build and start using 2.4.4 or should I just shut things down for a couple weeks until the dust settles?

-JK

Doesn't want to compile on linux.    src/main.cpp line 1305.   Doesn't like mix between floating point (double) and CBigNum which looks to be integer based.  Could static_cast to a long long but not sure if you will lose precision doing that.

possible solution:

CBigNum bnSubsidy = CBigNum(static_cast( nCoingAge * (posRate_13 / maxTimesPerYear_13)));

Also,  could change the definitions of  postRate_13 and maxTimesPerYear_13  to be "const".    Lots of warnings and side effects of current definitions.

-JK

Doesn't look like 10%,  more like 1%.    I have a block that last week generated 4.55 FLY,  this week  0.21.   

-JDK

Got it, works,  new link, had to clone it again.

Thanks

-JK

Is there a source update for 2.4?   Github has not been updated for 2 months.

Thanks

-JK

I just received my withdrawal from Cryptopia via a support ticket, 1400+ FLY.    Thanks for the support Adam,  this coin / wallet has been a clusterf--k  for all involved.   Tried to do some innovative things that just didn't work out.   Hopefully things are now headed in the right direction.

Vegas, thanks for the reply.   No problem with patience, just wanted to get it out there in case others are having similar issues with topia.

Sent a chunk of my coins to Cryptopia, they say old addresses won't work with new wallet (which has not been implemented there yet) and that my coins are in "limbo" and not to send any more.    What does this mean?   Are my coins goners?

When I enabled savings to YOBIT,  weight was lost and coins were lost.    It worked properly in the 1.6.0 wallet, stake transaction was generated then after 70 confirms,  savings transaction was generated and made it to YOBIT successfully.

In the 1.6.2 wallet,  stake and savings transactions were generated at the same time (did not wait 70 confirms).   Attempting to track the savings transaction was very confusing.    It appears to go to yobit wallet but then get paid out to other users presumably as part of a YOBIT transaction.   Tough to figure out. 

The transaction information in the 1.6.2 wallet doesn't make sense either.   I shows the stake and then a 100% fee charged.    I posted this info in the slack but got no feedback.   I assumed I just jumped the gun it and let it go.

According to wallet:

"amount" : -8.23381314,
"fee" : 8.23381315,
"confirmations" : 93,
"generated" : true,
"blockhash" : "48d71aff4d76b74e0d08e7e9b83f7ac459d5af90685c2fad03f2c646e0865f31",
"blockindex" : 1,
"blocktime" : 1447303358,
"txid" : "064ce96dcfb5b3d67b2f9e4bb6d1217f9da0b2a9a1a2b86843b8a97d727a8d48",
"time" : 1447303358,
"timereceived" : 1447303328,
"details" : [
{
"account" : "principal",
"address" : "FRNqyBF2wVXshGg2UtA8jcggWCVHAoN1qe",
"category" : "generate",
"amount" : 8.23381315
}