Topic: | Nxt | Blockchain Platform | Proof of Stake | Official - page 182. (Read 941260 times)

The NXT client will also give you an invalid address warning if you try to send to a BTC/whatever address.
Try talking to Cryptsy support....or otherwise, just check the withdraw address next time.

so i bought some ntx this week

1st withdraw all ok

but 2nd  not really sure what i did  but  i did not see them coming on my wallet

so i check crypsty transaction    what did i see     i sent my nxt to my bitcoin wallet  lol  who did i do that ?

i guess the coins are lost now

i always do cut and past for the adress, i guess i used bitcoin adress before i cut & pass  nxt adress in cryptsy

but why did it accept an adress what is not a nxt adress
if you put a litecoin address in a bitcoin wallet, it say it s not valid adress so you cannot make mistake

so i bought some ntx this week

1st withdraw all ok

but 2nd  not really sure what i did  but  i did not see them coming on my wallet

so i check crypsty transaction    what did i see     i sent my nxt to my bitcoin wallet  lol  who did i do that ?

i guess the coins are lost now

i always do cut and past for the adress, i guess i used bitcoin adress before i cut & pass  nxt adress in cryptsy

but why did it accept an adress what is not a nxt adress
if you put a litecoin address in a bitcoin wallet, it say it s not valid adress so you cannot make mistake

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Release 1.6.2

https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-client-1.6.2.zip

sha256:

954125b60578120dc32fac774eb923efe65ff046f31b1c8f29eab94349850ee3  nxt-client-1.6.2.zip

https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-client-1.6.2.jar

sha256:

6e7c77bd601783779aef72cd42ea04086698e7e921abf49aedb4ab9dab513427  nxt-client-1.6.2.jar

https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-client-1.6.2.exe

The exe and jar packages must have a digital signature by "Stichting NXT".


Change log:

The 1.6 series is no longer considered experimental. If upgrading from 1.5.15
or earlier, see the 1.6.0e and 1.6.1e changelogs for other important changes
in 1.6.

The account ledger now uses transaction id as event id for all events except
block generation. To apply this change, the account ledger table will be
automatically truncated on upgrade to this release. Users who desire to
restore the deleted past account ledger entries should run a full rescan from
the API test page. Note that account ledger records are only kept for 30000
blocks by default.

Added currency transfers history page to the Monetary System UI.

Added generate hallmark dialog to facilitate hallmarking your node. The host
field is pre-populated with the external node address as detected by UPnP.
Note that when using dynamic IP address you should set up and use a dynamic
DNS hostname instead of the numeric IP for the hallmark. And when using a
non-default port, the host field should be filled as host:port.

Added "clear results" link in the ShapeShift My Exchanges section, to allow
clearing past transaction history. As this history data is being retrieved
from the ShapeShift servers, it allows correlating Nxt accounts previously
used for exchange transactions with the current user IP address and with each
other, thus clearing history after no longer needed is important for the user
privacy.

Funding a new account using ShapeShift now relies on the ShapeShift sendamount
API which provides better conversion rate. The user first specifies the
amount of NXT to receive, the dialog then presents a deposit address for the
source currency which the user needs to fund with the exact amount within 10
minutes.

Added ledger tab to the account info dialog.

Added includeAssetInfo or includeCurrencyInfo parameters, default false, to
the getAccountAssets, getAccountCurrencies, getAccountExchangeRequests,
getExpectedAssetTransfers, and getExpectedCurrencyTransfers APIs.

Tabs are now sorted mostly alphabetically on the API test page.

Added nxt.hideErrorDetails property, default false, to allow suppressing node
specific configuration details in error messages returned to peers.

Increased default prunable lifetime setting to 90 days. Minimum enforced is
still 2 weeks.

The UPnP connection timeouts are now also configurable in nxt.properties.

Updated Bouncy Castle library to version 1.53, Jetty to version 9.3.5, IzPack
installer to 5.0.5, and weupnp to 0.1.4. Make sure to delete the old lib
folder if unpacking over a previous installation.


-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJWNQgzAAoJENqvaxkWiP4ZbrsP/i9jXuuaXoMx7+d6DOwPG9Z+
AUktpye5SXhbQvSDJQhQ2L4FSto1X6gbBuGGVaoHA5M+N5IN1GydTTYe9s2B9G8Q
wFZD5+WFzDM54ygv0JC2to8Ns8LU9/b9VIWqSczzdzYPQ+mbmMYXcglkgz70zgbM
yAwK5MbyO/sDiW8BE9QiyEgF6TvolbJT0GgdKb4wvOPuRJ9mx0zDVU0TA/W5zT5k
Xo1RxuDqqt97i0uaFVr29IGXnsJaxC5Pj1f7BjlHa9+cUmyBcIkbGMlA587grGzv
CV7gmG/tAh57wi6CY0yyQD23mzj54cS44Yi09Xz3kESkpIM5YkPiQ+D6/0uIU4Pb
PjKaNgCqv4CpjSC3iA7+qWENg8knZ0xdfTUgxIldOJHiZhhcq5qYRBpC/pKFIbpl
rsTceTZWUfITc1pCyh7QjlcrX1ZgzhpspvCFoTtJ3firESCcSZynp0W5IC0oaRxD
xvZSkso5b55y4iQT1TNMMESse8DVAqwBDDdsKhdX6OJCQohC5Tjw7xUamWzoXkZe
xWf1bMgYHPZKpViBWBc3UiN3Zj0T7jVwPkhWFK+QB9fj1QgdJDV2WOX+QwyiGZy4
WKKKI3TJ8FZzu1knJUECagffdfFt4P7tJK3XHtep7n0Df6UNX6XamWlJnnB3uiBb
1aSre/dZrGCWQNO06tuc
=6NJp
-----END PGP SIGNATURE-----

The next steps in Tennessee are starting to take shape:

Marketing/PR.
Part of the overall strategy for NXT/SuperNET PR is going to be aimed at putting a human faces (or faces) on the Nxt community, both removing the 'anonymous=evil' image problem that Nxt has, and giving people some other people that they can relate to.
Most effective marketing is not about the product itself, but is about how people interact with and use the product, and if we are to use this strategy for Nxt/SuperNET......we need people to stand up and be seen.

So, what I need is for people (particularly project leaders) to step up and write a short profile of themselves and their projects:
https://nxtforum.org/nxt-promotion/%28tennessee%29-an-overview-of-nxt-people-and-projects-help-needed!/msg198230/#msg198230
The profile doesn't have to be well-written, we can always tidy it up, but it does need to contain solid information and links.
I'm quite happy for people to remain anonymous, so you don't have to publish your real name, a profile under your forum handle will also be acceptable.
Though, obviously, for this strategy, we do need a reasonable number of non-anonymous profiles.
Get writing, please......

Client Development
The second thread of the TNSSE project is to help make the user experience for NXT/SuperNET as simple and user friendly as possible.
We've identified a  number of things that we can do to help out, and one of the first steps is to set up repositories for popular LInux distros:
https://nxtforum.org/nrs-client-development/%28tennesse%29-linux-repositories-for-nxtsupernet-software/
Non-crypto Linux users are a perfect market for Nxt, and for crypto in general. I've seen how Ethereum have handled Linux distributon of their client software, and it it's very professional and market orientated. We need to do the same.....

Tweeted!! 

Tweeted!! 

I have updated the Nxt Technology Tree OP with the current development roadmap (subject to change, if required) and walkthrough videos.

Check it out: https://bitcointalksearch.org/topic/nxt-development-discussion-the-dev-plan-that-keeps-on-delivering-831202  

In my opinion NXT is up because BTC is up, not because of Tennessee.

Not many coins going down these last 7 days, according to http://coinmarketcap.com/currencies/views/all/
But then have a look at http://coinmarketcap.com/currencies/views/all/#BTC.

NXT is up +5.84% for this week, look like the Tenessee operation is working!

It's exciting because Bitcoin is hitting new highs too! Looks like the good cryptocurrencies are differentiating eachother from the bad.

as a follow-up to my last post:

I ran diskdigger & recuva looking for the pass & tried every combination I could think of for the password to NXT...-FUB36.
Results = a lot of wasted addresses formed and no access to -FUB36.

So far no donations to help recover the 5k NXT lost   Understandable, but surprising none the less...

I don't understand what you mean when you say there were 2 addresses available. If you created a new account, after saving and re-introducing your automatically generated passphrase you will access the dashboard for the account you just created. Where did you see two addresses?

In any case, if you were able to get in the client the public key for your new account (which is not required, just an optional safety belt for the first transaction) that means you logged in using the account passphrase. So you should be able to access the same account again (NXT-ENWW-SPH8-RELM-FUB36). The client will only give you the public key for a new account if you log in using your passphrase, so it does look like you have the passphrase for the account where you sent the NXT.

Maybe you're overlooking the button in the left of the client login field? In 1.5.x you have two ways to access the client, by entering a NXT Account (which will open it on the dashboard, but of course you won't be able to do anything with it unless you also got the passphrase - otherwise it is like a built-in explorer) or if you click on that button, you'll see it switches to a key icon and shows Your Passphrase field. Perhaps you're entering NXT-ENWW-SPH8-RELM-FUB36 passphrase in the Account field, which happens to translate to  NXT-WE6V-Z3LC-V8VM-FRTG5 as it is interpreted by the RS format parser?

If that's the case, just make sure to introduce the passphrase with the "Key" login mode, and you'll go back to NXT-ENWW-SPH8-RELM-FUB36 where you sent your NXT.