New version of the Nxt Mac Client is available here:
http://nxtra.org/mac/
Sha256 for the zip file is also included on the page.
New features:
1) Ability to check for updates for beta releases. (0.4.9e) - enable in preferences.
2) Auto-updates now check the sha256 and won't continue if it does not match what is said in the blockchain.
Topic: NXT :: descendant of Bitcoin - Updated Information - page 1930. (Read 2761645 times)
...
Paying back stolen Nxt is not realistic. Shit happends.
However PaulyC (and for a smaller extent newcn) should (and did) get bounty for uncovering the method of the theft, saving others.
Paying back stolen Nxt is not realistic. Shit happends.
However PaulyC (and for a smaller extent newcn) should (and did) get bounty for uncovering the method of the theft, saving others.
Yeah, the amount of NXT stolen is quite a lot of money at this point, I can't imagine everyone being made whole. I'd love to be proved wrong, but I'm not expecting any compensation for what was my mistake in the end. Outside of EpicThomas refunding the NXT, or DGEX blacklisting/rerouting any attempts to sell the NXT, I'm not seeing this ending well for us.
Any chance some big holders want to cash out and crash the price a little? I'd love to buy back in at my original price.
I received a PM from someone who plans to send me some NXT to help divide up among those who lost NXT. Can we get a comprehensive list of who lost what as of right now.
Isn't there a javascript library to check sha256 sums? If so, somebody more fluent than me in javascript can easily add an update.html page to the client. It can request the value of the NRSversion alias from localhost, which contains the latest stable version and sha256, and I can also start putting the download url as a value of NRSrelease alias. Then download the zip file from that url, check if sha256 matches, and notify the user whether the downloaded zip file is legitimate or not. No need to trust a third party or manually check sha256 sums. Only the first time you download a client need to verify manually.
Great idea! Anyone fit in javascript?
I'll get working on this!
I love you.
I too am willing to chalk it up to an unfortunate mistake by you EpicThomas if you return EVERYONES' NXT.
Make sure he pays interest for holding these coins.
Isn't there a javascript library to check sha256 sums? If so, somebody more fluent than me in javascript can easily add an update.html page to the client. It can request the value of the NRSversion alias from localhost, which contains the latest stable version and sha256, and I can also start putting the download url as a value of NRSrelease alias. Then download the zip file from that url, check if sha256 matches, and notify the user whether the downloaded zip file is legitimate or not. No need to trust a third party or manually check sha256 sums. Only the first time you download a client need to verify manually.
Great idea! Anyone fit in javascript?
I'll get working on this!
rickyjames, you have made good investigation work to tracing thief! Thank you.
The fact is that the stolen NXT from all five of these guys is sitting stuck in the five thief accounts and it can't get converted to BTC without going thru Dgex. That ain't gonna happen.
This is a major crime in the tens of thousands of dollars range and we know who did it. People go to prison for years for this kind of crap.
(Are you reading this, EpicThomas? I know you are.)
You know, if the NXT were somehow to be magically transferred back into the accounts where it is supposed to be, maybe just maybe I won't personally make it my mission to find your home address and phone number, post it right here on this forum, and call the police in your local town or city.
Do you feel lucky, punk?
A MESSAGE TO EPIC THOMAS:
Dude, I'm coming for you. You had better put back the NXT where it belongs before I find out who you are and go to the police. I will stop if you repay the NXT you have taken from others. Once I find out a name and address and turn it over to law enforcement, things are out of my hands. Until that time you can save yourself. Do it.
My email to customer service at Digital Ocean:
Can you identify the real name, email address, mailing address, and telephone number of the user renting a cloud server from you at 162.243.246.233 for the past several days? This person is involved in illegal activities and has stolen over $23,000 that we know of so far through unauthorized transfers of assets. When you have obtained this information, please let me know the name and location of the representative who may be contacted by local law enforcement.
This is not a prank or joke. My name is X. I am a resident of X and you can contact me at my cell number of X if needed. Thank you, and I look forward to your prompt response.
I too am willing to chalk it up to an unfortunate mistake by you EpicThomas if you return EVERYONES' NXT.
Let's see... 0.4.8 was more stable than 0.4.7e, even on 512 Mb. If 0.4.9e is even better, then we're getting where it should be.
The goal is to run NRS on 64 KiB devices.
you kiddin?
Yes, 64 KiB is too small. The real goal is 1 MiB
Damn. I should stop coding my 6502 SHA256 library then.
The fact is that the stolen NXT from all five of these guys is sitting stuck in the five thief accounts and it can't get converted to BTC without going thru Dgex. That ain't gonna happen.
This is a major crime in the tens of thousands of dollars range and we know who did it. People go to prison for years for this kind of crap.
(Are you reading this, EpicThomas? I know you are.)
You know, if the NXT were somehow to be magically transferred back into the accounts where it is supposed to be, maybe just maybe I won't personally make it my mission to find your home address and phone number, post it right here on this forum, and call the police in your local town or city.
Do you feel lucky, punk?
A MESSAGE TO EPIC THOMAS:
Dude, I'm coming for you. You had better put back the NXT where it belongs before I find out who you are and go to the police. I will stop if you repay the NXT you have taken from others. Once I find out a name and address and turn it over to law enforcement, things are out of my hands. Until that time you can save yourself. Do it.
My email to customer service at Digital Ocean:
Can you identify the real name, email address, mailing address, and telephone number of the user renting a cloud server from you at 162.243.246.233 for the past several days? This person is involved in illegal activities and has stolen over $23,000 that we know of so far through unauthorized transfers of assets. When you have obtained this information, please let me know the name and location of the representative who may be contacted by local law enforcement.
This is not a prank or joke. My name is X. I am a resident of X and you can contact me at my cell number of X if needed. Thank you, and I look forward to your prompt response.
Let's see... 0.4.8 was more stable than 0.4.7e, even on 512 Mb. If 0.4.9e is even better, then we're getting where it should be.
The goal is to run NRS on 64 KiB devices.
you kiddin?
Yes, 64 KiB is too small. The real goal is 1 MiB
oh wait, that was KB... I read it as 64 MB.
Let's see... 0.4.8 was more stable than 0.4.7e, even on 512 Mb. If 0.4.9e is even better, then we're getting where it should be.
The goal is to run NRS on 64 KiB devices.
you kiddin?
Yes, 64 KiB is too small. The real goal is 1 MiB
The fact is that the stolen NXT from all five of these guys is sitting stuck in the five thief accounts and it can't get converted to BTC without going thru Dgex. That ain't gonna happen.
This is a major crime in the tens of thousands of dollars range and we know who did it. People go to prison for years for this kind of crap.
(Are you reading this, EpicThomas? I know you are.)
You know, if the NXT were somehow to be magically transferred back into the accounts where it is supposed to be, maybe just maybe I won't personally make it my mission to find your home address and phone number, post it right here on this forum, and call the police in your local town or city.
Do you feel lucky, punk?
A MESSAGE TO EPIC THOMAS:
Dude, I'm coming for you. You had better put back the NXT where it belongs before I find out who you are and go to the police. I will stop if you repay the NXT you have taken from others. Once I find out a name and address and turn it over to law enforcement, things are out of my hands. Until that time you can save yourself. Do it.
My email to customer service at Digital River:
Can you identify the real name, email address, mailing address, and telephone number of the user renting a cloud server from you at 162.243.246.233 for the past several days? This person is involved in illegal activities and has stolen over $23,000 that we know of so far through unauthorized transfers of assets. When you have obtained this information, please let me know the name and location of the representative who may be contacted by local law enforcement.
This is not a prank or joke. My name is X. I am a resident of X and you can contact me at my cell number of X if needed. Thank you, and I look forward to your prompt response.
Thanks ricky. This effort is of a great benefit for the community.
The fact is that the stolen NXT from all five of these guys is sitting stuck in the five thief accounts and it can't get converted to BTC without going thru Dgex. That ain't gonna happen.
This is a major crime in the tens of thousands of dollars range and we know who did it. People go to prison for years for this kind of crap.
(Are you reading this, EpicThomas? I know you are.)
You know, if the NXT were somehow to be magically transferred back into the accounts where it is supposed to be, maybe just maybe I won't personally make it my mission to find your home address and phone number, post it right here on this forum, and call the police in your local town or city.
Do you feel lucky, punk?
A MESSAGE TO EPIC THOMAS:
Dude, I'm coming for you. You had better put back the NXT where it belongs before I find out who you are and go to the police. I will stop if you repay the NXT you have taken from others. Once I find out a name and address and turn it over to law enforcement, things are out of my hands. Until that time you can save yourself. Do it.
My email to customer service at Digital River:
Can you identify the real name, email address, mailing address, and telephone number of the user renting a cloud server from you at 162.243.246.233 for the past several days? This person is involved in illegal activities and has stolen over $23,000 that we know of so far through unauthorized transfers of assets. When you have obtained this information, please let me know the name and location of the representative who may be contacted by local law enforcement.
This is not a prank or joke. My name is X. I am a resident of X and you can contact me at my cell number of X if needed. Thank you, and I look forward to your prompt response.
Cool
Let's see... 0.4.8 was more stable than 0.4.7e, even on 512 Mb. If 0.4.9e is even better, then we're getting where it should be.
The goal is to run NRS on 64 KiB devices.
you kiddin?
@Jean-Luc and CfB: Is there a concrete timeline or do we just have to refresh the browser every minute tomorrow? 
Refresh it once... on the 4th of Jan.
The fact is that the stolen NXT from all five of these guys is sitting stuck in the five thief accounts and it can't get converted to BTC without going thru Dgex. That ain't gonna happen.
This is a major crime in the tens of thousands of dollars range and we know who did it. People go to prison for years for this kind of crap.
(Are you reading this, EpicThomas? I know you are.)
You know, if the NXT were somehow to be magically transferred back into the accounts where it is supposed to be, maybe just maybe I won't personally make it my mission to find your home address and phone number, post it right here on this forum, and call the police in your local town or city.
Do you feel lucky, punk?
A MESSAGE TO EPIC THOMAS:
Dude, I'm coming for you. You had better put back the NXT where it belongs before I find out who you are and go to the police. I will stop if you repay the NXT you have taken from others. Once I find out a name and address and turn it over to law enforcement, things are out of my hands. Until that time you can save yourself. Do it.
My email to customer service at Digital Ocean:
Can you identify the real name, email address, mailing address, and telephone number of the user renting a cloud server from you at 162.243.246.233 for the past several days? This person is involved in illegal activities and has stolen over $23,000 that we know of so far through unauthorized transfers of assets. When you have obtained this information, please let me know the name and location of the representative who may be contacted by local law enforcement.
This is not a prank or joke. My name is X. I am a resident of X and you can contact me at my cell number of X if needed. Thank you, and I look forward to your prompt response.
...
Paying back stolen Nxt is not realistic. Shit happends.
However PaulyC (and for a smaller extent newcn) should (and did) get bounty for uncovering the method of the theft, saving others.
Paying back stolen Nxt is not realistic. Shit happends.
However PaulyC (and for a smaller extent newcn) should (and did) get bounty for uncovering the method of the theft, saving others.
Yeah, the amount of NXT stolen is quite a lot of money at this point, I can't imagine everyone being made whole. I'd love to be proved wrong, but I'm not expecting any compensation for what was my mistake in the end. Outside of EpicThomas refunding the NXT, or DGEX blacklisting/rerouting any attempts to sell the NXT, I'm not seeing this ending well for us.
Any chance some big holders want to cash out and crash the price a little? I'd love to buy back in at my original price.
Let's see... 0.4.8 was more stable than 0.4.7e, even on 512 Mb. If 0.4.9e is even better, then we're getting where it should be.
The goal is to run NRS on 64 KiB devices.
@Jean-Luc and CfB: Is there a concrete timeline or do we just have to refresh the browser every minute tomorrow?
Refresh it once... on the 4th of Jan.
Let's see... 0.4.8 was more stable than 0.4.7e, even on 512 Mb. If 0.4.9e is even better, then we're getting where it should be.
Jump to: