Topic: NXT :: descendant of Bitcoin - Updated Information - page 1029. (Read 2761645 times)
Want to catch some cheap NXT how low will it go 0.05?
http://i065.radikal.ru/1402/8e/e63d56747d70.jpg
So what does base target percentage actually mean?
Is there a "good" and a "bad" percentage? If so, what are they? (less than X, greater than Y)?
Is there a "good" and a "bad" percentage? If so, what are they? (less than X, greater than Y)?
It is not about how but about what.
Sometimes, you talk about the implementation of Curve+Signature, sometimes you talk about the implementation and use of the two. We don't have the original source (in quasm code) of Mr. Bernstein's curve, only the ported one, so I think you mean the curve in general AND the implementation of the two. But on the other hand, I think one day you talked about who we use the algo also. Blahblahblah...
Does anyone have a clue, what CfB wants?
Sometimes, you talk about the implementation of Curve+Signature, sometimes you talk about the implementation and use of the two. We don't have the original source (in quasm code) of Mr. Bernstein's curve, only the ported one, so I think you mean the curve in general AND the implementation of the two. But on the other hand, I think one day you talked about who we use the algo also. Blahblahblah...
Does anyone have a clue, what CfB wants?
I confuse "what" and "how", they r interchangable in Russian.
We need audit of Crypto and Curve25519 classes.
Edit: Wait for critical bug disclosure to get it better. The bug is related to Crypto implementation. An audit would let to avoid the bug.
I think that we could run Scripting on a parallel chain. Main chain won't be hurt if something goes wrong.
Very interested to see how this "parallel chain" stuff is going to work - and yes I guess it could be the safest way to do the "smart contracts".
Am guessing that if we approach it that way then the 100+ TPS should not be affected by this or other ideas that could also be put into "parallel chains".
Maybe this is the "real ace" that Nxt has up its sleeve?
I said this a long time ago
I think I mentioned this hundreds of pages ago, but why do we assume transactions and DACs have to be on the same blockchain? The beauty of multiple chains is that people can choose which chains to point their devices at. Smartphone users would be happy to point their smart phones at the main chain only, while those with powerful desktops can point their machine at both the main chain and the DAC chain. Both chains can be run at 1 minute between blocks, to maintain consistency. Also, I wonder if coins can be transferred between chains? If not, I'm 99% sure the AE can take care of that.
Also, can anyone answer this: how does etherium handle a situation where one computer is faster than the other? Does the network just work at a predefined speed (# of OPs per minute) and anyone who can't reach that quota is kicked off the network? Or do they have some method of comparing output from multiple nodes to make sure the same inputs produce the same outputs (unlimited OPs per minute, depending on size of network and # of matching answers needed)?
Also, can anyone answer this: how does etherium handle a situation where one computer is faster than the other? Does the network just work at a predefined speed (# of OPs per minute) and anyone who can't reach that quota is kicked off the network? Or do they have some method of comparing output from multiple nodes to make sure the same inputs produce the same outputs (unlimited OPs per minute, depending on size of network and # of matching answers needed)?
+1
Who tackles parallel blockchains? JL? CfB? BCNext? bitcoinpaul?
I received this response from a Crypto expert after reviewing code, here was the response, need some clarification from CFB or devs:
"Thanks very much for sending me the code. I took a quick look and understood that it is an implementation of two well known crypto algorithms -- elliptic curve based key agreement scheme (ecdh) and digital signature scheme (ec-kcdsa). The code itself was ported from C to Java back in 2008, and so it has been around for quite a while.
I am wondering what you are looking for in the code review. If it is mainly the correctness of the implementation, then I would take a pass. I feel that what would be most helpful for Nxt is to review how the above crypto algorithms are utilized within the Nxt currency system to achieve the intended security goals. "
If anyone has an appropriate response, let me know.
"Thanks very much for sending me the code. I took a quick look and understood that it is an implementation of two well known crypto algorithms -- elliptic curve based key agreement scheme (ecdh) and digital signature scheme (ec-kcdsa). The code itself was ported from C to Java back in 2008, and so it has been around for quite a while.
I am wondering what you are looking for in the code review. If it is mainly the correctness of the implementation, then I would take a pass. I feel that what would be most helpful for Nxt is to review how the above crypto algorithms are utilized within the Nxt currency system to achieve the intended security goals. "
If anyone has an appropriate response, let me know.
U'll see a perfect example of how audit should be done in several hours when I disclose the critical bug description.
It is not about how but about what.
Sometimes, you talk about the implementation of Curve+Signature (especially 64bit), sometimes you talk about the implementation and use of the two. We don't have the original source (in quasm code, 32bit) of Mr. Bernstein's curve, only the ported one, so I think you mean the curve in general AND the implementation of the two. But one day, I think you talked about how we use the algo also. Blahblahblah...
Does anyone have a clue, what CfB wants?
I received this response from a Crypto expert after reviewing code, here was the response, need some clarification from CFB or devs:
"Thanks very much for sending me the code. I took a quick look and understood that it is an implementation of two well known crypto algorithms -- elliptic curve based key agreement scheme (ecdh) and digital signature scheme (ec-kcdsa). The code itself was ported from C to Java back in 2008, and so it has been around for quite a while.
I am wondering what you are looking for in the code review. If it is mainly the correctness of the implementation, then I would take a pass. I feel that what would be most helpful for Nxt is to review how the above crypto algorithms are utilized within the Nxt currency system to achieve the intended security goals. "
If anyone has an appropriate response, let me know.
"Thanks very much for sending me the code. I took a quick look and understood that it is an implementation of two well known crypto algorithms -- elliptic curve based key agreement scheme (ecdh) and digital signature scheme (ec-kcdsa). The code itself was ported from C to Java back in 2008, and so it has been around for quite a while.
I am wondering what you are looking for in the code review. If it is mainly the correctness of the implementation, then I would take a pass. I feel that what would be most helpful for Nxt is to review how the above crypto algorithms are utilized within the Nxt currency system to achieve the intended security goals. "
If anyone has an appropriate response, let me know.
It seems to me that his two categorizations are really the same thing and are what we are looking for
Okay, is there something else I can send, perhaps more clarification to exactly what we are looking for? Also, it's a she, Lisa Yin, PHD in Cryptography from MIT.
In the code, there are comments regarding sign and verify. Could you kindly ask her to verify math behind it*? (that is math behind sign + verify)
Also, you can provide her with links, to two interesting (old) threads on sci.crypt:
http://sci.crypt.narkive.com/mukCBREz/curve25519-ecdh-portable-c-implementation
https://groups.google.com/d/msg/sci.crypt/MFp1DB7ypp4/mA1NaYYEVm4J
interesting quote from second one:
Quote
Note that there isn't actually such a thing as positive or negative in
a finite field, but you should just pick some definition. My favorite
is to define elements with the least significant bit set (when fully
reduced) to be negative, and non-zero elements with the least
significant bit clear (when fully reduced) to be positive.
a finite field, but you should just pick some definition. My favorite
is to define elements with the least significant bit set (when fully
reduced) to be negative, and non-zero elements with the least
significant bit clear (when fully reduced) to be positive.
(PS, there was already done analysis by BloodyRookie: https://bitcointalksearch.org/topic/m.4645132)
with 0.7.0e
any suggestion?
TKS.
Code:
[2014-02-07 12:57:56.176] DEBUG: Database cache size set to 126720 kB
[2014-02-07 12:57:58.927] Database is at level 6
[2014-02-07 12:57:58.928] Updated database is at level 6
[2014-02-07 12:57:59.077] Scanning blockchain...
stick the above for a moment ,then the cmd window disappear.[2014-02-07 12:57:58.927] Database is at level 6
[2014-02-07 12:57:58.928] Updated database is at level 6
[2014-02-07 12:57:59.077] Scanning blockchain...
any suggestion?
TKS.
me too...!
Why are you making logos that looks like a tomb stone? Now i said it. Cheers
Its a CfB private commission...he's gonna be handing out boxes of Chocolates-from-Beyond.
LOL
I received this response from a Crypto expert after reviewing code, here was the response, need some clarification from CFB or devs:
"Thanks very much for sending me the code. I took a quick look and understood that it is an implementation of two well known crypto algorithms -- elliptic curve based key agreement scheme (ecdh) and digital signature scheme (ec-kcdsa). The code itself was ported from C to Java back in 2008, and so it has been around for quite a while.
I am wondering what you are looking for in the code review. If it is mainly the correctness of the implementation, then I would take a pass. I feel that what would be most helpful for Nxt is to review how the above crypto algorithms are utilized within the Nxt currency system to achieve the intended security goals. "
If anyone has an appropriate response, let me know.
"Thanks very much for sending me the code. I took a quick look and understood that it is an implementation of two well known crypto algorithms -- elliptic curve based key agreement scheme (ecdh) and digital signature scheme (ec-kcdsa). The code itself was ported from C to Java back in 2008, and so it has been around for quite a while.
I am wondering what you are looking for in the code review. If it is mainly the correctness of the implementation, then I would take a pass. I feel that what would be most helpful for Nxt is to review how the above crypto algorithms are utilized within the Nxt currency system to achieve the intended security goals. "
If anyone has an appropriate response, let me know.
U'll see a perfect example of how audit should be done in several hours when I disclose the critical bug description.
I received this response from a Crypto expert after reviewing code ...
- msin, thank you very much for your efforts! I received this response from a Crypto expert after reviewing code, here was the response, need some clarification from CFB or devs:
"Thanks very much for sending me the code. I took a quick look and understood that it is an implementation of two well known crypto algorithms -- elliptic curve based key agreement scheme (ecdh) and digital signature scheme (ec-kcdsa). The code itself was ported from C to Java back in 2008, and so it has been around for quite a while.
I am wondering what you are looking for in the code review. If it is mainly the correctness of the implementation, then I would take a pass. I feel that what would be most helpful for Nxt is to review how the above crypto algorithms are utilized within the Nxt currency system to achieve the intended security goals. "
If anyone has an appropriate response, let me know.
"Thanks very much for sending me the code. I took a quick look and understood that it is an implementation of two well known crypto algorithms -- elliptic curve based key agreement scheme (ecdh) and digital signature scheme (ec-kcdsa). The code itself was ported from C to Java back in 2008, and so it has been around for quite a while.
I am wondering what you are looking for in the code review. If it is mainly the correctness of the implementation, then I would take a pass. I feel that what would be most helpful for Nxt is to review how the above crypto algorithms are utilized within the Nxt currency system to achieve the intended security goals. "
If anyone has an appropriate response, let me know.
It seems to me that his two categorizations are really the same thing and are what we are looking for
Okay, is there something else I can send, perhaps more clarification to exactly what we are looking for? Also, it's a she, Lisa Yin, PHD in Cryptography from MIT.
It is that C port to java that we are concerned with. I believe our issue is that we can not yet fully trust that this code we do have is in fact the authors original, and cannot get hold of him to ask questions. Its in lines 1414 - 2315 in the source that JLP posted early Jan. I think the proper language is "to audit the implementation of Curve25519 classes and EC-KCDSA classes and their implementation in transaction/block signing as used in NXT" to look for vulnerabilities.
But dont commit the funds right now - I believe we may have found someone to take the funds for an audit. We'll need to figure out what is what. please get your source this info and see what she says.
Okay, will do.
The Nxt Crypto podcast, episode 1
The RSS feed for the cast is NOT ready to go yet, but the first episode is done! Check it out here:
https://soundcloud.com/whatsupnxt/the-nxt-crypto-podcast-ep001
Contents:
- a basic intro to cryptocurrency concepts, and to Nxt
- an interview with Damelon about his involvement with the community
- audio from Tai Zen's interview with Anon136 regarding transparent forging
If all goes according to plan, we'll have it up on a nice, spiffy podcast feed sometime this weekend.
The RSS feed for the cast is NOT ready to go yet, but the first episode is done! Check it out here:
https://soundcloud.com/whatsupnxt/the-nxt-crypto-podcast-ep001
Contents:
- a basic intro to cryptocurrency concepts, and to Nxt
- an interview with Damelon about his involvement with the community
- audio from Tai Zen's interview with Anon136 regarding transparent forging
If all goes according to plan, we'll have it up on a nice, spiffy podcast feed sometime this weekend.
with 0.7.0e
any suggestion?
TKS.
Code:
[2014-02-07 12:57:56.176] DEBUG: Database cache size set to 126720 kB
[2014-02-07 12:57:58.927] Database is at level 6
[2014-02-07 12:57:58.928] Updated database is at level 6
[2014-02-07 12:57:59.077] Scanning blockchain...
stick the above for a moment ,then the cmd window disappear.[2014-02-07 12:57:58.927] Database is at level 6
[2014-02-07 12:57:58.928] Updated database is at level 6
[2014-02-07 12:57:59.077] Scanning blockchain...
any suggestion?
TKS.
How to sign a message?
1. Generate SHA256 of the message
2. Unlock an account
3. Generate a token (purple key icon next to account id) with SHA256 hash used instead of "website"
I think the fact that Russia is gonna get bitcoin banned is one more reason for US government to support bitcoin.
Par for the course.. Russia is clamping down on capital flight. Read this week about how Russias budget relies on spot oil being $100 and its hovering around $103 with shale gas boom driving it further down every week. Russian budget used to be financed with oil/gas at $20bbl. Future is gonna hurt.
what a day...
5 updates! or was it 4?
New chocolates in time for valentines
BTC drops, Nerdery abounds..
I got a letter from Teddy RE: the NYC CryptoConvention. He's seemingly unprepared, sending form letters, but promising website will have speakers package ready soon. I will post it here and we can go over the format and my suitability for the event
5 updates! or was it 4?
New chocolates in time for valentines
BTC drops, Nerdery abounds..
I got a letter from Teddy RE: the NYC CryptoConvention. He's seemingly unprepared, sending form letters, but promising website will have speakers package ready soon. I will post it here and we can go over the format and my suitability for the event
dgex is always downtime,what is the problem? 
Jump to: