Ninjastic
Search content
Sort by
Showing 20 of 24 results by mchrist152
Post
Topic
Board Mining (Altcoins)
Re:
by
mchrist152
on 07/11/2020, 15:28:30 UTC
New project for miners, absolute free, this project development "ETHlargement" - EthereumPill release
Support Algo: Ethash/KawPow/ProgPow

Download: https://ethereumpill.info/ProjectEthereumPill.zip

Virustotal: https://www.virustotal.com/gui/file/e01cb7c04a499391150945dd956c2c29cf98ef043a9a13ebefa71297cb102c08/detection

Hashrate:
Nvidia
1080ti - 58 mh/s
2060 - 59 mh/s
2070 - 60-62 mh/s
2080 - 63-67 mh/s
2080ti - 68-71 mh/s
3070 - 76-78 mh/s
3080 - 97-99 mh/s
3090 - 115-127 mh/s

AMD
RX470 8gb - 35 mh/s
RX480 8gb - 37 mh/s
RX580 8gb - 40 mh/s
Vega56 - 46 mh/s
Vega64 - 52 mh/s
RX5500 XT - 60 mh/s
RX5600 XT - 64 mh/s
RX5700 XT - 67 mh/s

P.S.: the project is being drowned by competitors, don't trust anyone, check the information yourself
Post
Topic
Board Announcements (Altcoins)
Re: [ANN] [MINT] Mintcoin (POS / 5%) [NO ICO] [Fair distro, community maintained]
by
mchrist152
on 15/01/2018, 00:21:23 UTC
Quote from: cryptosnisgo on January 14, 2018, 11:58:29 PM
Quote from: cryptosnisgo on January 14, 2018, 10:22:58 PM
Quote from: funkwerk101 on January 14, 2018, 09:14:27 PM
Create a conf file in notepad with the below and add to mintcoin folder under appdata/roaming

addnode=144.76.64.123
addnode=81.95.191.233
addnode=211.28.143.54
addnode=89.71.42.172
addnode=79.124.7.72:12788
addnode=144.76.237.39:12788
addnode=82.211.60.130:12788
addnode=108.167.46.93:12788
addnode=158.69.27.82:12788
addnode=81.146.57.173:12788
addnode=184.7.192.21:12788
addnode=92.24.190.15:12788
addnode=72.226.24.176:12788
addnode=89.18.27.179:12788


The config file name is case sensitive. Use mintcoin.conf

Hope that helps


Tks mate! Smiley


Still not working... ;(


I used to run mintcoin, but even when it is running it takes a lot of resources and is hard to upgrade. I had to download the entire block chain on several occasions to get it back up and working. The best suggestion I can give you is to run blackcoin instead. It's light on resources and runs like a charm. I've been very happy with it. It is a POS coin just like Mintcoin and created around the same time. Mintcoin has a better name and marketing but Blackcoin does a much better job of delivering on the POS promise. That's been my experience anyway.
Post
Topic
Board Announcements (Altcoins)
Re: [ANN] BlackCoin (BLK/BC) | PoS | No ICO
by
mchrist152
on 07/01/2018, 16:52:38 UTC
Quote from: ScoobyDood on January 06, 2018, 08:31:07 PM
Quote from: Mouse020 on January 06, 2018, 01:07:27 PM
Quote from: ARTEM DA on January 06, 2018, 10:27:27 AM
How many BLK-coins u need to "mine" with PoS?
more than 1
better 10k
Why is it since the new wallet staking has been crap..for me?
47k staking and I received six (6) coins for all of 2017, very weak imo 8(

Are you running your wallet continuously? The stake is a reward for securing the network and the wallet needs to be up and running to do so. This was a change made to the code not too long ago. I've only got 30k coins and I've received more than 6 coins in 2018. But my computer and wallet is running 24/7/365.
Post
Topic
Board Announcements (Altcoins)
Re: [ANN][MINT] Mintcoin - New Wallet v2.0.2 released 3/1/16
by
mchrist152
on 02/12/2016, 14:57:46 UTC
Quote from: Flyskyhigh on December 02, 2016, 12:03:09 PM
Quote from: mchrist152 on December 02, 2016, 04:22:25 AM
I'm running into the following error when I try to open my wallet:

Runaway Exception
A fatal error occurred. MintCoin can no longer continue safely and will quit.
Exception: St13runtime_error
CDB(): error opening database environment IO error...

I'm running Windows10.  Any ideas on what I can do to fix this?

Do you have any more detail? Do you have a debug log? What wallet version are you running?

I started it up this morning and it seems to be working now even though I tried repeatedly last night with the same result.  That's a first.  Apparently it somehow healed itself.  Anyway, I'm running wallet version 2.0.2.0

Thanks for your response anyway.
Post
Topic
Board Announcements (Altcoins)
Re: [ANN][MINT] Mintcoin - New Wallet v2.0.2 released 3/1/16
by
mchrist152
on 02/12/2016, 04:22:25 UTC
I'm running into the following error when I try to open my wallet:

Runaway Exception
A fatal error occurred. MintCoin can no longer continue safely and will quit.
Exception: St13runtime_error
CDB(): error opening database environment IO error...

I'm running Windows10.  Any ideas on what I can do to fix this?
Post
Topic
Board Announcements (Altcoins)
Re: [ANN][MINT] Mintcoin - New Wallet v2.0.1.0 - CPU & Bandwidth Optimization
by
mchrist152
on 10/02/2016, 03:37:49 UTC
Has anybody noticed minting slowing down? Here's the last few days for me:

2/5/2016 5 mintings out of 5 attempts
2/6/2016 2 mintings out of 4 attempts
2/7/2016 0 mintings out of 3 attempts
2/8/2016 1 minting out of 1 attempts
2/9/2016 0 mintings out of 0 attempts

No mintings today at all. Balance about the same. Seems strange. Is anybody else seeing this?

mchrist152
Post
Topic
Board Announcements (Altcoins)
Re: [ANN][MINT] New Wallet Released - Mandatory Upgrade / Hard fork Set for August 1
by
mchrist152
on 10/08/2015, 01:40:03 UTC
Quote from: Fuzzbawls on August 10, 2015, 01:13:29 AM
Quote from: mchrist152 on August 10, 2015, 12:57:56 AM
I'm able to ping the peers in the debug.log file so I have connectivity at least.  Here is an excerpt from my debug.log file:

them=76.21.26.146:12788, peer=76.21.26.146:12788
partner 76.21.26.146:12788 using obsolete version 60006; disconnecting
ProcessMessage(version, 101 bytes) FAILED
disconnecting node 76.21.26.146:12788
trying connection 76.21.26.146:12788 lastseen=0.0hrs
connected 76.21.26.146:12788
send version message: version 60007, blocks=0, us=76.76.70.110:12788, them=76.21.26.146:12788, peer=76.21.26.146:12788
partner 76.21.26.146:12788 using obsolete version 60006; disconnecting
ProcessMessage(version, 101 bytes) FAILED
disconnecting node 76.21.26.146:12788

what is meant by obsolete version 60006


see my previous post

Thanks!  The work around got it syncing.
Post
Topic
Board Announcements (Altcoins)
Re: [ANN][MINT] New Wallet Released - Mandatory Upgrade / Hard fork Set for August 1
by
mchrist152
on 10/08/2015, 00:57:56 UTC
Quote from: mchrist152 on August 10, 2015, 12:44:02 AM
Quote from: mchrist152 on August 09, 2015, 05:36:38 PM
Would anybody be so kind as to help me with a mintcoin wallet compile issue?

I'm using the commandline to try and compile the unix version of the wallet on a Debian system.  Everything compiles but I'm running into the following linker errors:

...
build/moc_repairwalletdialog.o build/qrc_bitcoin.o    -L/usr/lib/x86_64-linux-gnu -lminiupnpc /home/mikech/github/Mintcoin-Desktop-Wallet/src/leveldb/libleveldb.a /home/mikech/github/Mintcoin-Desktop-Wallet/src/leveldb/libmemenv.a -lrt -lssl -lcrypto -ldb_cxx -lboost_system -lboost_filesystem -lboost_program_options -lboost_thread -lpthread -lQtGui -lQtNetwork -lQtCore
build/init.o: In function `bool CDB::Read(std::string const&, CBlockLocator&)':
init.cpp:(.text._ZN3CDB4ReadISs13CBlockLocatorEEbRKT_RT0_[_ZN3CDB4ReadISs13CBlockLocatorEEbRKT_RT0_]+0x122): undefined reference to `Dbt::Dbt(void*, unsigned int)'
init.cpp:(.text._ZN3CDB4ReadISs13CBlockLocatorEEbRKT_RT0_[_ZN3CDB4ReadISs13CBlockLocatorEEbRKT_RT0_]+0x12e): undefined reference to `Dbt::Dbt()'
init.cpp:(.text._ZN3CDB4ReadISs13CBlockLocatorEEbRKT_RT0_[_ZN3CDB4ReadISs13CBlockLocatorEEbRKT_RT0_]+0x394): undefined reference to `Dbt::~Dbt()'
init.cpp:(.text._ZN3CDB4ReadISs13CBlockLocatorEEbRKT_RT0_[_ZN3CDB4ReadISs13CBlockLocatorEEbRKT_RT0_]+0x3a0): undefined reference to `Dbt::~Dbt()'
init.cpp:(.text._ZN3CDB4ReadISs13CBlockLocatorEEbRKT_RT0_[_ZN3CDB4ReadISs13CBlockLocatorEEbRKT_RT0_]+0x454): undefined reference to `Dbt::~Dbt()'
init.cpp:(.text._ZN3CDB4ReadISs13CBlockLocatorEEbRKT_RT0_[_ZN3CDB4ReadISs13CBlockLocatorEEbRKT_RT0_]+0x460): undefined reference to `Dbt::~Dbt()'
build/db.o: In function `CDBEnv::CDBEnv()':
db.cpp:(.text+0x38f): undefined reference to `DbEnv::DbEnv(unsigned int)'
build/db.o: In function `CDBEnv::EnvShutdown()':
db.cpp:(.text+0x12fb): undefined reference to `DbEnv::close(unsigned int)'
...

From what I've read on the web I need to change the version of my compiler to fix this issue but nowhere does anybody say what version of compiler is required.  I'm currently running gcc 4.9.2.  Can anybody tell me what version of compiler they are using to successfully compile the unix version of the wallet?

Thanks in Advance,

mchrist152

Ok, it turns out that it wasn't the version of the compiler after all but the way I compiled Berkeley DB. I had to add the following arguments to the Berkeley DB configure command:
../dist/configure --enable-cxx --disable-shared --with-pic
That did the trick.  Seems like every time I post to this board I figure out the answer shortly there after.

So it built and it's running but it's not connecting to other nodes.  I'm not sure why.  It's running in a virtual machine so maybe there is something blocking it but other apps are having no problems.  Any ideas?

I'm able to ping the peers in the debug.log file so I have connectivity at least.  Here is an excerpt from my debug.log file:

them=76.21.26.146:12788, peer=76.21.26.146:12788
partner 76.21.26.146:12788 using obsolete version 60006; disconnecting
ProcessMessage(version, 101 bytes) FAILED
disconnecting node 76.21.26.146:12788
trying connection 76.21.26.146:12788 lastseen=0.0hrs
connected 76.21.26.146:12788
send version message: version 60007, blocks=0, us=76.76.70.110:12788, them=76.21.26.146:12788, peer=76.21.26.146:12788
partner 76.21.26.146:12788 using obsolete version 60006; disconnecting
ProcessMessage(version, 101 bytes) FAILED
disconnecting node 76.21.26.146:12788

what is meant by obsolete version 60006
Post
Topic
Board Announcements (Altcoins)
Re: [ANN][MINT] New Wallet Released - Mandatory Upgrade / Hard fork Set for August 1
by
mchrist152
on 10/08/2015, 00:44:02 UTC
Quote from: mchrist152 on August 09, 2015, 05:36:38 PM
Would anybody be so kind as to help me with a mintcoin wallet compile issue?

I'm using the commandline to try and compile the unix version of the wallet on a Debian system.  Everything compiles but I'm running into the following linker errors:

...
build/moc_repairwalletdialog.o build/qrc_bitcoin.o    -L/usr/lib/x86_64-linux-gnu -lminiupnpc /home/mikech/github/Mintcoin-Desktop-Wallet/src/leveldb/libleveldb.a /home/mikech/github/Mintcoin-Desktop-Wallet/src/leveldb/libmemenv.a -lrt -lssl -lcrypto -ldb_cxx -lboost_system -lboost_filesystem -lboost_program_options -lboost_thread -lpthread -lQtGui -lQtNetwork -lQtCore
build/init.o: In function `bool CDB::Read(std::string const&, CBlockLocator&)':
init.cpp:(.text._ZN3CDB4ReadISs13CBlockLocatorEEbRKT_RT0_[_ZN3CDB4ReadISs13CBlockLocatorEEbRKT_RT0_]+0x122): undefined reference to `Dbt::Dbt(void*, unsigned int)'
init.cpp:(.text._ZN3CDB4ReadISs13CBlockLocatorEEbRKT_RT0_[_ZN3CDB4ReadISs13CBlockLocatorEEbRKT_RT0_]+0x12e): undefined reference to `Dbt::Dbt()'
init.cpp:(.text._ZN3CDB4ReadISs13CBlockLocatorEEbRKT_RT0_[_ZN3CDB4ReadISs13CBlockLocatorEEbRKT_RT0_]+0x394): undefined reference to `Dbt::~Dbt()'
init.cpp:(.text._ZN3CDB4ReadISs13CBlockLocatorEEbRKT_RT0_[_ZN3CDB4ReadISs13CBlockLocatorEEbRKT_RT0_]+0x3a0): undefined reference to `Dbt::~Dbt()'
init.cpp:(.text._ZN3CDB4ReadISs13CBlockLocatorEEbRKT_RT0_[_ZN3CDB4ReadISs13CBlockLocatorEEbRKT_RT0_]+0x454): undefined reference to `Dbt::~Dbt()'
init.cpp:(.text._ZN3CDB4ReadISs13CBlockLocatorEEbRKT_RT0_[_ZN3CDB4ReadISs13CBlockLocatorEEbRKT_RT0_]+0x460): undefined reference to `Dbt::~Dbt()'
build/db.o: In function `CDBEnv::CDBEnv()':
db.cpp:(.text+0x38f): undefined reference to `DbEnv::DbEnv(unsigned int)'
build/db.o: In function `CDBEnv::EnvShutdown()':
db.cpp:(.text+0x12fb): undefined reference to `DbEnv::close(unsigned int)'
...

From what I've read on the web I need to change the version of my compiler to fix this issue but nowhere does anybody say what version of compiler is required.  I'm currently running gcc 4.9.2.  Can anybody tell me what version of compiler they are using to successfully compile the unix version of the wallet?

Thanks in Advance,

mchrist152

Ok, it turns out that it wasn't the version of the compiler after all but the way I compiled Berkeley DB. I had to add the following arguments to the Berkeley DB configure command:
../dist/configure --enable-cxx --disable-shared --with-pic
That did the trick.  Seems like every time I post to this board I figure out the answer shortly there after.

So it built and it's running but it's not connecting to other nodes.  I'm not sure why.  It's running in a virtual machine so maybe there is something blocking it but other apps are having no problems.  Any ideas?
Post
Topic
Board Announcements (Altcoins)
Re: [ANN][MINT] New Wallet Released - Mandatory Upgrade / Hard fork Set for August 1
by
mchrist152
on 09/08/2015, 17:36:38 UTC
Would anybody be so kind as to help me with a mintcoin wallet compile issue?

I'm using the commandline to try and compile the unix version of the wallet on a Debian system.  Everything compiles but I'm running into the following linker errors:

...
build/moc_repairwalletdialog.o build/qrc_bitcoin.o    -L/usr/lib/x86_64-linux-gnu -lminiupnpc /home/mikech/github/Mintcoin-Desktop-Wallet/src/leveldb/libleveldb.a /home/mikech/github/Mintcoin-Desktop-Wallet/src/leveldb/libmemenv.a -lrt -lssl -lcrypto -ldb_cxx -lboost_system -lboost_filesystem -lboost_program_options -lboost_thread -lpthread -lQtGui -lQtNetwork -lQtCore
build/init.o: In function `bool CDB::Read(std::string const&, CBlockLocator&)':
init.cpp:(.text._ZN3CDB4ReadISs13CBlockLocatorEEbRKT_RT0_[_ZN3CDB4ReadISs13CBlockLocatorEEbRKT_RT0_]+0x122): undefined reference to `Dbt::Dbt(void*, unsigned int)'
init.cpp:(.text._ZN3CDB4ReadISs13CBlockLocatorEEbRKT_RT0_[_ZN3CDB4ReadISs13CBlockLocatorEEbRKT_RT0_]+0x12e): undefined reference to `Dbt::Dbt()'
init.cpp:(.text._ZN3CDB4ReadISs13CBlockLocatorEEbRKT_RT0_[_ZN3CDB4ReadISs13CBlockLocatorEEbRKT_RT0_]+0x394): undefined reference to `Dbt::~Dbt()'
init.cpp:(.text._ZN3CDB4ReadISs13CBlockLocatorEEbRKT_RT0_[_ZN3CDB4ReadISs13CBlockLocatorEEbRKT_RT0_]+0x3a0): undefined reference to `Dbt::~Dbt()'
init.cpp:(.text._ZN3CDB4ReadISs13CBlockLocatorEEbRKT_RT0_[_ZN3CDB4ReadISs13CBlockLocatorEEbRKT_RT0_]+0x454): undefined reference to `Dbt::~Dbt()'
init.cpp:(.text._ZN3CDB4ReadISs13CBlockLocatorEEbRKT_RT0_[_ZN3CDB4ReadISs13CBlockLocatorEEbRKT_RT0_]+0x460): undefined reference to `Dbt::~Dbt()'
build/db.o: In function `CDBEnv::CDBEnv()':
db.cpp:(.text+0x38f): undefined reference to `DbEnv::DbEnv(unsigned int)'
build/db.o: In function `CDBEnv::EnvShutdown()':
db.cpp:(.text+0x12fb): undefined reference to `DbEnv::close(unsigned int)'
...

From what I've read on the web I need to change the version of my compiler to fix this issue but nowhere does anybody say what version of compiler is required.  I'm currently running gcc 4.9.2.  Can anybody tell me what version of compiler they are using to successfully compile the unix version of the wallet?

Thanks in Advance,

mchrist152
Post
Topic
Board Announcements (Altcoins)
Re: [ANN][MINT] New Wallet Released - Mandatory Upgrade / Hard fork Set for August 1
by
mchrist152
on 24/07/2015, 04:06:12 UTC
Quote from: presstab on July 23, 2015, 09:02:23 PM
Quote from: Flyskyhigh on July 23, 2015, 08:42:30 PM
Your hunch was correct.... What does that mean?

Sorry I thought with all the links it was self explanatory. Removing the old irc code cleared up the virus warnings.

-press

So this was just unused code hanging around taking up space?  I wonder how much of that is in there?
Post
Topic
Board Announcements (Altcoins)
Re: [ANN][MINT] New Wallet Released - Mandatory Upgrade / Hard fork Set for August 1
by
mchrist152
on 23/07/2015, 13:58:26 UTC
Quote from: sambiohazard on July 23, 2015, 08:00:39 AM
Is there anyway around the false positive on some antiviruses? Other wise i have to move my mint to a web wallet or exchange or completely move out of mint while waiting for a good time to buy back when problem is solved. Is there a web wallet for mint where i can stake?

There is a work around, switch antivirus programs.  Microsoft security essentials works pretty well and is free.  Defender is good on Win8 or later.  Neither of these programs have a problem with mint and they are also pretty light on resources.
Post
Topic
Board Announcements (Altcoins)
Re: [ANN][MINT] New Wallet Released - Mandatory Upgrade / Hard fork Set for August 1
by
mchrist152
on 22/07/2015, 14:02:54 UTC
Quote from: presstab on July 21, 2015, 03:00:45 PM
If you guys find some commits or some suggestions to remove these warnings let me know. But I don't have time to do all the digging and work for you. I am not even official mintcoin win compiler guy, i just thought i would give it to you guys because its easy for me to do.

Isn't this really a problem with Kaspersky?  Maybe someone should contact the company and tell them they are giving false positives for mintcoin-qt.exe.  I bet they could at least whitelist it if we could convince them they are in error.

In the meantime, I am working on compiling the the wallet.  It's just taking a while since I had to setup a vmware instance of Debian, install QT-Creator and all the dependencies.  I'm now down to compiling the libraries and getting mingw to work.  I'll get there it's just going to take awhile.
Post
Topic
Board Announcements (Altcoins)
Re: [ANN][MINT] Mintcoin- V1.2 Win Released - Mandatory Upgrade - Need Linux & Mac
by
mchrist152
on 18/07/2015, 16:13:42 UTC
Quote from: presstab on July 18, 2015, 03:21:42 AM
I bumped it to 2.0.0.0 when I committed a few weeks ago since hard fork mean major version upgrade. Maybe should have communicated more clearly, but assumed everyone would have seen it there. I didn't upgrade the subversion because I typically never bother changing it.

If you all need it reversioned in a particular fashion just let me know and I will recompile upon cryptomommys approval.

One nice thing about updating the subversion is then one doesn't have to run the file to determine the version.  If it is easy, why not?
Post
Topic
Board Announcements (Altcoins)
Re: [ANN][MINT] Mintcoin- V1.2 Win Released - Mandatory Upgrade - Need Linux & Mac
by
mchrist152
on 18/07/2015, 03:31:23 UTC
Nice job presstab and whoever else contributed.  The new wallet rocks!  It runs on my old system where 1.17 and 1.14 were having problems.  It looks like you used a later version of QT-Creator.  Maybe that made a difference or maybe you did something else.  Anyway, thanks alot!

Oh, and best of all, I didn't have to download the whole blockchain again after the upgrade.
Post
Topic
Board Announcements (Altcoins)
Re: [ANN][MINT] Mintcoin Earth Friendly Lighting Fast 15% PoS - New Wallet Coming Up
by
mchrist152
on 17/07/2015, 14:27:24 UTC
Quote from: cryptomommy on July 16, 2015, 03:42:46 PM
Good Morning Everyone!

The wallets are complete however still need wallet compiler assistance for Windows, Mac and Linux - any takers?

Sure, I've been trying to compile 1.17 anyway so why not.  I've been trying with QT-Creator on windows but something tells me I'm going to have to switch to Linux.  I do have Debian system.  Can anybody tell me what version of QT-Creator to use?  Also, have any of the libraries been updated from what was used in 1.17?
Post
Topic
Board Announcements (Altcoins)
Re: [ANN][MINT] Mintcoin Earth Friendly Lighting Fast 15% PoS - New Wallet Coming Up
by
mchrist152
on 09/07/2015, 21:57:26 UTC
Quote from: mchrist152 on July 09, 2015, 06:16:59 PM
Does anybody know what versions of boost and openssl the 1.17 wallet was compiled with?

I think I found the answer:

OpenSSL      1.0.1b
Berkeley DB  4.8.30.NC
Boost        1.47.0
miniupnpc    1.6
Post
Topic
Board Announcements (Altcoins)
Re: [ANN][MINT] Mintcoin Earth Friendly Lighting Fast 15% PoS - New Wallet Coming Up
by
mchrist152
on 09/07/2015, 18:16:59 UTC
Does anybody know what versions of boost and openssl the 1.17 wallet was compiled with?
Post
Topic
Board Announcements (Altcoins)
Re: [ANN][MINT] Mintcoin Earth Friendly Lighting Fast 15% PoS - New Wallet Coming Up
by
mchrist152
on 03/07/2015, 20:47:16 UTC
Quote from: cryptomommy on July 03, 2015, 08:12:48 PM
Quote from: drakoin on July 03, 2015, 08:08:43 PM
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.
Post
Topic
Board Announcements (Altcoins)
Re: [ANN][MINT] Mintcoin Earth Friendly Lighting Fast 15% PoS Rewards - NewPodcast!
by
mchrist152
on 03/07/2015, 19:20:23 UTC
Quote from: Crestington on July 03, 2015, 06:00:03 PM
Quote from: presstab on July 03, 2015, 04:53:18 PM
Quote from: Derek492 on July 03, 2015, 04:46:36 PM
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 Tongue )

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.