Bitcoin Forum
June 28, 2017, 03:59:42 PM *
News: Latest stable version of Bitcoin Core: 0.14.2  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 [908] 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943 944 945 946 947 948 949 950 951 952 953 954 955 956 957 958 ... 1008 »
  Print  
Author Topic: [ANN][MINT] Mintcoin (POS) (5%) - New Wallet v2.0.2 released 3/1/16  (Read 1226334 times)
cryptomommy
Sr. Member
****
Offline Offline

Activity: 423


Nexus: Trust + Genesis = Much Love


View Profile
July 03, 2015, 03:19:54 PM
 #18141

I think 15/30 should work well. How much longer do you guys want to delay this? I have already started coding it in, but can hold off any final commits until there is a clear consesus about the hashdrift, interval, and fork time.

Please continue with 15/30 listening to the community this seems to be the most agreed upon. Once this is completed SupaSonic will implement the GUI modifications while I contact the exchanges with the raw wallet (only modification including the fork)

For the time please allow 30 days - this should give me plenty of time to work with the exchanges - they usually take 15 days or so to complete upgrades. I can also let them know when the expected fork will happen.

RoboGuy stuck in a network alert a few upgrades ago - please make sure to update the message to alert everyone when they open the wallet to upgrade to the newest version to help us get out the message.


Nexus: Taking Decentralization to a Whole New Realm
http://nexusearth.com/features.html
1498665582
Hero Member
*
Offline Offline

Posts: 1498665582

View Profile Personal Message (Offline)

Ignore
1498665582
Reply with quote  #2

1498665582
Report to moderator
1498665582
Hero Member
*
Offline Offline

Posts: 1498665582

View Profile Personal Message (Offline)

Ignore
1498665582
Reply with quote  #2

1498665582
Report to moderator
POLONIEX TRADING SIGNALS
+50% Profit and more via TELEGRAM
ALTCOINTRADER.CO
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1498665582
Hero Member
*
Offline Offline

Posts: 1498665582

View Profile Personal Message (Offline)

Ignore
1498665582
Reply with quote  #2

1498665582
Report to moderator
Derek492
Sr. Member
****
Offline Offline

Activity: 357



View Profile
July 03, 2015, 04:24:07 PM
 #18142

Is this code already implemented in other coins?

If yes, which?

PressTab has implemented this code in his own personal project HyperStake - another great coin making headway
Cool beans was referring to suprasonics statistics coding, not presstab timedrift coding.

Stop Mining.   Start Minting.   Mintcoin  [MINT]
5% annual minting reward. Mintcoins don't wear out like mining gear. They keep on minting!
Derek492
Sr. Member
****
Offline Offline

Activity: 357



View Profile
July 03, 2015, 04:26:38 PM
 #18143

I think 15/30 should work well. How much longer do you guys want to delay this? I have already started coding it in, but can hold off any final commits until there is a clear consesus about the hashdrift, interval, and fork time.

Please continue with 15/30 listening to the community this seems to be the most agreed upon. Once this is completed SupaSonic will implement the GUI modifications while I contact the exchanges with the raw wallet (only modification including the fork)

For the time please allow 30 days - this should give me plenty of time to work with the exchanges - they usually take 15 days or so to complete upgrades. I can also let them know when the expected fork will happen.

RoboGuy stuck in a network alert a few upgrades ago - please make sure to update the message to alert everyone when they open the wallet to upgrade to the newest version to help us get out the message.


Sounds good. I guess the higher the price goes the more secure it is too, by making it harder more consequential to attack, so that's a good thing.

Stop Mining.   Start Minting.   Mintcoin  [MINT]
5% annual minting reward. Mintcoins don't wear out like mining gear. They keep on minting!
cryptomommy
Sr. Member
****
Offline Offline

Activity: 423


Nexus: Trust + Genesis = Much Love


View Profile
July 03, 2015, 04:28:57 PM
 #18144

Cool beans was referring to suprasonics statistics coding, not presstab timedrift coding.

Dope! Gotcha

The statistics coding is something I have been trying to figure out for awhile now - If this does not interfere with the wallet itself I would love to test it out (especially if we can swap if need be back without a hard fork)

Nexus: Taking Decentralization to a Whole New Realm
http://nexusearth.com/features.html
Derek492
Sr. Member
****
Offline Offline

Activity: 357



View Profile
July 03, 2015, 04:46:36 PM
 #18145

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

Stop Mining.   Start Minting.   Mintcoin  [MINT]
5% annual minting reward. Mintcoins don't wear out like mining gear. They keep on minting!
cryptomommy
Sr. Member
****
Offline Offline

Activity: 423


Nexus: Trust + Genesis = Much Love


View Profile
July 03, 2015, 04:51:05 PM
 #18146

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.

Nexus: Taking Decentralization to a Whole New Realm
http://nexusearth.com/features.html
presstab
Legendary
*
Offline Offline

Activity: 1218


Pivx Core Developer - HyperStake Founder


View Profile
July 03, 2015, 04:53:18 PM
 #18147

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.


presstab's Block Explorer Service | Only $10/mo for most coins! | Richlist w/ Address Claim | Market Cap Charts | Stake Weight Tracking | PoS % Rate Tracking
PIVX - Private Instant Verified Tx | HyperStake - Fun & Easy High Reward Staking
Crestington
Hero Member
*****
Offline Offline

Activity: 784



View Profile
July 03, 2015, 06:00:03 PM
 #18148

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;
        }

PayCon: PV5JRYrQDuAnsKE7LN7PjCdHHAbj8gfSEx
My BTC address: 1jcXEw4v8DnMd9Ez6saYKxEpm1jXTTtEH
Curious about PayCon? Get your CON on!! [ANN] topic https://bitcointalk.org/index.php?topic=937480.0
Derek492
Sr. Member
****
Offline Offline

Activity: 357



View Profile
July 03, 2015, 06:53:04 PM
 #18149

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.



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

Stop Mining.   Start Minting.   Mintcoin  [MINT]
5% annual minting reward. Mintcoins don't wear out like mining gear. They keep on minting!
supasonic
Newbie
*
Offline Offline

Activity: 4


View Profile
July 03, 2015, 07:03:54 PM
 #18150

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.



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

Specific block. Estimated date.

MintCoin -  Mfz6nPPDYRE2qYBBRRFXE4QRX1Ahec2Eih
supasonic
Newbie
*
Offline Offline

Activity: 4


View Profile
July 03, 2015, 07:15:11 PM
 #18151

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.

MintCoin -  Mfz6nPPDYRE2qYBBRRFXE4QRX1Ahec2Eih
mchrist152
Newbie
*
Offline Offline

Activity: 21


View Profile
July 03, 2015, 07:20:23 PM
 #18152

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.
presstab
Legendary
*
Offline Offline

Activity: 1218


Pivx Core Developer - HyperStake Founder


View Profile
July 03, 2015, 07:34:12 PM
 #18153

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.



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's Block Explorer Service | Only $10/mo for most coins! | Richlist w/ Address Claim | Market Cap Charts | Stake Weight Tracking | PoS % Rate Tracking
PIVX - Private Instant Verified Tx | HyperStake - Fun & Easy High Reward Staking
presstab
Legendary
*
Offline Offline

Activity: 1218


Pivx Core Developer - HyperStake Founder


View Profile
July 03, 2015, 07:34:44 PM
 #18154

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.

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

presstab's Block Explorer Service | Only $10/mo for most coins! | Richlist w/ Address Claim | Market Cap Charts | Stake Weight Tracking | PoS % Rate Tracking
PIVX - Private Instant Verified Tx | HyperStake - Fun & Easy High Reward Staking
drakoin
Hero Member
*****
Offline Offline

Activity: 812

see my profile


View Profile
July 03, 2015, 08:08:43 PM
 #18155

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!

no sign of a signature
Crestington
Hero Member
*****
Offline Offline

Activity: 784



View Profile
July 03, 2015, 08:10:35 PM
 #18156

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.

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.

PayCon: PV5JRYrQDuAnsKE7LN7PjCdHHAbj8gfSEx
My BTC address: 1jcXEw4v8DnMd9Ez6saYKxEpm1jXTTtEH
Curious about PayCon? Get your CON on!! [ANN] topic https://bitcointalk.org/index.php?topic=937480.0
cryptomommy
Sr. Member
****
Offline Offline

Activity: 423


Nexus: Trust + Genesis = Much Love


View Profile
July 03, 2015, 08:12:48 PM
 #18157

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.

Nexus: Taking Decentralization to a Whole New Realm
http://nexusearth.com/features.html
Flyskyhigh
Sr. Member
****
Offline Offline

Activity: 292


Ezekiel 34:11, John 10:25-30


View Profile
July 03, 2015, 08:28:11 PM
 #18158

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.  Smiley

Sick of mining?  Start minting!  5% per year!  Mintcoin "MINT"
drakoin
Hero Member
*****
Offline Offline

Activity: 812

see my profile


View Profile
July 03, 2015, 08:38:25 PM
 #18159

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!


no sign of a signature
mchrist152
Newbie
*
Offline Offline

Activity: 21


View Profile
July 03, 2015, 08:47:16 PM
 #18160

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.
Pages: « 1 ... 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 [908] 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943 944 945 946 947 948 949 950 951 952 953 954 955 956 957 958 ... 1008 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!