Oh! no sync issue.
Topic: [ANN] [MINT] Mintcoin (POS / 5%) [NO ICO] [Fair distro, community maintained] - page 416. (Read 1369778 times)
April 05, 2014, 07:26:24 PM
My wallet has been minting like crazy today, so far my wallet has minted 3,782 baby Mints.
Oh! no sync issue.
Oh! no sync issue.
April 05, 2014, 07:17:46 PM
Looks like some people did not upgrade to the new version and created a fork...
I sync'ed fine, no issues.
If you can't sync, make sure you are using V1.7 (the latest), and using following addnodes (from my peers)
Quote
addnode=82.73.249.168
addnode=173.69.49.106
addnode=82.131.33.87
addnode=96.244.241.62
addnode=79.103.60.211
addnode=115.187.228.119
addnode=93.103.143.167
addnode=71.204.235.217
addnode=50.171.251.116
addnode=65.25.244.83
addnode=76.91.118.4
addnode=91.61.40.108
addnode=98.177.158.203
addnode=98.207.109.245
addnode=75.174.4.1
addnode=99.245.184.159
addnode=78.83.27.181
addnode=96.18.173.160
addnode=118.123.116.219
addnode=173.26.106.194
addnode=82.233.163.250
addnode=177.140.202.7
addnode=97.81.64.44
addnode=79.166.77.203
addnode=68.145.81.59
addnode=181.165.200.142
addnode=173.69.49.106
addnode=82.131.33.87
addnode=96.244.241.62
addnode=79.103.60.211
addnode=115.187.228.119
addnode=93.103.143.167
addnode=71.204.235.217
addnode=50.171.251.116
addnode=65.25.244.83
addnode=76.91.118.4
addnode=91.61.40.108
addnode=98.177.158.203
addnode=98.207.109.245
addnode=75.174.4.1
addnode=99.245.184.159
addnode=78.83.27.181
addnode=96.18.173.160
addnode=118.123.116.219
addnode=173.26.106.194
addnode=82.233.163.250
addnode=177.140.202.7
addnode=97.81.64.44
addnode=79.166.77.203
addnode=68.145.81.59
addnode=181.165.200.142
If after all these, you still see out of sync with some 300 blocks to catch up, don't worry, you are fine, just leave the client there. You can do send/receive all the transaction ok. It may take a little time for it to display the in sync.
Thanks. I am in sync now. Great!
Those who don't upgrade will waste all their pos blocks. All their pos blocks on the old chain will become orphans, and their wallet will be out of sync
April 05, 2014, 07:17:13 PM
upgrade to V1.7 please http://mintcoin.cc/download-wallet/
If you have upgraded after block 220000, you need to sync from scratch (that is delete all the file EXCEPT the wallet.dat from %appdata% dir, and then start the client to sync)
Then leave your wallet open.
If you have upgraded after block 220000, you need to sync from scratch (that is delete all the file EXCEPT the wallet.dat from %appdata% dir, and then start the client to sync)
Then leave your wallet open.
April 05, 2014, 07:14:55 PM
Don't upgrade guys until he tells us what he's spent the premine on.
We've got a right to know how much of the community premine has been spent and on what. What the addresses are of the funds being stored etc.
This is our chance.
We've got a right to know how much of the community premine has been spent and on what. What the addresses are of the funds being stored etc.
This is our chance.
Are you a garbage from an opposite camp like BC? Don't waste your time here. Get out of here.
April 05, 2014, 07:13:56 PM
Looks like some people did not upgrade to the new version and created a fork...
I sync'ed fine, no issues.
If you can't sync, make sure you are using V1.7 (the latest), and using following addnodes (from my peers)
Quote
addnode=82.73.249.168
addnode=173.69.49.106
addnode=82.131.33.87
addnode=96.244.241.62
addnode=79.103.60.211
addnode=115.187.228.119
addnode=93.103.143.167
addnode=71.204.235.217
addnode=50.171.251.116
addnode=65.25.244.83
addnode=76.91.118.4
addnode=91.61.40.108
addnode=98.177.158.203
addnode=98.207.109.245
addnode=75.174.4.1
addnode=99.245.184.159
addnode=78.83.27.181
addnode=96.18.173.160
addnode=118.123.116.219
addnode=173.26.106.194
addnode=82.233.163.250
addnode=177.140.202.7
addnode=97.81.64.44
addnode=79.166.77.203
addnode=68.145.81.59
addnode=181.165.200.142
addnode=173.69.49.106
addnode=82.131.33.87
addnode=96.244.241.62
addnode=79.103.60.211
addnode=115.187.228.119
addnode=93.103.143.167
addnode=71.204.235.217
addnode=50.171.251.116
addnode=65.25.244.83
addnode=76.91.118.4
addnode=91.61.40.108
addnode=98.177.158.203
addnode=98.207.109.245
addnode=75.174.4.1
addnode=99.245.184.159
addnode=78.83.27.181
addnode=96.18.173.160
addnode=118.123.116.219
addnode=173.26.106.194
addnode=82.233.163.250
addnode=177.140.202.7
addnode=97.81.64.44
addnode=79.166.77.203
addnode=68.145.81.59
addnode=181.165.200.142
If after all these, you still see out of sync with some 300 blocks to catch up, don't worry, you are fine, just leave the client there. You can do send/receive all the transaction ok. It may take a little time for it to display the in sync.
April 05, 2014, 07:06:22 PM
upgrade to V1.7 please http://mintcoin.cc/download-wallet/
If you have upgraded after block 220000, you need to sync from scratch (that is delete all the file EXCEPT the wallet.dat from %appdata% dir, and then start the client to sync)
Then leave your wallet open.
If you have upgraded after block 220000, you need to sync from scratch (that is delete all the file EXCEPT the wallet.dat from %appdata% dir, and then start the client to sync)
Then leave your wallet open.
April 05, 2014, 06:56:51 PM
Something is going totally wrong with my wallet, even though I have the latest version. Does not sync or at least it still
sync very-very slow.
Oh well, closing it and wait for possible news ...
sync very-very slow.
Oh well, closing it and wait for possible news ...
April 05, 2014, 06:46:56 PM
Indeed!
April 05, 2014, 06:45:06 PM
People already on 1.7 should probably open their wallet. I think it would help the network.
April 05, 2014, 06:23:52 PM
Yes people, upgrade to V1.7 please http://mintcoin.cc/download-wallet/
You may need to sync from scratch (that is delete all the file EXCEPT the wallet.dat from %appdata% dir, and then start the client to sync)
You may need to sync from scratch (that is delete all the file EXCEPT the wallet.dat from %appdata% dir, and then start the client to sync)
April 05, 2014, 06:22:32 PM
Looks like some people did not upgrade to the new version and created a fork...
April 05, 2014, 05:54:50 PM
Voted.
April 05, 2014, 04:41:22 PM
Coordinated FUD incoming. Just another day on the mintcoin forum.
Yup its pretty much non-stop. Hey everybody, show your support for Mintcoin and vote for it to be included on lovecrypto.com:
http://www.lovecrypto.com/vote
Vote for a coin below, 5 times per hour. Paid votes are also accepted
DONE.
Please keep voting
April 05, 2014, 04:33:37 PM
Ahh, ok we look good. I also just closed and re opened and it synced up fast.
Edit: I'm not an expert by any means, but if I was guessing I would say the hiccup was just from people opening earlier than block 220000 and the corresponding adjustment.
April 05, 2014, 04:32:47 PM
no sync issues here
April 05, 2014, 04:28:58 PM
The syncing lagged for me around block 220400, but it is all caught up now running smoothly. Haven't had any additional lags.
I'm seeing Current number of blocks around 268 blocks behind Estimated total blocks. (approx.)
Please post current block height if you are in sync.
Guessing that this is being caused by non-updated clients.
EDIT: NVM - It seems to sync. up eventually. All is well.
Yeah, mine took a while this latest opening too. I think you're right about old wallets though. Currently at 220703
April 05, 2014, 04:27:26 PM
I'm synced up and at 220700
April 05, 2014, 04:23:30 PM
The syncing lagged for me around block 220400, but it is all caught up now running smoothly. Haven't had any additional lags.
I'm seeing Current number of blocks around 268 blocks behind Estimated total blocks. (approx.)
Please post current block height if you are in sync.
Guessing that this is being caused by non-updated clients.
I'm about to hit block 220000 shortly will report
April 05, 2014, 04:18:40 PM
The syncing lagged for me around block 220400, but it is all caught up now running smoothly. Haven't had any additional lags.
I'm seeing Current number of blocks around 268 blocks behind Estimated total blocks. (approx.)
Please post current block height if you are in sync.
Guessing that this is being caused by non-updated clients.
EDIT: NVM - It seems to sync. up eventually. All is well.
Jump to: