Topic: NXT :: descendant of Bitcoin - Updated Information - page 1533. (Read 2761645 times)
Was there supposed to be a new coin on btc24 today?
The NEX community demand that Nxt developers release the source code that they have previously promised!
https://github.com/slothbag/nxt-decompiled/blob/master/Nxt.java
Decompiled code is not the same as source code.
Still you continue to mislead the community!
The NEX community demands the release of the source code!
Without the source code.... how can we believe that Nxt does not have a trojan or virus in their compiled code?
No source code... no trust.... fundamental crypto principle!
https://github.com/slothbag/nxt-decompiled/blob/master/Nxt.java
Release 0.5.9:
http://download.nxtcrypto.org/nxt-client-0.5.9.zip
http://download.nxtcrypto.org/nxt-client-0.5.9.zip
Ah nice. It's raining updates.
You all are doing a great job.
Keep it up.
TIA
-Fo-
how can we believe that Nxt does not have a trojan or virus in their compiled code?
Just look at the code, u already proved to be a Java expert, didn't u?
I am... wait what
how can we believe that Nxt does not have a trojan or virus in their compiled code?
Just look at the code, u already proved to be a Java expert, didn't u?
oops: got the following on my raspi:
[2014-01-19 13:18:53.017] Loading transactions...
[2014-01-19 13:19:37.863] ...Done
[2014-01-19 13:19:37.866] Loading blocks...
[2014-01-19 13:20:22.443] ...Done
[2014-01-19 13:20:22.446] Scanning blockchain...
[2014-01-19 13:21:20.902] Error initializing Nxt servlet
maybe I have to try and start again without blocks.nxt and transactions.nxt ?!?!
sry - forgot:
yes, the above was only the log output. The actual stacktrace looks like this:
pi@raspberrypi ~/nxt $ ./run_nxt.sh
WARNING: System properties and/or JVM args set. Consider using --dry-run or --exec
java.lang.NullPointerException
at Nxt$Block.analyze(Nxt.java:993)
at Nxt.init(Nxt.java:6077)
at org.eclipse.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:561)
at org.eclipse.jetty.servlet.ServletHolder.initialize(ServletHolder.java:351)
at org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:840)
at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:300)
at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1347)
at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:743)
at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:492)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:117)
at org.eclipse.jetty.util.component.ContainerLifeCycle.addBean(ContainerLifeCycle.java:281)
at org.eclipse.jetty.util.component.ContainerLifeCycle.addBean(ContainerLifeCycle.java:213)
at org.eclipse.jetty.util.component.ContainerLifeCycle.updateBeans(ContainerLifeCycle.java:763)
at org.eclipse.jetty.server.handler.HandlerCollection.setHandlers(HandlerCollection.java:89)
at org.eclipse.jetty.server.handler.ContextHandlerCollection.setHandlers(ContextHandlerCollection.java:144)
at org.eclipse.jetty.server.handler.HandlerCollection.addHandler(HandlerCollection.java:155)
at org.eclipse.jetty.deploy.bindings.StandardDeployer.processBinding(StandardDeployer.java:41)
at org.eclipse.jetty.deploy.AppLifeCycle.runBindings(AppLifeCycle.java:186)
at org.eclipse.jetty.deploy.DeploymentManager.requestAppGoal(DeploymentManager.java:498)
at org.eclipse.jetty.deploy.DeploymentManager.addApp(DeploymentManager.java:146)
at org.eclipse.jetty.deploy.providers.ScanningAppProvider.fileAdded(ScanningAppProvider.java:180)
at org.eclipse.jetty.deploy.providers.ScanningAppProvider$1.fileAdded(ScanningAppProvider.java:64)
at org.eclipse.jetty.util.Scanner.reportAddition(Scanner.java:605)
at org.eclipse.jetty.util.Scanner.reportDifferences(Scanner.java:528)
at org.eclipse.jetty.util.Scanner.scan(Scanner.java:391)
at org.eclipse.jetty.util.Scanner.doStart(Scanner.java:313)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
at org.eclipse.jetty.deploy.providers.ScanningAppProvider.doStart(ScanningAppProvider.java:150)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
at org.eclipse.jetty.deploy.DeploymentManager.startAppProvider(DeploymentManager.java:560)
at org.eclipse.jetty.deploy.DeploymentManager.doStart(DeploymentManager.java:235)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:69)
at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:117)
at org.eclipse.jetty.server.Server.start(Server.java:355)
at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:99)
at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:60)
at org.eclipse.jetty.server.Server.doStart(Server.java:324)
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:724)
at org.eclipse.jetty.start.Main.main(Main.java:103)
pi@raspberrypi ~/nxt $
The NEX community demand that Nxt developers release the source code that they have previously promised!
https://github.com/slothbag/nxt-decompiled/blob/master/Nxt.java
Decompiled code is not the same as source code.
Still you continue to mislead the community!
The NEX community demands the release of the source code!
Without the source code.... how can we believe that Nxt does not have a trojan or virus in their compiled code?
No source code... no trust.... fundamental crypto principle!
Good lord... they used a GET to post the secret pass phrase!
Aye. Without HTTPS.
No, his Windows system was most likely compromised with keylogger/trojan. He didn't use vanitygen at all, afaik.
I also want to repeat my advice to use private browsing mode, or a separate browser profile, when accessing the Nxt server at localhost. It is a known issue that localhost url's containing the user secret phrase are retained in the browser memory cache. Could a malicious javascript planted on some website access and retrieve those?
Any plans to fix this?
Good lord... they used a GET to post the secret pass phrase!
The NEX community demand that Nxt developers release the source code that they have previously promised!
https://github.com/slothbag/nxt-decompiled/blob/master/Nxt.java
DON'T BELIEVE THE FOOL WHO POSTED ABOVE ME.....TROLL OF THE CENTURY.....INTELLECTUAL PROPERTY THIEF
DOWN WITH THIEVING TROLLS!!!
DOWN WITH THIEVING TROLLS!!!
The NEX community demand that Nxt developers release the source code that they have previously promised!
Question to the javascript bounty:
This means tomorow noon, right?
How will it be tested? Different browsers may have different results concerning speed.
Do comments have an influence on the rating of the script?
Quote
The bounty is valid till the 20th of January, 2014 12:00:00 UTC. The complete code must be published in this thread.
This means tomorow noon, right?
How will it be tested? Different browsers may have different results concerning speed.
Do comments have an influence on the rating of the script?
Not sure about noon, but more than 12 and less 24 hours left.
I'll run all implementations on the same computer/browser.
Comments could help if we need tiebreak.
Question to the javascript bounty:
This means tomorow noon, right?
How will it be tested? Different browsers may have different results concerning speed.
Do comments have an influence on the rating of the script?
Quote
The bounty is valid till the 20th of January, 2014 12:00:00 UTC. The complete code must be published in this thread.
This means tomorow noon, right?
How will it be tested? Different browsers may have different results concerning speed.
Do comments have an influence on the rating of the script?
The amount of time you devote to NXT is breathtaking, you are clearly utterly fascinated by it.
This guy is awesome. That's why
Folks, do let me know when you release full source code.
There is a great demand by the NEX folks for your work:
https://bitcointalksearch.org/topic/ann-nex-nxt-reimagined-industrial-strength-imagine-fairness-422052
There is a great demand by the NEX folks for your work:
https://bitcointalksearch.org/topic/ann-nex-nxt-reimagined-industrial-strength-imagine-fairness-422052
The amount of time you devote to NXT is breathtaking, you are clearly utterly fascinated by it.
Folks, do let me know when you release full source code.
There is a great demand by the NEX folks for your work:
https://bitcointalksearch.org/topic/ann-nex-nxt-reimagined-industrial-strength-imagine-fairness-422052
There is a great demand by the NEX folks for your work:
https://bitcointalksearch.org/topic/ann-nex-nxt-reimagined-industrial-strength-imagine-fairness-422052
I think it will be the 3rd of April. Schedule ur plans according to this date, in the worst case it will be postponed for a couple of days, not more.
Folks, do let me know when you release full source code.
There is a great demand by the NEX folks for your work:
https://bitcointalksearch.org/topic/ann-nex-nxt-reimagined-industrial-strength-imagine-fairness-422052
There is a great demand by the NEX folks for your work:
https://bitcointalksearch.org/topic/ann-nex-nxt-reimagined-industrial-strength-imagine-fairness-422052
- agree 100%
web-client is one of the most attractive feature of Nxt.
web-client is one of the most attractive feature of Nxt.
It also allows you to easily have both local and remote wallets.
We'll get JS implementation of NRS sign/verify algo soon. It will be easy to create a web client.
Jump to: