Code:
Orphaned blocks [24107]
Topic: NXT :: descendant of Bitcoin - Updated Information - page 2203. (Read 2761629 times)
Oh! All blocks are gone,
Quote
I start noticing DDOS getting bigger in the last 15 mins
Quote
How can you tell?
Quote
Hold on, I'll post a screenshot of the bandwidth graph.
OK, you're monitoring bandwidth usage on your machine. Thanks for the screenshot.
People eating through sell walls on Dgex. We're going past 0.00006 soon.
1$ per NXT would be sweet 
4 cent atm yesterday at the same time around ~2.6
Just got to say to all the nxt devs: Nice work on 0.4.4, guys!!
More I dig thru changes in 0.4.4 more I believe that it's coz of increased number of legit peers. U should thank those who brought more nodes.
Well, something went very right all of a sudden......so thanks to absolutely everyone in the Nxt community!
People eating through sell walls on Dgex. We're going past 0.00006 soon.
Quote
I start noticing DDOS getting bigger in the last 15 mins
How can you tell?
Hold on, I'll post a screenshot of the bandwidth graph.
Just got to say to all the nxt devs: Nice work on 0.4.4, guys!!
More I dig thru changes in 0.4.4 more I believe that it's coz of increased number of legit peers. U should thank those who brought more nodes.
Quote
I start noticing DDOS getting bigger in the last 15 mins
How can you tell?
And a question: how many peers are other people seeing ?
I've got 38 Active and 228 Known at the moment, rising slowly.
I've got 38 Active and 228 Known at the moment, rising slowly.
Also seeing this version as much more stable than the last. Or perhaps it's the lower ddos and higher number of nodes - although some part of me doesn't quite buy that.
The client says: 544 active, 213, known, 0 blacklisted; currently on block 24091 (4895341814651187594).
Can anyone explain to me why my client keeps getting stuck on short chains? Why doesn't my client automatically query the peers that i am connected to, ask them if their chain is longer, and ask them to send over a copy if it is?
I can if u change value of "communicationLoggingMasks" in web.xml to "3" and send me the log after 15 mins of working.
Can anyone explain to me why my client keeps getting stuck on short chains? Why doesn't my client automatically query the peers that i am connected to, ask them if their chain is longer, and ask them to send over a copy if it is?
0.4.4 really makes a big difference.
Don't use the old blockchain, sync from scratch.
doing both of those things, still getting stuck on short chains.
Did you also start with a "fresh" blockchain.nrs file?
i just extracted the 0.4.4 archive and ran it as is.
that is strange indeed. Maybe DfB can help you.
Can anyone explain to me why my client keeps getting stuck on short chains? Why doesn't my client automatically query the peers that i am connected to, ask them if their chain is longer, and ask them to send over a copy if it is?
0.4.4 really makes a big difference.
Don't use the old blockchain, sync from scratch.
doing both of those things, still getting stuck on short chains.
Did you also start with a "fresh" blockchain.nrs file?
i just extracted the 0.4.4 archive and ran it as is.
By the way, I start noticing DDOS getting bigger in the last 15 mins,
Xmas greetings to DDOSers, why don't you guys get some rest for a day or two?
or maybe it's more legit nodes connecting, who knows, will find out soon.
Xmas greetings to DDOSers, why don't you guys get some rest for a day or two?
or maybe it's more legit nodes connecting, who knows, will find out soon.
Can anyone explain to me why my client keeps getting stuck on short chains? Why doesn't my client automatically query the peers that i am connected to, ask them if their chain is longer, and ask them to send over a copy if it is?
0.4.4 really makes a big difference.
Don't use the old blockchain, sync from scratch.
doing both of those things, still getting stuck on short chains.
Did you also start with a "fresh" blockchain.nrs file?
Can anyone explain to me why my client keeps getting stuck on short chains? Why doesn't my client automatically query the peers that i am connected to, ask them if their chain is longer, and ask them to send over a copy if it is?
0.4.4 really makes a big difference.
Don't use the old blockchain, sync from scratch.
doing both of those things, still getting stuck on short chains.
Can anyone explain to me why my client keeps getting stuck on short chains? Why doesn't my client automatically query the peers that i am connected to, ask them if their chain is longer, and ask them to send over a copy if it is?
0.4.4 really makes a big difference.
Don't use the old blockchain, sync from scratch.
Just got to say to all the nxt devs: Nice work on 0.4.4, guys!!
Installed it a couple of hours ago, steady as a rock up til now.
I used the old blockchain files from my 0.4.2 and it picked up and ran with them really nicely.
Haven't forked or deleted a blockchain in the last 3 hours...hurrah!
So once again, good job, guys!
And a question: how many peers are other people seeing ?
I've got 38 Active and 228 Known at the moment, rising slowly.
Installed it a couple of hours ago, steady as a rock up til now.
I used the old blockchain files from my 0.4.2 and it picked up and ran with them really nicely.
Haven't forked or deleted a blockchain in the last 3 hours...hurrah!
So once again, good job, guys!
And a question: how many peers are other people seeing ?
I've got 38 Active and 228 Known at the moment, rising slowly.
Can someone explain to me why my client keeps getting stuck on short chains. Why doesn't my client automatically query the peers that i am connected to, ask them if their chain is longer, and ask them to send over a copy if it is?
I had this probblem also in 0.4.2 , my node would just be stuck for a long time, until i restarted it. But with 0.4.4 it runs smoothly. Maybe upgrade?
Can anyone explain to me why my client keeps getting stuck on short chains? Why doesn't my client automatically query the peers that i am connected to, ask them if their chain is longer, and ask them to send over a copy if it is?
Jump to: