I checked my z_address today, I don't received my PIRATE coins.
So I think airdrop didn't happened.
Did anyone get it?

A spreadsheet has been made to verify your airdrop address:
https://docs.google.com/spreadsheets/d/10D9dJSabZGK2YOWeBl-wMgPthoGVpRgV0zIMDHTSvwc

Barterdex removed us because all of our traffic was on Poloniex, who then pump and dumped us along with a lot of other coins. 

How do you get the wallet from v2.0.0.1-g32a928e to the new V2.5 wallet if we cannot move the wallet.dat?
I dont see anywhere to export the private key from the v2.0 wallet, a quick little quide would be much appriciated if anyone knows how to do it?

Here's some:
164.132.19.178:16914
85.144.44.151:16914
79.137.126.63:16914
59.147.36.224:16914
As for project news, we're still here diligently working through small-print issues and hoping to reach final resolution before much longer.

http://5.9.253.199:7783/api/stats/orderbook?base=JUMBLR&rel=KMD

{"bids":[{"coin":"KMD","address":"RMdjuxKBhyr87yhKp6BLUg2p9673NMcPAu","price":7.29117634,"numutxos":59,"minvolume":0.00008154,"maxvolume":900.23273873,"pubkey":"040f1d2d5d12027afa2cec30477312e225b0d24c77cc4aa08d3fffe51277b904","age":0}, {"coin":"KMD","address":"RQzkkncY8ehpRg8M4kvKmDMcbFxcJvohgk","price":7.28841725,"numutxos":69,"minvolume":0.00008491,"maxvolume":960,"pubkey":"30eb3d952f66eba2df0100b97d6707257cf91dc8c8b0237cfb7c3aa70dc52d4d","age":0}, {"coin":"KMD","address":"RVPcbafNSi6uMaKDyss9epGpHCHbbzUFMd","price":7.28758069,"numutxos":50,"minvolume":0.00008298,"maxvolume":960,"pubkey":"e1d9ff940bd7fb30954e0d9297053457eb7f766e66da6c198e75c06b7d982124","age":0}, {"coin":"KMD","address":"RPMpwKpzWyg5KoMcsuy3mZucUWNdcP2ndD","price":7.28638222,"numutxos":50,"minvolume":0.00008802,"maxvolume":960,"pubkey":"b8c5f621194ffbe5641fecbfbd7ab75bf05574f2becccbcf79ffa9643dc6f163","age":0}, {"coin":"KMD","address":"RUPX5RWQL1qurMLmF4fFB4JAgRfwcNww4b","price":7.25025938,"numutxos":84,"minvolume":0.00008267,"maxvolume":960,"pubkey":"bb99c7042e092692191b7b4a636c7da28aeb36497ad038601cd599f356274051","age":0}, {"coin":"KMD","address":"RAzheh3L7QtBL7oNKByVa43CtgALht6bbT","price":7.23595284,"numutxos":60,"minvolume":0.00008203,"maxvolume":960,"pubkey":"50959696e9d954d5853b113b54bfd695f7dd1a272f01700b13d6cd7e4b9bc704","age":0}, {"coin":"KMD","address":"RMfQwu5ey23eWJ4as2ckd8dqsQJwo836ny","price":7.23169542,"numutxos":10,"minvolume":0.16440658,"maxvolume":0.79984000,"pubkey":"9468f3d40fed3a5220d26c0f7efd43fd818fffdc7ce71c48dcfae7da9f476101","age":0}, {"coin":"KMD","address":"RNyBS6ryQtPPQnJhavKn9o94U2RNExLZon","price":7.23169542,"numutxos":33,"minvolume":0.00008238,"maxvolume":960,"pubkey":"25a491638a815a6e669319532270b616124aab4bfd7e466fc08606ab46d48931","age":0}, {"coin":"KMD","address":"RXUF132uyPVTVUdLn16zCgvYoFXya3pyVb","price":7.22888971,"numutxos":37,"minvolume":0.00008088,"maxvolume":960,"pubkey":"825d0e1355117f6b76e7b3741f51c1827e72e25ddc688c0b20ad5b1ec7b28b4f","age":0}, {"coin":"KMD","address":"RT9MpMyucqXiX8bZLimXBnrrn2ofmdGNKd","price":7.00112144,"numutxos":128,"minvolume":0.00689061,"maxvolume":7459.20000000,"pubkey":"bab6ad2eebe1e666369cab504d4622b22c1f1ef718ef388e88020f30a1573e01","age":0}],"numbids":10,"asks":[{"coin":"JUMBLR","address":"RXUF132uyPVTVUdLn16zCgvYoFXya3pyVb","price":7.37419051,"numutxos":0,"minvolume":0,"maxvolume":0,"pubkey":"825d0e1355117f6b76e7b3741f51c1827e72e25ddc688c0b20ad5b1ec7b28b4f","age":0}, {"coin":"JUMBLR","address":"RMfQwu5ey23eWJ4as2ckd8dqsQJwo836ny","price":7.37705224,"numutxos":0,"minvolume":0,"maxvolume":0,"pubkey":"9468f3d40fed3a5220d26c0f7efd43fd818fffdc7ce71c48dcfae7da9f476101","age":0}, {"coin":"JUMBLR","address":"RNyBS6ryQtPPQnJhavKn9o94U2RNExLZon","price":7.37705224,"numutxos":0,"minvolume":0,"maxvolume":0,"pubkey":"25a491638a815a6e669319532270b616124aab4bfd7e466fc08606ab46d48931","age":0}, {"coin":"JUMBLR","address":"RAzheh3L7QtBL7oNKByVa43CtgALht6bbT","price":7.38139539,"numutxos":0,"minvolume":0,"maxvolume":0,"pubkey":"50959696e9d954d5853b113b54bfd695f7dd1a272f01700b13d6cd7e4b9bc704","age":0}, {"coin":"JUMBLR","address":"RUPX5RWQL1qurMLmF4fFB4JAgRfwcNww4b","price":7.39598951,"numutxos":0,"minvolume":0,"maxvolume":0,"pubkey":"bb99c7042e092692191b7b4a636c7da28aeb36497ad038601cd599f356274051","age":0}, {"coin":"JUMBLR","address":"RPMpwKpzWyg5KoMcsuy3mZucUWNdcP2ndD","price":7.43283837,"numutxos":0,"minvolume":0,"maxvolume":0,"pubkey":"b8c5f621194ffbe5641fecbfbd7ab75bf05574f2becccbcf79ffa9643dc6f163","age":0}, {"coin":"JUMBLR","address":"RVPcbafNSi6uMaKDyss9epGpHCHbbzUFMd","price":7.43406130,"numutxos":0,"minvolume":0,"maxvolume":0,"pubkey":"e1d9ff940bd7fb30954e0d9297053457eb7f766e66da6c198e75c06b7d982124","age":0}, {"coin":"JUMBLR","address":"RQzkkncY8ehpRg8M4kvKmDMcbFxcJvohgk","price":7.43491450,"numutxos":0,"minvolume":0,"maxvolume":0,"pubkey":"30eb3d952f66eba2df0100b97d6707257cf91dc8c8b0237cfb7c3aa70dc52d4d","age":0}, {"coin":"JUMBLR","address":"RMdjuxKBhyr87yhKp6BLUg2p9673NMcPAu","price":7.43772882,"numutxos":0,"minvolume":0,"maxvolume":0,"pubkey":"040f1d2d5d12027afa2cec30477312e225b0d24c77cc4aa08d3fffe51277b904","age":0}, {"coin":"JUMBLR","address":"RT9MpMyucqXiX8bZLimXBnrrn2ofmdGNKd","price":8.01558380,"numutxos":2,"minvolume":24.84830978,"maxvolume":29.81797174,"pubkey":"bab6ad2eebe1e666369cab504d4622b22c1f1ef718ef388e88020f30a1573e01","age":0}],"numasks":10,"base":"JUMBLR","rel":"KMD","timestamp":1509050608}

For 8 and earlier, follow the directions in YourPath/chips3/doc/build-unix.md
 

if you don't want to bother with the berkeley db 4.8 installation, you can also ignore it by using
./configure --with-incompatible-bdb
when building chipsd

Berkeley DB version only matters if you want to have cross client wallet compatible
 (a wallet created with a client that was build on 4.8 may not be usable with a client that was build on another version of bdb)

So if you extracted your privkeys and not planning to copy the wallet.dat for use with another client, you can ignore the dbd version 4.8 and use the version currently installed on your system

These steps only build the headless version (chips-cli, chipsd...), not QT version!
I didn't verified what dependency it needs to. If you want to build QT version, don't put the "--with-gui=no" parameter at the end of these steps.

• sudo apt-get install libboost-system-dev libboost-filesystem-dev libboost-chrono-dev libboost-program-options-dev libboost-test-dev libboost-thread-dev
• git clone https://github.com/jl777/chips3
• cd chips3

Install Berkeley DB 4.8 from source:

• BITCOIN_ROOT=$(pwd)
• BDB_PREFIX="${BITCOIN_ROOT}/db4"
• mkdir -p $BDB_PREFIX
• wget 'http://download.oracle.com/berkeley-db/db-4.8.30.NC.tar.gz'
• echo '12edc0df75bf9abd7f82f821795bcee50f42cb2e5f76a6a281b85732798364ef  db-4.8.30.NC.tar.gz' | sha256sum -c
  (it should display it succeeded)
• tar -xzvf db-4.8.30.NC.tar.gz
• cd db-4.8.30.NC/build_unix/
• ../dist/configure --enable-cxx --disable-shared --with-pic --prefix=$BDB_PREFIX
• make install

Continue with chips:

• cd $BITCOIN_ROOT
• ./autogen.sh
• ./configure LDFLAGS="-L${BDB_PREFIX}/lib/" CPPFLAGS="-I${BDB_PREFIX}/include/" --with-gui=no
• make
• ./chipsd -addnode=5.9.253.195

that's great!
for now, just post here so we have the info for when we make wiki

./komodod -ac_name=JUMBLR -ac_supply=999999 -addnode=78.47.196.146 &
Then you can use fiat/jumblr to invoke the command line the same way ./komodo-cli would be used (from ~/komodo/src)

That's a problem in your machine. 127.0.0.1 is your own computer. Sounds like your Virus program might be redirecting or, a fireware problem or, your DNS resolution is compromised. Better give that machine a checkup asap!

I only hope wasn't a transaction of your. And this also wasn't a notary node.

The blockchain was not under attack, it is similar to a DOS attack at the network level. Still not sure exactly how a killer packet was created, but a fix for the crashing is already updated in github. I estimate about 10% of nodes were affected.

If you are having crashes, just update and it should be fine. We are still testing the hotfix version, but the change was very small so it should be fine.

No funds were at risk, just annoyance of having to restart a node, but if you are in the process of syncing, it would likely make it much more difficult to do so as if it is crashed it wont sync.

They are individual inputs, there can be hundreds or even thousands depending on how many inputs etc you have.