Bitcoin Forum
October 18, 2017, 06:14:33 AM *
News: Latest stable version of Bitcoin Core: 0.15.0.1  [Torrent]. (New!)
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 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 959 960 961 962 963 964 965 [966] 967 968 969 970 971 972 973 974 975 976 977 978 979 980 981 982 983 984 985 986 987 988 989 990 991 992 993 994 995 996 997 998 999 1000 1001 1002 1003 1004 1005 1006 1007 1008 1009 1010 1011 1012 1013 »
  Print  
Author Topic: [ANN] [MINT] Mintcoin (POS / 5%) [NO ICO] [Fair distro, community maintained]  (Read 1293339 times)
nickenburg
Hero Member
*****
Offline Offline

Activity: 490


View Profile
March 03, 2016, 02:35:31 PM
 #19301

Guys do I need to download the 2.0.2 wallet?
Because when I start my wallet now it says:
Warning: checkpoint is to old. Wait for the blockchain to download or Contact developers.

So I Fully downloaded the blockchain and it still says the same.
Will the new wallet fix that or is something wrong?
1508307273
Hero Member
*
Offline Offline

Posts: 1508307273

View Profile Personal Message (Offline)

Ignore
1508307273
Reply with quote  #2

1508307273
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
sokol
Member
**
Offline Offline

Activity: 61


View Profile
March 03, 2016, 02:50:06 PM
 #19302

After updated my wallet on windows from v2.0.1 to 2.0.2 I have "error reading blkindex.dat"  Huh

Sounds like your datadir is corrupted... I would suggest downloading the bootstrap and replacing those files.

This likely happened either due to app crash, forcefully closing the app without letting it complete the exit process or a complete system crash

I downloaded the bootstrap from mincoint official and replaced data dir, and get some error  Sad

With v2.0.1 all OK
crzybilly
Sr. Member
****
Offline Offline

Activity: 409


View Profile
March 03, 2016, 02:52:11 PM
 #19303

Guys do I need to download the 2.0.2 wallet?
Because when I start my wallet now it says:
Warning: checkpoint is to old. Wait for the blockchain to download or Contact developers.

So I Fully downloaded the blockchain and it still says the same.
Will the new wallet fix that or is something wrong?


2.0.2 fixes that issue plus a few other issues
crzybilly
Sr. Member
****
Offline Offline

Activity: 409


View Profile
March 03, 2016, 02:53:07 PM
 #19304

After updated my wallet on windows from v2.0.1 to 2.0.2 I have "error reading blkindex.dat"  Huh

Sounds like your datadir is corrupted... I would suggest downloading the bootstrap and replacing those files.

This likely happened either due to app crash, forcefully closing the app without letting it complete the exit process or a complete system crash

I downloaded the bootstrap from mincoint official and replaced data dir, and get some error  Sad

With v2.0.1 all OK

I'll get my chain up-to-date again with 2.0.2 and upload bootstrap for you that should work exactly... there should be no reason that it continues to do that, because we didn't change bdb version.
BrotherJ
Full Member
***
Offline Offline

Activity: 216



View Profile
March 03, 2016, 09:53:27 PM
 #19305

After updated my wallet on windows from v2.0.1 to 2.0.2 I have "error reading blkindex.dat"  Huh

Sounds like your datadir is corrupted... I would suggest downloading the bootstrap and replacing those files.

This likely happened either due to app crash, forcefully closing the app without letting it complete the exit process or a complete system crash

I downloaded the bootstrap from mincoint official and replaced data dir, and get some error  Sad

With v2.0.1 all OK

I'm also having the same issue ("error reading blkindex.dat"). My 2.0.1 wallet is fully sync'ed to block #2371004 and has been working perfectly. I run it every day. I can tell you that in my appdata file there is no sub-file named blkindex.dat. Maybe this helps.

I believe the correct file name is "blk0001". At least that is what I have.

Ok, I just tried renaming this file "blkindex" but it still didn't help.

I wonder if something needs to be changed in the properties.

▓▓▓▓▓▓▓▓▓▓    ▶▶▶▶ Get Your Free Tokens Now ◀◀◀◀  First PoS Smart Contract Token
    PoSToken       Free Airdrop ●  No-ICO ●  100% Annual Interest First Year
▓▓▓▓▓▓▓▓▓▓    ANN ●  WebSite  ●  Twitter  ●  Slack  ●  Whitepaper
broken_pixel
Hero Member
*****
Offline Offline

Activity: 770



View Profile
March 03, 2016, 10:22:09 PM
 #19306

Just updated and get ("error reading blkindex.dat") also, version 2.0.1 worked fine.

GA-990FXA-UD5, 1x 7970L, 2x S1, AX1200i, RIVBE, 2x R290x, NEX1500, BTC: 1G9cQix8bMgh35MQ9wY3Rb9yNSSCtnoRmK, DGC: DFo9FcKYsutv9Vx5c5xUzkrt7VJdECZWTM, LTC: LaAN33aktPGaimN5ALL9kjHjuJekfmKfTh
crzybilly
Sr. Member
****
Offline Offline

Activity: 409


View Profile
March 03, 2016, 10:49:45 PM
 #19307


Guys please stick with 2.0.1 while I work with fuzzbawls to narrow down the issue.
deepcreek
Member
**
Offline Offline

Activity: 79


View Profile
March 03, 2016, 11:51:31 PM
 #19308

Updated mine today and everything looks to run smoothy.
kiklo
Legendary
*
Offline Offline

Activity: 1092



View Profile
March 04, 2016, 12:08:03 AM
 #19309

Updated mine today and everything looks to run smoothy.

Same here, but still too many orphans when trying to mint.


 Cool
Fuzzbawls
Hero Member
*****
Offline Offline

Activity: 740

★YoBit.Net★ 200+ Coins Exchange & Dice


View Profile
March 04, 2016, 12:21:02 AM
 #19310

Updated mine today and everything looks to run smoothy.

Same here, but still too many orphans when trying to mint.


 Cool

What kind of block sizes are you using? Smaller inputs generate weight at a much slower rate than larger inputs, which could indeed lead to excessive orphans.

kiklo
Legendary
*
Offline Offline

Activity: 1092



View Profile
March 04, 2016, 01:12:55 AM
 #19311

Updated mine today and everything looks to run smoothy.

Same here, but still too many orphans when trying to mint.


 Cool

What kind of block sizes are you using? Smaller inputs generate weight at a much slower rate than larger inputs, which could indeed lead to excessive orphans.

Blocks of 1 million, they mint with 1 confirmation and then fail to get the 2nd and become an orphan,
problem is it does it like 5 or more times before it is a success, try it with 2 different ISPs and PCs.

The problem first appeared after the last presstab update, so it is either being caused by the timedrift being so low or the code so mint does not stake the entire 60 seconds.
ZEIT adjusted our Time drift to a 1 minute max and we still stake the entire 60 seconds, Mint went down to a 30second time drift and does not stake the entire 60 seconds.
ZEIT is not seeing the multiple orphan issue like Mint , so it is one of those 2 changes that is causing all of the orphans in Mint.


 Cool
coolbeans94
Hero Member
*****
Offline Offline

Activity: 613


Mintcoin: Get some


View Profile
March 04, 2016, 02:05:52 AM
 #19312

MINT has just a 30 second block time, so how would increasing the drift time to 60 seconds be any more helpful here? There is nothing essentially wrong with orphans anyway, so guess I don't see why that's such a big deal. You might want to consolidate your 1 million coins into a single transaction, as that will revamp the weight for a single minting, so you will will mint more successfully, yet less often.

Does anyone have a screenshot of the new wallet? I am curious, did you guys manage to incorporate the change to the GUI so that is says "Minting" instead of "Stake"?

(1.) Moral happiness depends upon moral order.
(2.) Moral order depends upon the harmonious action of all our powers, as
individuals and as members of society.
crzybilly
Sr. Member
****
Offline Offline

Activity: 409


View Profile
March 04, 2016, 02:13:09 AM
 #19313

MINT has just a 30 second block time, so how would increasing the drift time to 60 seconds be any more helpful here? There is nothing essentially wrong with orphans anyway, so guess I don't see why that's such a big deal. You might want to consolidate your 1 million coins into a single transaction, as that will revamp the weight for a single minting, so you will will mint more successfully, yet less often.

Does anyone have a screenshot of the new wallet? I am curious, did you guys manage to incorporate the change to the GUI so that is says "Minting" instead of "Stake"?

design hasn't gone through yet... we are testing the code side of it first... after code passes alpha, then the design gets put in
crzybilly
Sr. Member
****
Offline Offline

Activity: 409


View Profile
March 04, 2016, 02:21:32 AM
 #19314


Windows Users... We have fixed the issue in 2.0.2 that was causing the error with blkindex.dat

http://www.mediafire.com/download/ci6ve0d1y4yp1d0/MintCoin-Qt.zip
kiklo
Legendary
*
Offline Offline

Activity: 1092



View Profile
March 04, 2016, 03:20:39 AM
 #19315

MINT has just a 30 second block time, so how would increasing the drift time to 60 seconds be any more helpful here? There is nothing essentially wrong with orphans anyway, so guess I don't see why that's such a big deal. You might want to consolidate your 1 million coins into a single transaction, as that will revamp the weight for a single minting, so you will will mint more successfully, yet less often.

Does anyone have a screenshot of the new wallet? I am curious, did you guys manage to incorporate the change to the GUI so that is says "Minting" instead of "Stake"?

I use alot of wallets, it is a problem and should be fixed.
I don't know for certain if it is the 30 second time drift setting or the not staking for the full 60 seconds.
But I am 100% certain it is one of them, since Mint staked Normally before that update.
It is not a weight problem, because it does stake , but it fails to get that 2nd confirmation so much it is a pain in the butt , and should be corrected.

Make a version or give me a way that makes Mint stake for the full 60 seconds like it did before, if it works normally, then than is the problem , if it still fails then the problem is the time drift at 30 seconds is too short and needs to be increased to 60 seconds.

 Cool
BrotherJ
Full Member
***
Offline Offline

Activity: 216



View Profile
March 04, 2016, 04:01:21 AM
 #19316


Thanks. Works perfect.

▓▓▓▓▓▓▓▓▓▓    ▶▶▶▶ Get Your Free Tokens Now ◀◀◀◀  First PoS Smart Contract Token
    PoSToken       Free Airdrop ●  No-ICO ●  100% Annual Interest First Year
▓▓▓▓▓▓▓▓▓▓    ANN ●  WebSite  ●  Twitter  ●  Slack  ●  Whitepaper
deepcreek
Member
**
Offline Offline

Activity: 79


View Profile
March 04, 2016, 05:24:31 AM
 #19317

There are also some other wallets that i know of which have a option to show/hide orphan blocks. Whilst this will not solve the problem it will at least clean up the transaction screen.
Maybe a idea to integrate in the next update?

Deepcreek.
Fuzzbawls
Hero Member
*****
Offline Offline

Activity: 740

★YoBit.Net★ 200+ Coins Exchange & Dice


View Profile
March 04, 2016, 06:06:39 AM
 #19318

MINT has just a 30 second block time, so how would increasing the drift time to 60 seconds be any more helpful here? There is nothing essentially wrong with orphans anyway, so guess I don't see why that's such a big deal. You might want to consolidate your 1 million coins into a single transaction, as that will revamp the weight for a single minting, so you will will mint more successfully, yet less often.

Does anyone have a screenshot of the new wallet? I am curious, did you guys manage to incorporate the change to the GUI so that is says "Minting" instead of "Stake"?

I use alot of wallets, it is a problem and should be fixed.
I don't know for certain if it is the 30 second time drift setting or the not staking for the full 60 seconds.
But I am 100% certain it is one of them, since Mint staked Normally before that update.
It is not a weight problem, because it does stake , but it fails to get that 2nd confirmation so much it is a pain in the butt , and should be corrected.

Make a version or give me a way that makes Mint stake for the full 60 seconds like it did before, if it works normally, then than is the problem , if it still fails then the problem is the time drift at 30 seconds is too short and needs to be increased to 60 seconds.

 Cool

Pretty sure you are getting confused between the various blockchains here...there is no such thing a "the full 60 seconds" with mint as the block time is only 30 seconds. Trying to stake at greater intervals would only INCREASE orphan rate (all other things being equal).

For comparison's sake, most of my blocks are at or above 200k and my orphan stake rate is very low

kiklo
Legendary
*
Offline Offline

Activity: 1092



View Profile
March 04, 2016, 06:33:45 AM
 #19319

Pretty sure you are getting confused between the various blockchains here...there is no such thing a "the full 60 seconds" with mint as the block time is only 30 seconds. Trying to stake at greater intervals would only INCREASE orphan rate (all other things being equal).

For comparison's sake, most of my blocks are at or above 200k and my orphan stake rate is very low

I am talking about the code that you explained to me was similar to Presstab litestake, but you said did not qualify as litestake.
-        static int nMaxStakeSearchInterval = 60;
+        static int nMaxStakeSearchInterval = 15;
That is one change.

The Timedrift was the other change.
My blocks are 1 million a piece and never had this many orphans until after the presstab update for time drift to a 30 second window,
and just for FYI, even Presstab coins like hyperstake never went below 1 minute for their time drift.
Mint Community voted and presstab complied to the 30 second window.

But one of those 2 changes is causing the orphan increase.

If no one will look into fixing it ,
Ok, your choice , but I am informing you it is a problem and I personally would like to see it fixed.


 Cool
Fuzzbawls
Hero Member
*****
Offline Offline

Activity: 740

★YoBit.Net★ 200+ Coins Exchange & Dice


View Profile
March 04, 2016, 06:49:57 AM
 #19320

Pretty sure you are getting confused between the various blockchains here...there is no such thing a "the full 60 seconds" with mint as the block time is only 30 seconds. Trying to stake at greater intervals would only INCREASE orphan rate (all other things being equal).

For comparison's sake, most of my blocks are at or above 200k and my orphan stake rate is very low

I am talking about the code that you explained to me was similar to Presstab litestake, but you said did not qualify as litestake.
That is one change.

The Timedrift was the other change.
My blocks are 1 million a piece and never had this many orphans until after the presstab update for time drift to a 30 second window,
and just for FYI, even Presstab coins like hyperstake never went below 1 minute for their time drift.
Mint Community voted and presstab complied to the 30 second window.

But one of those 2 changes is causing the orphan increase.

If no one will look into fixing it ,
Ok, your choice , but I am informing you it is a problem and I personally would like to see it fixed.


 Cool

FYI:
Somewhere in the Commits on Aug 1, 2015 cause the orphan increase.
https://github.com/MintcoinCommunity/Mintcoin-Desktop-Wallet/commits/master

Litestake is a method of keeping tabs on which input has tried to stake and when, and ensures that stake attempts don't bog down the system by needlessly trying to stake when there isn't much possibility of actually staking a successful block....MINT doesn't have this.


Presstab coins (HYP/XRA) use a longer search interval because they can...he has NEVER used a 30s block time target so his search interval has much more leeway to it. Think of it this way: a search interval LONGER than the block time can cause a myriad of issues and leaves the network open to attack vectors. With MINT's 30s block time, the maximum search interval is also 30s.

Your personal results with orphans may indeed show an increase, rather, a variance, but the Aug hardfork has statistically reduced the number of orphans on the blockchain by quite a bit.

Pages: « 1 ... 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 959 960 961 962 963 964 965 [966] 967 968 969 970 971 972 973 974 975 976 977 978 979 980 981 982 983 984 985 986 987 988 989 990 991 992 993 994 995 996 997 998 999 1000 1001 1002 1003 1004 1005 1006 1007 1008 1009 1010 1011 1012 1013 »
  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!