Author

Topic: [ANN] [MINT] Mintcoin (POS / 5%) [NO ICO] [Fair distro, community maintained] - page 128. (Read 1369788 times)

member
Activity: 71
Merit: 10
member
Activity: 71
Merit: 10
When is the hard fork wallet released? People need time to update their wallets in order to ensure a smooth transition when the fork happens. A lot of people going on vacation this time of year may be gone for several weeks and not be able to update. Also Mintcoin blocks tend to be faster than 30 seconds, if it is based on a certain block, make sure there is plenty of time, we don't want a surprise where the fork happens a week early or something and it messes things up. I'm sure everything will be fine. Just saying, I would personally like us to have ample time to make the switch. We are now less than 3 weeks from August 1. Thank you for all for your efforts on this coin. The future of this coin looks very promising. Thanks.

Wallets are ready to be compiled now - exchanges have already been alerted.

https://github.com/MintcoinCommunity/Mintcoin-Desktop-Wallet

Currently we are looking for Mac and Linux

Thanks.

I just clicked the link and was scrolling down the page and the READ ME looks like some of the information needs to be updated.
sr. member
Activity: 425
Merit: 250
When is the hard fork wallet released? People need time to update their wallets in order to ensure a smooth transition when the fork happens. A lot of people going on vacation this time of year may be gone for several weeks and not be able to update. Also Mintcoin blocks tend to be faster than 30 seconds, if it is based on a certain block, make sure there is plenty of time, we don't want a surprise where the fork happens a week early or something and it messes things up. I'm sure everything will be fine. Just saying, I would personally like us to have ample time to make the switch. We are now less than 3 weeks from August 1. Thank you for all for your efforts on this coin. The future of this coin looks very promising. Thanks.

Wallets are ready to be compiled now - exchanges have already been alerted.

https://github.com/MintcoinCommunity/Mintcoin-Desktop-Wallet

Currently we are looking for Mac and Linux
member
Activity: 71
Merit: 10
When is the hard fork wallet released? People need time to update their wallets in order to ensure a smooth transition when the fork happens. A lot of people going on vacation this time of year may be gone for several weeks and not be able to update. Also Mintcoin blocks tend to be faster than 30 seconds, if it is based on a certain block, make sure there is plenty of time, we don't want a surprise where the fork happens a week early or something and it messes things up. I'm sure everything will be fine. Just saying, I would personally like us to have ample time to make the switch. We are now less than 3 weeks from August 1. Thank you for all for your efforts on this coin. The future of this coin looks very promising. Thanks.
sr. member
Activity: 269
Merit: 252
I have a lot of rejected mint attempts but some get through ;
I wonder if this will improve in the next update and hardfork .
I'm still minting but it looks not efficient with so many rejects


Easy way to increase your chance of minting, is to combine blocks after they have minted.
The more mint per block the higher your block's weight , highest weight wins the right to stake.
CoinAge also has an effect on the block weight.

Here a link to Zeit coin control info should be close enough to mint for it to help you.
https://bitcointalksearch.org/topic/m.10296134


 Cool

Thanks kiklo , I wasn't aware of this , I will look into it , but I already see I have always many thousand confirmations per block that worked , and I don't move my coins around , not trading at all , so the coinage is max or on its way to for the new ones … ballin' on the MintCoin  Roll Eyes
legendary
Activity: 1092
Merit: 1000
FYI:  Mint already has orphan issues, they are just not noticed as much, due to the fact that so few are staking 24x7 .  For example at the moment only 3.2% of coin are staking, so your orphan rate is lower.
Your staking rate changes daily and on days where you have over 10% staking your Orphan rate is higher.
Easy test , start a new mint wallet and sync it from scratch when your staking rate is higher, you will notice it freeze up on blocks during the sync, check the debug.log file and you will see the orphan problem.

That's strange. Whenever I have looked over the network, it always seemed to me that during the times of highest difficulty, and highest staking rate, the orphans rate spiked down to the fewest orphans.


This is what I mean:



At this time, the it is up to 16% and the orphan rate chart is spiked down. Seems to me to be opposite of what you were saying kiklo. Just wanted to paint a visual.

Just checked the Updated Explorer for July 10,
See with 2 address competing your orphan rate is higher even on the block explorer.
Fyi hold the mouse at the end of the line and it shows the exact #

 Cool
legendary
Activity: 1092
Merit: 1000
I have a lot of rejected mint attempts but some get through ;
I wonder if this will improve in the next update and hardfork .
I'm still minting but it looks not efficient with so many rejects


Easy way to increase your chance of minting, is to combine blocks after they have minted.
The more mint per block the higher your block's weight , highest weight wins the right to stake.
CoinAge also has an effect on the block weight.

Here a link to Zeit coin control info should be close enough to mint for it to help you.
https://bitcointalksearch.org/topic/m.10296134


 Cool
sr. member
Activity: 269
Merit: 252
I have a lot of rejected mint attempts but some get through ;
I wonder if this will improve in the next update and hardfork .
I'm still minting but it looks not efficient with so many rejects
legendary
Activity: 1092
Merit: 1000
Even thru the Block explorer is showing low orphans,
Start a new Mintcoin wallet install and you will see the orphans that I am talking about,
I just started one and let it run for 15 minutes , here is some of the debug.log from a fresh install less then 15 minutes old.
___________________________________________________________________________
ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block 61912796db798a1d7e17ffd170e3b3e040a664a9821d04f7e2f3ce85f1a2afca
received block 35006178714cf1c4a467
ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block 35006178714cf1c4a4678a95b446e76b27b88e50b2d459926fabd7b9ce16269b
received block 339c4af7f735fbacc9cf
ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block 339c4af7f735fbacc9cf258c89493d9313a122f9d46e84f371ed67208b7cc204
received block 0000000000db56cbec1a
ProcessBlock: ORPHAN BLOCK, prev=00000000078cbd2d9d65
received block 0000000009970bb5b8c4
ProcessBlock: ORPHAN BLOCK, prev=0000000000db56cbec1a
received block 0000000004d2ddaf9ad1
ProcessBlock: ORPHAN BLOCK, prev=0000000009970bb5b8c4
received block 0000000000fd1e5bd562
ProcessBlock: ORPHAN BLOCK, prev=0000000004d2ddaf9ad1
received block 000000000a89810157a1
ProcessBlock: ORPHAN BLOCK, prev=0000000000fd1e5bd562
received block 0000000009c17a761921
ProcessBlock: ORPHAN BLOCK, prev=000000000a89810157a1
received block 000000000d90d112d4fe
ProcessBlock: ORPHAN BLOCK, prev=0000000009c17a761921
received block 0000000006853c3612de
ProcessBlock: ORPHAN BLOCK, prev=000000000d90d112d4fe
received block 00000000041d5a017c3e
ProcessBlock: ORPHAN BLOCK, prev=0000000006853c3612de
received block 000000000393b5764dd2
ProcessBlock: ORPHAN BLOCK, prev=00000000041d5a017c3e
received block 0000000004226330e056
ProcessBlock: ORPHAN BLOCK, prev=000000000393b5764dd2
received block 0000000004650d1f0e33
ProcessBlock: ORPHAN BLOCK, prev=0000000004226330e056
received block 0000000002da56ce955c
ProcessBlock: ORPHAN BLOCK, prev=0000000004650d1f0e33
received block 0000000009827d996b4c
ProcessBlock: ORPHAN BLOCK, prev=0000000002da56ce955c
received block 000000000083db7b5c63
ProcessBlock: ORPHAN BLOCK, prev=0000000009827d996b4c
received block 000000000211ee390be4
ProcessBlock: ORPHAN BLOCK, prev=000000000083db7b5c63
received block 00000000013f2a3054b5
ProcessBlock: ORPHAN BLOCK, prev=000000000211ee390be4
received block 0000000003b4ef496a79
ProcessBlock: ORPHAN BLOCK, prev=00000000013f2a3054b5
received block 00000000090637db8c17
ProcessBlock: ORPHAN BLOCK, prev=0000000003b4ef496a79
received block 000000000625a02680e9
ProcessBlock: ORPHAN BLOCK, prev=00000000090637db8c17
received block 000000000a83cbd51a28
ProcessBlock: ORPHAN BLOCK, prev=000000000625a02680e9
received block 0000000003cfaf38cf47
ProcessBlock: ORPHAN BLOCK, prev=000000000a83cbd51a28
received block 00000000090d83016628
ProcessBlock: ORPHAN BLOCK, prev=0000000003cfaf38cf47
received block 0000000007bd925d41a6
ProcessBlock: ORPHAN BLOCK, prev=00000000090d83016628
received block 0000000003c2327b92a0
ProcessBlock: ORPHAN BLOCK, prev=0000000007bd925d41a6
received block 0000000005bf93463dd1
ProcessBlock: ORPHAN BLOCK, prev=0000000003c2327b92a0
received block 0000000003b43d4e37d3
ProcessBlock: ORPHAN BLOCK, prev=0000000005bf93463dd1
received block 0000000003e35a59df60
ProcessBlock: ORPHAN BLOCK, prev=0000000003b43d4e37d3
received block 0000000001d4389fe306
ProcessBlock: ORPHAN BLOCK, prev=0000000003e35a59df60
received block 000000000149297ff1d3
ProcessBlock: ORPHAN BLOCK, prev=0000000001d4389fe306
received block 00000000061385b81ec2
ProcessBlock: ORPHAN BLOCK, prev=000000000149297ff1d3
received block 0000000002ef1e85d250
ProcessBlock: ORPHAN BLOCK, prev=00000000061385b81ec2
received block 00000000014a3f486bc5
ProcessBlock: ORPHAN BLOCK, prev=0000000002ef1e85d250
received block 000000000bd7c6c08260
ProcessBlock: ORPHAN BLOCK, prev=00000000014a3f486bc5
received block 000000000452d6cece4a
ProcessBlock: ORPHAN BLOCK, prev=000000000bd7c6c08260
received block 0000000000c4acb3b7f0
ProcessBlock: ORPHAN BLOCK, prev=000000000452d6cece4a
received block 0000000006ab6460e183
ProcessBlock: ORPHAN BLOCK, prev=0000000000c4acb3b7f0
received block 00000000005c993044c4
ProcessBlock: ORPHAN BLOCK, prev=0000000006ab6460e183
received block 000000000381e1af6b68
ProcessBlock: ORPHAN BLOCK, prev=00000000005c993044c4
received block 000000000012d2d3279a
ProcessBlock: ORPHAN BLOCK, prev=000000000381e1af6b68
received block 00000000014fb00438f2
ProcessBlock: ORPHAN BLOCK, prev=000000000012d2d3279a
received block 0000000005b4749be806
ProcessBlock: ORPHAN BLOCK, prev=00000000014fb00438f2
received block 000000000108f0c3b690
ProcessBlock: ORPHAN BLOCK, prev=0000000005b4749be806
received block 00000000032b01a8bd27
ProcessBlock: ORPHAN BLOCK, prev=000000000108f0c3b690
received block 00000000079ede07db8d
ProcessBlock: ORPHAN BLOCK, prev=00000000032b01a8bd27
received block 00000000057a1ea15cb2
ProcessBlock: ORPHAN BLOCK, prev=00000000079ede07db8d
received block 000000000551c5f0f4ce
ProcessBlock: ORPHAN BLOCK, prev=00000000057a1ea15cb2
received block 0000000008a1fdc1bf62
ProcessBlock: ORPHAN BLOCK, prev=000000000551c5f0f4ce
received block 0000000005f7786e205d
ProcessBlock: ORPHAN BLOCK, prev=0000000008a1fdc1bf62
received block 000000000b43585bb531
ProcessBlock: ORPHAN BLOCK, prev=0000000005f7786e205d
received block 000000000322d03bd3f5
ProcessBlock: ORPHAN BLOCK, prev=000000000b43585bb531
received block 00000000000d18791b57
ProcessBlock: ORPHAN BLOCK, prev=000000000322d03bd3f5
received block 0000000000654a00701e
ProcessBlock: ORPHAN BLOCK, prev=00000000000d18791b57
received block 0000000005ace68f6848
ProcessBlock: ORPHAN BLOCK, prev=0000000000654a00701e
received block 0000000008dfbe398748
ProcessBlock: ORPHAN BLOCK, prev=0000000005ace68f6848
received block 00000000053a73612a6d
ProcessBlock: ORPHAN BLOCK, prev=0000000008dfbe398748
received block 0000000003e4658df67c
ProcessBlock: ORPHAN BLOCK, prev=00000000053a73612a6d
received block 0000000000f867bcd180
ProcessBlock: ORPHAN BLOCK, prev=0000000003e4658df67c
received block 00000000059a94639849
ProcessBlock: ORPHAN BLOCK, prev=0000000000f867bcd180
received block 0000000001e16951dd3a
ProcessBlock: ORPHAN BLOCK, prev=00000000059a94639849
received block 00000000021e238acc32
ProcessBlock: ORPHAN BLOCK, prev=0000000001e16951dd3a
received block 00000000013a85c04888
ProcessBlock: ORPHAN BLOCK, prev=00000000021e238acc32
received block 000000000491b0f43a3c
ProcessBlock: ORPHAN BLOCK, prev=00000000013a85c04888
received block 0000000003b46ea7ebea
ProcessBlock: ORPHAN BLOCK, prev=000000000491b0f43a3c
received block 0000000002da8f2e11d8
ProcessBlock: ORPHAN BLOCK, prev=0000000003b46ea7ebea
received block 00000000033898e7ae93
ProcessBlock: ORPHAN BLOCK, prev=0000000002da8f2e11d8
received block 0000000006af099c9e52
ProcessBlock: ORPHAN BLOCK, prev=00000000033898e7ae93
received block 0000000004bb8841e1b3
ProcessBlock: ORPHAN BLOCK, prev=0000000006af099c9e52
received block 00000000007171ecf7f6
ProcessBlock: ORPHAN BLOCK, prev=0000000004bb8841e1b3
received block 0000000005f1d313ef1e
ProcessBlock: ORPHAN BLOCK, prev=00000000007171ecf7f6
received block 0000000002eb49934aa8
ProcessBlock: ORPHAN BLOCK, prev=0000000005f1d313ef1e
received block 0000000006f8210d8173
ProcessBlock: ORPHAN BLOCK, prev=0000000002eb49934aa8 
_______________________________________________________________

 Cool
legendary
Activity: 1092
Merit: 1000
Ok , I'll bite

You do realize that currently most of the staking is 1 guy which is why your orphans are lower.
Not really a lot of competition to orphan at the moment
Staking Addresses
1   MpKoNedH... (Rich #4)      33 %   25.6 %
2   MboLySzh... (Rich #3)      11 %   8.7 %
3   MbaN4rfh... (Rich #216)   8 %   4.4 %
4   Mg5wXJ6g... (Rich #5)      5 %   15.0 %
5   MYarRNRW... (Rich #2)      5 %   8.9 %

https://chainz.cryptoid.info/mint/address.dws?MpKoNedHje6reWCsgF6ELgyeVhSsPup6si.htm

 Cool

hero member
Activity: 613
Merit: 500
Mintcoin: Get some
FYI:  Mint already has orphan issues, they are just not noticed as much, due to the fact that so few are staking 24x7 .  For example at the moment only 3.2% of coin are staking, so your orphan rate is lower.
Your staking rate changes daily and on days where you have over 10% staking your Orphan rate is higher.
Easy test , start a new mint wallet and sync it from scratch when your staking rate is higher, you will notice it freeze up on blocks during the sync, check the debug.log file and you will see the orphan problem.

That's strange. Whenever I have looked over the network, it always seemed to me that during the times of highest difficulty, and highest staking rate, the orphans rate spiked down to the fewest orphans.


This is what I mean:



At this time, the it is up to 16% and the orphan rate chart is spiked down. Seems to me to be opposite of what you were saying kiklo. Just wanted to paint a visual.
sr. member
Activity: 356
Merit: 250
We have come a long way. More to come. Patience.


Right now, We really need to make this mandatory wallet upgrade. Hopefully we can get the fork version released asap so we can get as many people as possible switched over as soon as possible. This will help ensure a smooth transition.

I am really looking forward to it, and also having it behind us.  The upgrade will make mintcoin even more secure, which translates to more safekeeping and trust for holding bigger sums, which means higher prices to come, even vs Bitcoin.
sr. member
Activity: 269
Merit: 252
As soon as we add some markets (real …  Cool ) MintCoin will gain much more traction and appreciation . Soup is heating up already …   Roll Eyes
hero member
Activity: 611
Merit: 500
Anglo Saxon Crypto Enthusiast
Mintcoin has recovered well after a flurry and is trending upward the past month, US Dollar chart from www.coingecko.com



vs Bitcoin, The lean time at single digit SAT figures is over, settling in nicely around 40 right now on Cryptsy.



newbie
Activity: 23
Merit: 0
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
newbie
Activity: 23
Merit: 0
Does anybody know what versions of boost and openssl the 1.17 wallet was compiled with?
sr. member
Activity: 275
Merit: 250
Is there a blockchain source?, I'm having trouble downloading via the qt wallet.
I've just spent 3 days downloading and it has corrupted at 80% (again) maybe due to windows vista 32bit?

Make your life easier by using the bootstrap link from http://www.mintcoinofficial.com/ Wink



Thanks, thought I btsnyc would not run on vista 32 bit. I used my mac and moved the blockchain over.
Now all sync'd up.
sr. member
Activity: 425
Merit: 250
How is progress on the new wallet coming along?


Good - the fork version is ready for release to the exchanges - SupaSonic should have the other changes completed by the weeks end.

Stay tuned!
sr. member
Activity: 356
Merit: 250
How is progress on the new wallet coming along?
sr. member
Activity: 425
Merit: 250
cryptomommy , do You think we can implement this technology into MINT and be the first crypto who does ?
http://cointelegraph.com/news/114628/worlds-1st-sqrl-login-making-keyloggers-trackers-obsolete

That's pretty cool actually Smiley

I will put it up for future discussion. Thanks!
Jump to: