It's working on https://ico.wavesplatform.com/.
Thanks 

I can't login to my ICO account on https://www.wavesplatform.com.
I always get an reCAPTCHA error: "ERROR for site owner: Invalid domain for site key".
Does anybody have the same Problem?

As far as i can tell the nas network/chain is still working fine.
What's still needed are more nodes to secure the network and stabilize it.

In order to connect there are, unfortunately, some things to check:
- If you can't find any node you need to add some peers to the wellKnownPeers in the nas config (using tikers public node or the informations provides in this thread)
- Using the nas Version 1.1.3N2 may help, i think the known peers are added there
- depending of your nas database you may need to rollback to a previous state or start from scratch. The nodes/wallets and database from the exchanges (Poloniex and BTC38 as mentioned)  might have a state where connection to the existing network doesn't work anymore. (forks, broken DB, …)
Last time I checked, 1-1,5 month ago, starting from scratch worked perfectly when connected to at least one of the well known peers.

I'm not sure if poloniex even tried to connect/sync there node. I still have some nas there and till today they tell me that they send/transfered successfully the nas coins. But unfortunately I can't find  the mentioned Transaction on the network, nor did I ever receive the coins. On the withdraw page the transaction is still mentioned as successful and there are no nas left in my account.

 
@CryptoJohn:
What's your nas account? I could try to send you some nas.
Did your account worked before?
Is it a new account?

Hi Kolbas,

PM is out but I'll also post here as well.

I'm also not aware of any problem with the NAS Blockchain. My nodes are running fine and are in sync with the network and Tiker's public node.

It's pretty hard to find a solution to the issue DGEX is having without some more informations.

Here are some ideas, of the top of my head, in addition to Tiker's reply.

# Using the last “Official” Version 1.1.3N1 is fine. There's also the Version 1.1.3N2.

# Don't use the Version 1.1.6N1 as there's a problem with sending NAS
https://bitcointalk.org/index.php?topic=523187.msg11440700#msg11440700

# A list of working peers, if connection to the network is an issue, can be found here:
https://bitcointalk.org/index.php?topic=523187.msg11179394#msg11179394

# If the java Version is a problem:
Try it with Java 1.8, it should work. I'm using Java 1.8 here.
Patapato mentioned something about having forgotten to compile with 1.7 compatibility:
https://bitcointalk.org/index.php?topic=523187.msg11412265#msg11412265
as posted here:
https://bitcointalk.org/index.php?topic=523187.msg11518497#msg11518497

# Quick guide to setup a NAS node as posted here:
https://bitcointalk.org/index.php?topic=523187.msg10804867#msg10804867

I don't know any Blockexplorer for NAS right now, I'd love to have one, but i have no time to implement it.
There's an, maybe better, alternative to a blockchain explorer: the public server of tiker 
A public NAS client/wallet, connected and sync to the right chain.

Try i with Java 1.8, it should work. I'm using Java 1.8 here.
Patapato mentioned something about having forgotten to compile with 1.7 compatibility:
https://bitcointalk.org/index.php?topic=523187.msg11412265#msg11412265

Seems to be the right blockchain.
There should be 2 main forgers on the chain.
You can verify you're client is connected to the right blochchain by using the public server of tiker.
Current block height:327261

The "Unsupported major.minor version 52.0" does indicate runtime Java is older than the Java used to compile the classes.
Try updating your java version.

The genesis Account should be: NAS-MRCC-2YLS-8M54-3CMAJ

https://bitcointalk.org/index.php?topic=523187.msg10544383#msg10544383

Awesome news!  Thanks a lot

@patapato

While i'm at it, there are a few little things wrong in the shell script "*.sh" files for Linux:

- Line endings: the line ending in the script files is "CR LF"(\r\n)[windows line ending] and should be only "LF"(\n)[*nix line ending]

- compile.sh needs also changes, here is what i'm using(should match win-compile.sh):

I think the problem is the default java version used.
I have/had the same problem here on Ubuntu and i have several Java versions installed: 6,7 and 8 (6 and 7 are OpenJDK, 8 is Oracle)
Might be a problem with OpenJDK, not sure if Java 8 is required or an Oracle Java is required(patapato might know more about it).
What i think is that both 1.1.6.N1 and 1.1.3.N2 require Java 8.

Here is what i get in the terminal:
I get:
Using this version(./run.sh in terminal in nas folder) i get:

Using java 8, located here in "/usr/lib/jvm/java-8-oracle/jre/bin/java" it works fine:
I get:
Launching it with the following command:

On Ubuntu(might work on Mint and Suse) i can get the installed Java version with the following:
I get:

You can change the default Java using:
I get:

Hope this helps.

Just a quick update: my second node successfully synced with the current network, from scratch, in one go, only "nas.wellKnownPeers" was set. 

Oops! … I Did It Again 

No, seriously, it was really great teamwork from us three.
I'm glad we did it.

NAS is back on track again 

My main node is connected and forging on block chain fork that the other NAS forgers agreed on.

[User1397367406 make a small wave with his hand] You don't need to see my second node.
This is not the node you're looking for.
...
Wait that's another movie

I'm currently trying to sync a second node from scratch in order to confirm the fork is legit.
Seems to sync all right: block height 87443 and still downloading.
I've put our three node in "nas.wellKnownPeers".
I'll keep you informed.

I tried to sync a client on my main computer, different from my forging node, and ended up with the above mentioned result. I wanted to see what would happen.
I re-started my forging node yesterday and stopped forging on it, it's still there doing nothing, at block 280284   4/7/2015 22:19:56, connected to 4 nodes: funkyvps3, patapato, 99.227.*.* and 106.187.*.*
The blockchain was not reset but i was forging all the block and so maybe i'm on my own fork.


I'll blacklist lcharles node. Not sure if i ever saw his node connected. Should start taking screenshots of the connected nodes and such
I'll try connecting my other client to see what happen, enabling some logging.

I agree on only distributing/leasing a smaller amount of NAS.

I tried syncing a client on my computer from mid march and so far it seems to sync until block 277934 and 277940 :
Blocks after 277934 appearing and dissapearing ...
Very strange thing and it seems we have, again(sigh) a messed up network.

I stopped forging after the re-start.
Right now i only have these nodes connected:
funkyvps3.funkymonkey.org and 99.227.*.*
patapato.ddns.net comes and goes ...

I was forging all the time, just re-started my node as i was forging on my own little fork ;(
The branch might have accured arround block height 279182 as from what i saw i started forging one block after another and still was till now (as far as i could tell from the block list).
The Log doesn't show anything too interesting ...
The log has some of the following:
As far as i can tell, during the last days there where several periodes where my node was forging block after block.
It's hard to tell with the log as there is only the timestamp of a block generated by my node.

I think these messages "nxt.BlockchainProcessor$BlockNotAcceptedException: Generation signature verification failed" are because of my node:
* these IPs resolve to my internet provider
* My IP changes every day as i'm on dynamic IP
* The DNS name for my node is updated periodicaly
* the peer name, of my node, displayed on the client resolves to different IP. Don't know if the client stores also the IPs.
* As my IP changes, depending on the DNS update, blocks generated from my node should trigger these messages as the Signature is bound to the provided host name.

The network is still vulnerable to all kind if things, with only 2-3 nodes.
During the last couple of days i had some periodes where my node forged all the blocks.
Not sure if this was the exact network status or if it synced since then.
A couple of days back i had some similar strange things going on as suddenly the last block list updated itself.

My node seems to be relatively in sync with Patapatos:

That's great news 

My node was offline for the most part today, had to manualy re-boot the modem/rooter in order to connect.
Synced fine with the network.