Other conditions are met?
I didn't check it yet. It's not fast enough AFAIK.
Topic: NXT :: descendant of Bitcoin - Updated Information - page 1746. (Read 2761645 times)
I didn't check it yet. It's not fast enough AFAIK.
Nobody tried to convert cpp to js?
The code must be readable so ppl could make sure that it doesn't steal their passphrase.
Bounty announcement
100'000 NXT will be paid for working JavaScript code that signs and verifies signatures using NRS algo.
- The licence must allow to use the code in any application
- Sign/verify speed must be not lower than 100 signatures per second on a 1 GHz CPU (1 core)
- All the code must be in a single non-obfuscated well-formatted .js file
- Input/output values must be strings like "8302504e4e57c6c65335289879c6915a273d3aae7bd086058e403fcd2bc18341"
The bounty is valid till the 20th of January, 2014 12:00:00 UTC. The complete code must be published in this thread.
Currently i can't see solution for speed up my code to achieve goal, so i decided release it in current state. Other conditions are met.100'000 NXT will be paid for working JavaScript code that signs and verifies signatures using NRS algo.
- The licence must allow to use the code in any application
- Sign/verify speed must be not lower than 100 signatures per second on a 1 GHz CPU (1 core)
- All the code must be in a single non-obfuscated well-formatted .js file
- Input/output values must be strings like "8302504e4e57c6c65335289879c6915a273d3aae7bd086058e403fcd2bc18341"
The bounty is valid till the 20th of January, 2014 12:00:00 UTC. The complete code must be published in this thread.
https://github.com/moadib/nxt_crypto_js
On my PC(core i5 2.6ghz) Java implementation from Nxt sources took approx 20ms for one signature.
My JS code on Google V8(chrome, nodejs) took approx 200ms.
The main problem is that JS doesn't support 64bit math, so script spend most time on emulating this.
Quote
Dependencies, included in script:
Long class from Google Closure Library (Apache license)
jssha256 by B. Poettering (GNU GPL)
Long class from Google Closure Library (Apache license)
jssha256 by B. Poettering (GNU GPL)
Other conditions are met?
Bounty announcement
100'000 NXT will be paid for working JavaScript code that signs and verifies signatures using NRS algo.
- The licence must allow to use the code in any application
- Sign/verify speed must be not lower than 100 signatures per second on a 1 GHz CPU (1 core)
- All the code must be in a single non-obfuscated well-formatted .js file
- Input/output values must be strings like "8302504e4e57c6c65335289879c6915a273d3aae7bd086058e403fcd2bc18341"
The bounty is valid till the 20th of January, 2014 12:00:00 UTC. The complete code must be published in this thread.
100'000 NXT will be paid for working JavaScript code that signs and verifies signatures using NRS algo.
- The licence must allow to use the code in any application
- Sign/verify speed must be not lower than 100 signatures per second on a 1 GHz CPU (1 core)
- All the code must be in a single non-obfuscated well-formatted .js file
- Input/output values must be strings like "8302504e4e57c6c65335289879c6915a273d3aae7bd086058e403fcd2bc18341"
The bounty is valid till the 20th of January, 2014 12:00:00 UTC. The complete code must be published in this thread.
Nobody tried to convert cpp to js?
CFB - any input on what this guy has done?
I didn't check if it works correctly. If noone shows code that works much faster then hoax will get part of the bounty.
p.s. I hope he doesn't say now "Thank you for your frictionlesscoin competent opinion" 
Bounty announcement
100'000 NXT will be paid for working JavaScript code that signs and verifies signatures using NRS algo.
- The licence must allow to use the code in any application
- Sign/verify speed must be not lower than 100 signatures per second on a 1 GHz CPU (1 core)
- All the code must be in a single non-obfuscated well-formatted .js file
- Input/output values must be strings like "8302504e4e57c6c65335289879c6915a273d3aae7bd086058e403fcd2bc18341"
The bounty is valid till the 20th of January, 2014 12:00:00 UTC. The complete code must be published in this thread.
Currently i can't see solution for speed up my code to achieve goal, so i decided release it in current state. Other conditions are met.100'000 NXT will be paid for working JavaScript code that signs and verifies signatures using NRS algo.
- The licence must allow to use the code in any application
- Sign/verify speed must be not lower than 100 signatures per second on a 1 GHz CPU (1 core)
- All the code must be in a single non-obfuscated well-formatted .js file
- Input/output values must be strings like "8302504e4e57c6c65335289879c6915a273d3aae7bd086058e403fcd2bc18341"
The bounty is valid till the 20th of January, 2014 12:00:00 UTC. The complete code must be published in this thread.
https://github.com/moadib/nxt_crypto_js
On my PC(core i5 2.6ghz) Java implementation from Nxt sources took approx 20ms for one signature.
My JS code on Google V8(chrome, nodejs) took approx 200ms.
The main problem is that JS doesn't support 64bit math, so script spend most time on emulating this.
CFB - any input on what this guy has done?
I just read 300+ pages of Come-from-Beyond's posts 
I'm freak I know...(actually was quite fun cause very often you are not sure if he is serious or he is trolling trolls )
I have to say though that I found in his posts more valueable info than anywhere else! I think anyone who does this will feel much more confident about NXT!
p.s. I hope he doesn't say now "Thank you for yourfrictionlesscoin competent opinion"
I'm freak I know...(actually was quite fun cause very often you are not sure if he is serious or he is trolling trolls )I have to say though that I found in his posts more valueable info than anywhere else! I think anyone who does this will feel much more confident about NXT!
p.s. I hope he doesn't say now "Thank you for your
You made a good point. Someone's acount can also have weak password.
But isn't there any difference between passwords locking common users accounts and these unused with NXTs sent there by mistake? Isn't it different format of password like random string + ending with string of zeros?
If there is a difference we can simply create a standard for treasure hunting of only these lost NXTs.
But isn't there any difference between passwords locking common users accounts and these unused with NXTs sent there by mistake? Isn't it different format of password like random string + ending with string of zeros?
If there is a difference we can simply create a standard for treasure hunting of only these lost NXTs.
If u use SHA256(Curve25519(Random256Bits)) instead of SHA256(Curve25519(SHA256(RandomChars))) to hack the accounts then u still will be a good guy.
If there are some accounts with substancial amounts of NXT which are nobody's property and have weaker passwords than maybe we could create special thread to organise group cracking.
I'm sure a lot of people would like to use script/program to make such group brute force treasure hunting
It could be constructed in similar way as altcoins pool mining with system of distribution f.e. lucky one would get half of found NXTs and the rest of could get proportional part of other half. Also it could be a simple solo treasure hunting.
This would be great for increasing NXT community and would be simply fun. In future because of growing amounts of NXT's lost in void it would become even more successful. What do you think about it?
I'm sure a lot of people would like to use script/program to make such group brute force treasure hunting
It could be constructed in similar way as altcoins pool mining with system of distribution f.e. lucky one would get half of found NXTs and the rest of could get proportional part of other half. Also it could be a simple solo treasure hunting.
This would be great for increasing NXT community and would be simply fun. In future because of growing amounts of NXT's lost in void it would become even more successful. What do you think about it?
I would love to have a group like this exist. It would really show how difficult (or easy
) it is to crack a NXT account.I would gladly raise a funding for a project like this even just for research purpose.
I would consider that to be morally wrong, at least trying to crack private keys for weak passphrases. However, the hiberNXT on the other hard where there are no published public keys are another story.
You made a good point. Someone's acount can also have weak password.
But isn't there any difference between passwords locking common users accounts and these unused with NXTs sent there by mistake? Isn't it different format of password like random string + ending with string of zeros?
If there is a difference we can simply create a standard for treasure hunting of only these lost NXTs.
There is a difference between black hat and white hat hackers. We can try to hack even normal accounts, not to take the money away but to inform the owner and also raise the awareness about the security issue. I think it is normal procedure for security firm to invite or hire white hat hackers to hack their system to see if there is any compromise.
If there are some accounts with substancial amounts of NXT which are nobody's property and have weaker passwords than maybe we could create special thread to organise group cracking.
I'm sure a lot of people would like to use script/program to make such group brute force treasure hunting
It could be constructed in similar way as altcoins pool mining with system of distribution f.e. lucky one would get half of found NXTs and the rest of could get proportional part of other half. Also it could be a simple solo treasure hunting.
This would be great for increasing NXT community and would be simply fun. In future because of growing amounts of NXT's lost in void it would become even more successful. What do you think about it?
I'm sure a lot of people would like to use script/program to make such group brute force treasure hunting
It could be constructed in similar way as altcoins pool mining with system of distribution f.e. lucky one would get half of found NXTs and the rest of could get proportional part of other half. Also it could be a simple solo treasure hunting.
This would be great for increasing NXT community and would be simply fun. In future because of growing amounts of NXT's lost in void it would become even more successful. What do you think about it?
I would love to have a group like this exist. It would really show how difficult (or easy
) it is to crack a NXT account.I would gladly raise a funding for a project like this even just for research purpose.
I would consider that to be morally wrong, at least trying to crack private keys for weak passphrases. However, the hiberNXT on the other hard where there are no published public keys are another story.
You made a good point. Someone's acount can also have weak password.
But isn't there any difference between passwords locking common users accounts and these unused with NXTs sent there by mistake? Isn't it different format of password like random string + ending with string of zeros?
If there is a difference we can simply create a standard for treasure hunting of only these lost NXTs.
As CfB said, its to allow future recovery of "lost" NXT in the future. "Lost" as in someone mistakenly sent NXT to the wrong address that doesnt yet exist.
So basically, CfB and BCNext are here to tell you that that was the plan all along, and that EVERYONE is advised to secure all accounts by paying for at least 1 transaction/alias.
CAUSE IM COMING FOR YOUR HIBERNXT WITH MA CURVE25519 ASIC IN 2015
Any ways to speed up block generating? Maybe target manipulating?
http://www.links.org/files/decentralised-currencies.pdf
Beyonce posted this a while back... Are there any discussions on bitcointalk about it?
I finally read that paperBeyonce posted this a while back... Are there any discussions on bitcointalk about it?
I have a better question: if I hardcode 136941 first blocks and run it at single node will my chain win? Why not?
If there are some accounts with substancial amounts of NXT which are nobody's property and have weaker passwords than maybe we could create special thread to organise group cracking.
I'm sure a lot of people would like to use script/program to make such group brute force treasure hunting
It could be constructed in similar way as altcoins pool mining with system of distribution f.e. lucky one would get half of found NXTs and the rest of could get proportional part of other half. Also it could be a simple solo treasure hunting.
This would be great for increasing NXT community and would be simply fun. In future because of growing amounts of NXT's lost in void it would become even more successful. What do you think about it?
I'm sure a lot of people would like to use script/program to make such group brute force treasure hunting
It could be constructed in similar way as altcoins pool mining with system of distribution f.e. lucky one would get half of found NXTs and the rest of could get proportional part of other half. Also it could be a simple solo treasure hunting.
This would be great for increasing NXT community and would be simply fun. In future because of growing amounts of NXT's lost in void it would become even more successful. What do you think about it?
I would love to have a group like this exist. It would really show how difficult (or easy
) it is to crack a NXT account.I would gladly raise a funding for a project like this even just for research purpose.
I would consider that to be morally wrong, at least trying to crack private keys for weak passphrases. However, the hiberNXT on the other hard where there are no published public keys are another story.
You made a good point. Someone's acount can also have weak password.
But isn't there any difference between passwords locking common users accounts and these unused with NXTs sent there by mistake? Isn't it different format of password like random string + ending with string of zeros?
If there is a difference we can simply create a standard for treasure hunting of only these lost NXTs.
Any ways to speed up block generating? Maybe target manipulating?
http://www.links.org/files/decentralised-currencies.pdf
Beyonce posted this a while back... Are there any discussions on bitcointalk about it?
I finally read that paper Beyonce posted this a while back... Are there any discussions on bitcointalk about it?
We can't just extend 15 sec limit. Node owners will stop watching their clocks and the network will become vulnerable to time travel attacks.
Bug report:
Registered alias via alias.html
Filled fields. Pressed button. Button disabled. Wait. Wait. Button enabled. No text in bottom text field appeared.
What should I do?
Registered alias via alias.html
Filled fields. Pressed button. Button disabled. Wait. Wait. Button enabled. No text in bottom text field appeared.
What should I do?
I would wait for at least ten blocks to see if a transaction appears in that account.
Edit: This just happened to me too... I got a transaction number for the alias assignment... but nothing has appeared in the Block Explorer yet.
I know, I know. And we know that
Most mainstream users just like what are friendly and easy to use.
An easy fix would be to extend 15 sec gap for transaction timestamp... If a timestamp is more than 15 sec in the future, the transation is ignored.
U just have to convince the community that it's a useful feature and find someone who will write the code.
Bug report:
Registered alias via alias.html
Filled fields. Pressed button. Button disabled. Wait. Wait. Button enabled. No text in bottom text field appeared.
What should I do?
Registered alias via alias.html
Filled fields. Pressed button. Button disabled. Wait. Wait. Button enabled. No text in bottom text field appeared.
What should I do?
I have encountered it at least 5 times.
Bug report:
I have a bug when sending out money, twice in a row. The transactions still went though but the server stopped working and the send money command never moved to "money is sent" stage.
I have a bug when sending out money, twice in a row. The transactions still went though but the server stopped working and the send money command never moved to "money is sent" stage.
What was the error message in the console?
I already restarted the client. Sorry to ask it again but How to record a log in Window ?
[Alt] + [PrintScreen]
Bug report:
Registered alias via alias.html
Filled fields. Pressed button. Button disabled. Wait. Wait. Button enabled. No text in bottom text field appeared.
What should I do?
Registered alias via alias.html
Filled fields. Pressed button. Button disabled. Wait. Wait. Button enabled. No text in bottom text field appeared.
What should I do?
I would wait for at least ten blocks to see if a transaction appears in that account.
Edit: This just happened to me too... I got a transaction number for the alias assignment... but nothing has appeared in the Block Explorer yet.
I know, I know. And we know that
Most mainstream users just like what are friendly and easy to use.
An easy fix would be to extend 15 sec gap for transaction timestamp... If a timestamp is more than 15 sec in the future, the transation is ignored.
Bug report:
I have a bug when sending out money, twice in a row. The transactions still went though but the server stopped working and the send money command never moved to "money is sent" stage.
I have a bug when sending out money, twice in a row. The transactions still went though but the server stopped working and the send money command never moved to "money is sent" stage.
What was the error message in the console?
I already restarted the client. Sorry to ask it again but How to record a log in Window ?
Jump to: