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

[mchrist152]

Would anybody be so kind as to help me with a mintcoin wallet compile issue?

I'm using the commandline to try and compile the unix version of the wallet on a Debian system.  Everything compiles but I'm running into the following linker errors:

...
build/moc_repairwalletdialog.o build/qrc_bitcoin.o    -L/usr/lib/x86_64-linux-gnu -lminiupnpc /home/mikech/github/Mintcoin-Desktop-Wallet/src/leveldb/libleveldb.a /home/mikech/github/Mintcoin-Desktop-Wallet/src/leveldb/libmemenv.a -lrt -lssl -lcrypto -ldb_cxx -lboost_system -lboost_filesystem -lboost_program_options -lboost_thread -lpthread -lQtGui -lQtNetwork -lQtCore
build/init.o: In function `bool CDB::Read<std::string, CBlockLocator>(std::string const&, CBlockLocator&)':
init.cpp:(.text._ZN3CDB4ReadISs13CBlockLocatorEEbRKT_RT0_[_ZN3CDB4ReadISs13CBlockLocatorEEbRKT_RT0_]+0x122): undefined reference to `Dbt::Dbt(void*, unsigned int)'
init.cpp:(.text._ZN3CDB4ReadISs13CBlockLocatorEEbRKT_RT0_[_ZN3CDB4ReadISs13CBlockLocatorEEbRKT_RT0_]+0x12e): undefined reference to `Dbt::Dbt()'
init.cpp:(.text._ZN3CDB4ReadISs13CBlockLocatorEEbRKT_RT0_[_ZN3CDB4ReadISs13CBlockLocatorEEbRKT_RT0_]+0x394): undefined reference to `Dbt::~Dbt()'
init.cpp:(.text._ZN3CDB4ReadISs13CBlockLocatorEEbRKT_RT0_[_ZN3CDB4ReadISs13CBlockLocatorEEbRKT_RT0_]+0x3a0): undefined reference to `Dbt::~Dbt()'
init.cpp:(.text._ZN3CDB4ReadISs13CBlockLocatorEEbRKT_RT0_[_ZN3CDB4ReadISs13CBlockLocatorEEbRKT_RT0_]+0x454): undefined reference to `Dbt::~Dbt()'
init.cpp:(.text._ZN3CDB4ReadISs13CBlockLocatorEEbRKT_RT0_[_ZN3CDB4ReadISs13CBlockLocatorEEbRKT_RT0_]+0x460): undefined reference to `Dbt::~Dbt()'
build/db.o: In function `CDBEnv::CDBEnv()':
db.cpp:(.text+0x38f): undefined reference to `DbEnv::DbEnv(unsigned int)'
build/db.o: In function `CDBEnv::EnvShutdown()':
db.cpp:(.text+0x12fb): undefined reference to `DbEnv::close(unsigned int)'
...

From what I've read on the web I need to change the version of my compiler to fix this issue but nowhere does anybody say what version of compiler is required.  I'm currently running gcc 4.9.2.  Can anybody tell me what version of compiler they are using to successfully compile the unix version of the wallet?

Thanks in Advance,

mchrist152

Ok, it turns out that it wasn't the version of the compiler after all but the way I compiled Berkeley DB. I had to add the following arguments to the Berkeley DB configure command:
../dist/configure --enable-cxx --disable-shared --with-pic
That did the trick.  Seems like every time I post to this board I figure out the answer shortly there after.

So it built and it's running but it's not connecting to other nodes.  I'm not sure why.  It's running in a virtual machine so maybe there is something blocking it but other apps are having no problems.  Any ideas?

I'm able to ping the peers in the debug.log file so I have connectivity at least.  Here is an excerpt from my debug.log file:

them=76.21.26.146:12788, peer=76.21.26.146:12788
partner 76.21.26.146:12788 using obsolete version 60006; disconnecting
ProcessMessage(version, 101 bytes) FAILED
disconnecting node 76.21.26.146:12788
trying connection 76.21.26.146:12788 lastseen=0.0hrs
connected 76.21.26.146:12788
send version message: version 60007, blocks=0, us=76.76.70.110:12788, them=76.21.26.146:12788, peer=76.21.26.146:12788
partner 76.21.26.146:12788 using obsolete version 60006; disconnecting
ProcessMessage(version, 101 bytes) FAILED
disconnecting node 76.21.26.146:12788

what is meant by obsolete version 60006

[1713966991]

1713966991

[1713966991]

1713966991

[1713966991]

1713966991

[Fuzzbawls]

I'm able to ping the peers in the debug.log file so I have connectivity at least.  Here is an excerpt from my debug.log file:

them=76.21.26.146:12788, peer=76.21.26.146:12788
partner 76.21.26.146:12788 using obsolete version 60006; disconnecting
ProcessMessage(version, 101 bytes) FAILED
disconnecting node 76.21.26.146:12788
trying connection 76.21.26.146:12788 lastseen=0.0hrs
connected 76.21.26.146:12788
send version message: version 60007, blocks=0, us=76.76.70.110:12788, them=76.21.26.146:12788, peer=76.21.26.146:12788
partner 76.21.26.146:12788 using obsolete version 60006; disconnecting
ProcessMessage(version, 101 bytes) FAILED
disconnecting node 76.21.26.146:12788

what is meant by obsolete version 60006

see my previous post

[mchrist152]

I'm able to ping the peers in the debug.log file so I have connectivity at least.  Here is an excerpt from my debug.log file:

them=76.21.26.146:12788, peer=76.21.26.146:12788
partner 76.21.26.146:12788 using obsolete version 60006; disconnecting
ProcessMessage(version, 101 bytes) FAILED
disconnecting node 76.21.26.146:12788
trying connection 76.21.26.146:12788 lastseen=0.0hrs
connected 76.21.26.146:12788
send version message: version 60007, blocks=0, us=76.76.70.110:12788, them=76.21.26.146:12788, peer=76.21.26.146:12788
partner 76.21.26.146:12788 using obsolete version 60006; disconnecting
ProcessMessage(version, 101 bytes) FAILED
disconnecting node 76.21.26.146:12788

what is meant by obsolete version 60006

see my previous post

Thanks!  The work around got it syncing.

[GKar]

I'll address a couple issues here:

First, the user having issues with the linux wallet:
Without knowing more details, like what distro, I'd say that your downloaded package is corrupt. I just tested downloading, extracting, and running both the Qt wallet and headless daemon on my clean install of Mint Linux. Both packages are fine and produce a valid binary file.

Suggested to redownload and if issue persists, provide me with more details as to your OS distro.

Second, users having issues syncing:
At the moment, without a valid peers.dat or proper MintCoin.conf, syncing will not work. This is a known issue and it is being worked on from 2 viable angles. There is a workaround, and that involves using addnode=x in your MintCoin.conf file.

There are currently a LOT of nodes that are still using the old version, for what reason I have no clue. The new version (and proper blockchain) is designed to outright reject any client/node running on the old version. You absolutely MUST be running the new version (protocolversion : 60007) in order to sync the blockchain.

Now, on to the workaround I mentioned: MintCoin.conf (note: not mintcoin.conf, not Mintcoin.conf...MintCoin.conf). This file goes in the same folder/directory as your wallet.dat, peers.dat, debug.log, etc. and should be formatted as follows:

Code:

rpcuser=x
rpcpassword=y
rpcallowip=127.0.0.1
addnode=198.50.243.84
addnode=185.16.59.233
addnode=50.168.101.34
addnode=101.174.162.119
addnode=74.197.221.45
addnode=176.37.23.74

x and y above are whatever you want. One of those nodes is mine, and unless my wallet is offline for whatever reason, it WILL accept connections provided you are attempting to connect with the correct version. Now, attempting to connect repeatedly with the WRONG version will result in nodes banning you for a period of time, if this happens then you'll have to update to the new version and wait for bans to be released. So again, you absolutely MUST be running the new version to do ANYTHING with MintCoin.


I have tested and verified working all of the above multiple times on multiple machines. I obviously cannot test every OS/build (especially with the countless linux distros), so if you're still having issues I'm going to need raw dumps of your debug.log and MintCoin.conf files to further assist

Thank You!   That solved my sync problems.   I now have 12 connections.     

[sambiohazard]

You can always get the latest list of up to date nodes as CryptoID block explorer sees them

https://chainz.cryptoid.info/mint/#!network

[BobTheVeg]

You can always get the latest list of up to date nodes as CryptoID block explorer sees them

https://chainz.cryptoid.info/mint/#!network

Interesting, my IP was part of the list.

[MarSas]

Mine is too

[crzybilly]

Mine is too

mines not, because I have a firewall rule setup to block incoming connections from all non standard ports. that way I can monitor hackers trying to steal my crap.

[Flyskyhigh]

Mine is too

mines not, because I have a firewall rule setup to block incoming connections from all non standard ports. that way I can monitor hackers trying to steal my crap.

How do you set that up or configure this? I would like to do this too.

[devlin85]

I sent this transaction to cryptsy.. ed0166a850e31978f54bf075149fe3ea0547d5a4316d0abc8a57637e21ddcd79 on 8/11 for 295070.448625 mint. It showed up on cryptsy, was in the order forms to sell for over 24 hours, then I restarted my computer with the wallet on it, it disappeared from cryptsy, and it and every other recent POS mint (in the last week) is now not confirmed either, how the hell do I fix this? I tried reindex already, nothing.

[sambiohazard]

I sent this transaction to cryptsy.. ed0166a850e31978f54bf075149fe3ea0547d5a4316d0abc8a57637e21ddcd79 on 8/11 for 295070.448625 mint. It showed up on cryptsy, was in the order forms to sell for over 24 hours, then I restarted my computer with the wallet on it, it disappeared from cryptsy, and it and every other recent POS mint (in the last week) is now not confirmed either, how the hell do I fix this? I tried reindex already, nothing.

Have you updated to latest version 2.0.0.1 we had afork on August 1? Also try Help->Repair wallet in the wallet menu.

[devlin85]

The non updated wallet was the problem. Just REALLY weird how it showed up, confirmed, was on sale, then disappeared..   I did the repair, it told me there was a mismatch, but it took a -reindex -rescan to get the coins back.

Anyway, price dropped.. not even sending em now..  

[sambiohazard]

The non updated wallet was the problem. Just REALLY weird how it showed up, confirmed, was on sale, then disappeared..  I did the repair, it told me there was a mismatch, but it took a -reindex -rescan to get the coins back.

Anyway, price dropped.. not even sending em now.. 

Maybe both you & cryptsy were not updated. When they updated your coins disappeared from exchange, now after update & repair you have them back. Price dropped but is now stable. That is a good thing.

[duplan]

This is the moment to buy more MINT , the retracing is over now ,
from here it will grow up in the following weeks and next month ,
over 50 sat , then over 100 , in september++ . Buy now & stake …

[Cryptoid]

I'll address a couple issues here:

First, the user having issues with the linux wallet:
Without knowing more details, like what distro, I'd say that your downloaded package is corrupt. I just tested downloading, extracting, and running both the Qt wallet and headless daemon on my clean install of Mint Linux. Both packages are fine and produce a valid binary file.

Suggested to redownload and if issue persists, provide me with more details as to your OS distro.

Second, users having issues syncing:
At the moment, without a valid peers.dat or proper MintCoin.conf, syncing will not work. This is a known issue and it is being worked on from 2 viable angles. There is a workaround, and that involves using addnode=x in your MintCoin.conf file.

There are currently a LOT of nodes that are still using the old version, for what reason I have no clue. The new version (and proper blockchain) is designed to outright reject any client/node running on the old version. You absolutely MUST be running the new version (protocolversion : 60007) in order to sync the blockchain.

Now, on to the workaround I mentioned: MintCoin.conf (note: not mintcoin.conf, not Mintcoin.conf...MintCoin.conf). This file goes in the same folder/directory as your wallet.dat, peers.dat, debug.log, etc. and should be formatted as follows:

Code:

rpcuser=x
rpcpassword=y
rpcallowip=127.0.0.1
addnode=198.50.243.84
addnode=185.16.59.233
addnode=50.168.101.34
addnode=101.174.162.119
addnode=74.197.221.45
addnode=176.37.23.74

x and y above are whatever you want. One of those nodes is mine, and unless my wallet is offline for whatever reason, it WILL accept connections provided you are attempting to connect with the correct version. Now, attempting to connect repeatedly with the WRONG version will result in nodes banning you for a period of time, if this happens then you'll have to update to the new version and wait for bans to be released. So again, you absolutely MUST be running the new version to do ANYTHING with MintCoin.

I have tested and verified working all of the above multiple times on multiple machines. I obviously cannot test every OS/build (especially with the countless linux distros), so if you're still having issues I'm going to need raw dumps of your debug.log and MintCoin.conf files to further assist

I have been syncing from scratch for more than 4 days, I'm only up to Feb 19, 2015.  I have the newest wallet 2.0.0.1 (protocolversion 60007), I replaced the MintCoin.conf with the recommendation listed above, I have a new valid peers.dat file.  My data connection is 6.5Mbit.

"getpeerinfo" shows all connected wallets are @ 60007

The wallet will get a few hundred blocks, then stop/freeze for 5-10 minutes or longer.  Any other ideas what to do to speed up the process?  I should be ok in a couple more days, just looking to get this done quicker.

[Fuzzbawls]

Unfortunately, syncing from block 0 does take time, and while I haven't personally tested it, syncing the new client with the available bootstrapped blockchain SHOULD work (provided you still make the necessary changes to your MintCoin.conf file).

[fonzerrellie]

This is the moment to buy more MINT , the retracing is over now ,
from here it will grow up in the following weeks and next month ,
over 50 sat , then over 100 , in september++ . Buy now & stake …

thats what I was thinking, I wish I could buy up that 5 btc sell wall on cryptsy... but could only afford a little nibble

[Cryptoid]

Well, I'm now up to Feb 25th.  I searched for a bootstrap to download previously, but came up empty.  I'm so close now, I guess I'll just wait it out.  Should be done in the next 48 hours - I hope.

Thanks for the replies.

[coolbeans94]

Well, I'm now up to Feb 25th.  I searched for a bootstrap to download previously, but came up empty.  I'm so close now, I guess I'll just wait it out.  Should be done in the next 48 hours - I hope.

Thanks for the replies.

I have always synced from scratch, myself. It does take time though. Just let it run 24/7 and try not to think about it. Unlike Bitcoin, which creates a block every 10 minutes, Mintcoin creates a block every 30 seconds, and each block has to to be downloaded, synced, and verified. This takes time, but is what ensures the security of the network. The flipside, is that with Mintcoin we get to enjoy Super Speedy Transactions, once you are synced up. It is about the fastest Crypto-Coin there is. You just have to endure the syncing battle in the beginning. Also keep in mind, that when syncing from scratch, or a large amount of blocks, sometimes the GUI can lag out, and appear "not responding", even though it is really still syncing up in the background, if you check your Mintcoin folder, see the blockchain file getting bigger every few seconds. If you just keep waiting though, it will eventually catch up and everything will look normal once you are fully synced.

[duplan]

I've noticed some people really have an annoying time waiting to get all done ,
In case some cannot wait many days and don't want to do the bootstrap thing ,
I managed to upload my own blockchain file to the following mega repository :

https://mega.nz/#!R0kiiIqZ!35Xni7L_KUXHi6SMokn38gwPPM3B-uGJtx9eGR1KCqM

It took me some hours to get it uploaded , so it's less than a day old , from my mac wallet .
I updated my wallet some hours before the hardfork deadline , I had no issues of any kind .

If anyone should want to use this , do it only if you you feel comfortable enough ; check it …