Sorry to be Johnny come lately, is anything going on with nxxtyACCI asset?
I just noticed I had some on NXT asset exchange but noone is trading it.
Thanks.
 

Here is my Ubuntu Linux build of KoreCoin 2.0 staking wallet (no VoIP): https://mega.nz/#!Nk110QaT!yuf_cVCyKtXoJufgi3kJk6VcvsC4r92WP4ZMtnBrbeY
Version: 64 bit Ubuntu Linux 14.04 LTS Trusty

Prerequisites (Needs boost 1.55, Berkeley db4.8++):
sudo apt-get update
sudo apt-add-repository ppa:bitcoin/bitcoin
sudo apt-add-repository ppa:boost-latest/ppa
sudo apt-get install unzip qt4-qmake libqt4-dev build-essential libboost1.55-all-dev libssl-dev libdb4.8++-dev libminiupnpc-dev libminiupnpc8
sudo apt-get upgrade

unzip korecoin-qt.zip
chmod u+x korecoin-qt
korecoin-qt

Then exit and replace the .KoreCoin/peers.dat with the one above

Re-launch wallet

Thanks MikeMike!  That peers.dat does work for my 64 bit Ubuntu 14.04 LTS wallet I built from the git repo.

If I copy the peers.dat file over to my Linux wallet will that work?  The Windows wallet has 0 active connections for hours.

I'm using the new Windows wallet which MikeMike posted, but its still not syncing have any ideas how to fix the issue?  Thanks in advance!

I have BitBay marketplace installed, recently I am having a sync issue where it says Synchronizing 217121: (this number does increment)
but the status bar is stuck at 0%
I tried the Rescan feature or restarting BitBay market but this did not fix the sync issue.
Thanks in advance any help appreciated!

Once we are synced on to the right fork can we switch listen back to 1 this time?  I don't think my staking wallet will work good with only two nodes...

I have staking issues as well, a lot of generated but not accepted.  Is there multiple forks going on?  I have started from scratch having deleted the .litedoge directory, restore old wallet and then execute repairwallet from the debug console last night will do this again now...

Same for me, no lockdown all pending

Thanks received 

Thanks worked like a charm 

I sent some coins to bittrex from the linux wallet and the transaction will not confirm (on the wallet side) even after more than a day.  Does anyone know of a way to fix this?

I had the same issue with my nodes as well.

Thanks Joe second payment successfully received +127 x2

XDN is a decent coin.  HitBTC also has XDN and a few other cryptonote coins such as BCN and FCN even.  Someone from FCN board recommended it (that one is truly in dire shape). https://hitbtc.com/market-overview
This exchange does not have super high volume but the trading interface is nice, plus they support fiat deposit and withdrawals.

This exchange looks very nice plus they support withdrawing/depositing USD to your bank account and robot trading. 
Has anyone had any experience trading here what do you think of them (hitbtc)?

At Bter you get 2 free votes per hour.  KORE is #19 we can do it!  Every hour click-click 
https://bter.com/voting

KORE: KMXVAiWCSUFpzSnqs9uhfSxVdt6GdnMpJ9

I still have 30 or so FCN stashed away in my wallet. (crosses fingers)

+1 I am in, just signed up 

I am participating in PoM with:

1. Dell Poweredge C6100 server I got from eBay with 4 nodes and two 4 core Intel Xeon L5420 CPUs per node.  Hash rate per node=~70 Kh/s
    Here is the cpubenchmark.com comparison for the Dual Xeon L5420 compared to other CPUs: https://cpubenchmark.net/cpu.php?cpu=Intel+Xeon+L5420+%40+2.50GHz&id=1259&cpuCount=2
2. Dell Poweredge C6105 server (eBay) with 3 Nodes, and two 6 core AMD Opteron 2419EE (North Bridge) variety. Hash rate per node=~77Kh/s
    Here is the cpubenchmark.com comparison for the Dual AMD Opteron 2419EE compared to other CPUs: http://www.cpubenchmark.net/cpu.php?cpu=AMD+Opteron+2419&id=1858&cpuCount=2

Current hash rate on nonce-pool for these two servers combined is 556.61 KH/s.

One server draws at max load about 450 watts for 4 nodes.  For 3 nodes it will be less than 450 watts.

I was previously mining ducknote with these, here is the YouTube video I made: http://youtu.be/zmvVZMRcvFE

Counter-intuitively, the AMD Opteron CPU is cheaper but hashes quicker on M7M algo.
The more expensive Xeon CPU will hash quicker on cryptonight algorithm than the Opteron CPU (as expected).

*** JoeLao the 3-node Dell Poweredge C6105 is dirt cheap looks junky on the outside (refurbished of course) but it works good, if you need a spare development server. 
Here is the eBay link they still have a ton of these (48GB RAM total, so 16GB Ram/node, comes with 3 250GB HD one for each node) ***:
http://www.ebay.com/itm/DELL-C6105-CLOUD-SERVER-6x-1-8GHz-AMD-6-CORE-48GB-RAM-3x-250GB-C6100-SERIES-/171187983886?pt=COMP_EN_Servers&hash=item27db99560e

Can anyone help with this Ubuntu 14.04 LTS compile error?  Previously I had no problems compiling ducknote (just had to tweak CMakeLists.txt, to support gcc 4.9.x instead of 4.8.x)
Now though I get this bug:

/usr/local/darknote# make
mkdir -p build/release
cd build/release && cmake -D CMAKE_BUILD_TYPE=Release ../..
-- Boost version: 1.55.0
-- Found the following Boost libraries:
--   system
--   filesystem
--   thread
--   date_time
--   chrono
--   regex
--   serialization
--   program_options
-- Found Git: /usr/bin/git
-- Could NOT find Threads (missing:  Threads_FOUND)
-- Configuring done
-- Generating done
-- Build files have been written to: /usr/local/darknote/build/release
cd build/release && make
make[1]: Entering directory `/usr/local/darknote/build/release'
make[2]: Entering directory `/usr/local/darknote/build/release'
make[3]: Entering directory `/usr/local/darknote/build/release'
make[3]: Leaving directory `/usr/local/darknote/build/release'
make[3]: Entering directory `/usr/local/darknote/build/release'
fatal: No names found, cannot describe anything.
CMake Warning at src/version.cmake:3 (message):
  Cannot determine current revision.  Make sure that you are building either
  from a Git working tree or from a source archive.


make[3]: Leaving directory `/usr/local/darknote/build/release'
[  0%] Built target version
make[3]: Entering directory `/usr/local/darknote/build/release'
make[3]: Leaving directory `/usr/local/darknote/build/release'
[  2%] Built target epee
make[3]: Entering directory `/usr/local/darknote/build/release'
make[3]: Leaving directory `/usr/local/darknote/build/release'
[ 13%] Built target upnpc-static
make[3]: Entering directory `/usr/local/darknote/build/release'
make[3]: Leaving directory `/usr/local/darknote/build/release'
[ 17%] Built target common
make[3]: Entering directory `/usr/local/darknote/build/release'
make[3]: Leaving directory `/usr/local/darknote/build/release'
[ 32%] Built target crypto
make[3]: Entering directory `/usr/local/darknote/build/release'
make[3]: Leaving directory `/usr/local/darknote/build/release'
[ 43%] Built target cryptonote_core
make[3]: Entering directory `/usr/local/darknote/build/release'
make[3]: Leaving directory `/usr/local/darknote/build/release'
[ 44%] Built target connectivity_tool
make[3]: Entering directory `/usr/local/darknote/build/release'
make[3]: Leaving directory `/usr/local/darknote/build/release'
[ 45%] Built target rpc
make[3]: Entering directory `/usr/local/darknote/build/release'
make[3]: Leaving directory `/usr/local/darknote/build/release'
[ 46%] Built target daemon
make[3]: Entering directory `/usr/local/darknote/build/release'
make[3]: Leaving directory `/usr/local/darknote/build/release'
[ 48%] Built target node_rpc_proxy
make[3]: Entering directory `/usr/local/darknote/build/release'
make[3]: Leaving directory `/usr/local/darknote/build/release'
[ 49%] Built target simpleminer
make[3]: Entering directory `/usr/local/darknote/build/release'
make[3]: Leaving directory `/usr/local/darknote/build/release'
[ 58%] Built target wallet
make[3]: Entering directory `/usr/local/darknote/build/release'
make[3]: Leaving directory `/usr/local/darknote/build/release'
[ 60%] Built target simplewallet
make[3]: Entering directory `/usr/local/darknote/build/release'
make[3]: Leaving directory `/usr/local/darknote/build/release'
[ 60%] Built target TestGenerator
make[3]: Entering directory `/usr/local/darknote/build/release'
make[3]: Leaving directory `/usr/local/darknote/build/release'
[ 61%] Built target core_proxy
make[3]: Entering directory `/usr/local/darknote/build/release'
make[3]: Leaving directory `/usr/local/darknote/build/release'
[ 71%] Built target coretests
make[3]: Entering directory `/usr/local/darknote/build/release'
make[3]: Leaving directory `/usr/local/darknote/build/release'
[ 76%] Built target crypto-tests
make[3]: Entering directory `/usr/local/darknote/build/release'
make[3]: Leaving directory `/usr/local/darknote/build/release'
make[3]: Entering directory `/usr/local/darknote/build/release'
Linking CXX executable difficulty-tests
/tmp/ccfBwXlX.ltrans0.ltrans.o: In function `cryptonote::construct_tx(cryptonote::account_keys const&, std::vector<cryptonote::tx_source_entry, std::allocator<cryptonote::tx_source_entry> > const&, std::vector<cryptonote::tx_destination_entry, std::allocator<cryptonote::tx_destination_entry> > const&, std::vector<unsigned char, std::allocator<unsigned char> >, cryptonote::Transaction&, unsigned long)':
ccfBwXlX.ltrans0.o:(.text+0x12a): undefined reference to `crypto::crypto_ops::generate_keys(crypto::public_key&, crypto::secret_key&)'
ccfBwXlX.ltrans0.o:(.text+0x60e): undefined reference to `epee::log_space::log_singletone::get_prefix_entry()'
ccfBwXlX.ltrans0.o:(.text+0x6de): undefined reference to `epee::log_space::log_singletone::do_log_message(std::string const&, int, int, bool, char const*)'
ccfBwXlX.ltrans0.o:(.text+0x6ff): undefined reference to `epee::log_space::log_singletone::get_set_err_count(bool, unsigned long)'
ccfBwXlX.ltrans0.o:(.text+0x70d): undefined reference to `epee::log_space::log_singletone::get_set_err_count(bool, unsigned long)'
ccfBwXlX.ltrans0.o:(.text+0xa9b): undefined reference to `crypto::crypto_ops::generate_key_derivation(crypto::public_key const&, crypto::secret_key const&, crypto::key_derivation&)'
ccfBwXlX.ltrans0.o:(.text+0xac4): undefined reference to `crypto::crypto_ops::derive_public_key(crypto::key_derivation const&, unsigned long, crypto::public_key const&, crypto::public_key&)'
...
Thanks in advance!