Author

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

sr. member
Activity: 291
Merit: 250
Ezekiel 34:11, John 10:25-30
Mine is too Smiley

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.
sr. member
Activity: 703
Merit: 250
Mine is too Smiley

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.
hero member
Activity: 574
Merit: 500
newbie
Activity: 4
Merit: 0
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.
hero member
Activity: 840
Merit: 1000
You can always get the latest list of up to date nodes as CryptoID block explorer sees them

https://chainz.cryptoid.info/mint/#!network
full member
Activity: 180
Merit: 100
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.     
newbie
Activity: 23
Merit: 0
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.
hero member
Activity: 750
Merit: 500
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
newbie
Activity: 23
Merit: 0
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 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
newbie
Activity: 23
Merit: 0
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 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?
hero member
Activity: 750
Merit: 500
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
legendary
Activity: 1190
Merit: 1000
Kaspa
my new MINT win7 wallet works great, just staked the other day
sr. member
Activity: 703
Merit: 250
Still can't under windows 8.1 64bit and windows 7 32 bit get v2.0.0.1 to sync.

win7:
deleted peers.dat and wallet.dat.
result: no joy. connection keeps blinking  between zero and one connections and won;t sync

Win8:
tried same as above and aslo the following:
start from scratch, use woking block fgrom prior to upgrade; the daily torrent block update.
Even tired all this on 1 computer on a diffenet ISP.

results: no change to problem

Have tried all the addnodes from last 2 pages that were said to work. Did not for me.


Is windows firewall enabled? does your AV have a firewall built into it?
full member
Activity: 180
Merit: 100
Still can't under windows 8.1 64bit and windows 7 32 bit get v2.0.0.1 to sync.

win7:
deleted peers.dat and wallet.dat.
result: no joy. connection keeps blinking  between zero and one connections and won;t sync

Win8:
tried same as above and aslo the following:
start from scratch, use woking block fgrom prior to upgrade; the daily torrent block update.
Even tired all this on 1 computer on a diffenet ISP.

results: no change to problem

Have tried all the addnodes from last 2 pages that were said to work. Did not for me.

newbie
Activity: 23
Merit: 0
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 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
sr. member
Activity: 703
Merit: 250


Here is the information I have so far - let me know if you need anything else:
hi. mintcoin-qt 2.o.o.1 doesn't work for limux

linux

I've extracted it file from the compressed file. when I run it, a file with a filename like "&#@*&#" is created and nothing else happens

i have both the qt and the mintcoind d in the same folder as well

@C@w@8

That's the file created in the same folder when qt is run

empty 0B
sounds corrupted.
full member
Activity: 398
Merit: 110
I upgraded wallet to latest version and now it won't hold even 1 connection. It keeps flickering between 0 and 1.

I've tried importing a fresh block chain that I d/l from here and deleting the chain. Makes no difference.
Even tried it both ways with & without conf file.

listen=1
addnode=76.111.80.147
addnode=78.234.66.199
addnode=71.89.162.42
addnode=46.40.98.56
addnode=46.4.95.176
addnode=78.27.187.7
addnode=187.233.181.141
addnode=71.164.166.156
addnode=99.136.121.44
addnode=115.29.243.40
addnode=178.78.11.32
addnode=37.229.38.196
maxconnections=100
server=1
daemon=1
addnode=144.76.220.169
addnode=213.114.153.118
addnode=1.80.150.168
addnode=184.72.188.245
addnode=162.243.4.85
addnode=115.28.140.128
addnode=113.135.64.107
addnode=27.33.253.164
addnode=209.190.29.2
addnode=155.210.52.121
addnode=62.178.31.2
addnode=91.228.76.83
addnode=115.29.224.192
addnode=128.199.255.172
addnode=223.199.16.58
addnode=23.253.55.13
addnode=162.243.70.241
addnode=107.170.26.18
addnode=115.28.177.49
addnode=93.78.120.235
addnode=218.77.97.176
addnode=182.112.134.112
addnode=155.210.52.121
addnode=94.194.77.2
addnode=5.255.66.44
addnode=115.28.129.207




Connection went out because these are dead nodes. Delete the peer.dat and start it again. Though no one can sync either, better extract the private key and create a raw transaction without downloading the whole blockchain.
sr. member
Activity: 425
Merit: 250
Good morning everyone!
I have a trouble ticket on facebook with a Linux user who is unable to execute the mintcoin wallet install - any suggestions?

can you provide more details?

Here is the information I have so far - let me know if you need anything else:
hi. mintcoin-qt 2.o.o.1 doesn't work for limux

linux

I've extracted it file from the compressed file. when I run it, a file with a filename like "&#@*&#" is created and nothing else happens

i have both the qt and the mintcoind d in the same folder as well

@C@w@8

That's the file created in the same folder when qt is run

empty 0B
sr. member
Activity: 703
Merit: 250
Good morning everyone!
I have a trouble ticket on facebook with a Linux user who is unable to execute the mintcoin wallet install - any suggestions?

can you provide more details?
sr. member
Activity: 425
Merit: 250
Good morning everyone!
I have a trouble ticket on facebook with a Linux user who is unable to execute the mintcoin wallet install - any suggestions?
Jump to: