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

[broken_pixel]

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

[1713517730]

1713517730

[1713517730]

1713517730

[crzybilly]

Guys please stick with 2.0.1 while I work with fuzzbawls to narrow down the issue.

[deepcreek]

Updated mine today and everything looks to run smoothy.

[kiklo]

Updated mine today and everything looks to run smoothy.

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


 

[Fuzzbawls]

Updated mine today and everything looks to run smoothy.

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


 

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]

Updated mine today and everything looks to run smoothy.

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


 

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.


 

[coolbeans94]

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"?

[crzybilly]

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]

Guys please stick with 2.0.1 while I work with fuzzbawls to narrow down the issue.

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]

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.

 

[BrotherJ]

Guys please stick with 2.0.1 while I work with fuzzbawls to narrow down the issue.

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

Thanks. Works perfect.

[deepcreek]

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]

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.

 

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]

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.


 

[Fuzzbawls]

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.


 

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.

[kiklo]

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.

What I am telling you is ZEIT went to a 1 minute timedrift and DID NOT change static int nMaxStakeSearchInterval to 15;
and our Staking is completely the same as before we updated for the timedrift, MINT Staking is NOT the same as before those updates, it is Worse.
I informed you when the problem started, the rest is up to you.


 

[MintyAllDay]

MINT Staking is NOT the same as before those updates, it is Worse.

Do you think the orphans chart historical data at https://chainz.cryptoid.info/mint/#!extraction backs up this statement?

[Flyskyhigh]

MINT Staking is NOT the same as before those updates, it is Worse.

Do you think the orphans chart historical data at https://chainz.cryptoid.info/mint/#!extraction backs up this statement?

Well to be fair, that chart only shows the last 1000 blocks, which is about 8 days worth of time.  it would be nice to see a bigger history.

Isn't the reason ZEIT can get away with a longer time is because their block time is longer than MINT's? With the presstab update, yes, I think the orphans went up a little bit like you were saying, from like 300 per day to 600 or so, but the security benefits outway the cost of performance due to orphans, imo. Security is number 1 priority, because if that is broken you don't even have a coin at all, so orphans are secondary concern. MINT is definitely pushing the limits with the 30 second blocks but it seems to perform well overall. This just shows why we can't just do 1 second blocks...some things need time to work right.

[MintyAllDay]

Well to be fair, that chart only shows the last 1000 blocks, which is about 8 days worth of time.  it would be nice to see a bigger history.

I'm seeing almost a years worth of orphan data.  Do you see the dates on the infographic?

[kiklo]

MINT Staking is NOT the same as before those updates, it is Worse.

Do you think the orphans chart historical data at https://chainz.cryptoid.info/mint/#!extraction backs up this statement?

Compare
https://chainz.cryptoid.info/zeit/#!extraction