[AC] AsiaCoin | Pure PoS | 100% Interest

[Maestro1]

I removed the block to re-update the new wallet. Wallet showed 12 available nodes, but is very slow to update

I have 30+ available nodes here. You didn't need to remove the blockchain, I mentioned it specifically in the instructions that you don't need to redownload the entire blockchain again. But no harm done, just some download

[SENPIER]

Now looks good, the problem may be my computer.

[CryptoSteam]

The AsiaCoin Team is calling for more articles. If you are a writer, then go ahead and write an article about the resurrection of AsiaCoin! You have all the information you need.

[coin-swap]

I just want to let everyone know that I've staked successfully in the new wallet. It is working great!

I have to give micryon kudos for his technical expertise that helped save AsiaCoin and Maestro1 to his tireless effort in reviving this coin.

AsiaCoin has resurrected from the dead in 7 days, which is just simply jaw-dropping, amazing and historical for the cryptocurrency world.

This revival will be remembered for years to come.

Maestro1 has done a tremendous job.

[Maestro1]

The AsiaCoin Team is calling for more articles. If you are a writer, then go ahead and write an article about the resurrection of AsiaCoin! You have all the information you need.

We need more people to push it hard to blogs and websites, mostly in local languages, and mostly in Asian local languages. That's the key audience.

[johntseng]

just donated 10,000 AC
8a461586e431f240ebee51b550408c9ace5edbfc7c74a403231a0bf06bfc4bc4

Great jobs and thanks to the team.

[Maestro1]

I just want to let everyone know that I've staked successfully in the new wallet. It is working great!

I have to give micryon kudos for his technical expertise that helped save AsiaCoin and Maestro1 to his tireless effort in reviving this coin.

AsiaCoin has resurrected from the dead in 7 days, which is just simply jaw-dropping, amazing and historical for the cryptocurrency world.

This revival will be remembered for years to come.

I just want to add that this is not the finish, this is the beginning. In order to make Asia Coin what all of us wanted it to be, it will take all of us. This includes helping out in marketing, development, donation, testing and many more.

That's why we're creating a foundation, somewhere everyone can join, we will have our own website and a Slack channel for coordination. We need people who are fully committed to the project in order to make Asia Coin what we want it to become. A lot of people, including the experienced members here, mentioned that AC can be 0.001 BTC at some point within 2014, but it will not get there by itself. This revival is the example that the community is all that matters for a coin, and it's always true, not just at the moments of crisis.

Look at other successful examples and see who made them what they are today, and it's always the community. Look at failed examples and see who failed the coins? The community. So whether our revival is forgotten in a couple of weeks or become a shining example in the years to come will depends on ALL OF US, the community.

Now that the technical challenge is over and AC is already listed on many exchanges and will be on major ones very shortly, all of us have a decision to make. We can go as quickly as we can (in a race) to dump our coins onto others to revive a fraction of our initial investments, or we can help make AC what we wanted it to be when we made our investments. There will be people who cut their losses and will dump, and it's fine, it's their right. Nobody can tell people what to do with their own stuff. This is a decision that all of us have to make. After all that we've been through, what's the best thing to do? Get out while you can for a fraction of your initial investment or help us build Asia Coin. You have some time to think about it

[menu74]

Is the coin PoW difficulty frozen at 274.46071294? What's up with that? It's stayed static over the past 5000 blocks or so, and I see the hash rate hasn't really changed either. According to the latest wallet, networkhashps  went from ~19GH at block 27377 up to ~21GH at block 32106. What's up with that? Are people still trying to mine AC directly? Or are these just miscellaneous bugs? Considering the temporary block explorer is down, I think we still have a problem. Hopefully it doesn't really matter, but given the checkered past of this coin things like this won't help instill confidence!

AsiaCoin is already in POS stage, no more directing mining of AC. The only way to mine AC is to mine on multipools and have your payout in AC.

After PoW stage, it should be difficult to reach 19,21 GH of network hashpowers at block 27377 and 32106. We will be stay at PoW+PoS stage if the data trogdorjw73 provided is correct. Is this possible to reopen the block explorer let more community members to check this issue? We should do more care about this matter since three exchanges allow AC transaction now.  Thanks for all your efforts, great community and team members.  

[ORiN]

Is the coin PoW difficulty frozen at 274.46071294? What's up with that? It's stayed static over the past 5000 blocks or so, and I see the hash rate hasn't really changed either. According to the latest wallet, networkhashps  went from ~19GH at block 27377 up to ~21GH at block 32106. What's up with that? Are people still trying to mine AC directly? Or are these just miscellaneous bugs? Considering the temporary block explorer is down, I think we still have a problem. Hopefully it doesn't really matter, but given the checkered past of this coin things like this won't help instill confidence!

AsiaCoin is already in POS stage, no more directing mining of AC. The only way to mine AC is to mine on multipools and have your payout in AC.

After PoW stage, it should be difficult to reach 19,21 GH of network hashpowers at block 27377 and 32106. We will be stay at PoW+PoS stage if the data trogdorjw73 provided is correct. Is this possible to reopen the block explorer let more community members to check this issue? We should do more care about this matter since three exchanges allow AC transaction now.  Thanks for all your efforts, great community and team members. 

A hard fork will be required. However, the community and the current team has already decided on retaining the PoS specification with some with ensure that the total number of coins will be similar to the original specifications.

[noobthegreat]

MICRYON FOR EMPEROR

[Howthecoin]

just donated 10,000 AC
8a461586e431f240ebee51b550408c9ace5edbfc7c74a403231a0bf06bfc4bc4

Great jobs and thanks to the team.

Welcome guy, thank you very much for your contribution to this new born community.

[tramphuochuy]

+5000 AC & Thanks you very much

You saved $1 million of investor’s money
The dragon with second heart will rise again , far more , for sure

[micryon]

After PoW stage, it should be difficult to reach 19,21 GH of network hashpowers at block 27377 and 32106. We will be stay at PoW+PoS stage if the data trogdorjw73 provided is correct. Is this possible to reopen the block explorer let more community members to check this issue? We should do more care about this matter since three exchanges allow AC transaction now.  Thanks for all your efforts, great community and team members.  

I'm not sure what you mean, can you clarify?

Do you mean that you think PoW is still going on?

I can assure that PoW is not currently being accepted into the blockchain at this point.  Although one can try to generate a proof of work, no other nodes would accept it into the blockchain due to this statement in CBlock::AcceptBlock()

Code:

	if (IsProofOfWork() && nHeight > CUTOFF_HEIGHT)
        return DoS(100, error("AcceptBlock() : No proof-of-work allowed anymore (height = %d)", nHeight));

[ORiN]

+5000 AC & Thanks you very much

You saved $1 million of investor’s money
The dragon with second heart will rise again , far more , for sure

Nice dragon there! I usually think of us as more of a phoenix that rises from its ashes

[Maestro1]

After PoW stage, it should be difficult to reach 19,21 GH of network hashpowers at block 27377 and 32106. We will be stay at PoW+PoS stage if the data trogdorjw73 provided is correct. Is this possible to reopen the block explorer let more community members to check this issue? We should do more care about this matter since three exchanges allow AC transaction now.  Thanks for all your efforts, great community and team members.  

I'm not sure what you mean, can you clarify?

Do you mean that you think PoW is still going on?

I can assure that PoW is not currently being accepted into the blockchain at this point.  Although one can try to generate a proof of work, no other nodes would accept it into the blockchain due to this statement in CBlock::AcceptBlock()

Code:

	if (IsProofOfWork() && nHeight > CUTOFF_HEIGHT)
        return DoS(100, error("AcceptBlock() : No proof-of-work allowed anymore (height = %d)", nHeight));

But it's still interesting to me, where does that ~19 GH/s come from? I mean, someone or some pool with that amount of hashpower should clearly know that they're not getting reward for their hashrate. I think it could be a pool whose settings gone totally wrong. getdifficulty output:

Code:

{
"proof-of-work" : 274.46071294,
"proof-of-stake" : 0.00367996,
"search-interval" : 1
}

[micryon]

Actually the nethash rate from the client is NOT a real number.. No one is actually mining 19 Gh/s.

It's just a calculated number using timestamp delta between blocks and difficulty

It is simply just this forumla: https://en.bitcoin.it/wiki/Difficulty#What_is_the_formula_for_difficulty.3F

In code..

Code:

// Litecoin: Return average network hashes per second based on last number of blocks.
Value GetNetworkHashPS(int lookup) {
    if (pindexBest == NULL)
        return 0;

    // If lookup is -1, then use blocks since last difficulty change.
    if (lookup <= 0)
        lookup = pindexBest->nHeight % 2016 + 1;

    // If lookup is larger than chain, then set it to chain length.
    if (lookup > pindexBest->nHeight)
        lookup = pindexBest->nHeight;

    CBlockIndex* pindexPrev = pindexBest;
    for (int i = 0; i < lookup; i++)
        pindexPrev = pindexPrev->pprev;

    double timeDiff = pindexBest->GetBlockTime() - pindexPrev->GetBlockTime();
    double timePerBlock = timeDiff / lookup;

    return (boost::int64_t)(((double)GetDifficulty() * pow(2.0, 32)) / timePerBlock);
}

[nutildah]

Hi guys, is there any evidence that the old wallet contains keyloggers or malware to steal other coins from other wallets? I can't get a straight answer on this. Any help would be appreciated.

thanks

I can't say if it does or not, my guess is that it doesn't... the original dev was probably trying to make it as clean as possible other than his original scam of the hidden pre-mine. He probably wouldn't risk a keylogger on the software for fear it might be discovered before his premine was.

That is all pure speculation on my part though. anybody ran a wireshark on the asiacoin program to see if it tries to connect to anything besides the asiacoin network?

ya i agree, his scam worked perfectly and a keylogger and/or other virus/malware add-on would've been caught early as you say. As a result, he wouldn't of been able to steal as much $$$

So can anyone actually confirm if the wallet has a virus? Malwarebytes tries to block it from contacting a server but it could be benign, I'm gonna look into it. I'd rather not even open it if there's a slight possibility of virus tho.

[Maxikosw]

Ty for your great work team!!!


"Tonight we're flying and we're free,
We're free before the thunderstorm,
On towards the wilderness,
Our quest carries on,
Far beyond the sundown,
Far beyond the moonlight!!!"

https://www.youtube.com/watch?v=0jgrCKhxE1s

[micryon]

But it's still interesting to me, where does that ~19 GH/s come from? I mean, someone or some pool with that amount of hashpower should clearly know that they're not getting reward for their hashrate. I think it could be a pool whose settings gone totally wrong. getdifficulty output:

Code:

{
"proof-of-work" : 274.46071294,
"proof-of-stake" : 0.00367996,
"search-interval" : 1
}

To expand further on where these numbers come from..

So NetHashRate uses the GetDifficulty() and timestamps from blocks to calculate.. (thats why it may seem variable because timestamps differ.. so it'll bounce around 18-19..

GetDifficulty() itself basically returns the *last* block that was proof of work.  And thus it's always stable.  

The code is just a while loop that keeps searching the prevblock index until it finds a block that was done via PoW:

Code:

const CBlockIndex* GetLastBlockIndex(const CBlockIndex* pindex, bool fProofOfStake)
{
    while (pindex && pindex->pprev && (pindex->IsProofOfStake() != fProofOfStake))
        pindex = pindex->pprev;
    return pindex;
}

double GetDifficulty(const CBlockIndex* blockindex)
{
    // Floating point number that is a multiple of the minimum difficulty,
    // minimum difficulty = 1.0.
    if (blockindex == NULL)
    {
        if (pindexBest == NULL)
            return 1.0;
        else
            blockindex = GetLastBlockIndex(pindexBest, false);
    }

And.. I guess that must have been the last block at 20160... yep, last PoW block difficulty was indeed locked at : 274.46071294.

Code:

getblockhash 20160
0000000000bd301676a0e57aeb7c63165f875dd015ed2e44262a41ce3feca390

getblock 0000000000bd301676a0e57aeb7c63165f875dd015ed2e44262a41ce3feca390
{
"hash" : "0000000000bd301676a0e57aeb7c63165f875dd015ed2e44262a41ce3feca390",
"confirmations" : 12230,
"size" : 5540,
"height" : 20160,
"version" : 4,
"merkleroot" : "47105789d11856e5f2cea3356a3d3e4f57e3387fc3e0f0f5be80e44ef57f232c",
"mint" : 5000.03700000,
"time" : 1398926850,
"nonce" : 4172128409,
"bits" : "1c00eec7",
"difficulty" : 274.46071294,
"previousblockhash" : "0000000000b94ea70342a8219e89b8bcf6c6f402e90bf493996942b64e8bfb5e",
"nextblockhash" : "99dbd72ce0b370df3b6dad5d61be279ce874aa5cbfc3accbcb69ab1bedee89e7",
"flags" : "proof-of-work",
"proofhash" : "0000000000bd301676a0e57aeb7c63165f875dd015ed2e44262a41ce3feca390",
"entropybit" : 0,
"modifier" : "5b13c49e3d59da47",
"modifierchecksum" : "76639dba",
"tx" : [
"640666e861238d5212b78219a68b329f4de1642cfc92d92e683f445a78f07ff6",
"397b22d78097de1619a70dd7891218c4f014e2ac36954c27a788c38740c6d151",
"d510fcf164267a0bf44bf9bc7d39cd9d4f851bad5d65fd9cfb61e1fbc8114e48",
"f724ce029cad2a88281d81bb0e5081c9d573a65eb756b096f3e59fc5c767ecaf",
"838ea24c4d87c97344c5334cda4870d8dfcfc530abb5507244b1c0c45c8e1b49"
],
"signature" : "3044022076f574731c818943b983d8460fe99ca02f27f4f494cf421bfdd83aec9820dc2002202e7c2da59be560228af0e3614d2dc1adf9d40db5218c6c48257c3ed6cd4085bd"
}

So in a very simple sense: the RPC calls for getmininginfo and getdifficulty are showing the frozen state of the last PoW block difficulty and nethash rates.

I think when everyone cloned their coins from ppcoin, which was supposed to be a PoW/PoS coin.. moving to 100% PoS, a lot of the RPC calls were never modified to take this into account to return the proper information.. PPcoin wasn't designed to be a 100% PoS coin to begin with...

I bet rat4 and others may be updating the code under blackcoin to clean up some of this stuff.... or i can just update it.. but this stuff is just informational data through the RPC calls, it doesn't factor into actual operations..

[micryon]

Oh and in case anyone is interested, I posted a winmerge report of main.cpp (one of the key files), line by line diffs between Asiacoinfix and Cinni

http://www.realstackcoin.org/asiacoinfix_cinni.htm

Just search for the yellow sections to see the diffs.

So just to prove that we're no worse than the other coins in other areas (aside from the security patch).