[ANN] microCoin MRC - alcurEX - Scrypt-Jane - nFactor

[randywald]

Now i have played back the backup of C:\Users\YourUserName\AppData\Roaming\microCoin which i made between the wallet update from v2.1.1.1 to 2.1.1.2.

It works fine now and has already synced to latest block.


I thought that i need to do this as it is said on page 1 of this thread:

If you want to make sure your wallet will stay unharmed, update your wallet and delete everything except wallet.dat and microcoin.conf at C:\Users\YourUserName\AppData\Roaming\microCoin
 
So it is not necessary?

[Del137]

Well, like my grandma said "If its not broken - dont fix it" 

[svennand]

I will try it, or can i just use the old blk0001.dat and blkindex.dat from version 2.1.1.1? At every wallet update i backed up the appdata directory of microcoin and deleted the files except wallet.dat and microcoin.coinf in that directory to resync all blocks...

hmm, never deleted any .DAT files during 3 updates, all work fine 

(facepalm)
Please for future reference each time an crypto coin has this kind of changes.
go into your coin data dir (usually user/appdata/roaming/coinx, and delete everything except wallet.dat

Then start the wallet and let it update to an clean and correct version of the blockchain.

This was also mentioned on the OP page that people had to do for the prev version.

[Bansheroom]

I will try it, or can i just use the old blk0001.dat and blkindex.dat from version 2.1.1.1? At every wallet update i backed up the appdata directory of microcoin and deleted the files except wallet.dat and microcoin.coinf in that directory to resync all blocks...

hmm, never deleted any .DAT files during 3 updates, all work fine  

(facepalm)
Please for future reference each time an crypto coin has this kind of changes.
go into your coin data dir (usually user/appdata/roaming/coinx, and delete everything except wallet.dat

Then start the wallet and let it update to an clean and correct version of the blockchain.

This was also mentioned on the OP page that people had to do for the prev version.

The OP states this, but it isnt really necessary.
Not a single bit of the blockchain will be different, regardless if you delete before the update or not.
There are no "clean" or "dirty" versions of the blockchain.

edit: Always keep a backup (better more thane one) of your wallet.dat in a safe place, thats all you need, regardless of any updates.

[svennand]

I will try it, or can i just use the old blk0001.dat and blkindex.dat from version 2.1.1.1? At every wallet update i backed up the appdata directory of microcoin and deleted the files except wallet.dat and microcoin.coinf in that directory to resync all blocks...

hmm, never deleted any .DAT files during 3 updates, all work fine  

(facepalm)
Please for future reference each time an crypto coin has this kind of changes.
go into your coin data dir (usually user/appdata/roaming/coinx, and delete everything except wallet.dat

Then start the wallet and let it update to an clean and correct version of the blockchain.

This was also mentioned on the OP page that people had to do for the prev version.

The OP states this, but it isnt really necessary.
Not a single bit of the blockchain will be different, regardless if you delete before the update or not.
There are no "clean" or "dirty" versions of the blockchain.

edit: Always keep a backup (better more thane one) of your wallet.dat in a safe place, thats all you need, regardless of any updates.

True, and +1 on the wallet.dat save, But also note that if it isnt well encrypted and it falls in the wrong hands, they will have full access to your funds...
I just allways just delete everything (except wallet.dat). Only takes an hour or two to resync anyways

[randywald]

If i delete everything except wallet.dat and open the new wallet it will sync till block 159,999 and nothing more! So i cannot do it as it is recommended. Don't know what the reason is...

[reftop123]

If i delete everything except wallet.dat and open the new wallet it will sync till block 159,999 and nothing more! So i cannot do it as it is recommended. Don't know what the reason is...

the reason is... dev like CTRL+V

[kryptopojken]

lol very true

[randywald]

I will try to start the client v2.1.1.2 in a virtual machine without any old files and without wallet.dat. Let's see if it jumps over block 159,999 - otherwise new users without existing wallet have a problem. Maybe i made a mistake but why should it be exactly block 159,999 when it stops?

[Don007]

Mine is stuck at #303429. I downloaded the newest version, but it isn't synching.. Well, it's connected to the network, but it won't synch.

I might try synching with the older version soon.

[Bansheroom]

I will try it, or can i just use the old blk0001.dat and blkindex.dat from version 2.1.1.1? At every wallet update i backed up the appdata directory of microcoin and deleted the files except wallet.dat and microcoin.coinf in that directory to resync all blocks...

hmm, never deleted any .DAT files during 3 updates, all work fine  

(facepalm)
Please for future reference each time an crypto coin has this kind of changes.
go into your coin data dir (usually user/appdata/roaming/coinx, and delete everything except wallet.dat

Then start the wallet and let it update to an clean and correct version of the blockchain.

This was also mentioned on the OP page that people had to do for the prev version.

The OP states this, but it isnt really necessary.
Not a single bit of the blockchain will be different, regardless if you delete before the update or not.
There are no "clean" or "dirty" versions of the blockchain.

edit: Always keep a backup (better more thane one) of your wallet.dat in a safe place, thats all you need, regardless of any updates.

True, and +1 on the wallet.dat save, But also note that if it isnt well encrypted and it falls in the wrong hands, they will have full access to your funds...
I just allways just delete everything (except wallet.dat). Only takes an hour or two to resync anyways

Wallet has to be encrypted, yeah, very true.
I bet you never mined huntercoin? Last time i had to redownload the blockchain was a real pain in the ass, took me 2 days and at least 20% of my SSD lifetime 

[Bansheroom]

If i delete everything except wallet.dat and open the new wallet it will sync till block 159,999 and nothing more! So i cannot do it as it is recommended. Don't know what the reason is...

the reason is... dev like CTRL+V

Please do us all a favor and show us your great math skills, as it sounds you could have done this all better.

Please start by subtracting yourself from this forum and community.
If you managed this, go on and multiply yourself with the usefullness of all your posts.

[trogdorjw73]

Um... don't we have buggy code still? Let me post what's in there right now:

Code:

int64 GetProofOfWorkReward( int nHeight, uint256 prevHash)
{

// microCoin block size.
        int64 nSubsidy = 1 * COIN;
        if(nHeight < 10000)    
        {
                nSubsidy = 0.0001 * COIN;		// Premining 1 coin. (10000 blocks * 0.0001 coins) = Total 1 coin. ** For network security purpose. (Needed with the fair launch).
        }
		else if(nHeight >= 10000 && nHeight < 160000) // Launch start. Increasing block size on every blocks +1. ** Blocks: 1001 - 160000
        {
				nSubsidy = nHeight * COIN;
		}	
		else if (nHeight >= 310000 && nHeight <= 315000) // 310,000 block rewards, decreasing 0.01 on every block
		{
		nSubsidy = (310000 - ((nHeight - 310000) * 0.01)) * COIN;
		}

		else if (nHeight <= 318000) // 0.01 block rewards (wrong logic as coin spec, but we need to keep it because it's already happened)
		{
		nSubsidy = (3100 - ((nHeight * 0.01) - 310000)) - 300000;
		}

		else
		{
		nSubsidy = (10000 - ((nHeight - 318000) * 0.01)) * COIN;
		if (nSubsidy <= 1000 * COIN) nSubsidy = 1000 * COIN; // Rest of blocks are 1000 coins. Then network working forever with stake blocks.
		}


    return nSubsidy;
}

It seems we're missing the case of the block number being 160000-310000 with rewards going from 160000 back to 10000. Doesn't that matter? Actually, right now blocks 160000-310000 would be in the category of <= 318000, which would mean blocks 160000-310000 and 315000-318000 would be worth the wrong values. Anyone grabbing a new wallet and downloading the block chain would get all sorts of problems, wouldn't they? If I'm reading that correctly and understand the code (which I may not!), then the correct code should be as follows (with a bit of modified formatting for readability because the indentations were off):

Code:

int64 GetProofOfWorkReward( int nHeight, uint256 prevHash)
{

	// microCoin block reward amount.
	int64 nSubsidy = 1 * COIN;
	
	// Premining 1 coin. (10000 blocks * 0.0001 coins) = Total 1 coin. ** For network security purpose. (Needed with the fair launch).
	if(nHeight < 10000)
	{
		nSubsidy = 0.0001 * COIN;
	}
	
	// Launch start. Increasing block size on every blocks +1. ** Blocks: 1001 - 160000
	else if(nHeight >= 10000 && nHeight < 160000)
	{
		nSubsidy = nHeight * COIN;
	}
	
	// Count back down from 160K to 10K block rewards.
	else if (nHeight >= 160000 && nHeight < 310000)
	{
		nSubsidy = (320000 - nHeight) * COIN;
	}
	
	// Erroneous 310,000-309,950 block rewards, decreasing 0.01 on every block (this already happened so we keep it)
	else if (nHeight >= 310000 && nHeight <= 315000)
	{
		nSubsidy = (310000 - ((nHeight - 310000) * 0.01)) * COIN;
	}
	
	// Erroneous 0.01 block rewards (wrong logic again, but we need to keep it because it's already happened)
	else if (nHeight <= 318000)
	{
		nSubsidy = (3100 - ((nHeight * 0.01) - 310000)) - 300000;
		// NOTE: Seriously!? Who came up with this code as the "fix"? It's the same as:
		// nSubsidy = 13100 - nHeight * 0.01;
		// That's so utterly wrong and confusing to begin with, it's no wonder things broke.
	}
	
	// Rewards decrease from 10000 to 10000 in 0.01 steps; minimum reward is 1000 coins.
	else
	{
		nSubsidy = (10000 - ((nHeight - 318000) * 0.01)) * COIN;
		
		// The remaining blocks are 1000 coins each, with network continuing forever with stake blocks.
		if (nSubsidy <= 1000 * COIN) nSubsidy = 1000 * COIN;
	}

    return nSubsidy;
}

This is insane, people. As someone that studied computer science 20 years back, I can't believe the sort of hack-job coding we're seeing. Let me give you some advise: properly commented code is important, and obfuscating code with behind-the-scenes math is a bad idea.

MRC donations for my awesome code (which will be worth squat very soon at this rate): 14LADSmN8FkX7kfsAkvgvmPH8ZGJUdABLV

[trogdorjw73]

If i delete everything except wallet.dat and open the new wallet it will sync till block 159,999 and nothing more! So i cannot do it as it is recommended. Don't know what the reason is...

the reason is... dev like CTRL+V

The real reason: see my code above. The dev forgot about the case of blocks 160000-309999. *Sigh*

[randywald]

That's exactly why my new wallet stops syncing at block 159,999

For now, don't update your wallet to v2.1.1.2. It's defective

[Bansheroom]

Um... don't we have buggy code still? Let me post what's in there right now:

....

It seems we're missing the case of the block number being 160000-310000 with rewards going from 160000 back to 10000. Doesn't that matter? Actually, right now blocks 160000-310000 would be in the category of <= 318000, which would mean blocks 160000-310000 and 315000-318000 would be worth the wrong values. Anyone grabbing a new wallet and downloading the block chain would get all sorts of problems, wouldn't they? If I'm reading that correctly and understand the code (which I may not!), then the correct code should be as follows (with a bit of modified formatting for readability because the indentations were off):

....

This is insane, people. As someone that studied computer science 20 years back, I can't believe the sort of hack-job coding we're seeing. Let me give you some advise: properly commented code is important, and obfuscating code with behind-the-scenes math is a bad idea.

MRC donations for my awesome code (which will be worth squat very soon at this rate): 14LADSmN8FkX7kfsAkvgvmPH8ZGJUdABLV

Sound for me as you found the explanation for new wallets stopping sync at 159.999
Still time to change code and (hopefully last time) inform all involved parties.
I will also donate you plenty of MRC, but after this all is sorted out. I dont risk sending coins now with whatever version.
As soon as we are stable again....if this happens ever  

[aikklond]

client hangs on launch with message "loading block explorer"

[trogdorjw73]

Addendum to my above post: I had some more bad math. Hahaha... it's why I'm not the developer. :-)

Basically, the 160000-309999 case was returning 150000 to 0 coins, not 160000 to 10000 coins. I've edited my post (changed 310000 to 320000 on that one line), but you can see the incorrect code quoted above me.

[Bansheroom]

Addendum to my above post: I had some more bad math. Hahaha... it's why I'm not the developer. :-)

Basically, the 160000-309999 case was returning 150000 to 0 coins, not 160000 to 10000 coins. I've edited my post (changed 310000 to 320000 on that one line), but you can see the incorrect code quoted above me.

fixed it so noone can copy wrong code, seems to be very complicated to code.

[randywald]

I can definitely confirm the problem as i saw that the new wallet in my virtual machine now also stopped syncing at block 159,999 (as i said a few posts before)...