FYI, newcomers!
Did you know you can mine NXT in the Lucky node project?
Computational and bandwidth requirements are very low - some users run it on a Raspberry Pi.
Run the node 24/7 or as often as you can while you work or play.
Join in with the over 100 nodes that are already in the project.
Topic: Nxt source code flaw reports (Read 113312 times)
What proves that ?
It's one of those unprovable statements that are nevertheless true, see https://en.wikipedia.org/wiki/G%C3%B6del%27s_incompleteness_theorems
What proves that ?
What is confirmed
that satoshi ran away and came under the cover as bcnext.
What is confirmed
Not sure if its logic flaw, but somebody could simply change initial allocation in genesis block to give themselves a lot of NXT.
We have seen a case of altered client already, so changing genesis block's hardcoding and hypnotizing jean-luc into signing it as the official release, would be an obvious but effective way to steal a lot of NXT
James
We have seen a case of altered client already, so changing genesis block's hardcoding and hypnotizing jean-luc into signing it as the official release, would be an obvious but effective way to steal a lot of NXT
James
True, that's why noone knows who Jean-Luc is.
Maybe he is BCNext!
Well, BCNext, "Jean-Luc" and Come-from-Beyond are all three Russian.
I'm not entirely sure who is who or whether all three are one, but that makes it more exciting
WOOOOOOOOOOOOOOOOOOOOOOOOOOOW! THANKS!
Appreciate that bounty,
my account is: 15421585458835302363
Too bad you transfered the nxt to bter and left nxt completely already. I was going to donate you some NXT in order to motivate you to stay with usAppreciate that bounty,
my account is: 15421585458835302363
Could be, but could also be, that he stores them on bter or that he moves them through bter to disguise the origin - don't jump to conclusions please
WOOOOOOOOOOOOOOOOOOOOOOOOOOOW! THANKS!
Appreciate that bounty,
my account is: 15421585458835302363
Too bad you transfered the nxt to bter and left nxt completely already. I was going to donate you some NXT in order to motivate you to stay with usAppreciate that bounty,
my account is: 15421585458835302363
That would be stupid. He will dump them too. Let it be. Donate them to some worthy cause
Congrats, Evil-Knievel 
Enjoy your reward and yes please, do stick around ^^
Enjoy your reward and yes please, do stick around ^^ 
funny, I knew ''k'' was picked, I wasn't aware haven't figured out it could be abused in such way:
It's a normal behavior, not a bug, don't waste too much time on that.
That depends on algo.
In case of Nxt's EC-KCDSA "k" value is picked not choosen randomly,
So if you feed it with the same data, sig should be te same...
(k is calculated from 1360-1365, that's Y in NXT code
https://bitbucket.org/JeanLucPicard/nxt-public/src/4073c21098076d3469b3f74d49e73ffabe3a2001/Nxt.java?at=master#cl-1360
and it's based on "sig priv key" (s based on user's pub key) and message
)
Actually, there might be a bug in the C++ code. I compiled it and ran a few tests with sign, but the signature that gets generated is different each time i run the program (typically the sign of an uninitialized variable somewhere). The problem appears to happen somewhere in divmod.
It's a normal behavior, not a bug, don't waste too much time on that.
That depends on algo.
In case of Nxt's EC-KCDSA "k" value is picked not choosen randomly,
So if you feed it with the same data, sig should be te same...
(k is calculated from 1360-1365, that's Y in NXT code
https://bitbucket.org/JeanLucPicard/nxt-public/src/4073c21098076d3469b3f74d49e73ffabe3a2001/Nxt.java?at=master#cl-1360
and it's based on "sig priv key" (s based on user's pub key) and message
)
Yes, congratulations. I didn't realize this bounty was still open. I would have never caught that, even when I had the time to study the code.
WOOOOOOOOOOOOOOOOOOOOOOOOOOOW! THANKS!
Appreciate that bounty,
my account is: 15421585458835302363
This message was too old and has been purged
16386134630970163904: Not a bad account if you're just targeting one... (30,002,058 NXT)
http://www.mynxt.info/blockexplorer/details.php?action=ac&ac=16386134630970163904
http://www.mynxt.info/blockexplorer/details.php?action=ac&ac=16386134630970163904
I'm not sure what I missed, but why is 16386134630970163904 HiberNXT?
http://localhost:7876/nxt?requestType=getAccountPublicKey&account=16386134630970163904
It isn't. Someone just thought that 0 outgoing transaction equals no public key. But forging counts as creating a public key too!
I know - we just saved some trees here
16386134630970163904: Not a bad account if you're just targeting one... (30,002,058 NXT)
http://www.mynxt.info/blockexplorer/details.php?action=ac&ac=16386134630970163904
http://www.mynxt.info/blockexplorer/details.php?action=ac&ac=16386134630970163904
I'm not sure what I missed, but why is 16386134630970163904 HiberNXT?
http://localhost:7876/nxt?requestType=getAccountPublicKey&account=16386134630970163904
It isn't. Someone just thought that 0 outgoing transaction equals no public key. But forging counts as creating a public key too!
16386134630970163904: Not a bad account if you're just targeting one... (30,002,058 NXT)
http://www.mynxt.info/blockexplorer/details.php?action=ac&ac=16386134630970163904
http://www.mynxt.info/blockexplorer/details.php?action=ac&ac=16386134630970163904
I'm not sure what I missed, but why is 16386134630970163904 HiberNXT?
http://localhost:7876/nxt?requestType=getAccountPublicKey&account=16386134630970163904
This message was too old and has been purged
@Twin: This is just a quick-and-dirty implementation, If we had a good structure (maybe some B-trees with a lookup complexity of O(log) ) where all NXT accounts were stored, we could mine them all parallely.
Thats what the github Repository is for ... let us make this "first approach" better ;-)
Thats what the github Repository is for ... let us make this "first approach" better ;-)
I am not doubting that.
We could make a mining pool/mining list where we add account numbers, where we are XX% sure that they are DarkNXT (not accessible because of lost/forgotten passphrase)
They would be "lost" if the sender sent them to wrong ID (mistyped, copy paste error, etc).
This message was too old and has been purged
@Twin: This is just a quick-and-dirty implementation, If we had a good structure (maybe some B-trees with a lookup complexity of O(log) ) where all NXT accounts were stored, we could mine them all parallely.
Thats what the github Repository is for ... let us make this "first approach" better ;-)
Thats what the github Repository is for ... let us make this "first approach" better ;-)
I am not doubting that.
We could make a mining pool/mining list where we add account numbers, where we are XX% sure that they are DarkNXT (not accessible because of lost/forgotten passphrase)
Jump to: