I'm new to NXT (as you can tell from my prior posts)....NXT is written in Java? Is it going to get re-written in C++ (if thats even possible)?
It's already rewritten in C#. Someone could rewrite it in C++, Delphi, JavaScript.
Topic: NXT :: descendant of Bitcoin - Updated Information - page 1183. (Read 2761624 times)
It's already rewritten in C#. Someone could rewrite it in C++, Delphi, JavaScript.
Count me in.
I've been thinking about this whole 1000 TPS thing and have a basic question. If ANYBODY can be the node that generates a block, but a node with a low rate data link can't support 1000TPS, then are we saying that the NXT TPS chain is only as strong / fast as its weakest link?
James
So we start by telling people they can forge NXT based on their stake, then blacklist them forever if they can't meet a certain level of performance?
If this is true then we better stop telling people they can forge on their smartphones now, rather than later. Some promotional material may need to be changed to reflect a realistic cost of forging on a high TPS network.
As time goes on, everything gets faster and faster so maybe at first only high end smartphones can handle a sustained 1000TPS network, but later more and more can.
Unlike with BTC, as time goes on, more and more hardware can keep up
If this is true then we better stop telling people they can forge on their smartphones now, rather than later. Some promotional material may need to be changed to reflect a realistic cost of forging on a high TPS network.
It's possible to forge on smartphones even with 1000 tps. U confuse numbers I think.
Looks like jl777 is looking for some skilled developers to join his effort. His plan has merit. Watching with interest!
Me too.
It's interesting to see what possible use one can get out of an old system, which is completely different, has limitations that make it impractical, will be completely rewritten from scratch by the zerocoin guys and implemented as a stand-alone altcoin instead of a Bitcoin integration. I also have no idea what this imaginary "zerocoin API" is that he keeps talking about.
So I think he, indeed, needs some skilled developers to explain to him why this might not be such a good idea...
Meanwhile, if anyone interested in Zerocash (i.e. Zerocoin 2.0) and its possible integration with NXT, follow http://wiki.nxtcrypto.org/wiki/NxtCash - I will keep updating it as we go.
Watching NxtChg with interest too.
I'm new to NXT (as you can tell from my prior posts)....NXT is written in Java? Is it going to get re-written in C++ (if thats even possible)?
Would that be json related?
No. It's legacy of NRS web interface.
Could we feasably get 200Ktps with full TF using JSON transport? Or will full TF just absolutely REQUIRE binary transport, regardless of the desired performance?
We could switch to 200 tps rate but it's not that cool as switching to 1'000 tps, is it?
I dont think anyone posted this yet..
What Is Transparent Forging In Nextcoin (NXT)? - By Tai Zen,
http://www.youtube.com/watch?v=DfFZBuyXI-s
What Is Transparent Forging In Nextcoin (NXT)? - By Tai Zen,
http://www.youtube.com/watch?v=DfFZBuyXI-s
waaaaaaay to go Anon!
Why dont you become NXT speaker?
Count me in.
I've been thinking about this whole 1000 TPS thing and have a basic question. If ANYBODY can be the node that generates a block, but a node with a low rate data link can't support 1000TPS, then are we saying that the NXT TPS chain is only as strong / fast as its weakest link?
James
So we start by telling people they can forge NXT based on their stake, then blacklist them forever if they can't meet a certain level of performance?
If this is true then we better stop telling people they can forge on their smartphones now, rather than later. Some promotional material may need to be changed to reflect a realistic cost of forging on a high TPS network.
I guess after the migration that the API as we know it now would cease to exist?
No. Why?
I just guessed (incorrectly, apparently) that with you just talking about JSON p2p transport going away, coupled with that we also have the previous thread with all the talks of APIv2 and API1 going away, that APIv2 was related to the conversion of binary transport as the p2p mechanism, and I assumed that JSON API stuff would disappear. So with that out of the way.
Could we feasably get 200Ktps with full TF using JSON transport? Or will full TF just absolutely REQUIRE binary transport, regardless of the desired performance?
interesting thing early in the morning! I'll just jump on that with my Raspi: Raspi seems to need 1000ms or sometimes 2000ms to answer a simple query! The testnet used to have ~150ms.
This is some serious performance concern to me. Would that be json related?
I guess after the migration that the API as we know it now would cease to exist?
No. Why?
I just guessed (incorrectly, apparently) that with you just talking about JSON p2p transport going away, coupled with that we also have the previous thread with all the talks of APIv2 and API1 going away, that APIv2 was related to the conversion of binary transport as the p2p mechanism, and I assumed that JSON API stuff would disappear. So with that out of the way.
Could we feasably get 200Ktps with full TF using JSON transport? Or will full TF just absolutely REQUIRE binary transport, regardless of the desired performance?
I guess after the migration that the API as we know it now would cease to exist?
No. Why?
just gave an interview with tai zen 
it was fun.
it was fun.Do u have the link?
no he says its going to take a day or two to finish the editing.
I've seen the interview. And we know ur real name. Looks like u should change ur nickname now (Anon136).
CfB can offer a minimum bound on bandwidth required for 1000 TPS (1 MBS) but can't say how many NXT service nodes that can handle the full blockchain are required.
I forgot about a very important detail. 1000 tps @ 1 Mbps assumes that we use binary protocol. Now all data in protocol is encoded in JSON, this adds 3x-5x overhead.
We have to migrate to binary protocol before switching TF on.
I guess after the migration that the API as we know it now would cease to exist? If so, how about if we did switch to full TF, but kept JSON transport? Obviously we couldnt expect 1Mtps then, but could we expect 200Ktps?
If so that should sustain us well long enough to get a testbed setup to convert peerexplorer, block explorers, and custom clients over to a binary transport protocol.
CfB can offer a minimum bound on bandwidth required for 1000 TPS (1 MBS) but can't say how many NXT service nodes that can handle the full blockchain are required.
I forgot about a very important detail. 1000 tps @ 1 Mbps assumes that we use binary protocol. Now all data in protocol is encoded in JSON, this adds 3x-5x overhead.
We have to migrate to binary protocol before switching TF on.
Ok so in NXTSolaris, I'm getting an error saying: could not convert variant of type (null) into type (currency).
Thanks for any help
Also, an EAcess violation??
Clearly, I have no idea what I am doing. ...but man, the crypto world has a LONG way to go before mass adoption.
Thanks for any help
Also, an EAcess violation??
Clearly, I have no idea what I am doing. ...but man, the crypto world has a LONG way to go before mass adoption.
Try posting here:
https://nextcoin.org/index.php/topic,2793.0.html
It's the NXTSolaris help forum.
I've never used the NXTSolaris client so I don't know how to help. Sorry.
Ok so in NXTSolaris, I'm getting an error saying: could not convert variant of type (null) into type (currency).
Thanks for any help
Also, an EAcess violation??
Clearly, I have no idea what I am doing. ...but man, the crypto world has a LONG way to go before mass adoption.
Thanks for any help
Also, an EAcess violation??
Clearly, I have no idea what I am doing. ...but man, the crypto world has a LONG way to go before mass adoption.
Such an awful Nxt icon
We even had 2 (/nextcoin and /nxtcoin) and both contain coin. I think NXT represents our cause way better!
IMO /Nxt would be representing "the cause" more than /NXT (the latter would be equivalent to having /BTC rather than /Bitcoin).
I've looked at the wiki, and do not find any definition of a valid block.
How does the client validate the blockchain? What is the computation?
How does the client validate the blockchain? What is the computation?
Jump to: