i like it, the natural look is cool ;-)
But without "E" it would look better IMO.
Topic: NXT :: descendant of Bitcoin - Updated Information - page 2508. (Read 2761645 times)
But without "E" it would look better IMO.
Just made this. It's rough but let me know what you guys think so far. 
i like it, the natural look is cool ;-)
So how can we get coins to start mining? I know you don't want this thread spammed by requests, but still.
http://dgex.com/
Just made this. It's rough but let me know what you guys think so far. http://i.imgur.com/Gix0YM1.png
Is it a photo of a real gold bar?
much better and more stable, just run a second complete blockchain scan from genesis without any problems.
as said, each request invokes the above mentioned pattern but ist seems it doesn't hurt the client.
(well, pointer execptions are normally a serious thing but it looks like the client don't care much about ;-)
as said, each request invokes the above mentioned pattern but ist seems it doesn't hurt the client.
(well, pointer execptions are normally a serious thing but it looks like the client don't care much about ;-)
Looking forward to see the code that creates more errors but do things much better. Now I think BCNext is a genius!
BTW, I found another way to scan the blockchain. Get last block via getState and scan backwards using previousBlock. Don't need to worry about orphans or branches.
yes, this makes sense, latest as soon the blockchain reached a critical size, making a root traverse to expensive.
So how can we get coins to start mining? I know you don't want this thread spammed by requests, but still.
Just made this. It's rough but let me know what you guys think so far.
much better and more stable, just run a second complete blockchain scan from genesis without any problems.
as said, each request invokes the above mentioned pattern but ist seems it doesn't hurt the client.
(well, pointer execptions are normally a serious thing but it looks like the client don't care much about ;-)
as said, each request invokes the above mentioned pattern but ist seems it doesn't hurt the client.
(well, pointer execptions are normally a serious thing but it looks like the client don't care much about ;-)
Looking forward to see the code that creates more errors but do things much better. Now I think BCNext is a genius!
BTW, I found another way to scan the blockchain. Get last block via getState and scan backwards using previousBlock. Don't need to worry about orphans or branches.
Version 0.2.18 - https://dl.dropboxusercontent.com/u/67242472/Nxt.zip
Changed direct buffer allocation mechanism for peers and API bots. Could anyone test bot part? Is it more or less stable now?
Changed direct buffer allocation mechanism for peers and API bots. Could anyone test bot part? Is it more or less stable now?
testing, getting flooded by this error pattern for each request but it works!
5: java.nio.channels.AsynchronousCloseException
4: java.lang.NullPointerException
4: java.lang.NullPointerException
4: java.lang.NullPointerException
great!, ~7.000 serial requests in a row (the whole blockchain + transactions).
with 0.2.17 at ~500 the client stopped responding. thanks, this makes things much easier.
More errors but more stable? Confirm plz.
much better and more stable, just run a second complete blockchain scan from genesis without any problems.
as said, each request invokes the above mentioned pattern but ist seems it doesn't hurt the client.
(well, pointer execptions are normally a serious thing but it looks like the client don't care much about ;-)
edit: tomorrow i will do some benchmarks for massive serial and concurrent request while watching the memory and sockets.
Version 0.2.18 - https://dl.dropboxusercontent.com/u/67242472/Nxt.zip
Changed direct buffer allocation mechanism for peers and API bots. Could anyone test bot part? Is it more or less stable now?
Changed direct buffer allocation mechanism for peers and API bots. Could anyone test bot part? Is it more or less stable now?
testing, getting flooded by this error pattern for each request but it works!
5: java.nio.channels.AsynchronousCloseException
4: java.lang.NullPointerException
4: java.lang.NullPointerException
4: java.lang.NullPointerException
great!, ~7.000 serial requests in a row (the whole blockchain + transactions).
with 0.2.17 at ~500 the client stopped responding. thanks, this makes things much easier.
More errors but more stable? Confirm plz.
Version 0.2.18 - https://dl.dropboxusercontent.com/u/67242472/Nxt.zip
Changed direct buffer allocation mechanism for peers and API bots. Could anyone test bot part? Is it more or less stable now?
Changed direct buffer allocation mechanism for peers and API bots. Could anyone test bot part? Is it more or less stable now?
testing, getting flooded by this error pattern for each request but it works!
5: java.nio.channels.AsynchronousCloseException
4: java.lang.NullPointerException
4: java.lang.NullPointerException
4: java.lang.NullPointerException
great!, ~7.000 serial requests in a row (the whole blockchain + transactions).
with 0.2.17 at ~500 the client stopped responding. thanks, this makes things much easier.
So you would just not include their transactions.
I find it interesting that your coin supply is basically your total hash: therefore your coin supply (percentage) is your hash rate (percentage).
This brings to mind many security issues, namely the practicality of a 51% attack.
Since all the coins are currently held (?), the network cannot be secure until the coins are distributed.
What am I missing here?
Also, since the giveaway thread is locked, no one can get coins to start mining from a faucet.
I find it interesting that your coin supply is basically your total hash: therefore your coin supply (percentage) is your hash rate (percentage).
This brings to mind many security issues, namely the practicality of a 51% attack.
Since all the coins are currently held (?), the network cannot be secure until the coins are distributed.
What am I missing here?
Also, since the giveaway thread is locked, no one can get coins to start mining from a faucet.
The network is secured by founders now. They r very interested in keeping it secure until they sell their coins. After they sell the coins they won't be able to do anything.
Would love to get a couple NXT so i can start mining 
We decided to block accounts that r posted in this thread for giveaway. U have a few minutes to remove ur account id.
Kidding. But this thead is not for giveaways.
well, the giveaway thread is locked atm :S and cryptsy is being wierd again so i cant buy to start mining atm
How do you mine this coin. I have only web "wallet set up"
Can you even do that?
Only if u have 51% of all coins.
So you would just not include their transactions.
I find it interesting that your coin supply is basically your total hash: therefore your coin supply (percentage) is your hash rate (percentage).
This brings to mind many security issues, namely the practicality of a 51% attack.
Since all the coins are currently held (?), the network cannot be secure until the coins are distributed.
What am I missing here?
Also, since the giveaway thread is locked, no one can get coins to start mining from a faucet.
Can you even do that?
Only if u have 51% of all coins.
Any ETA for a version that fixes the block write exceptions?
0.2.18 fixes memory issue a little so block write exceptions should appear less often.
Version 0.2.18 - https://dl.dropboxusercontent.com/u/67242472/Nxt.zip
Changed direct buffer allocation mechanism for peers and API bots. Could anyone test bot part? Is it more or less stable now?
Changed direct buffer allocation mechanism for peers and API bots. Could anyone test bot part? Is it more or less stable now?
Any ETA for a version that fixes the block write exceptions?
Can you even do that?
Jump to: