imo these nxt threads should include a clearly marked section "initial coin distribution any why it's fair" in the first post, I immediatelly disregarded this coin utill it was in the "list of all cryptocoins" as "lol scam" without reading further because of this.
also why hasn't BCNext posted since november?
Topic: NXT :: descendant of Bitcoin - Updated Information - page 1884. (Read 2761645 times)
...Unzip the archive to a directory and start the NXTclient.exe. ...
Tried to run it under Wine in Linux, it crashed. Can't risk to run on the Windows box just yet, sorry
hey guys what do u think about first day of nxt's release?
yet unnamed, NXT client for Windows.
May I suggest a name.... Nxt Jupiter Client ...or Jupiter for short.
I like that. :-) I'll think about it (and registered the alias... ;-) )
or Solara....Jupiter might be already taken
My Nxt ID for donations is: 3209075099254042753 - any donation is appreciated.
Thank you,
Wesley
he does it again....i'm becoming ur fanboy Wesley
did someone finished reading the source code ......?
conclusion?
One file, all static. conclusion?
Very interesting way
to use Java. So is Satoshi author or not?
No. Satoshi used 4 files for the source code.
yet unnamed, NXT client for Windows.
May I suggest a name.... Nxt Jupiter Client ...or Jupiter for short.
I like that. :-) I'll think about it (and registered the alias... ;-) )
Hi Jean-Luc, CFB and others interested;
I'm ready with that client side implementation of an SHA256 test. I would like some people to test this. I have tested it on the latest Safari, Firefox, and chrome.
As far as I know this will only run in IE10+, earlier versions of IE are not supported.
You can download the files here: http://nxtra.org/update/update.zip
Unzip, then go to your nxt folder and navigate to webapps > root. Paste the two files there.
Now you should be able to open http://localhost:7874/update.html in the browser.
For this test you will always receive the update notice. An older version is hardcoded in. This is to allow for testing of the sha256 hashing function.
Just follow the instructions; download the client, and then drop it over the dropzone to see if it compares to the official release.
If all goes well you should see this screen:
Now also test it with another file, just a simple txt file or another zip, it doesn't matter. Just pretend this is a fake release.
If that goes well, you should see the following:
I hope this will increase the security of everyone, if you have any feedback, please share.
My Nxt ID for donations is: 3209075099254042753 - any donation is appreciated.
Thank you,
Wesley
I'm ready with that client side implementation of an SHA256 test. I would like some people to test this. I have tested it on the latest Safari, Firefox, and chrome.
As far as I know this will only run in IE10+, earlier versions of IE are not supported.
You can download the files here: http://nxtra.org/update/update.zip
Unzip, then go to your nxt folder and navigate to webapps > root. Paste the two files there.
Now you should be able to open http://localhost:7874/update.html in the browser.
For this test you will always receive the update notice. An older version is hardcoded in. This is to allow for testing of the sha256 hashing function.
Just follow the instructions; download the client, and then drop it over the dropzone to see if it compares to the official release.
If all goes well you should see this screen:
Now also test it with another file, just a simple txt file or another zip, it doesn't matter. Just pretend this is a fake release.
If that goes well, you should see the following:
I hope this will increase the security of everyone, if you have any feedback, please share.
My Nxt ID for donations is: 3209075099254042753 - any donation is appreciated.
Thank you,
Wesley
yet unnamed, NXT client for Windows.
May I suggest a name.... Nxt Jupiter Client ...or Jupiter for short.
What about Last (LST).
just to explain why a colored feedback is not only eyecandy but usefull, consider this.
Ok, if you can make it purely on the client by checking local blockchain fast and cheap - that's great and should be added.
I am just saying that this doesn't solve anything. You don't protect against typos, because there are plenty of legit cases where address will not be in the blockchain.
Then, you don't protect against unhealthy server at all, because, well, you're a client.
Checksums are used everywhere. Here we are talking about big money and the cost of failure is irreversible loss of it.
Honestly, it's beyond me why are we even arguing this.
you are misinterpreting my statement here. i am not against checksum at all.
as said, this is an simple, quick and effective improvement compared to the
current client, not more, not less.
@marcus03, great work marcus. i have some question about how you have managed orphaned blocks and checkpoints etc.
will contact you via pm.
yet unnamed, NXT client for Windows.
May I suggest a name.... Nxt Jupiter Client ...or Jupiter for short.
So is Satoshi author or not?
I belive not. Satoshi is excellent in C++ not in Java
did someone finished reading the source code ......?
conclusion?
One file, all static. conclusion?
Very interesting way
to use Java. So is Satoshi author or not?
just to explain why a colored feedback is not only eyecandy but usefull, consider this.
Ok, if you can make it purely on the client by checking local blockchain fast and cheap - that's great and should be added.
I am just saying that this doesn't solve anything. You don't protect against typos, because there are plenty of legit cases where address will not be in the blockchain.
Then, you don't protect against unhealthy server at all, because, well, you're a client.
Checksums are used everywhere. Here we are talking about big money and the cost of failure is irreversible loss of it.
Honestly, it's beyond me why are we even arguing this.
Since I need to take a day off of programming, here's the first version of my, yet unnamed, NXT client for Windows.
As it is, it's really more of a block chain explorer (you can't send NXT, register aliases, etc. and you are currently not asked for secret phrases for accounts).
Unzip the archive to a directory and start the NXTclient.exe. Make sure that NRS is running locally, or enter an URL like "http://192.168.178.12:7874" when asked (it defaults to "http://127.0.0.1:7874").
The data subdirectory holds the blockchain data in proprietary format as of an hour ago. To import new blocks/transactions from the NRS blockchain into the client, click on the little Refresh icon and relax.
All the data in the blockchain explorer part can't be edited (since it's imported from and in synx with NRS), except for the column "Description" in the list of accounts.
The interface is still very, let's say functional - no bells and whistles yet.
NXTclient-v1.0.zip (28.2 MB) - Download: https://mega.co.nz/#!ONd3XCLQ!O_xx-C6os70pe41Tc3j6CmoUTEl6922SDytC8WD8lko
SHA256 checksum for NXTclient-v1.0.zip: 485735CCB66323E6F0FBF016A4D15134263D6970A9AA81E82CFF5D1AF17C9FEC
Next on my TODO list:
Hope it's already helpful for anyone (e.g. when the online NXT blockchain explorer is down).
Of course, I would not feel like a real NXTer without asking for tips... NXT: 1758531264253431177
As it is, it's really more of a block chain explorer (you can't send NXT, register aliases, etc. and you are currently not asked for secret phrases for accounts).
Unzip the archive to a directory and start the NXTclient.exe. Make sure that NRS is running locally, or enter an URL like "http://192.168.178.12:7874" when asked (it defaults to "http://127.0.0.1:7874").
The data subdirectory holds the blockchain data in proprietary format as of an hour ago. To import new blocks/transactions from the NRS blockchain into the client, click on the little Refresh icon and relax.
All the data in the blockchain explorer part can't be edited (since it's imported from and in synx with NRS), except for the column "Description" in the list of accounts.
The interface is still very, let's say functional - no bells and whistles yet.
NXTclient-v1.0.zip (28.2 MB) - Download: https://mega.co.nz/#!ONd3XCLQ!O_xx-C6os70pe41Tc3j6CmoUTEl6922SDytC8WD8lko
SHA256 checksum for NXTclient-v1.0.zip: 485735CCB66323E6F0FBF016A4D15134263D6970A9AA81E82CFF5D1AF17C9FEC
Next on my TODO list:
- Add aliases to blockchain explorer
- Send NXT function and personal account management
Hope it's already helpful for anyone (e.g. when the online NXT blockchain explorer is down).
Of course, I would not feel like a real NXTer without asking for tips...
NXT: 1758531264253431177Great work! Looks great.
did someone finished reading the source code ......?
conclusion?
One file, all static. conclusion?
Very interesting way
to use Java. U haven't seen 0.2.*
Since I need to take a day off of programming, here's the first version of my, yet unnamed, NXT client for Windows.
As it is, it's really more of a block chain explorer (you can't send NXT, register aliases, etc. and you are currently not asked for secret phrases for accounts).
Unzip the archive to a directory and start the NXTclient.exe. Make sure that NRS is running locally, or enter an URL like "http://192.168.178.12:7874" when asked (it defaults to "http://127.0.0.1:7874").
The data subdirectory holds the blockchain data in proprietary format as of an hour ago. To import new blocks/transactions from the NRS blockchain into the client, click on the little Refresh icon and relax.
All the data in the blockchain explorer part can't be edited (since it's imported from and in synx with NRS), except for the column "Description" in the list of accounts.
The interface is still very, let's say functional - no bells and whistles yet.
NXTclient-v1.0.zip (28.2 MB) - Download: https://mega.co.nz/#!ONd3XCLQ!O_xx-C6os70pe41Tc3j6CmoUTEl6922SDytC8WD8lko
SHA256 checksum for NXTclient-v1.0.zip: 485735CCB66323E6F0FBF016A4D15134263D6970A9AA81E82CFF5D1AF17C9FEC
Next on my TODO list:
Hope it's already helpful for anyone (e.g. when the online NXT blockchain explorer is down).
Of course, I would not feel like a real NXTer without asking for tips... NXT: 1758531264253431177
As it is, it's really more of a block chain explorer (you can't send NXT, register aliases, etc. and you are currently not asked for secret phrases for accounts).
Unzip the archive to a directory and start the NXTclient.exe. Make sure that NRS is running locally, or enter an URL like "http://192.168.178.12:7874" when asked (it defaults to "http://127.0.0.1:7874").
The data subdirectory holds the blockchain data in proprietary format as of an hour ago. To import new blocks/transactions from the NRS blockchain into the client, click on the little Refresh icon and relax.
All the data in the blockchain explorer part can't be edited (since it's imported from and in synx with NRS), except for the column "Description" in the list of accounts.
The interface is still very, let's say functional - no bells and whistles yet.
NXTclient-v1.0.zip (28.2 MB) - Download: https://mega.co.nz/#!ONd3XCLQ!O_xx-C6os70pe41Tc3j6CmoUTEl6922SDytC8WD8lko
SHA256 checksum for NXTclient-v1.0.zip: 485735CCB66323E6F0FBF016A4D15134263D6970A9AA81E82CFF5D1AF17C9FEC
Next on my TODO list:
- Add aliases to blockchain explorer
- Send NXT function and personal account management
Hope it's already helpful for anyone (e.g. when the online NXT blockchain explorer is down).
Of course, I would not feel like a real NXTer without asking for tips...
NXT: 1758531264253431177 already wrote about this two weeks ago.
the client wil handle it this way:
1. check if address is within own address book -> green
2. if account exist within blockchain -> yellow
3. don't exist within blockchain -> red
simple visual control.
the client wil handle it this way:
1. check if address is within own address book -> green
2. if account exist within blockchain -> yellow
3. don't exist within blockchain -> red
simple visual control.
Why invent crazy schemes when there is a simple, elegant solution, which covers both client AND server - checksums. The way it's implemented in bitcoin.
I don't buy the whole "oh my god performance" line of reasoning. You wrote it in Java, for god's sake
as soon the extra bit's are available for this, i can add it.
just to explain why a colored feedback is not only eyecandy but usefull, consider this.
the first step is to enter the address where to send the funds. when done the address
field is loosing focus because you do the next step, enter the amount. at this point you
get the visual feedback already about the account number. no need to fill out all other
fields and press send to know something is wrong with your address.
just a little thing but userfriendly and i can add it right now.
as said, just an example...
did someone finished reading the source code ......?
conclusion?
One file, all static. conclusion?
Very interesting way
to use Java. CfB + jean-luc + nexern,
There are millions of darkNXT and more being created all the time. darkNXT is NXT sent to an address that doesn't belong to anybody. I am assuming this is something we don't want the end user to be able to do easily. Anyone with direct API access could do whatever they wanted, but end users should NOT be allowed to create darkNXT, especially when all it takes is a typo or memory corruption.
The solution to this is so simple I am at a loss as to why it has not been implemented. NXT sent to an acct without key will create darkNXT, there is a call to detect if an acct has a key. Why has this simple guard not been implemented?
This is a very serious flaw and even ripple has a solution to this by not allowing money to an unfunded acct. We can't let horrible flawed useless ripple be better than NXT in this area can we?
James
P.S. For those not in the real world, EVERYTIME and end user creates darkNXT, it will create at least a support incident at worst lawsuits against a vendor supporting NXT. Need I remind people that we need widespread NXT adoption.
There are millions of darkNXT and more being created all the time. darkNXT is NXT sent to an address that doesn't belong to anybody. I am assuming this is something we don't want the end user to be able to do easily. Anyone with direct API access could do whatever they wanted, but end users should NOT be allowed to create darkNXT, especially when all it takes is a typo or memory corruption.
The solution to this is so simple I am at a loss as to why it has not been implemented. NXT sent to an acct without key will create darkNXT, there is a call to detect if an acct has a key. Why has this simple guard not been implemented?
This is a very serious flaw and even ripple has a solution to this by not allowing money to an unfunded acct. We can't let horrible flawed useless ripple be better than NXT in this area can we?
James
P.S. For those not in the real world, EVERYTIME and end user creates darkNXT, it will create at least a support incident at worst lawsuits against a vendor supporting NXT. Need I remind people that we need widespread NXT adoption.
I hope nexern will fix this issue on client side.
already wrote about this two weeks ago.
the client wil handle it this way:
1. check if address is within own address book -> green
2. if account exist within blockchain -> yellow
3. don't exist within blockchain -> red
simple visual control.
what about double sending? Simple solution is to send 1 Nxt first, then users can check the trade on the blockchain - and then make a real trade to the same account
Jump to: