Bitcoin Forum
October 21, 2017, 11:31:01 PM *
News: Latest stable version of Bitcoin Core: 0.15.0.1  [Torrent]. (New!)
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 [922] 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943 944 945 946 947 948 949 950 951 952 953 954 955 956 957 958 959 960 961 962 963 964 965 966 967 968 969 970 971 972 ... 1013 »
  Print  
Author Topic: [ANN] [MINT] Mintcoin (POS / 5%) [NO ICO] [Fair distro, community maintained]  (Read 1294798 times)
GKar
Full Member
***
Offline Offline

Activity: 136


View Profile
August 09, 2015, 08:19:15 PM
 #18421

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.

1508628661
Hero Member
*
Offline Offline

Posts: 1508628661

View Profile Personal Message (Offline)

Ignore
1508628661
Reply with quote  #2

1508628661
Report to moderator
1508628661
Hero Member
*
Offline Offline

Posts: 1508628661

View Profile Personal Message (Offline)

Ignore
1508628661
Reply with quote  #2

1508628661
Report to moderator
1508628661
Hero Member
*
Offline Offline

Posts: 1508628661

View Profile Personal Message (Offline)

Ignore
1508628661
Reply with quote  #2

1508628661
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
crzybilly
Sr. Member
****
Offline Offline

Activity: 409


View Profile
August 09, 2015, 09:11:48 PM
 #18422

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?
fonzerrellie
Hero Member
*****
Offline Offline

Activity: 952


MZC, BERN, TECH, SQL


View Profile
August 09, 2015, 09:39:26 PM
 #18423

my new MINT win7 wallet works great, just staked the other day

EXP -Expanse-  https://bitcointalk.org/index.php?topic=1173722.0
https://www.crypto-city.com (needs more users but is a great site)
PIVX, ARK, STRAT, NXS, AMP, BAT, BLK, EDG, BITB, VRC/VRM, WAVES, NEO, OMG
Fuzzbawls
Hero Member
*****
Offline Offline

Activity: 740

★YoBit.Net★ 200+ Coins Exchange & Dice


View Profile
August 09, 2015, 10:41:30 PM
 #18424

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

mchrist152
Newbie
*
Offline Offline

Activity: 21


View Profile
August 10, 2015, 12:44:02 AM
 #18425

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?
mchrist152
Newbie
*
Offline Offline

Activity: 21


View Profile
August 10, 2015, 12:57:56 AM
 #18426

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
Fuzzbawls
Hero Member
*****
Offline Offline

Activity: 740

★YoBit.Net★ 200+ Coins Exchange & Dice


View Profile
August 10, 2015, 01:13:29 AM
 #18427

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
Newbie
*
Offline Offline

Activity: 21


View Profile
August 10, 2015, 01:40:03 AM
 #18428

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
Full Member
***
Offline Offline

Activity: 136


View Profile
August 10, 2015, 01:54:12 PM
 #18429

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
Hero Member
*****
Offline Offline

Activity: 840



View Profile
August 10, 2015, 04:23:50 PM
 #18430

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

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

Rent Rigs @ MiningRigRentals: https://www.miningrigrentals.com/register?ref=9685 | Mine Zcash, X11, ETH, BTC, LTC hashrate available @ Genesis Mining: 9yx2ib (Promo Code for 3% off)
Sell & Buy/Rent hashing power @ Nicehash.com: https://www.nicehash.com/?refby=63551
Trade BTCINR on Coinsecure.in (Global trade available: http://blog.coinsecure.in/post/153309186530/coinsecure-goes-global-by-reducing-the-barrier-for): https://coinsecure.in/signup/z5ehHIOLvHN5sWAq3wTu
BobTheVeg
Newbie
*
Offline Offline

Activity: 4


View Profile
August 13, 2015, 04:02:33 AM
 #18431

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
Hero Member
*****
Offline Offline

Activity: 560


View Profile
August 13, 2015, 04:44:24 AM
 #18432

Mine is too Smiley
crzybilly
Sr. Member
****
Offline Offline

Activity: 409


View Profile
August 13, 2015, 08:59:00 AM
 #18433

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.
Flyskyhigh
Sr. Member
****
Offline Offline

Activity: 292


Ezekiel 34:11, John 10:25-30


View Profile
August 13, 2015, 01:13:14 PM
 #18434

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.

Sick of mining?  Start minting!  5% per year!  Mintcoin "MINT"
devlin85
Full Member
***
Offline Offline

Activity: 133


The Blockchain Evolution of Prediction Markets


View Profile
August 13, 2015, 06:32:28 PM
 #18435

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
Hero Member
*****
Offline Offline

Activity: 840



View Profile
August 13, 2015, 06:56:54 PM
 #18436

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.

Rent Rigs @ MiningRigRentals: https://www.miningrigrentals.com/register?ref=9685 | Mine Zcash, X11, ETH, BTC, LTC hashrate available @ Genesis Mining: 9yx2ib (Promo Code for 3% off)
Sell & Buy/Rent hashing power @ Nicehash.com: https://www.nicehash.com/?refby=63551
Trade BTCINR on Coinsecure.in (Global trade available: http://blog.coinsecure.in/post/153309186530/coinsecure-goes-global-by-reducing-the-barrier-for): https://coinsecure.in/signup/z5ehHIOLvHN5sWAq3wTu
devlin85
Full Member
***
Offline Offline

Activity: 133


The Blockchain Evolution of Prediction Markets


View Profile
August 13, 2015, 07:15:11 PM
 #18437

The non updated wallet was the problem. Just REALLY weird how it showed up, confirmed, was on sale, then disappeared..  Huh Huh 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..  Undecided Undecided

sambiohazard
Hero Member
*****
Offline Offline

Activity: 840



View Profile
August 14, 2015, 06:23:34 AM
 #18438

The non updated wallet was the problem. Just REALLY weird how it showed up, confirmed, was on sale, then disappeared..  Huh Huh 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..  Undecided Undecided
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.

Rent Rigs @ MiningRigRentals: https://www.miningrigrentals.com/register?ref=9685 | Mine Zcash, X11, ETH, BTC, LTC hashrate available @ Genesis Mining: 9yx2ib (Promo Code for 3% off)
Sell & Buy/Rent hashing power @ Nicehash.com: https://www.nicehash.com/?refby=63551
Trade BTCINR on Coinsecure.in (Global trade available: http://blog.coinsecure.in/post/153309186530/coinsecure-goes-global-by-reducing-the-barrier-for): https://coinsecure.in/signup/z5ehHIOLvHN5sWAq3wTu
duplan
Sr. Member
****
Offline Offline

Activity: 286


View Profile
August 14, 2015, 03:09:55 PM
 #18439

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
Member
**
Offline Offline

Activity: 68


View Profile
August 14, 2015, 06:31:55 PM
 #18440

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.
Pages: « 1 ... 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 [922] 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943 944 945 946 947 948 949 950 951 952 953 954 955 956 957 958 959 960 961 962 963 964 965 966 967 968 969 970 971 972 ... 1013 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!