Как-то грустно все это. Если единственное спасение NXT - покупка все большего числа VPS, то это все больше выглядит как какая-то маркетинговая акция digitalocean и иже с ним. Почему код клиента запрограмирован так, что нужно массово покупать сервера? Предыдущая атака привела к тому, что изначальный сетевой код BCNext заменили на Jetty. Теперь оказывается, что в этой атаке как раз Jetty и виноват. Что же дальше?  |
|
|
|
How many forks are there? On one with 22875 i have ...161NXT, on 22928 - ...291NXT. And on blockexplorer - (same 22928) - ...250NXT!  |
|
|
|
Other fork is still alive! 22817 2043614891389818346 Monday, December 23, 2013 16:03:21
0 0 + 0 0 B
1 957565152895610238 190110 % |
|
|
|
But rest assured Ripple also had expenses, since it's a proper private company, there were costs involved with wages, renting space, etc... so yes, they've put money in as well.
So they made all process public and open and anybody could participate? lol. "Private company" does mean something.  |
|
|
|
A small group of people control all existing coins, all the coins that will ever exist. While everyone else has to buy NXT or beg for some NXTin some giveaway or bounty.
People in that group also bought their NXT, can you say this about ripple? |
|
|
|
Why on 22800+ i see Unconfirmed transactions [2243] ? |
|
|
|
Oh, on 22800+ chain i loose several hundreds of NXT  |
|
|
|
I accept your comments only if you will be willing to continue to participate in the discussion once/if things turn out the way you are NOT expecting today for NXT. So... do I have your word on it?
What do you mean by "accept comments"? They are as they are, no need to accept them. And of course as >1M genesis block stakeholder i will "continue to participate in the discussion" whatever happens  |
|
|
|
Time will tell...
For now time tells that the first BCNext network code was wrong. And CFB decision to use Jetty again was wrong. Whats next?  |
|
|
|
In other words, not only are the attackers losing the war, they technically didn't even win this particular battle. Doesn't look so  Avg. Target / Day
Day : 28 1708582.40 % |
|
|
|
But we have the tools to make fight the attack if the network is bigger, need to grow it by an order of magnitude in the next 2 weeks.
Tools to buy more vps, which will be attacked again and paralysis will be eternal? |
|
|
|
So, the attacker won? Network is paralyzed, exchange is paralyzed, devs cannot handle it? |
|
|
|
2013-12-23 02:13:11.504:WARN:oejs.HttpChannel:qtp729770861-47: Commit failed
java.util.concurrent.TimeoutException: Idle timeout expired: 30007/30000 ms
at org.eclipse.jetty.io.IdleTimeout.checkIdleTimeout(IdleTimeout.java:15
3)
at org.eclipse.jetty.io.IdleTimeout$1.run(IdleTimeout.java:50)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
access$201(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
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)
2013-12-23 02:13:41.578:WARN:oejs.ServletHandler:qtp729770861-49: /nxt
java.io.IOException: java.util.concurrent.TimeoutException: Idle timeout expired
: 30007/30000 ms
at org.eclipse.jetty.util.BlockingCallback.block(BlockingCallback.java:1
01)
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(Unknown Source)
at Nxt.doGet(Unknown Source)
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:696
)
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java
:526)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.j
ava:143)
at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.jav
a:568)
at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandl
er.java:221)
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandl
er.java:1110)
at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:
453)
at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandle
r.java:183)
at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandle
r.java:1044)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.j
ava:141)
at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(Cont
extHandlerCollection.java:199)
at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerColl
ection.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.jav
a:229)
at org.eclipse.jetty.io.AbstractConnection$1.run(AbstractConnection.java
:505)
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPoo
l.java:607)
at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool
.java:536)
at java.lang.Thread.run(Unknown Source)
Caused by:
java.util.concurrent.TimeoutException: Idle timeout expired: 30007/30000 ms
at org.eclipse.jetty.io.IdleTimeout.checkIdleTimeout(IdleTimeout.java:15
3)
at org.eclipse.jetty.io.IdleTimeout$1.run(IdleTimeout.java:50)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
access$201(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.
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) |
|
|
|
Node with 22310 says Generated an incorrect block. Waiting for the next one...
|
|
|
|
|
One node 22310 and no timer other 22291
|
|
|
|
|
Very strange. One my client shows block 22291, other 22301
|
|
|
|
Its funny - CFB managed to make transaction before the genesis block! ACCOUNT : 11541844302056663007 | Timestamp | Account | Amount | Fee | Transaction | Block | | 24.11.2013 13:00:00 | 1739068987193023818 | 4,987,575 | 0 | 2119615107677390707 | 2680262203532249785 | | 24.11.2013 12:44:31 | 78880408059 | 1,000,000 | 100 | 4016189039045729226 | 14084146571794201371 |
(Really it get into sixth block ) |
|
|
|
Got both iPhone & iOS... hey maybe just these two get me my 1,000,000 NXT... although I would gladly transfer all aliases for that!!!
Place your bids people or BUY IT NOW for 1,000,000 NXT! lmao ...this is going to be fun!!!
you paid 4x100 Nxt for Iphone  I have iPod for 1 Nxt ipad, mac, osx here |
|
|
|
|
Show Posts
