what's the best way to get some Nxt coins? any exchanges?
btw my address is
24730343118596591
Topic: NXT :: descendant of Bitcoin - Updated Information - page 2514. (Read 2761645 times)
Well, good news my VPS has been running the app with no crashes since the last update and the block number seems accurate.
The only problem, one that I haven't been able to resolve, is the blacklisting of peers. I've got 8 Active peers and 41 Blacklisted. Is there any way you can quickly implement something to periodically clear the blacklist? I've got a clock sync running on a cron-job to periodically sync the clock, this didn't help.
These are the only ports I have open: 7874, 7875, 80 (forwards to 7875) all TCP.
The only problem, one that I haven't been able to resolve, is the blacklisting of peers. I've got 8 Active peers and 41 Blacklisted. Is there any way you can quickly implement something to periodically clear the blacklist? I've got a clock sync running on a cron-job to periodically sync the clock, this didn't help.
These are the only ports I have open: 7874, 7875, 80 (forwards to 7875) all TCP.
If I wanted to get involved in Nxt, realistically how many coins would I need to purchase to start mining?
Somewhat of a complicated answer...
Technically, 1 coin... However I think it would take you 1902 years to mine anything. (this is based on the chance of Mining a block is YOUR # OF COINS / TOTAL NUMBER OF COINS (1 Billion)... and there are 1440 blocks mined in 1 day...)
Ok, so lets look at if you had 1 Million coins.
You would mine 1.4 Blocks per day.
BUT a block Value = Only the transaction fees of Transactions occurring in that block. (The majority of which at the moment are ZERO)
The more Coins each person has, the less people that have coins.
The less people that have coins, the less the coins get used, and thus the less they are traded.
The less use they have, the less value they have.
The less they are traded, the less transaction fees.
So which would you prefer??
To have 1 Million NXT, and mine 1.4 Blocks/day... but the 1 Million NXT be worth less than 1 BTC, and the 1.4 Block that you do mine, be lucky to be worth only 1 NXT.
OR...
Have 10,000 NXT and mine 5 Blocks/year... but the 10,000 NXT be worth 10 BTC, and the 5 Blocks that you do mine, have 1000 NXT in each block??
If I wanted to get involved in Nxt, realistically how many coins would I need to purchase to start mining?
1 Million.
damn thats about 1.1 btc on the exchange
I haven't been able to send more than 1/10 transaction attempts since 0.2.17 was released.
I've tried deleting all nxt files (sorry, it's not something I do on a wim), reinstall NXT, and reinstall Java. Nothing seems to help.
And I keep getting errors:
I've tried deleting all nxt files (sorry, it's not something I do on a wim), reinstall NXT, and reinstall Java. Nothing seems to help.
And I keep getting errors:
Nxt uses direct memory buffers for networking part. If Nxt requests such a buffer JVM takes space reserved for heap and gives it to the buffer. After the buffer is no longer needed JVM "forgets" its reference but reserved memory is not claimed immediately, it depends on OS internal mechanisms. After a while this chunk of RAM can be used again, but if the flow of requests is very intensive, then JVM simply runs out of free memory. That's why we can see a lot of "Not enough memory/heap" errors and NullPointerExceptions.
Could Java gurus confirm this, please?
If I wanted to get involved in Nxt, realistically how many coins would I need to purchase to start mining?
1 Million.
The high CPU load after running the browser for some time is a separate problem, but it has nothing to do with java, this is a javascript issue in the client (i.e. in the browser). I also have to restart firefox on my desktop because it gets slower and slower after a while, even though I run the Nxt java process on a separate machine. So don't blame java for this at least.
I didn't blame Java for the high CPU load. The edit was related to build 17 (build 15 had no high cpu usage), just didn't want to clutter the thread with an extra post. I blame Java only for the horrible memory management. About any Java Windows program I've used tanks out after 1-3 days with some memory issue. Even on systems with 16GB ram and 10 GB free all the time.
If I wanted to get involved in Nxt, realistically how many coins would I need to purchase to start mining?
Woah, seems like we have some issues going on here now. My client is showing a balance of 0.00 in the top right header, transaction count jumped around on loading localhost. Blocks section is showing -4399 blocks and 4459 orphaned blocks
Remove all *.nxt files and start the client again.
Thank you, that fixed it.
It's not related to the OS, it's just Javas crappy memory handler.
edit:
With Build 17 Chrome has 80% CPU usage on Core i3 when the client is open on localhost.
The high CPU load after running the browser for some time is a separate problem, but it has nothing to do with java, this is a javascript issue in the client (i.e. in the browser). I also have to restart firefox on my desktop because it gets slower and slower after a while, even though I run the Nxt java process on a separate machine. So don't blame java for this at least.edit:
With Build 17 Chrome has 80% CPU usage on Core i3 when the client is open on localhost.
What is the difference between the windows Client and the online wallet http://88.198.210.245:7875/? Did I just need a Password to access the wallet? what is of different people use the same password (secret phrase)?
Woah, seems like we have some issues going on here now. My client is showing a balance of 0.00 in the top right header, transaction count jumped around on loading localhost. Blocks section is showing -4399 blocks and 4459 orphaned blocks
Remove all *.nxt files and start the client again.
Woah, seems like we have some issues going on here now. My client is showing a balance of 0.00 in the top right header, transaction count jumped around on loading localhost. Blocks section is showing -4399 blocks and 4459 orphaned blocks
java -Xms512m -Xmx1024m -cp Nxt.zip Nxt
Tried that then it reset back to 0
then tried the normal java -cp Nxt.zip Nxt but it cancelled saying block was broken. Had the NXT block\accounts etc zip u posted though and built from there using the normal java start up command.
Tried that then it reset back to 0
then tried the normal java -cp Nxt.zip Nxt but it cancelled saying block was broken. Had the NXT block\accounts etc zip u posted though and built from there using the normal java start up command.
These things r not related. It's still better to run with Xms/Xmx options.
java -Xms512m -Xmx1024m -cp Nxt.zip Nxt
Tried that then it reset back to 0
then tried the normal java -cp Nxt.zip Nxt but it cancelled saying block was broken. Had the NXT block\accounts etc zip u posted though and built from there using the normal java start up command.
Tried that then it reset back to 0
then tried the normal java -cp Nxt.zip Nxt but it cancelled saying block was broken. Had the NXT block\accounts etc zip u posted though and built from there using the normal java start up command.
, it depends on OS internal mechanisms. After a while this chunk of RAM can be used again, but if the flow of requests is very intensive, then JVM simply runs out of free memory. That's why we can see a lot of "Not enough memory/heap" errors and NullPointerExceptions.
Could Java gurus confirm this, please?
Could Java gurus confirm this, please?
It's not related to the OS, it's just Javas crappy memory handler.
edit:
With Build 17 Chrome has 80% CPU usage on Core i3 when the client is open on localhost.
Is there any Build newer than .15?
.17 - https://dl.dropboxusercontent.com/u/67242472/Nxt.zip
3 API requests were added and a little changes in the interface (transaction id is visible now).
Win7 x64, JRE 7.
Deleted all *.nxt files, run the client. Launched with java -Xms512m -Xmx1024m -cp Nxt.zip Nxt
It did catch up to the latest block. But few minutes later it's at 0 blocks again and this error is given:
[2013-11-29 22:41:28.814] Saving blocks...
[2013-11-29 22:41:29.001] ...Done
Exception in thread "pool-2-thread-4" java.nio.channels.WritePendingException
at sun.nio.ch.AsynchronousSocketChannelImpl.write(Unknown Source)
at sun.nio.ch.AsynchronousSocketChannelImpl.write(Unknown Source)
at java.nio.channels.AsynchronousSocketChannel.write(Unknown Source)
at Nxt$4.completed(Unknown Source)
at Nxt$4.completed(Unknown Source)
at sun.nio.ch.Invoker.invokeUnchecked(Unknown Source)
at sun.nio.ch.Invoker$2.run(Unknown Source)
at sun.nio.ch.AsynchronousChannelGroupImpl$1.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
After intensive profiling of Nxt client I seem to figured out why it crashes so often.
Nxt uses direct memory buffers for networking part. If Nxt requests such a buffer JVM takes space reserved for heap and gives it to the buffer. After the buffer is no longer needed JVM "forgets" its reference but reserved memory is not claimed immediately, it depends on OS internal mechanisms. After a while this chunk of RAM can be used again, but if the flow of requests is very intensive, then JVM simply runs out of free memory. That's why we can see a lot of "Not enough memory/heap" errors and NullPointerExceptions.
Could Java gurus confirm this, please?
Nxt uses direct memory buffers for networking part. If Nxt requests such a buffer JVM takes space reserved for heap and gives it to the buffer. After the buffer is no longer needed JVM "forgets" its reference but reserved memory is not claimed immediately, it depends on OS internal mechanisms. After a while this chunk of RAM can be used again, but if the flow of requests is very intensive, then JVM simply runs out of free memory. That's why we can see a lot of "Not enough memory/heap" errors and NullPointerExceptions.
Could Java gurus confirm this, please?
I'll assume Bossland is honest then and used just weak secret phrase.
Let it be warning for all NEXT users, Use extremly strong phrases
Let it be warning for all NEXT users, Use extremly strong phrases
Jump to: