Although the Nxt Asset Exchange will be a useful addition I think that we are missing something that could be much more useful (and perhaps a "killer" addition) and that is "atomic cross-chain crypto-currency transfers" (some of you would recall I've already mentioned it). As far as I can tell no-one has actually built such a system and also so far I can't even tell if such a transfer using TierNolan's approach ( https://en.bitcoin.it/wiki/Atomic_cross-chain_trading) has ever actually been tested (if anyone has a link that shows such a transaction having taken place then I'd be very interested to see it). IMO this would really be a "game changer" as it could allow people to trade crypto's directly without an exchange and without risk (beyond having to wait for the "refund" problem that is necessary for TierNolan's solution in case the trade doesn't get finalised). It wouldn't work fast enough to do "day trading" but for those not in a huge rush the promise of 100% secure transactions with only minimal blockchain fees would be pretty appealing. What do you guys think? This is what I visualized way back in late Nov when I first started reading about NXT, and why I resolved to not be jelly and got in even though I missed genesis |
|
|
|
For success, 2 things are needed the most.
(1) Very good native client (a few of them coming soon)
(2) The native client should be able to sign the transactions and broadcast it to a public node. That way people don't have to install java and and run complex Nxt server
These two things should be top priority.
That's why there is a bounty for JS signing. I believe we are close |
|
|
|
|
uhhhh... why the big hangup on block 60000?
|
|
|
|
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.
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. |
|
|
|
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.
It seems to me that his two categorizations are really the same thing and are what we are looking for |
|
|
|
|
you guys are killing me. where can I go to read more on this PoN? Cause google aint doin it for me
|
|
|
|
Apparently Im the only one worried about blockchain bloat. Currently a standard NXT transfer costs 1 NXT, and it takes up 128bytes, and lasts forever. We are concerned about AM spamming so the plan is to charge a single rate (currently 1NXT, possibly moving to .1 or .01 or .001 in the near future) for all transaction types and to then just periodically prune AMs so as to make it too expensive to effectively spam the blockchain with AM bloat. A 1000byte AM's transaction takes up about 1132bytes after signature/overhead. And our plan is to prune out all those 1132byte spams periodically. What if I told you that right now, I can spam 1231bytes PERMANENTLY onto the blockchain, for only 1 NXT per transaction. And how cheap will that be when we move min fee to .1 NXT, or even to .01 or HOLY CRAP TO .001?  |
|
|
|
Utopianfuture: Put a bounty on the head of scammers
Anyone willing to sort through NXT adresses sending NXT to different addresses used to claim extra stakes: go for it. x NEM Bounty for anyone that exposes (and proofs) a scammer
wow thats a great idea... lol say every 10 scammers you expose is an additional stake? maybe? or some other number besides 10 |
|
|
|
If you see the NRS stopped message and no errors, then there were no problem with the shutdown. What exactly error do you see on startup?
Client starts... passes all stages... scans blockchain... and then crashes!?!?! ...this after a successful download of the whole blockchain and a clean shutdown... Let me ask again. What error do you see on startup? As in, what gets printed to the console? In 0.7.0e hovering over +10 in transaction list won't reveal actual number of verifications. it does for me Chrome 32.0.1700.107 linux Chrome 32.0.1700.77 |
|
|
|
If you see the NRS stopped message and no errors, then there were no problem with the shutdown. What exactly error do you see on startup?
Client starts... passes all stages... scans blockchain... and then crashes!?!?! ...this after a successful download of the whole blockchain and a clean shutdown... Let me ask again. What error do you see on startup? As in, what gets printed to the console? In 0.7.0e hovering over +10 in transaction list won't reveal actual number of verifications. it does for me |
|
|
|
ctrl-c has been signaling shutdown, I dont think it used to handle it properly, but lately, ctrl-c signals process to end and do a final write to blocks.nxt and transactions.nxt.
I can't do ctrl-c as I don't have the console. I have kill JVM from the task bar. NRS client should have a console or something to shut down the server cleanly. Then we wouldn't have so many issues with corrupted files |
|
|
|
So when I do my installer for 0.7, is it going to cause any issues if I include the nxt_db folder as I include blocks.nxt and transactions.nxt now?
No, but make sure the server has been shutdown cleanly before saving that nxt_db folder. What's the best way to shut down the server "cleanly"? ctrl-c has been signaling shutdown, I dont think it used to handle it properly, but lately, ctrl-c signals process to end and do a final write to blocks.nxt and transactions.nxt. if you just killed the java process, then you were ok as long as either one of those files was not being written to, and that was fairly rare, so you were usually safe by doing that, but there was a risk. using ctrl-c was the resolution i suspect we can still use ctrl-c, but i think just killing the process now may carry a higher risk of corruption since we dont have flat *.nxt files anymore. |
|
|
|
|
ok someone point me to a beginners explanation of pon. Ive never heard about it
|
|
|
|
What does peer.state == 2 signify? TheNxtWiki does not mention it.
you cna use getConstants API to determine stuff like that. peerStates: description: Non-connected value: 0 description: Connected value: 1 description: Disconnected value: 2 |
|
|
|
|
can we expect to be able to zip up the nxt_db file to be used on VPSs when turning up new nodes? Or in migrating from 0.7.0e to 0.7.1?
Also, I normally back up my blockchain with my client running. i just check current block, then zip up the 2 .nxt files then check to make sure the same block is still current. Will this still be possible with the new nxt_db?
|
|
|
|
Has anyone put together a guide for configuring web.xml to run a public hallmarked node? It's been so long since I configured my web.xml. For example, should I change the value of "myport" to 7875 if I'm using 7875 to connect to NRS?
hallmarks are in the wiki under how to most likely no reason at all to change myport. you should leave that as is at 7874 and can still connect to NRS on either 7874 or 7875. myport is the p2p port the client uses |
|
|
|
Has anyone put together a guide for configuring web.xml to run a public hallmarked node? It's been so long since I configured my web.xml. For example, should I change the value of "myport" to 7875 if I'm using 7875 to connect to NRS?
Its in the wiki, but could use some updating wow. damn, has anyone else seen that doc page? I dont think any other crypto has anything like that, prob cause theyre not java based lol. that is simply AMAZING. Will be a huge boon for future devs.
very nice work guys
which one? |
|
|
|
my all time favorite:  |
|
|
|
|
wow. damn, has anyone else seen that doc page? I dont think any other crypto has anything like that, prob cause theyre not java based lol. that is simply AMAZING. Will be a huge boon for future devs.
very nice work guys
|
|
|
|
yes thanks to the creator of peerexplorer crimi666 creating and spreading FUD in his peerexplorer thread on nextcoin. That is the source of this article's 'facts', and is the same thread that I referred to yesterday where I was attacked while trying to explain weights/forging differences. oh well. |
|
|
|
|
Show Posts
