I'm just learning this myself.  The Reddit site might be a better place to ask questions.
https://www.reddit.com/r/joinmarket/

This thread appears to be about the same card...

https://bitcointalk.org/index.php?topic=792507.msg8941661#msg8941661

I'm hoping they remove the minimal withdrawal limits for the closing to 0 out everything...

Are there any other online wallets like this that offer PoS staking?

Look under:
c:\Users\<profile name>\AppData\Roaming\Ethereum\keystore

There should be 1 file for each account you have.

There's also sites like https://ethereumwallet.com/ which will generate a wallet for you.  This one allows you to download the key which I believe will work with GETH / Mist clients.  I don't know how safe sites like this are so you'll have to determine for yourself if they're safe enough or not.

My pending withdrawals came through last night.  Ads are back as well so it looks like it's working again.

I thought I'd give the ShapeShift to NXT config a try again but it still doesn't work.

It gives "Invalid or Missing Parameters." in the blue box now.

Thanks.  Please let us know when it's working.

The original post for this was made 1.5 years ago.  Not really an announcement any more.

Using the ShapeShift.io feature to convert to NXT doesn't appear to be working.

Setting up for NXT shows a blue area with no text so there's no confirmation that the setup to NXT is successful.  The shape shifting status does not update under the statistics tab either.

I replied to the private message you sent me but I'll respond here as well.

I'm not aware of any problems with the NAS block chain.  Looking at my public NAS node http://funkyvps3.funkymonkey.org:7873/ things look fine.  When I gain access to my private NAS nodes this evening I'll check things in more detail.

Without knowing what the withdrawal issue is that DGEX is having there's not much I or anyone else can do.  If DGEX is having an issue with their node then resetting their node and re-downloading the block chain would fix the issue.  If it's a peer related issue (can't find peers to connect to) then inform them that my public node can be used.  It is open for all to see and abuse.  If DGEX is removing NAS from their exchange and do not want to spend time trying to resolve their issues to process withdrawal requests, they can send their transactions to my public node as well.

If the other exchanges are disabling deposits then it's their own choice.  I've sent BTER my contact details a couple of times several months ago and they have not attempted to contact me yet as far as I know.

I'm not aware of any NAS related blockchain issues so there's not much else I can do to fix an issue.  If the exchanges are having issues and want assistance, have them post here and I'll see what I can do.

Also remember, sending any coin from exchange to exchange directly isn't a good idea.  You should always withdrawal from an exchange to a local wallet then deposit to the next exchange.

Is there a minimum deposit required?  Just playing around I sent a few DASH transactions from a faucet to my address.  I received a bunch of messages in the HZ wallet saying a transaction was detected and assets will be transferred once confirmed but the assets haven't been sent.  The first message was sent July 3rd so it's been a couple of weeks.

Excellent.  I'll wait for the update then. 

Thanks.

Any plans to to submit a pull request to the official Coinomi to add support for this coin?  There's really no need to start running multiple Coinomi apps just to have support for one additional coin.

There is also a .txt file in the ChangeLog directory inside the .zip files with the same information.

The new GUI doesn't look too bad so far.  It's functional and it's not using a font that hurts to read.

Please keep working on this personal project.  It's 100x better than the official client. 

I've registered.

Username:  tiker

Thanks.

There is no reason to run NAS on Java 1.8 as far as the code & features go.  The only reason we say it now is because Patapato compliled NAS 1.1.3N2 and 1.1.6N1 (NAS with NXT 1.1.6 patches) from his own system using Java 1.8 which makes it a requirement to run.

If you have Java 1.7 and don't want to re-compile the code, use NAS 1.1.3N1.

If you have Java 1.7 JDK and want to compile 1.1.6N1 yourself to run on 1.7, you can find the sources here - https://bitbucket.org/patapato/nas/overview

Ask Poloniex to use my public NAS node as a block explorer - http://funkyvps3.funkymonkey.org:7873

Login with any random password, click on "Blocks" from the left column.  This will show the recent blocks on the NAS chain.  There really isn't a need for a block explorer for NAS because it's built into the client.

If Poloniex needs some sort of referral or public agreement that my public node is correct; ask them to read this thread.  There a few posts in this thread from people referring to my public node as a node to reference when checking for a fork status, well known peer to connect to, etc.

User1397367406's message a few posts up is an example.

(I'll email them as well when I get a few minutes so they can ask me any questions they might have about the resurrection of NAS.)

Edit:
Hrm.. now that I've re-read the response from Poloniex, perhaps they're looking for a method to compare the transactions from their wallet(s) to what is on the current public chain.  The built in block explorer might be a bit too limiting for this unless they're willing to search for each transaction by transaction ID assuming they have that information.