[ANN] [MINT] Mintcoin (POS / 5%) [NO ICO] [Fair distro, community maintained]

[cryptomommy]

So basically it will just be 5% gain per year forever. Cool. I actually think that is better because it will always motivate people to keep minting. Like a goid savings bond not too low, but not too high. BTW, Mintcoin just hit a new all time high.  80 sats! ^ ^

Indeed RoboGuy pointed this out to me when he first started and we agreed to leave it - this will make up for the coins "lost" for whatever reason. Mintpal.com (no relations to Mintcoin) was holding a significant amount of coins when they went under. We have no idea if those coins were lost of cashed out.

[1713959201]

1713959201

[1713959201]

1713959201

[1713959201]

1713959201

[1713959201]

1713959201

[1713959201]

1713959201

[presstab]

So the fork will be at about 85,000 blocks from now?

I am coding in the fork as we speak. I have set it for:

Code:

static const unsigned int FORK_TIME = 1438444800; // Sat, 01 Aug 2015 16:00:00 GMT

This is a time and date when I will be available to provide some QR code if needed (quick response )

Watch https://github.com/presstab/Mintcoin-Desktop-Wallet/commits/master today if you want to watch the fork commits. It will be merged with the main mintcoin repo after proper scrutiny.

[Crestington]

So the fork will be at about 85,000 blocks from now?

I am coding in the fork as we speak. I have set it for:

Code:

static const unsigned int FORK_TIME = 1438444800; // Sat, 01 Aug 2015 16:00:00 GMT

This is a time and date when I will be available to provide some QR code if needed (quick response )

Watch https://github.com/presstab/Mintcoin-Desktop-Wallet/commits/master today if you want to watch the fork commits. It will be merged with the main mintcoin repo after proper scrutiny.

I would suggest that if coding in a fork to also bump the protocol number and reject old clients once the fork is in effect. Even if the fork is set a month in advance, there are many that would not upgrade and will just use their old client and this can lead to chain conflicts, stuck blocks. If you reject old protocols then they will not be able to sync with the rest of the network, this is fine because if someone cannot sync, they will come here anyways and ask why, realize they need to be on the latest version and upgrade and back up to speed. If you do not reject old clients then they may be able to sync, it won't be apparent they need to upgrade and won't so it's best not to allow that to happen.

You can add it to the main.cpp file and Block old clients based on time and protocol number, this is an example from PayCon.

        if (nTime > 1430124800 && pfrom->nVersion < 70122)
        {
            // Since February 20, 2012, the protocol is initiated at version 209,
            // and earlier versions are no longer supported
            printf("partner %s using obsolete version %i; disconnecting\n", pfrom->addr.ToString().c_str(), pfrom->nVersion);
            pfrom->fDisconnect = true;
            return false;
        }

[Derek492]

So the fork will be at about 85,000 blocks from now?

I am coding in the fork as we speak. I have set it for:

Code:

static const unsigned int FORK_TIME = 1438444800; // Sat, 01 Aug 2015 16:00:00 GMT

This is a time and date when I will be available to provide some QR code if needed (quick response )

Watch https://github.com/presstab/Mintcoin-Desktop-Wallet/commits/master today if you want to watch the fork commits. It will be merged with the main mintcoin repo after proper scrutiny.

Does it happen according to a specific date or a specific block? Im a little confused.

[supasonic]

So the fork will be at about 85,000 blocks from now?

I am coding in the fork as we speak. I have set it for:

Code:

static const unsigned int FORK_TIME = 1438444800; // Sat, 01 Aug 2015 16:00:00 GMT

This is a time and date when I will be available to provide some QR code if needed (quick response )

Watch https://github.com/presstab/Mintcoin-Desktop-Wallet/commits/master today if you want to watch the fork commits. It will be merged with the main mintcoin repo after proper scrutiny.

Does it happen according to a specific date or a specific block? Im a little confused.

Specific block. Estimated date.

[supasonic]

Kind of off topic but I'm an owner of mintcoin and a developer so I thought I'd try to go through the code. I've downloaded the code and I was going to build it but I wonder what the recommended IDE is.  Are you guys use QT-Creator?  That's what robo guy said he was using.  I'm mostly a windows guy.  Is it possible to successfully build the mintcoin wallet in windows or is that not recommended?  Thanks is advance.

I code on Mint! The Debian version, a linux distro, using qtCreator and sublime. It can be done on windows using minGW but its an involved process which makes you think like a linux user. At that point just become one with virtualbox and any free distro.

Sticking with windows I saw a thread that may be helpful in trying it.
https://bitcointalk.org/index.php?topic=149479.0

I am working on a guide for a partner getting into crypto and linux. Might just post that when its done.

[mchrist152]

So the fork will be at about 85,000 blocks from now?

I am coding in the fork as we speak. I have set it for:

Code:

static const unsigned int FORK_TIME = 1438444800; // Sat, 01 Aug 2015 16:00:00 GMT

This is a time and date when I will be available to provide some QR code if needed (quick response )

Watch https://github.com/presstab/Mintcoin-Desktop-Wallet/commits/master today if you want to watch the fork commits. It will be merged with the main mintcoin repo after proper scrutiny.

I would suggest that if coding in a fork to also bump the protocol number and reject old clients once the fork is in effect. Even if the fork is set a month in advance, there are many that would not upgrade and will just use their old client and this can lead to chain conflicts, stuck blocks. If you reject old protocols then they will not be able to sync with the rest of the network, this is fine because if someone cannot sync, they will come here anyways and ask why, realize they need to be on the latest version and upgrade and back up to speed. If you do not reject old clients then they may be able to sync, it won't be apparent they need to upgrade and won't so it's best not to allow that to happen.

You can add it to the main.cpp file and Block old clients based on time and protocol number, this is an example from PayCon.

        if (nTime > 1430124800 && pfrom->nVersion < 70122)
        {
            // Since February 20, 2012, the protocol is initiated at version 209,
            // and earlier versions are no longer supported
            printf("partner %s using obsolete version %i; disconnecting\n", pfrom->addr.ToString().c_str(), pfrom->nVersion);
            pfrom->fDisconnect = true;
            return false;
        }

I agree with this completely.  People don't always pay attention to wallet releases and if the wallet appears to be working normally they just let it go.  This will let them know that they need to upgrade.

[presstab]

So the fork will be at about 85,000 blocks from now?

I am coding in the fork as we speak. I have set it for:

Code:

static const unsigned int FORK_TIME = 1438444800; // Sat, 01 Aug 2015 16:00:00 GMT

This is a time and date when I will be available to provide some QR code if needed (quick response )

Watch https://github.com/presstab/Mintcoin-Desktop-Wallet/commits/master today if you want to watch the fork commits. It will be merged with the main mintcoin repo after proper scrutiny.

Does it happen according to a specific date or a specific block? Im a little confused.

Specific block. Estimated date.

It's a specific epoch/Unix time. Please don't give out details if you aren't quite sure, this will help avoid confusion with the fork.

[presstab]

So the fork will be at about 85,000 blocks from now?

I am coding in the fork as we speak. I have set it for:

Code:

static const unsigned int FORK_TIME = 1438444800; // Sat, 01 Aug 2015 16:00:00 GMT

This is a time and date when I will be available to provide some QR code if needed (quick response )

Watch https://github.com/presstab/Mintcoin-Desktop-Wallet/commits/master today if you want to watch the fork commits. It will be merged with the main mintcoin repo after proper scrutiny.

I would suggest that if coding in a fork to also bump the protocol number and reject old clients once the fork is in effect. Even if the fork is set a month in advance, there are many that would not upgrade and will just use their old client and this can lead to chain conflicts, stuck blocks. If you reject old protocols then they will not be able to sync with the rest of the network, this is fine because if someone cannot sync, they will come here anyways and ask why, realize they need to be on the latest version and upgrade and back up to speed. If you do not reject old clients then they may be able to sync, it won't be apparent they need to upgrade and won't so it's best not to allow that to happen.

You can add it to the main.cpp file and Block old clients based on time and protocol number, this is an example from PayCon.

        if (nTime > 1430124800 && pfrom->nVersion < 70122)
        {
            // Since February 20, 2012, the protocol is initiated at version 209,
            // and earlier versions are no longer supported
            printf("partner %s using obsolete version %i; disconnecting\n", pfrom->addr.ToString().c_str(), pfrom->nVersion);
            pfrom->fDisconnect = true;
            return false;
        }

I agree with this completely.  People don't always pay attention to wallet releases and if the wallet appears to be working normally they just let it go.  This will let them know that they need to upgrade.

Don't worry this is all already covered in the fork commit.

[drakoin]

Ooooops coinmarket 20, not bad. Hadn't looked at this for months. Congratulations!

Question: I have a wallet v1.14, anything I need to know to update to v1.17?

Thx!

[Crestington]

So the fork will be at about 85,000 blocks from now?

I am coding in the fork as we speak. I have set it for:

Code:

static const unsigned int FORK_TIME = 1438444800; // Sat, 01 Aug 2015 16:00:00 GMT

This is a time and date when I will be available to provide some QR code if needed (quick response )

Watch https://github.com/presstab/Mintcoin-Desktop-Wallet/commits/master today if you want to watch the fork commits. It will be merged with the main mintcoin repo after proper scrutiny.

I would suggest that if coding in a fork to also bump the protocol number and reject old clients once the fork is in effect. Even if the fork is set a month in advance, there are many that would not upgrade and will just use their old client and this can lead to chain conflicts, stuck blocks. If you reject old protocols then they will not be able to sync with the rest of the network, this is fine because if someone cannot sync, they will come here anyways and ask why, realize they need to be on the latest version and upgrade and back up to speed. If you do not reject old clients then they may be able to sync, it won't be apparent they need to upgrade and won't so it's best not to allow that to happen.

You can add it to the main.cpp file and Block old clients based on time and protocol number, this is an example from PayCon.

        if (nTime > 1430124800 && pfrom->nVersion < 70122)
        {
            // Since February 20, 2012, the protocol is initiated at version 209,
            // and earlier versions are no longer supported
            printf("partner %s using obsolete version %i; disconnecting\n", pfrom->addr.ToString().c_str(), pfrom->nVersion);
            pfrom->fDisconnect = true;
            return false;
        }

I agree with this completely.  People don't always pay attention to wallet releases and if the wallet appears to be working normally they just let it go.  This will let them know that they need to upgrade.

Don't worry this is all already covered in the fork commit.

All good, was just making sure. I had people still on old versions months later and since there was an original OP I couldn't control, there were also people trying to download there too but they could never connect and ask about it, I'd ask them what version it was and if they didn't know I'd get them to post a picture (It's also helpful if there are some cosmetic changes too) and then can just get them sorted and on the right version.

[cryptomommy]

Ooooops coinmarket 20, not bad. Hadn't looked at this for months. Congratulations!

Question: I have a wallet v1.14, anything I need to know to update to v1.17?

Thx!

Do it soon - I understand mintcoin stops minting if you are not on 1.17

We should be releasing the new version in the next couple weeks.

[Flyskyhigh]

Ooooops coinmarket 20, not bad. Hadn't looked at this for months. Congratulations!

Question: I have a wallet v1.14, anything I need to know to update to v1.17?

Thx!

Do it soon - I understand mintcoin stops minting if you are not on 1.17

We should be releasing the new version in the next couple weeks.

1.15 works for minting too. The problem with 1.15 is it over calculates your total coins ever minted, because it counts orphans. So its not an accurate number. 1.17 is the wallet to be on at right now.

I'm excited for this coin. Probably more now than ever! Great to see good developments and cooperation.

Stoked about the  upcoming new wallet! Thank you all for your great work and commitment! Mintcoins going to be great! (Already is imo), looking forward to the future. 

[drakoin]

Ooooops coinmarket 20, not bad. Hadn't looked at this for months. Congratulations!
Question: I have a wallet v1.14, anything I need to know to update to v1.17?
Thx!

Do it soon - I understand mintcoin stops minting if you are not on 1.17
We should be releasing the new version in the next couple weeks.

Thanks, mommy ;-)

Done, and works. Beautiful, kudos. Syncing as we speak; that will take a while.

(-: Mf7wCiDe84QfG9SQgUkwTYxfYvpY2Rooua Thx!

[mchrist152]

Ooooops coinmarket 20, not bad. Hadn't looked at this for months. Congratulations!

Question: I have a wallet v1.14, anything I need to know to update to v1.17?

Thx!

Do it soon - I understand mintcoin stops minting if you are not on 1.17

We should be releasing the new version in the next couple weeks.

Upgrade as soon as possible.  I was in the same situation.  To make a long story short, when I upgraded, I had to re-download the whole blockchain and repair the wallet (although I'm told there are quicker ways to do this).  I lost some coins but I think it was only because 1.14 said I was minting but I don't think I really was.  This is why it is so important to let users know that they need to upgrade their wallet.  I had no idea until I tried to upgrade and ran into this frustrating issue.

[drakoin]

Ooooops coinmarket 20, not bad. Hadn't looked at this for months. Congratulations!
Question: I have a wallet v1.14, anything I need to know to update to v1.17?
Thx!

Do it soon - I understand mintcoin stops minting if you are not on 1.17
We should be releasing the new version in the next couple weeks.

Thanks, mommy ;-)
Done, and works. Beautiful, kudos. Syncing as we speak; that will take a while.
(-: Mf7wCiDe84QfG9SQgUkwTYxfYvpY2Rooua Thx!

bootstrap.dat blockchain download anywhere? I am too impatient to wait a whole night ...

[MarSas]

http://www.mintcoinofficial.com/
Download wallet
Download bootstrap.dat

[Vicky789]

My wallet is out of sync and struck at block at 1268345 and is 76% done. It's been struck at that block from about last five days.. I have 8 active connections(nodes)as well on my wallet.. I am using mac and wallet version is v1.14.0.0. I also downloaded the lastest wallet v1.17.0.0 but when I open that it says error loading blinded.dat.. Please help

[cryptomommy]

My wallet is out of sync and struck at block at 1268345 and is 76% done. It's been struck at that block from about last five days.. I have 8 active connections(nodes)as well on my wallet.. I am using mac and wallet version is v1.14.0.0. I also downloaded the lastest wallet v1.17.0.0 but when I open that it says error loading blinded.dat.. Please help

Please go to %appdata% and click on the mintcoin folder - backup the wallet.dat file, delete everything else in the folder and try to re-install the wallet. PM me if you would like further assistance on this process.

[MarSas]

My wallet is out of sync and struck at block at 1268345 and is 76% done. It's been struck at that block from about last five days.. I have 8 active connections(nodes)as well on my wallet.. I am using mac and wallet version is v1.14.0.0. I also downloaded the lastest wallet v1.17.0.0 but when I open that it says error loading blinded.dat.. Please help

You get that message because version 1.17 needs a complete resync.