The last version (0.3.3) deadlocks very often while trying to get the blockchain. After it hangs, Ctrl-C cannot kill it (because the thread is waiting to obtain a lock and ignores interrupts), so the only way to kill the java process is kill -9. Which leaves blocks.nxt in a corrupted state, so next time I try to start it, it fails with EOFException... not much fun.

Looks like multiple threads are trying to update a HashMap (or several HashMaps) and deadlock one another. Would using a ConcurrentHashMap help?


I see quite a few of the above when sending a kill -3 to the java process.

Take note of megacoin
I'm sure everyone noticed the $0.012 to nearly $2 recent jump in 2weeks.  Yes thats 150x.  Look at their website and ANN thread in bitcointalk.org. nothing revolutionary about this coin at all. All marketing. Different languages etc

Take note take heed

I get one of this messages on vps again:

wait im confused. is the code open source? has anyone audited it? im VERY interested in a 100% proof of stake coin but i cant drop real resources into closed source code. that would be economic suicide. what convinced other people to do this?

Stuck on 9341756182137841475

9341756182137841475 is the block id

What block number? Do you have 0.3.3 version?

My latest is 6327. One minute ago

Do I need to edit web.xml?

6334 (block id 11411852692899549778)
Clean install, no problem so far.

Okay, so on a public node it should just be my public-facing IP?

Getting this too