Topic: NXT :: descendant of Bitcoin - Updated Information - page 1048. (Read 2761644 times)

OK....got both my home nodes up and running with 6.0, VPS is currently rebuilding its blockchain.

I've stopped hating J-L and am back in friendly mode. Got slightly irritated last night, but 4 hours sleep has made me a new man.  

Being not-too-techy:
 Do not blindly transfer your old web.xml over to 6.0 or u will get a monster Java crash on start up.
The important line is :

New version, 6.0:  


    
        Nxt
        nxt.Nxt

Old version:


    
        Nxt
        Nxt



VPS seems to be sweet as well, everything is on:

59377      16386134630970163904      donderdag 6 februari 2014 10:12:33   
      
      0      0 + 0      0 B   
      
      2      8507575767315242138      503 %


Good job, guys, thx very muchly.

What if someone creates a new account just before a pruning? It would be frustrating to have it deleted before getting a chance to send Nxt to it.

What if someone creates a new account just before a pruning? It would be frustrating to have it deleted before getting a chance to send Nxt to it.

Disappeared.

Isn't the whole point that the block chain will be shrunk?  So, at this stage who would have the master block chain?

Come-from-Beyond: Any news regarding how is Nxtgirl doing? Thanks

I think we should seriously consider forcing this behavior so we can prune public keys of accounts with no balance and no aliases

Master blockchain.

That might be circumvented cryptographically.

Additionally, who else is going to verify that transaction? Nobody, because they don't see the super special bonus additions. So, the guy will spend nothing of the additional money.

11th of Feb - public test
Xth of Feb - release

I'm receiving these errors:

What's to stop malicious nodes from creating their own genesis blocks with super special bonus additions?

BCNext is now some magical fairy

[2014-02-06 08:36:19.098] NRS 0.6.0 started successfully.
[2014-02-06 08:36:33.536] DEBUG: Failed to accept block received from 192.80.146.102, blacklisting
[2014-02-06 08:36:42.634] DEBUG: Failed to accept block received from 65.49.77.102, blacklisting
[2014-02-06 08:36:56.667] DEBUG: Failed to accept block received from 65.49.77.101, blacklisting
[2014-02-06 08:37:18.174] DEBUG: Failed to accept block received from 62.4.23.171, blacklisting
[2014-02-06 08:37:50.971] DEBUG: Failed to accept block received from 80.86.92.70, blacklisting
[2014-02-06 08:37:57.267] DEBUG: Failed to accept block received from node15.mynxt.info, blacklisting
[2014-02-06 08:38:01.185] DEBUG: Error processing GET request
java.lang.NullPointerException
   at nxt.http.GetAccountTransactionIds.processRequest(GetAccountTransactionIds.java:74)
   at nxt.http.HttpRequestHandler.process(HttpRequestHandler.java:92)
   at nxt.Nxt.doGet(Nxt.java:356)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:687)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
   at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:717)
   at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1644)
   at org.eclipse.jetty.servlets.CrossOriginFilter.handle(CrossOriginFilter.java:248)
   at org.eclipse.jetty.servlets.CrossOriginFilter.doFilter(CrossOriginFilter.java:211)
   at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1624)
   at org.eclipse.jetty.servlets.DoSFilter.doFilterChain(DoSFilter.java:457)
   at org.eclipse.jetty.servlets.DoSFilter.doFilter(DoSFilter.java:326)
   at org.eclipse.jetty.servlets.DoSFilter.doFilter(DoSFilter.java:299)
   at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1615)
   at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:550)
   at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
   at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:568)
   at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:221)
   at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1110)
   at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:479)
   at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:183)
   at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1044)
   at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
   at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:199)
   at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:109)
   at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
   at org.eclipse.jetty.server.Server.handle(Server.java:459)
   at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:281)
   at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:232)
   at org.eclipse.jetty.io.AbstractConnection$1.run(AbstractConnection.java:505)
   at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:607)
   at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:536)
   at java.lang.Thread.run(Thread.java:724)
[2014-02-06 08:38:03.887] DEBUG: Failed to accept block received from 83.143.232.49, blacklisting
[2014-02-06 08:38:08.211] DEBUG: Failed to accept block received from vps18.nxtcrypto.org, blacklisting

I am making good progress on getting AE into my Client - as let's see what the testing does. Any tentative dates for 'official launch' of AE??

I think from your list of possible features "anonymous transactions" would be the killer feature.

Not just the possibility to use some kind of mixing service, but actually changing pseudo anonymity to real anonymity. It is beyond me to say if this is possible, but if it is and gets implemented, NXT will explode (not (just) the price, but adoption, resources and everything else).

Atomic-cross chain transactions and the like will require a hash function (I would assume SHA256 would be the most likely to include).

If we can't get atomic-cross chain transactions to work then I think the idea of being able to have a trust-less P2P "coin" exchange simply won't work (not that we have to use a "smart contract" to do this of course but it would seem like something reasonable to support as other such "use cases" undoubtedly will arise).