This is exact copy of Java version |
|
|
|
Normal cash is being phased out. It is not "legal tender for all debts public and private" anymore. You cant even buy wifi time at airports with cash!
Maybe that doesnt bother you, thats ok. I am working on creating a replacement for cash for people who care about stuff like privacy, which also relates to freedom
James
Or just wandering aimlessly from one thing to another without completing a single thing that is functional and deployed. "Money" is not something that any govt (or even society) will ever allow to be totally anonymous and untraceable. There are taxes, child porn sellers, paid assassins, prostitutes, fraudsters, thieves that require some check and balances. If it ever comes even close to be mainstream and anonymous, the govts will make it illegal (felony with 5 years and more prison time). That will make it useless so fast that you will think lighting has struck you. If the US govt makes all crypto illegal that will be pretty much end of it. No Coinbase, overstock and all all mainstream businesses gone within a week (or less). Bitcoin will be back to less than $1 No mainstream business will ever want to be get involved in something that is illegal (who wants prison time? ) so that will relegate it to only criminals who too will give it up after they realize they can't use it for anything useful. Fortunately, crypto is not yet anonymous. People have to convert it to fiat for everyday use. That very crucial step is not anonymous, and it's already illegal to stay anonymous when converting crypto to fiat. |
|
|
|
|
He is like in to.0.1‰? of bitcoin hoader
|
|
|
|
Bitcoin, Nxt and other currencies are only traceable if you have access to the bank records at the source. Retailers, regular people have no way to know who sent them crypto unless that person broadcasted the address in connection with their name somewhere in public. That is plenty of anonymity for anyone who is not doing something fucked up.
Yes, I agree. It's total waste of time and resources spending money and resources on useless "features" like ZeroCash/ZeroCoin whatever you want to call it. This is not going to do crap for Nxt. Everything is already anonymous. For ultra paranoid, use Tor. Everything can be made untraceable by using exchanges from one crypto to another and back. Nothing is anonymous if you try to convert crypto into fiat. If you do try to stay anonymous during fiat conversion , that would be a felony. |
|
|
|
|
I think we need interest outside the speculators. Right now there are only the original stakeholders, developers, and the speculators. We need to make it genuinely useful to outside of these three groups.
Maybe asset wesleh's client and asset exchange will bring some of that market. Not sure.
Until that happens, Nxt isn't going anywhere up.
As for distributed storage, I am not sure about that. We have to seriously consider the consequence of people uploading child porn. How will Nxt prevent that?
|
|
|
|
|
Is there online blockchain explorer?
|
|
|
|
|
Another Aurora ride?
Lets do it.
Pump it to $20 at least
|
|
|
|
|
Who owns NXT.org now?
Shouldn't it be the default instead of just being forwarded to nxtcrypto.org?
|
|
|
|
No, I actually thought of AES256-CBC: Wallet encryption uses AES-256-CBC to encrypt only the private keys that are held in a wallet. The keys are encrypted with a master key which is entirely random. This master key is then encrypted with AES-256-CBC with a key derived from the passphrase using SHA512 and OpenSSL's EVP_BytesToKey and a dynamic number of rounds determined by the speed of the machine which does the initial encryption (and is updated based on the speed of a computer which does a subsequent passphrase change). https://en.bitcoin.it/wiki/Wallet_encryptionExactly what I said. AES is encryption. It's not applied "repeatedly". The password is HASHED repeatedly (in this case with SHA512) PBKDF2 does exactly the same thing http://en.wikipedia.org/wiki/PBKDF2The encryption can still be AES with PBKDF2 So it works like this. User's password = password Hash the password, lets say 100,000 times to slow brute force. 100,000 times: password = Hash (password) .. Use the end result of that 100K hashes to encrypt with AES |
|
|
|
Please consider using multiple rounds of AES256 encryption for the wallet (bitcoin-qt style) until you meet a given time,
You mean multiple rounds of password hashing to generate the AES key http://en.wikipedia.org/wiki/PBKDF2Repeatedly doing AES does nothing, as AES is designed to be fast and it is implemented at hardware, like in Intel CPUs |
|
|
|
" How long will it take that the NXT accounts are all discovered?"
If the password is strong, it will take trillions of years. Can we build something to prevent this? Yes enforce stronger password/pass phrase usage. |
|
|
|
This endless discussion about nodecoin became quite boring, I'm going to derail it a little...
I skip every post that mentions nodecoin. |
|
|
|
Crypto Review Completed, please read. Thanks to Jesse James for completing with thorough review and BloodyRookie for reference. From Jesse James:"I spent some quality time reviewing the core crypto NXT relies on. As part of my review I re-implemented the relevant algorithms https://gist.github.com/doctorevil/9521126 using a different approach in a different language to make sure I understood everything deeply. Although the implementation NXT uses doesn't follow certain algorithm specifications to the letter, the deviations noted (motivated by simplicity and/or performance) seemed reasonable and in general nothing stuck out as a red flag. There was one bug in the signature generation function (that NXT is aware of and currently working around) for which I've provided a patch (or more precisely tweaked BloodyRookie's proposed patch). It should be should be safe for devs to incorporate this patch at their convenience. Review: https://gist.github.com/doctorevil/9521116Code: https://gist.github.com/doctorevil/9521126 " Wow. I trust this guy more than C++ converted to Java implementation that we are using right now. I talked to both the original C++ author and Java converter and both seem to be clueless, really. Can we at least fix signing now? public static final boolean sign(byte[] v, byte[] h, byte[] x, byte[] s) {
// v = (x - h) s mod q
int w, i;
byte[] h1 = new byte[32], x1 = new byte[32];
byte[] tmp1 = new byte[64];
byte[] tmp2 = new byte[64];
// Don't clobber the arguments, be nice!
cpy32(h1, h);
cpy32(x1, x);
// Reduce modulo group order
byte[] tmp3=new byte[32];
divmod(tmp3, h1, 32, ORDER, 32);
divmod(tmp3, x1, 32, ORDER, 32);
// v = x1 - h1
// If v is negative, add the group order to it to become positive.
// If v was already positive we don't have to worry about overflow
// when adding the order because v < ORDER and 2*ORDER < 2^256
mula_small(v, x1, 0, h1, 32, -1);
mula_small(v, v , 0, ORDER, 32, 1);
// tmp1 = (x-h)*s mod q
mula32(tmp1, v, s, 32, 1);
divmod(tmp2, tmp1, 64, ORDER, 32);
for (w = 0, i = 0; i < 32; i++)
w |= v = tmp1;
return w != 0;
}
This would also apply to javascript version that wesleh would use. |
|
|
|
Crypto Review Completed, please read. Thanks to Jesse James for completing with thorough review and BloodyRookie for reference. From Jesse James:"I spent some quality time reviewing the core crypto NXT relies on. As part of my review I re-implemented the relevant algorithms https://gist.github.com/doctorevil/9521126 using a different approach in a different language to make sure I understood everything deeply. Although the implementation NXT uses doesn't follow certain algorithm specifications to the letter, the deviations noted (motivated by simplicity and/or performance) seemed reasonable and in general nothing stuck out as a red flag. There was one bug in the signature generation function (that NXT is aware of and currently working around) for which I've provided a patch (or more precisely tweaked BloodyRookie's proposed patch). It should be should be safe for devs to incorporate this patch at their convenience. Review: https://gist.github.com/doctorevil/9521116Code: https://gist.github.com/doctorevil/9521126 " Wow. I trust this guy more than C++ converted to Java implementation that we are using right now. I talked to both the original C++ author and Java converter and both seem to be clueless, really. |
|
|
|
Question about public key thingie;
Don't users only get a public key after they made an outgoing transaction? So their first transaction, if they use an online client, would be insecure?
Right, or you will have to calculate the public key from the secret phrase on the client side too. Ah ok, cool. Hi, make this implementation a top priority. This is key to introducing Nxt to masses without them having to download java and understand "batch" files". Marketers can then promote your client as the only requirement to use Nxt. You can upload them on Chrome and Firefox app stores. This will change the tone here where people think Nxt is too complicated. |
|
|
|
mynxt.info nodes appear to be using 0.7.5 87.230.14.1 use 0.8.5. Seems like a bug with 0.8.5... bter also has problems with confirmations no, it's just 87.230.14.1 |
|
|
|
ps. @IE; I have to move my cursor to generate a password. @Chrome; Password generated automatically. Without moving mouse.
You need to update to IE 11. IE 10 and older requires mouse movement |
|
|
|
Assume there is a bounty for solving the problem, then when the problem gets solved, the coin dies naturally and the bounty can be divided just by buying all the coins using it.
I think this would totally change how the researches that need massive computing resource are done, or every one is aware of such an idea?
Doesn't make sense. Why would the coin have any value if it can be killed by a solvable "weakness"? |
|
|
|
|
Show Posts
