NXT :: descendant of Bitcoin - Updated Information - page 2402.

Hampuz

full member

Activity: 140

Merit: 100

Could someone sell me some NXT? Can pay in BTC/LTC/$$

mvag

newbie

Activity: 44

Merit: 0

Quote from: Come-from-Beyond on December 12, 2013, 04:04:55 AM

- Stakeholders will start doing anything and Nxt will grow

The fundraising was anonymous -- how can BCNext tell who of the contributing people is a stakeholder?

omo

full member

Activity: 147

Merit: 100

I updated the client from 0.3.16 to 0.3.18 on a centos box,
I got the following errors:

Code:

java -Xms512m -Xmx1024m -jar start.jar
2013-12-12 16:58:15.412:INFO:oejs.Server:main: jetty-9.1.0.v20131115
2013-12-12 16:58:15.438:INFO:oejdp.ScanningAppProvider:main: Deployment monitor [file:/home/nxt/nxt/webapps/] at interval 1
[2013-12-12 16:58:15.568] Nxt 0.3.18 started.
[2013-12-12 16:58:15.568] "blockchainStoragePath" set to "blockchain.nrs"
[2013-12-12 16:58:15.571] "myAddress" set to ""
[2013-12-12 16:58:15.572] "myHallmark" set to ""
[2013-12-12 16:58:15.572] "wellKnownPeers" set to "134.119.3.19; 146.185.168.142; 162.243.145.83; 162.243.232.67; 64.22.108.120; 69.146.88.14; 76.74.212.230; 85.17.190.73; 88.198.210.245; nxt.airdns.org"
[2013-12-12 16:58:15.572] "allowedUserHosts" set to "*"
[2013-12-12 16:58:15.572] "allowedBotHosts" set to "*"
[2013-12-12 16:58:15.572] "blacklistingPeriod" set to "300"
[2013-12-12 16:58:15.572] "logPeerCommunication" set to "false"
[2013-12-12 16:58:15.573] Loading transactions...
[2013-12-12 16:58:15.735] ...Done
[2013-12-12 16:58:15.735] Loading peers...
[2013-12-12 16:58:15.738] 10: java.io.InvalidClassException: Nxt$Account; class invalid for deserialization
2013-12-12 16:58:15.738:INFO:oejsh.ContextHandler:main: Started o.e.j.w.WebAppContext@7cf27a6e{/,file:/home/nxt/nxt/webapps/root/,AVAILABLE}{/root}
2013-12-12 16:58:15.745:WARN:oejuc.AbstractLifeCycle:main: FAILED ServerConnector@1c76b9da{HTTP/1.1}{0.0.0.0:7874}: java.net.BindException: address already in use
java.net.BindException: address already in use
at sun.nio.ch.Net.bind0(Native Method)
at sun.nio.ch.Net.bind(Net.java:444)
at sun.nio.ch.Net.bind(Net.java:436)
at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:214)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
at org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:279)
at org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
at org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:218)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
at org.eclipse.jetty.server.Server.doStart(Server.java:336)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
at org.eclipse.jetty.xml.XmlConfiguration$1.run(XmlConfiguration.java:1250)
at java.security.AccessController.doPrivileged(Native Method)
at org.eclipse.jetty.xml.XmlConfiguration.main(XmlConfiguration.java:1174)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.eclipse.jetty.start.Main.invokeMain(Main.java:297)
at org.eclipse.jetty.start.Main.start(Main.java:706)
at org.eclipse.jetty.start.Main.main(Main.java:103)
2013-12-12 16:58:15.746:WARN:oejuc.AbstractLifeCycle:main: FAILED ServerConnector@36a3a5cf{SSL-http/1.1}{0.0.0.0:7875}: java.net.BindException: address already in use
java.net.BindException: address already in use
at sun.nio.ch.Net.bind0(Native Method)
at sun.nio.ch.Net.bind(Net.java:444)
at sun.nio.ch.Net.bind(Net.java:436)
at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:214)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
at org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:279)
at org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
at org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:218)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
at org.eclipse.jetty.server.Server.doStart(Server.java:336)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
at org.eclipse.jetty.xml.XmlConfiguration$1.run(XmlConfiguration.java:1250)
at java.security.AccessController.doPrivileged(Native Method)
at org.eclipse.jetty.xml.XmlConfiguration.main(XmlConfiguration.java:1174)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.eclipse.jetty.start.Main.invokeMain(Main.java:297)
at org.eclipse.jetty.start.Main.start(Main.java:706)
at org.eclipse.jetty.start.Main.main(Main.java:103)
2013-12-12 16:58:15.746:WARN:oejuc.AbstractLifeCycle:main: FAILED org.eclipse.jetty.server.Server@31dad50f: MultiException[java.net.BindException: address already in use, java.net.BindException: address already in use]
MultiException[java.net.BindException: address already in use, java.net.BindException: address already in use]
at org.eclipse.jetty.server.Server.doStart(Server.java:302)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
at org.eclipse.jetty.xml.XmlConfiguration$1.run(XmlConfiguration.java:1250)
at java.security.AccessController.doPrivileged(Native Method)
at org.eclipse.jetty.xml.XmlConfiguration.main(XmlConfiguration.java:1174)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.eclipse.jetty.start.Main.invokeMain(Main.java:297)
at org.eclipse.jetty.start.Main.start(Main.java:706)
at org.eclipse.jetty.start.Main.main(Main.java:103)
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.eclipse.jetty.start.Main.invokeMain(Main.java:297)
at org.eclipse.jetty.start.Main.start(Main.java:706)
at org.eclipse.jetty.start.Main.main(Main.java:103)
Caused by: MultiException[java.net.BindException: address already in use, java.net.BindException: address already in use]
at org.eclipse.jetty.server.Server.doStart(Server.java:302)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
at org.eclipse.jetty.xml.XmlConfiguration$1.run(XmlConfiguration.java:1250)
at java.security.AccessController.doPrivileged(Native Method)
at org.eclipse.jetty.xml.XmlConfiguration.main(XmlConfiguration.java:1174)
... 7 more

Come-from-Beyond

legendary

Activity: 2142

Merit: 1010

Newbie

I've got a private message from one of the stakeholders who asked to remove my post about bad news. Sorry, guys, BCNext asked me to post this and it will stay there.

I see 2 scenarios there:
- Stakeholders will start doing anything and Nxt will grow
- Stakeholders will sell their coins to those who do something and Nxt will grow

Both scenarios look good to me.

NxtChoice

full member

Activity: 238

Merit: 100

Wow!

If the fundraising limit to everyone to be 0.05 BTC at most, then there will be more stakeholders involved and the coin distribution should be better than now.

Come-from-Beyond

legendary

Activity: 2142

Merit: 1010

Newbie

Quote from: starik69 on December 12, 2013, 03:56:41 AM

Quote from: Come-from-Beyond on December 12, 2013, 03:27:27 AM

They don't run their nodes,

You made it impossible to run it under NAT. Angry

I bet u can afford to pay 10$ per month for VPS.

Quote from: Come-from-Beyond on December 12, 2013, 03:27:27 AM

they don't support bounties

I wanted to participate in some bounty yesterday but didnt find its addresses in two topics on this forum. Roll Eyes

That's good, the others didn't even try.

Quote from: Come-from-Beyond on December 12, 2013, 03:27:27 AM

they don't take part in Nxt promotion.

You cannot expect everyone to be a good promoter. Sad

True.

ParmaBTC

legendary

Activity: 1218

Merit: 1002

Quote from: Pouncer on December 12, 2013, 01:45:10 AM

Finally managed to have the hallmark done and decoded correctly, after manually encoding all special characters.

Quote from: Jean-Luc on December 07, 2013, 02:50:36 PM

Yes, you have to url-encode at least # and &, that I can think of. You can't even fix it on the server side because in the case of # I don't think the string after the hash gets submitted to the server at all. So, people with special characters in the password will have to encode them manually, see e.g. table here:
http://www.w3schools.com/tags/ref_urlencode.asp
Or do a simple javascript page that does the encoding in javascript on the client. Obviously, don't submit your passwords to any online services that offer url-encoding.

Warning:
After doing this request, http://localhost:7874/nxt?requestType=markHost&secretPhrase=MY_SECRET&host=MY_HOST&weight=HOST_WEIGHT&date=CURRENT_DATE
your secret passphrase is stored in clear text in your browsing history! Remember to securely delete your browsing history after doing this task.

this is true, but you can use Anonymous mode of your browser, and nothing is stored

starik69

legendary

Activity: 1367

Merit: 1000

Quote from: Come-from-Beyond on December 12, 2013, 03:27:27 AM

They don't run their nodes,

You made it impossible to run it under NAT. Angry

Quote from: Come-from-Beyond on December 12, 2013, 03:27:27 AM

they don't support bounties

I wanted to participate in some bounty yesterday but didnt find its addresses in two topics on this forum. Roll Eyes

Quote from: Come-from-Beyond on December 12, 2013, 03:27:27 AM

they don't take part in Nxt promotion.

You cannot expect everyone to be a good promoter. Sad

Quote from: Come-from-Beyond on December 12, 2013, 03:27:27 AM

he can quit this project and join other cryptocoin

This blackmail thing is very sad Cry

To be angry because of this - is like to be angry because of stars on the sky. The things that are completely out of your control. I think it is a symptom.

Come-from-Beyond

legendary

Activity: 2142

Merit: 1010

Newbie

Now time for bad news.

BCNext is becoming more and more angry coz of stakeholders who don't help Nxt. They don't run their nodes, they don't support bounties, they don't take part in Nxt promotion. He can't force them to do all these things but he can quit this project and join other cryptocoin, no matter if it's called ClonedNxt, and contribute his ideas and code to a competitor of Nxt...

My personal opinion: This guy doesn't care about money nor how much 1 NXT will be worth, I'm 100% sure he will do what he said. I think that Nxt clone will have the same problems and decision to quit Nxt would be one of the worst decisions, but he has his own opinion.
Edit: If stakeholders don't change situation they should sell their coins before price drops below ZERO.

Come-from-Beyond

legendary

Activity: 2142

Merit: 1010

Newbie

Quote from: laowai80 on December 12, 2013, 02:36:25 AM

I have this bug to report. It's a second or third time I've seen it and I think it's easily reproduceable. This is on Debian Linux. Not sure if this is OS specific, but trying to give all details here. It may even be a known issue, not sure.

I have started NXT 0.3.18 and it began to download the blockchain. Then I tried to terminate it with CTRL+C BEFORE it fully downloaded, but it didn't want to exit, so I issued a kill -9 PID. Then I started the software again, but it turns out the blocks.nxt got corrupted, because the browser began to spit the java.nullpointer exception message. Had to stop the server, replace blocks.nxt with the blocks.nxt.bak file, and then start it again, and then it was alright.

So, why is it, that before the full block chain is downloaded and you stop the server, the server doesn't want to exit, and kill -9 PID corrupts the blocks.nxt file. There has to be a way to exit the server without corrupting the block chain even though the block chain isn't fully downloaded. Or did I have to wait longer for the server to exit after CTRL+C?

Thx for the report. I'll add a code that checks if CTRL+C was pressed during blockchain downloading.

Those who don't see blocks, please, check if ur blocks.nxt file is growing.

allwelder

legendary

Activity: 1512

Merit: 1004

http://i.youku.com/nextcoin

If this helpful ,please donate:
15904446403154732365

laowai80

member

Activity: 98

Merit: 10

I have this bug to report. It's a second or third time I've seen it and I think it's easily reproduceable. This is on Debian Linux. Not sure if this is OS specific, but trying to give all details here. It may even be a known issue, not sure.

I have started NXT 0.3.18 and it began to download the blockchain. Then I tried to terminate it with CTRL+C BEFORE it fully downloaded, but it didn't want to exit, so I issued a kill -9 PID. Then I started the software again, but it turns out the blocks.nxt got corrupted, because the browser began to spit the java.nullpointer exception message. Had to stop the server, replace blocks.nxt with the blocks.nxt.bak file, and then start it again, and then it was alright.

So, why is it, that before the full block chain is downloaded and you stop the server, the server doesn't want to exit, and kill -9 PID corrupts the blocks.nxt file. There has to be a way to exit the server without corrupting the block chain even though the block chain isn't fully downloaded. Or did I have to wait longer for the server to exit after CTRL+C?

abctc

legendary

Activity: 1792

Merit: 1038

Quote from: ImmortAlex on December 12, 2013, 01:39:02 AM

I have same issue since last evening

- hmmm.. have no problem with 0.3.18. Current block is 13900, id=1438896222878112845, 301 active peers.

pandaisftw

full member

Activity: 224

Merit: 100

Quote from: ImmortAlex on December 12, 2013, 01:39:02 AM

Quote from: pandaisftw on December 12, 2013, 01:30:41 AM

I have a problem with the newest versions (17 and 18) where I will catch up to the latest blocks... then that's it. It won't get any new blocks generated after that (stuck on catching up..)

I have same issue since last evening, with 0.3.17 and 0.3.18.
One more attack on network?

Come-from-beyond did mention that non-hallmarked clients may not be able to connect if the network is under attack, so that is very possible.

Pouncer

sr. member

Activity: 252

Merit: 250

Finally managed to have the hallmark done and decoded correctly, after manually encoding all special characters.

Quote from: Jean-Luc on December 07, 2013, 02:50:36 PM

Yes, you have to url-encode at least # and &, that I can think of. You can't even fix it on the server side because in the case of # I don't think the string after the hash gets submitted to the server at all. So, people with special characters in the password will have to encode them manually, see e.g. table here:
http://www.w3schools.com/tags/ref_urlencode.asp
Or do a simple javascript page that does the encoding in javascript on the client. Obviously, don't submit your passwords to any online services that offer url-encoding.

Warning:
After doing this request, http://localhost:7874/nxt?requestType=markHost&secretPhrase=MY_SECRET&host=MY_HOST&weight=HOST_WEIGHT&date=CURRENT_DATE
your secret passphrase is stored in clear text in your browsing history! Remember to securely delete your browsing history after doing this task.

ImmortAlex

hero member

Activity: 784

Merit: 501

Quote from: pandaisftw on December 12, 2013, 01:30:41 AM

I have a problem with the newest versions (17 and 18) where I will catch up to the latest blocks... then that's it. It won't get any new blocks generated after that (stuck on catching up..)

I have same issue since last evening, with 0.3.17 and 0.3.18.
One more attack on network?

pandaisftw

full member

Activity: 224

Merit: 100

I have a problem with the newest versions (17 and 18) where I will catch up to the latest blocks... then that's it. It won't get any new blocks generated after that (stuck on catching up..)

No difference if I am logged in or out. I have replaced my NXT files with the newest files included with version 18. I also tried deleting all of my NXT files, but all that caused was for me to be stuck on the genesis block with no peers.

msin

legendary

Activity: 1470

Merit: 1004

It's been working fine for me, was down for about 30 minutes, but came back up.

fgjfgh63

newbie

Activity: 14

Merit: 0

cant go to the nxt forum

pinarello

full member

Activity: 266

Merit: 100

NXT is the future

forum down ? Huh

Topic: NXT :: descendant of Bitcoin - Updated Information - page 2402. (Read 2761626 times)