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

[kiklo]

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 
_______________________________________________________________

 

[1713560258]

1713560258

[1713560258]

1713560258

[1713560258]

1713560258

[1713560258]

1713560258

[duplan]

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

[kiklo]

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://bitcointalk.org/index.php?topic=487814.msg10296134#msg10296134


 

[kiklo]

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 #

 

[duplan]

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://bitcointalk.org/index.php?topic=487814.msg10296134#msg10296134


 

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  

[Ricklosti]

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.

[cryptomommy]

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

[Ricklosti]

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.

[Ricklosti]

DC Charts for MINT

w/ Customizable indicators



http://dc-charts.com/chart_mint.php?ex=2&cu=0&tz=6&ar=1&re=0

[cryptomommy]

DC Charts for MINT

w/ Customizable indicators



http://dc-charts.com/chart_mint.php?ex=2&cu=0&tz=6&ar=1&re=0

Nice! Love it

[someguy4]

Could we have some details on the decided changes?

[coolbeans94]

Could we have some details on the decided changes?

This may sound like tech Jargon but I'll do my best to explain:

As far as I know, the only thing being changed that requires the hard fork is the time allowed for the search interval (hashdrift) and also the timedrift. This is basically a security update related to the possible vulnerability of a time-warp attack. Basically, all that is happening is that the time allowed for the hashdrift and the timedrift are being reduced. The hashdrift is being reduced to 15 seconds and the timedrift is being reduced to 30 seconds which is in line with mintcoin's 30 second block target. A timedrift that is further out in time than the block target presents a vulnerability. The vulnerability is a potential to trick the Mintcoin network into ever decreasing difficulty. This hard fork will make this impossible. The hashdrift (timestamp search interval) is being lowered to help prevent a surge in orphan blocks, as it is better to have the time of the hashdrift below the time of the timedrift. The hashdrift (timestamp search interval) helps the network know what time it is so that it can basically keep the ledger going on a continual time that everyone agrees on.

Specifically:
The hashdrift (timestamp search interval) is being reduced to 15 seconds.
The timedrift is being reduced to 30 seconds.

As far as Supasonic's changes, these are just some wallet GUI optimizations that don't require the hard fork, but are going to be included in it anyway, just to make the wallet more user-friendly.

I hope that helps explain. If anyone knows better, or wants to add to this, please do.   

[wdyer]

DC Charts for MINT

w/ Customizable indicators



http://dc-charts.com/chart_mint.php?ex=2&cu=0&tz=6&ar=1&re=0

Cool chart. Thank you that website is new to me 

[flipme]

Is there a normal torrent somewhere, or do I have to use this btsync crap to get to the bootstrap file?
I don't want that shit on my system.
I've been trying to sync this wallet now for more than a week, what a mess!

[MarSas]

Not at the moment. But there is also the option to uninstall the client after you've downloaded the blockchain.

[kamronk]

Hello everybody!

I'm pretty late on getting help on this, but has anyone seen this error before when starting up the mintcoin daemon

root@bigsmall:~/Mintcoin-Desktop-Wallet/src# ./mintcoind
mintcoind: main.cpp:2585: bool LoadBlockIndex(bool): Assertion `block.GetHash() == (!fTestNet ? hashGenesisBlock : hashGenesisBlockTestNet)' failed.
Aborted

Some notes to add to the context here:

I'm building the daemon on an ARM processor, and had to remove a number of arguments in the make files that pertained to i86 processors. The daemon built successfully after a number of error resolutions that most of which pertained to ARM processors.

Is there any other info I could provide on this? (OS = ubuntu 14.04, mintcoin source direct from github)

[searle421]

I don't know what you mean by "normal torrent" but here's the magnet addy for the b-chain magnet:?xt=urn:btih:4a6c6d7915fa212c09f9d39524bbaa7c046efda9&dn=mintcoin-blockchain-easter-2014.7z

[cryptomommy]

Mintcoin Fund Board Members Needed to complete USA Registration for Non-Profit Status. in list Discussion

"How many directors will serve on the Board of Directors?
Enter the number of regular directors who will serve, starting with the first annual Mintcoin Fund meeting. The number of directors cannot be less than three. This number does not need to be the same number as the initial directors named in the Articles of Incorporation. Next enter the term, in years, that each will serve. If staggered terms were established by the Articles, some of the initial directors will serve a shorter term."

Please let me know if you are interested in a long-term board position for Mintcoin Fund. As a board member we will vote on charities which we support and will be notified when funds transfer hands between the community and charity for which we are funding.

https://trello.com/c/SQzM3NZR/1-mintcoin-board-members-needed-to-complete-usa-registration-for-non-profit-status
Please PM me for a trello invite if interested and unable to access.

[someguy4]

Could we have some details on the decided changes?

This may sound like tech Jargon but I'll do my best to explain:

As far as I know, the only thing being changed that requires the hard fork is the time allowed for the search interval (hashdrift) and also the timedrift. This is basically a security update related to the possible vulnerability of a time-warp attack. Basically, all that is happening is that the time allowed for the hashdrift and the timedrift are being reduced. The hashdrift is being reduced to 15 seconds and the timedrift is being reduced to 30 seconds which is in line with mintcoin's 30 second block target. A timedrift that is further out in time than the block target presents a vulnerability. The vulnerability is a potential to trick the Mintcoin network into ever decreasing difficulty. This hard fork will make this impossible. The hashdrift (timestamp search interval) is being lowered to help prevent a surge in orphan blocks, as it is better to have the time of the hashdrift below the time of the timedrift. The hashdrift (timestamp search interval) helps the network know what time it is so that it can basically keep the ledger going on a continual time that everyone agrees on.

Specifically:
The hashdrift (timestamp search interval) is being reduced to 15 seconds.
The timedrift is being reduced to 30 seconds.

As far as Supasonic's changes, these are just some wallet GUI optimizations that don't require the hard fork, but are going to be included in it anyway, just to make the wallet more user-friendly.

I hope that helps explain. If anyone knows better, or wants to add to this, please do.  

Thanks that makes sense I think , I got a couple of things wrong on how I thought my p2p protocol worked (it actually uses the average time calculated between connected clients and removed outliers above a certain limit but not looked at it for like 14 months. it also had a different purpose than a coin and was designed more like bittorrent as a distributed database. Building 50 nodes in an L(1) configuration Vid on 1 computer using TCP average of 14 connections per client, 320 nodes in a least redundancy configuration=vid I'm sure there are some major flaws in security but I'm learning)
(in case anyone is interested)

[kiklo]

FYI:
Consider updating your subversion in this wallet release.
Sub-version is /MintCoin:0.7.2/ since the start last year, when you click on the node list in chainz ,  it shows all IP addresses by subver, so it will not separate the IPs by version, unless the subver is updated.
Protocol update to 6007 will only show the # on that protocol , not the IP address.
https://chainz.cryptoid.info/mint/#!network