Topic: NXT :: descendant of Bitcoin - Updated Information - page 2206. (Read 2761629 times)

- may be you opened your new account with freshly bought NXTs (they need to mature)?

For now, when there is a lot of blockchains and a few hosts, re-downloading it is good idea. You most probably get most popular chain.
In future, ofc, it is better to save previous one

Working on node infrastructure with a full redesign of nxtbase to support 100+. I won't open source my new management stuff for a bit, but here's a handy one for you VPSers running ubuntu.


Then copy file like this to /etc/supervisor/conf.d/nrs.conf:

Replace $MIN and $MAX with your memory limits. Replace $USER with your user. The run:

Now, what do you get for your efforts?

Restart on crash
Restart on reboot
handy commands for start/stop/restart/status (sudo supervisorctl CMD nrs).

Cool huh?

Is it true that the only way for someone to get their first NXT coins would be to purhcase them or be given them? Since there is no proof of work system? I understand that you can forge more once you own some, but how do you get your initial NXT ?

What values would you advise for the above cases? I am not a java expert, so any suggestions are welcome.

what does it mean when my unlocked client is seeing new blocks (i see 24010 at 332%) but no countdown timer to forge next block?

Ah, one more point on this guide - which otherwise I like, sorry I'm being picky

If a server has 512MB RAM then a max heap size of 480MB is likely to be too large. There is the perm gem to think about (currently something like 20MB, but could go higher if more is added to the distribution), plus general memory used by the Java process itself, plus anything used by the OS and any other applications you have running. Setting a heap size such that Java needs to write to swap normally results in bad performance.

Same for the other values.

With the latest 0.4.4 release my client seems to have gotten stuck and isn't grabbing blocks. It just gets block 0 then seems to stall. There are no peers listed under active either. Tried deleting blocks.nxt, any other ideas?

Edit: Hmm, working now but took a few restarts

Well, I guess you have valid points, but at this time since the blockchain is small, that'll do I guess.
Or maybe it's really best to copy the files.
Let's ask CfB

It's a nice guide. But to reduce unnecessary traffic on other nodes shouldn't we aim to keep the existing block chain as part of the upgrade process?

(At least, when it's a clean upgrade that isn't due to a corrupted block chain. I've sometimes seen NPEs in the logs which could only be fixed by starting from zero or from a known good partial block chain).

So - that would mean:
 - Graceful shutdown, rather than kill -9
 - Copying over the old block data after unzipping

Also, a 'verify shasum' step is optional but should be encouraged...

Thanks for the donations guys, i'll add 2-3 nodes tomorrow.
512mb vps are working well

To explain further, the NXT you earn from forging comes from transactions. The more transactions there are on the network the more NXT available for forgers to potentially grab.

Right now since it's a very new project the transaction volume is low. As network transaction volume increases forging will become more lucrative.

That is my understanding of it

I hit a block that paid 77 during a couple of hours after alias system launch. There was a block with more than 200K in fee.

Only when the transaction pick up that the forging income become relevant. It is proven at alias launch that even small stack at 50k-100k could have a chance of hitting a substantial block reward. Imagine even more transactions when Nxt network activity scales up as market for alias transfer and asset market begin to work properly.
Don't give up, the future is bright with Nxt.

Is anyone else having more luck?

in terms of mining, its still way to early to worry about it. there are very little paid transactions going out. I have 250k and have tried to be open for the past two weeks, but I have mined 2 blocks and earned 1nxt

http://87.230.14.1/nxt/nxt.cgi?action=3000&acc=15436509232181115695

How to upgrade your NXT node guide.

Step 1) Log in to your node using Putty (user 'root' and pass that your received in the welcome email from your VPS company).

Step 2) Enter the following commands in the terminal:

1) 'top' command, it will show a line similar to this for 'java' process:

2973 root       20   0 1166m 428m  10m S   0.0 41.8   9:57.51 java


2973 is your process ID.


press 'q' to exit top;

2) kill -9 2973      (kills the java process, enter your 'java' process ID number instead of 2973).

3) cd    (switch to your home directory);

4) rm nxt.zip   (delete the old nxt.zip file);

4a) rm -rf /root/nxt.old   (this removes the old nxt working directory if it's not the first upgrade you do);

5) mv nxt nxt.old   (rename the old nxt working directory);

6) wget http://download.nxtcrypto.org/nxt-client-0.8.9.zip

7) unzip nxt-client-0.8.9.zip

8 ) cat ~/nxt.old/webapps/root/WEB-INF/web.xml  
(this lists the contents of the old config file, copy-paste your myAddress and myHallmark parameters from it into a text file on your PC, if you hadn't saved them earlier.

9) nano conf/nxt-default.properties

a) in the section  ###PEER NETWORKING ###, find the following lines:

put IP address you got from the host.

It should look like:

nxt.myAddress=x.x.x.x

b) if you use a hallmark on your node, put your hallmark there (make sure no whitespace character is left in it when you copy-paste it)

press CTRL+X and then Y to save the file.


a) If your VPS has 512 MB RAM, replace the line:

java -Xmx1024M -cp nxt.jar:lib/*:conf nxt.Nxt

with

java -Xmx450M -cp nxt.jar:lib/*:conf nxt.Nxt

b) If your VPS has 1024 MB RAM, replace the line:

java -Xmx1024M -cp nxt.jar:lib/*:conf nxt.Nxt

with

java -Xmx800M -cp nxt.jar:lib/*:conf nxt.Nxt

-----

press CTRL+X and then Y to save the file.

12)
13) run  to show running processes, check that you see process 'java' running and using CPU and RAM, if it is, then press 'q' to enter 'top'.

14)

Got another high-speed, hallmarked public node up an running at 109.230.224.65 (Germany, Europe).

Feel free to use it in your XML config, if you so desire.

Digitalocean.
4gb are useless looking the work, especially if they are not-hallmarked
now i'm paying 30$/months, 3 with 4gb will cost to me 120$/months, it's a bit too much i think

Bubble incoming!

Are we ready for the next wave of zombies attack?