Topic: NXT :: descendant of Bitcoin - Updated Information - page 2387. (Read 2761626 times)
whats cur version? i think my node is down since days
Where is the description on the marking of the node? I want to index it for reference.
Thanks.
https://nextcoin.org/index.php/topic,607.0.html Thanks.
Did u find that transaction? 11 min is normal, forging is a probabilistic process.
- yes, see here.And I think, that sudden 11min gap (after 10 or more strictly 1 min blocks) is not normal.
And such >10 min gaps repeated from time to time. Not 3 min or 5 min, but huge.
1) when will be released an official client (i mean i final version, for all)?
2) how much is the block found reward?
3) do you think this coin will be really used from a large amount of people?
4) why i see my "found block time" changing 1000 times from 4 days to 9 months?
- 1) hmmm.. bitcoin-qt now has version 0.8.6 When will be final version? Who knows..2) how much is the block found reward?
3) do you think this coin will be really used from a large amount of people?
4) why i see my "found block time" changing 1000 times from 4 days to 9 months?
2) Please read 1ts post of this thread carefully.
3) yes, I do. It is highly innovative crypto.
4) Because the forging is a probabilistic process :-)). Please, estimate your chances here.
Why is it so hard to get a stable client?
Do u mean that ur client crashes?
Since there is a limit to the connected number of peers, can people use smaller (eg: 512mb RAM) VPS instances to support the network?
There is no limit for connected private peers.
Why is it so hard to get a stable client?
Im getting this fairly frequently on 0.3.18 (i CRTL-c out and rerun the jar, and it still happens every few mins):
Quote
10b8772{SSL-http/1.1}{0.0.0.0:7875}
2013-12-13 11:06:51.271:WARN:oejs.HttpChannel:Scheduler-31607536: Commit failed
java.util.concurrent.TimeoutException: Idle timeout expired: 5000/5000 ms
at org.eclipse.jetty.io.IdleTimeout.checkIdleTimeout(IdleTimeout.java:15
..........................................
..........................................
..........................................
2013-12-13 11:06:51.271:WARN:oejs.HttpChannel:Scheduler-31607536: Commit failed
java.util.concurrent.TimeoutException: Idle timeout expired: 5000/5000 ms
at org.eclipse.jetty.io.IdleTimeout.checkIdleTimeout(IdleTimeout.java:15
..........................................
..........................................
..........................................
Any Jetty guru there?
v.0.3.19e. Trying to send transaction. After 40 min there is no confirmations at all ..
4 orphaned blocks. Server is on CentOS.
And there is no new blocks during the last 11 min.
4 orphaned blocks. Server is on CentOS.
And there is no new blocks during the last 11 min.
Did u find that transaction? 11 min is normal, forging is a probabilistic process.
CfB,
is blocks.nxt file not immediately updated when new blocks have downloaded? I noticed, the browser shows new blocks already with the new timestamp, but the blocks.nxt file is still a few minutes away, the new blocks sync'ed into the file only a few minutes later. Is this standard operation or again openvz vps node strange behavior?
is blocks.nxt file not immediately updated when new blocks have downloaded? I noticed, the browser shows new blocks already with the new timestamp, but the blocks.nxt file is still a few minutes away, the new blocks sync'ed into the file only a few minutes later. Is this standard operation or again openvz vps node strange behavior?
It's standard since 0.3.19e. After all blocks r caught soft will dump all stuff to the disk.
So the terminal won't tell me if i found a block, right?
- you can only see that moment online: your time ticker drops to 3 sec.. 2 sec.. 1 sec.. and you'll see that the block appeared in the widget.Thanks again :p
4 last questions and i'll give you a free biscuit
:1) when will be released an official client (i mean i final version, for all)?
2) how much is the block found reward?
3) do you think this coin will be really used from a large amount of people?
4) why i see my "found block time" changing 1000 times from 4 days to 9 months?
So the terminal won't tell me if i found a block, right?
- you can only see that moment online: your time ticker drops to 3 sec.. 2 sec.. 1 sec.. and you'll see that the block appeared in the widget. v.0.3.19e. Trying to send transaction. After 40 min there is no confirmations at all ..
- actually there was confirmations, but they do not appeared in the browser.. albeit that unconfirmed transaction successfully disapeared from the transaction widget after 1 hour (expiration time I have set). After expiration I sent that transaction again, this time from 0.3.19e server on Win7, and later both transaction appeared in the blockchain. 5) what now? how can i know if i got 1 block?
- check your account with blockexplorer ("Fee Earned").and.. what happens if i let the terminal open from 2 clients on the same "wallet" unlocked?
- you will just slightly increase the rate of the orphaned blocks.Thanks
So the terminal won't tell me if i found a block, right?
5) what now? how can i know if i got 1 block?
- check your account with blockexplorer ("Fee Earned").and.. what happens if i let the terminal open from 2 clients on the same "wallet" unlocked?
- you will just slightly increase the rate of the orphaned blocks. Since there is a limit to the connected number of peers, can people use smaller (eg: 512mb RAM) VPS instances to support the network?
- actually you can use 512 MB VPS even with 0.3.18.
Errors on my box
Code:
2013-12-13 11:19:21.345:WARN:oejs.HttpChannel:Scheduler-203777958: Commit failed
java.util.concurrent.TimeoutException: Idle timeout expired: 5000/5000 ms
at org.eclipse.jetty.io.IdleTimeout.checkIdleTimeout(IdleTimeout.java:153)
at org.eclipse.jetty.io.IdleTimeout$1.run(IdleTimeout.java:50)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:724)
2013-12-13 11:19:26.354:WARN:oejs.ServletHandler:qtp2016627616-33: /nxt
java.io.IOException: java.util.concurrent.TimeoutException: Idle timeout expired: 5000/5000 ms
at org.eclipse.jetty.util.BlockingCallback.block(BlockingCallback.java:101)
at org.eclipse.jetty.server.HttpChannel.write(HttpChannel.java:734)
at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:307)
at java.io.OutputStream.write(OutputStream.java:75)
at Nxt.doPost(Unknown Source)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:696)
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:526)
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:453)
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:280)
at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:229)
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)
Caused by:
java.util.concurrent.TimeoutException: Idle timeout expired: 5000/5000 ms
at org.eclipse.jetty.io.IdleTimeout.checkIdleTimeout(IdleTimeout.java:153)
at org.eclipse.jetty.io.IdleTimeout$1.run(IdleTimeout.java:50)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:724)
2013-12-13 12:08:22.804:WARN:oejs.HttpChannel:Scheduler-203777958: Commit failed
java.util.concurrent.TimeoutException: Idle timeout expired: 5000/5000 ms
at org.eclipse.jetty.io.IdleTimeout.checkIdleTimeout(IdleTimeout.java:153)
at org.eclipse.jetty.io.IdleTimeout$1.run(IdleTimeout.java:50)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:724)
2013-12-13 12:08:22.808:WARN:oejs.ServletHandler:qtp2016627616-34: /nxt
java.io.IOException: java.util.concurrent.TimeoutException: Idle timeout expired: 5000/5000 ms
at org.eclipse.jetty.util.BlockingCallback.block(BlockingCallback.java:101)
at org.eclipse.jetty.server.HttpChannel.write(HttpChannel.java:734)
at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:307)
at java.io.OutputStream.write(OutputStream.java:75)
at Nxt.doPost(Unknown Source)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:696)
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:526)
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:453)
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:280)
at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:229)
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)
Caused by:
java.util.concurrent.TimeoutException: Idle timeout expired: 5000/5000 ms
at org.eclipse.jetty.io.IdleTimeout.checkIdleTimeout(IdleTimeout.java:153)
at org.eclipse.jetty.io.IdleTimeout$1.run(IdleTimeout.java:50)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:724)
java.util.concurrent.TimeoutException: Idle timeout expired: 5000/5000 ms
at org.eclipse.jetty.io.IdleTimeout.checkIdleTimeout(IdleTimeout.java:153)
at org.eclipse.jetty.io.IdleTimeout$1.run(IdleTimeout.java:50)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:724)
2013-12-13 11:19:26.354:WARN:oejs.ServletHandler:qtp2016627616-33: /nxt
java.io.IOException: java.util.concurrent.TimeoutException: Idle timeout expired: 5000/5000 ms
at org.eclipse.jetty.util.BlockingCallback.block(BlockingCallback.java:101)
at org.eclipse.jetty.server.HttpChannel.write(HttpChannel.java:734)
at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:307)
at java.io.OutputStream.write(OutputStream.java:75)
at Nxt.doPost(Unknown Source)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:696)
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:526)
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:453)
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:280)
at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:229)
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)
Caused by:
java.util.concurrent.TimeoutException: Idle timeout expired: 5000/5000 ms
at org.eclipse.jetty.io.IdleTimeout.checkIdleTimeout(IdleTimeout.java:153)
at org.eclipse.jetty.io.IdleTimeout$1.run(IdleTimeout.java:50)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:724)
2013-12-13 12:08:22.804:WARN:oejs.HttpChannel:Scheduler-203777958: Commit failed
java.util.concurrent.TimeoutException: Idle timeout expired: 5000/5000 ms
at org.eclipse.jetty.io.IdleTimeout.checkIdleTimeout(IdleTimeout.java:153)
at org.eclipse.jetty.io.IdleTimeout$1.run(IdleTimeout.java:50)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:724)
2013-12-13 12:08:22.808:WARN:oejs.ServletHandler:qtp2016627616-34: /nxt
java.io.IOException: java.util.concurrent.TimeoutException: Idle timeout expired: 5000/5000 ms
at org.eclipse.jetty.util.BlockingCallback.block(BlockingCallback.java:101)
at org.eclipse.jetty.server.HttpChannel.write(HttpChannel.java:734)
at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:307)
at java.io.OutputStream.write(OutputStream.java:75)
at Nxt.doPost(Unknown Source)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:696)
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:526)
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:453)
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:280)
at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:229)
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)
Caused by:
java.util.concurrent.TimeoutException: Idle timeout expired: 5000/5000 ms
at org.eclipse.jetty.io.IdleTimeout.checkIdleTimeout(IdleTimeout.java:153)
at org.eclipse.jetty.io.IdleTimeout$1.run(IdleTimeout.java:50)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:724)
Since there is a limit to the connected number of peers, can people use smaller (eg: 512mb RAM) VPS instances to support the network?
- actually you can use 512 MB VPS even with 0.3.18.
Forging:
1) I run terminal as normal
2) i go to localhost:7875 and i unlock my "wallet"
3) i close my "wallet" without locking it
4) i let the terminal open
5) what now? how can i know if i got 1 block?
and.. what happens if i let the terminal open from 2 clients on the same "wallet" unlocked?
1) I run terminal as normal
2) i go to localhost:7875 and i unlock my "wallet"
3) i close my "wallet" without locking it
4) i let the terminal open
5) what now? how can i know if i got 1 block?
and.. what happens if i let the terminal open from 2 clients on the same "wallet" unlocked?
Version 0.3.19e - https://dl.dropboxusercontent.com/u/67242472/nxt-experimental.zip
This is an experimental version, use it only if u want to help us as a tester.
Added "peerScheme" and "peerPort" in web.xml. This is for migration to HTTPS and different ports.
Added "maxNumberOfConnectedPublicPeers" in web.xml. Ur node will keep connecting to public peers until this number is reached. Previous version does it until total number of public and private peers < 100.
Removed code related to Colored Coins (to prepare source code for review). Now u don't have to copy so many .class files.
Made an attempt to fix blockchain downloading issue related to stuck "Catching up..." message. I removed it from .html files completely, so u won't see it anymore... It's a joke, I also changed a few lines of server code. Now blocks r downloaded faster (2 mins vs 30 mins in previous version) and u don't need to lock/unlock account to unfreeze Recent blocks widget (I hope). I wasn't able to check how the changes handle blockchain reorgs when orphaned blocks appear, that's why this version is experimental. If u can, please, install it and report if u see at least one orphaned block or the blockchain stops growing.
Since there is a limit to the connected number of peers, can people use smaller (eg: 512mb RAM) VPS instances to support the network? This is an experimental version, use it only if u want to help us as a tester.
Added "peerScheme" and "peerPort" in web.xml. This is for migration to HTTPS and different ports.
Added "maxNumberOfConnectedPublicPeers" in web.xml. Ur node will keep connecting to public peers until this number is reached. Previous version does it until total number of public and private peers < 100.
Removed code related to Colored Coins (to prepare source code for review). Now u don't have to copy so many .class files.
Made an attempt to fix blockchain downloading issue related to stuck "Catching up..." message. I removed it from .html files completely, so u won't see it anymore... It's a joke, I also changed a few lines of server code. Now blocks r downloaded faster (2 mins vs 30 mins in previous version) and u don't need to lock/unlock account to unfreeze Recent blocks widget (I hope). I wasn't able to check how the changes handle blockchain reorgs when orphaned blocks appear, that's why this version is experimental. If u can, please, install it and report if u see at least one orphaned block or the blockchain stops growing.
Jump to: