Topic: NXT :: descendant of Bitcoin - Updated Information - page 1754. (Read 2761645 times)

To be fair, it should comfort you to know that the exchange is well capitalised and, thus, won't default on your deposits.

Or. You 3 are simply so terrified by the cost of the change, your brain starts malfunctioning when it comes to this issue.

I see you keep saying that since transaction is/will be signed on the client, no checksums are needed and this is bullshit!

This is not even a bias, it's a full-blown delusion.

I don't know what to do here and how to get through. We need a professional shrink.

I'm finally out of dgex.com (still had BTC in the account, bought NXT and got them out after "just" two days) and I am out of buying and selling NXT as long as there is no alternative exchange. (Please no Peercover/Ripple/Private Escrow follow-ups... Thank you.)


Allow me some final words regarding dgex.com.

1.) GCInc, thanks a lot for your service over the last weeks. I think the dgex exchange was very important for NXT and you did a good and brave job with setting it up and running it.

2.) GCInc, you are a thief. You've just stolen around US$20 from me and the service you provided for me over the last weeks is worth more than US$20, but still you are thief. It feels like a friend asked you to borrow some money from you and when he pays back, he tells you that he changed his mind and only pays you back 99% of what you borrowed him. You totally lost credibility with your move to change the fees without previous notice, thus I am out of dgex until its under new management.

3.) I came for the quick profit - I stay because of the very cool community. With this NXT community there were other ways to "cover your ass". While you still had a reputation for what you've done for NXT you had a good chance to explain why you lost 800.000 with your exchange and ask for help from the community. After following here over the last weeks, I am convinced you would have gotten help from us.

4.) "Third in command"? This is a PR disaster... Unfortuntely, your way of managing dgex and answering only questions that you think you have good answers for makes me fear that this is in fact how you see yourself. I don't want to make business with you having the feeling that you are the boss and not that were a business partners.

5.)

Well, nobody else jumped onto this, but this was the point when all (remaining) alarm bells began to rang. What you basically said was that we have an exchange that is run in a way to have a NXT market value that the exchange owner is comfortable with. WTF??? So, because you still have 800.000 NXT missing you have an interest in low market values and you actually run the exchange in your interest. This is just beyond me... And it is totally beyond me that anyone still uses dgex after your sentence above.

20 hours right now (after 0.5.3 update)

_{512Mb RAM}

Max 10 hours. Never generated a block, allways error.

@0.000047?

NxtPool - first forging NXT pool
https://bitcointalksearch.org/topic/nxt-nxtpoolcom-first-forging-nxt-pool-161-knxt-closed-406331

And:

http://wiki.nxtcrypto.org/wiki/Nxt_API
https://bitcointalksearch.org/topic/nxt-api-of-nxt-313082

http://localhost:7874/nxt?requestType=getConstants

Is anybody willing to sell me 360k Nxt @ 0.000045?

There is no liquidity on Dgex..

If a transaction is confirmed then enough.

I got no reply on my question regarding account to send the reward to. Could u contact the owner and ask if he needs 20K for the 3rd place in Exchange category?

Ok, I'll tell u. We have plans that will make CRC on server side unnecessary. Can't tell u more right now.

Future clients will sign transactions by themselves. Sending a secret phrase to a remote node is insecure. That's why input should be validated on client side.

Each post should has its own link url in this forum and we can exactly locate the post. For example, you post should be link https://bitcointalksearch.org/topic/m.4401865

Edit: I also summarize a post for Nxt Client Update Link and see my signature.

I converted .pem to openssh format. As said here it was not even needed. "note: PEM private keys are OpenSSH's native format for protocol 2 keys"

Check the username. For ubuntu default is "ubuntu"

My client is doing the SAME thing... but it only happens after my client has gone into the "negative recent blocks" and "thousands of unconfirmed transactions" phase.

I have to limit my reading on this forum, my paranoia is just under "don't trust the doctors."

OK trying out the amazon free EC2 VPS... Now im no stranger to SSH key authentication, Ive got 12 VPS doing it now.  But this amazon shit dont work... it doesnt like the private key they gave me... Dont even see anywhere to go to ask them to reset it either.

what next?