NXT :: descendant of Bitcoin - Updated Information

[Come-from-Beyond]

You're killing me!!!

[podyx]

You're killing me!!!

lol

isnt there any way to send nxt to solaris though?

[lucky88888]

No wallets are coming out. We at nxt only uses passwords/passphrase/brainwallet
Type in anything in the nxt client after pressing the unlock button and it will be your account, remember to use a really long (30characters/symbols+) jiberish password that makes no sense and write it down somewhere. I printed mine out. If your password is hellothisismypassworditisreallylong then your nxt will be stolen in less than a minute after depositing. Make your password something like helLo101this*(*ismy*(&$^&pass<><.,;'{word31it(*&isHJHreally+_+{LonG&**

so which client is it then? i had about 5 clients thrown at me and none of them work/are useless

If you're on Windows, the link in my signature is to my Windows Installer for NRS.

doesnt work either..

Do you use apple computers?

no windows

Did you try the link i post before which is this one.. http://www.mediafire.com/download/51ipys4v4rblbvd/Nxt_0.6.1_Web_Setup.exe

yea, that was the one i just tried

What didn't work? It's been downloaded and installed over 3,000 times without much of an issue.

when i launch it, it just comes up a black screen which closes after

well here is the ultra hard installer, but it works everytime. if you get this one going you will be rich.
http://download.nxtcrypto.org/nxt-client-0.6.1.zip

[Jean-Luc]

fresh 0.6.1, blocks stuck...

Edit: I guess, we will upgrade to 0.7.0e then

You are on a fork, just look at the huge % target numbers. No need to upgrade to 0.7.0e, but you have to delete the .nxt files and start again.

[opticalcarrier]

Has anyone put together a guide for configuring web.xml to run a public hallmarked node?  It's been so long since I configured my web.xml.  For example, should I change the value of "myport" to 7875 if I'm using 7875 to connect to NRS?

hallmarks are in the wiki under how to

most likely no reason at all to change myport.  you should leave that as is at 7874 and can still connect to NRS on either 7874 or 7875.  myport is the p2p port the client uses

[Come-from-Beyond]

Yay! Stress-test is over! Back to work...

[TwinWinNerD]

Yay! Stress-test is over! Back to work...

You got enough coffee and redbull?

GOGO!

[fmiboy]

fresh 0.6.1, blocks stuck...

Edit: I guess, we will upgrade to 0.7.0e then

You are on a fork, just look at the huge % target numbers. No need to upgrade to 0.7.0e, but you have to delete the .nxt files and start again.

right, will do... thanks

question though, about future feature...
so with 0.7.0e and onwards Are we taking steps to implement blockchain pruning?

[msin]

Has anyone put together a guide for configuring web.xml to run a public hallmarked node?  It's been so long since I configured my web.xml.  For example, should I change the value of "myport" to 7875 if I'm using 7875 to connect to NRS?

hallmarks are in the wiki under how to

most likely no reason at all to change myport.  you should leave that as is at 7874 and can still connect to NRS on either 7874 or 7875.  myport is the p2p port the client uses

Okay, got it. thanks.

[pinarello]

[Come-from-Beyond]

@ AE client devs:

Do u need more APIs? Tomorrow I'm going to download a lot of new code into my brain so I won't be able to pay attention to other things. Post if u need anything urgently.

[Come-from-Beyond]

ROFL

[wesleyh]

You're killing me!!!

lol

isnt there any way to send nxt to solaris though?

You send nxt to an account ID, not to a client...

[mthcl]

 Also, would be great to have a "setting up hallmarked node" section in the wiki, can't seem to find it.

It should be somewhere in the wiki. At least I recall translating it a few days ago.

[google98]

Which elements will be implemented in NRS 1.0? Any roadmap?

[pinarello]

lol

isnt there any way to send nxt to solaris though?

go watch some videos.

https://www.youtube.com/my_videos?o=U

[msin]

 Also, would be great to have a "setting up hallmarked node" section in the wiki, can't seem to find it.

It should be somewhere in the wiki. At least I recall translating it a few days ago.

Found it, thanks.

[marcus03]

@ AE client devs:

Do u need more APIs? Tomorrow I'm going to download a lot of new code into my brain so I won't be able to pay attention to other things. Post if u need anything urgently.

For the record: I havn't even looked into AE.

[msin]

Haha, Pin, good one.

[Mistafreeze]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Release 0.7.0e - experimental

http://download.nxtcrypto.org/nxt-client-0.7.0e.zip

sha256: aa778bade323d2b3f4cf13c925aa7b541d57f0853a5828385b72254ac92010bc

Change log:

This is the first release using an embedded java database (H2) to store
the blockchain, instead of serialized java object files. Because this is
a major change, this version is to be considered experimental.

The blocks.nxt and transactions.nxt and .bak files are no longer used.
Furthermore, they will not be loaded at startup, when you start with
empty database the very first time it will need to download the full
blockchain from the network.

The database is stored under the nxt_db directory, as of now it will
take around 100 MB when downloaded. If anything goes wrong and you need
to start fresh, it is safe to delete that nxt_db directory, it will be
recreated.

There are no changes in the web.xml file compared to 0.6.1. I will add
parameters to tweak database settings later, if needed.

The database will use 50% of the memory available to java for its cache.
The actual value is printed out at startup.

Currently only blocks and transactions are stored in database tables,
everything else such as accounts, aliases, assets, orders, messages,
is loaded at startup and then kept in memory. The amount of memory
those take is still small, relative to what was needed for all blocks
and transactions.

At startup, the blockchain scan takes a bit longer, this is normal.
If anything else is unusually slow, I will look into profiling and
optimizing it.

There are no new user-visible features compared to 0.6.1, the code is
kept in sync now (including the critical bugfixes). Having both 0.6.1
and 0.7.0e nodes on the network should not result in forks. I will
maintain both the 0.6.x and 0.7.x branches for some time, until all
major database related issues are discovered and fixed. Please report
bugs, including the stack traces.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBAgAGBQJS88S2AAoJEFOhyXc7+e2A45IP/j6Wy+UrJ3BTipd6ddcvtXuG
3CuNxP5XXZn56dW5/2CS9dWKLNUSaaQr6GV2z/bEVOQBZQ3XPkX6MYQaKucInDOC
LltAh6pvHN/plP/ll+Wlglwu3k/qM193hfFezAvXwJNiHym/NanYp9HRJRF8DJmz
ZB3J/Qr1K91+9mWUNd0kMXv9IhgOHMoP+CWOrAoefTk/7XNH9pOBDdi5uUHP0gtF
4O6kis5HVkICIVkHGNi8rdED5z6drQFYpnwm5OG0CONK9fUatymSRjUPy0PHd+aI
MRxihtfV05gRIhBOtrMre2WYbSTBCDL0ITy0b4ejtYW7WU2TC7bW8Gk10o6DjSbx
inOWUm5EWs1MbebpERskjVd8cLLc8EgGtBpuEs8XPmzNiWw7ma5msUpnbPFWF5hT
nYSOgmGzY5MsTaFLzGARXFm3xv52JS0mM+catOOCKyHH/+1geJXjkbyK5eVgtshJ
5TxdnUA/LjX73bAVJOtOJlULFHwzrnKfl26qGoZRwR9gSJRLEoeA8yW5Wv2Bnx9N
2fwkVy9cfTeZTerVe0r0SfxywqmDMG3Og+9GhxLD3qE58aolRC3yOZZnh1xspT+s
LI1j3Q6GbaR7Mb5QXbrs2qtxDRjdnrmg/4CkhTAmAku1nBFtgeCXJY/wgtxGH+BL
Q4q/PI4rf99LkSxbe2l+
=TssU
-----END PGP SIGNATURE-----

So when I do my installer for 0.7, is it going to cause any issues if I include the nxt_db folder as I include blocks.nxt and transactions.nxt now?