NEM (XEM) Official Thread - 100% New Code - Easy To Use APIs

[Come-from-Beyond]

We don't want to publish a list of names because of privacy reasons.

I can compile a chart of the registration dates, ranks, and post counts of NEM stakeholders. Or do you have other suggestions?

At this point, I'm fairly comfortable that there are no major sockmasters.

Is there time to do an extra round of sockpuppet hunt that would affect a potential insider?

Look at the situation from point of view of a guy from outside:

Mr.X owns 100 sockpuppet stakes.
He does a great analysis and finds 400 sockpuppet stakes belonging to someone else.
He comes to NEM devs and shows the analysis that reveals only those stakes that are not controlled by him.
NEM devs get rid of those 400 sockpuppets.

NEM devs are happy = they removed 400 rogue stakes.
Mr.X is happy = he has 100 his stakes safe (noone will do an extra round after such the great analysis).
Some guys who know double agent tricks are not happy.

[patmast3r]

IMPORTANT: https://forum.nemcoin.com/nem-news-alerts/the-age-of-extinction-the-final-blow-to-sockmasters/msg14065/#msg14065

[mjrmac]

We don't want to publish a list of names because of privacy reasons.

I can compile a chart of the registration dates, ranks, and post counts of NEM stakeholders. Or do you have other suggestions?

At this point, I'm fairly comfortable that there are no major sockmasters.

Is there time to do an extra round of sockpuppet hunt that would affect a potential insider?

Look at the situation from point of view of a guy from outside:

Mr.X owns 100 sockpuppet stakes.
He does a great analysis and finds 400 sockpuppet stakes belonging to someone else.
He comes to NEM devs and shows the analysis that reveals only those stakes that are not controlled by him.
NEM devs get rid of those 400 sockpuppets.

NEM devs are happy = they removed 400 rogue stakes.
Mr.X is happy = he has 100 his stakes safe (noone will do an extra round after such the great analysis).
Some guys who know double agent tricks are not happy.

Too difficult ...    
... in the level of the used transparency.

[patmast3r]

We don't want to publish a list of names because of privacy reasons.

I can compile a chart of the registration dates, ranks, and post counts of NEM stakeholders. Or do you have other suggestions?

At this point, I'm fairly comfortable that there are no major sockmasters.

Is there time to do an extra round of sockpuppet hunt that would affect a potential insider?

Look at the situation from point of view of a guy from outside:

Mr.X owns 100 sockpuppet stakes.
He does a great analysis and finds 400 sockpuppet stakes belonging to someone else.
He comes to NEM devs and shows the analysis that reveals only those stakes that are not controlled by him.
NEM devs get rid of those 400 sockpuppets.

NEM devs are happy = they removed 400 rogue stakes.
Mr.X is happy = he has 100 his stakes safe (noone will do an extra round after such the great analysis).
Some guys who know double agent tricks are not happy.

What exactly do you have in mind ? What would that look like ?

[Come-from-Beyond]

What exactly do you have in mind ? What would that look like ?

Everyone who controls private keys to a set of stakes that need to be investigated (excluding those from Nxt AE I think) launches NEM wallet and leave it open. At some moment (triggered by Bitcoin block N, data can be gotten from Blockchain.Info easily) all the wallets start solving cryptographical puzzles depending on Bitcoin block hash and NEM account id. In 15 minutes these puzzles are sent to a server controlled by NEM devs and the hash of received puzzles is published and copied by a lot of people who have to wait these 15 minutes.

After that we can make a good assessment how many computers "controlled" by a particular NEM stake and we can verify the puzzles because their hash is publicly known. Someone owning 100 stakes have to find 100 computers.

[punapeter]

Thanks for opening the appeal processing so soon. Just sent a PM to makoto and I hope it will be carefully reviewed.

[makoto1337]

We don't want to publish a list of names because of privacy reasons.

I can compile a chart of the registration dates, ranks, and post counts of NEM stakeholders. Or do you have other suggestions?

At this point, I'm fairly comfortable that there are no major sockmasters.

Is there time to do an extra round of sockpuppet hunt that would affect a potential insider?

Look at the situation from point of view of a guy from outside:

Mr.X owns 100 sockpuppet stakes.
He does a great analysis and finds 400 sockpuppet stakes belonging to someone else.
He comes to NEM devs and shows the analysis that reveals only those stakes that are not controlled by him.
NEM devs get rid of those 400 sockpuppets.

NEM devs are happy = they removed 400 rogue stakes.
Mr.X is happy = he has 100 his stakes safe (noone will do an extra round after such the great analysis).
Some guys who know double agent tricks are not happy.

If you flew to Japan and bought me some sake, I'd walk through all the redemption data with you

[makoto1337]

Thanks for opening the appeal processing so soon. Just sent a PM to makoto and I hope it will be carefully reviewed.

Of course we will treat every NEMster seriously. Please just be polite!

[patmast3r]

What exactly do you have in mind ? What would that look like ?

Everyone who controls private keys to a set of stakes that need to be investigated (excluding those from Nxt AE I think) launches NEM wallet and leave it open. At some moment (triggered by Bitcoin block N, data can be gotten from Blockchain.Info easily) all the wallets start solving cryptographical puzzles depending on Bitcoin block hash and NEM account id. In 15 minutes these puzzles are sent to a server controlled by NEM devs and the hash of received puzzles is published and copied by a lot of people who have to wait these 15 minutes.

After that we can make a good assessment how many computers "controlled" by a particular NEM stake and we can verify the puzzles because their hash is publicly known. Someone owning 100 stakes have to find 100 computers.

That would basically be another round of redemption and that takes months. I don't think we have the time for that. You could have suggested that half a year ago

[makoto1337]

I'm pretty busy, so don't be concerned if I don't reply to your pm's immediately. I'll get through the appeal within 24 hours or so.

[Fatih87SK]

When the distribution is complete and I have my NEM.

Is the Private key I own right now the most important access to it?
So, there is no way I can lose it when my laptop crashes or something?

[patmast3r]

When the distribution is complete and I have my NEM.

Is the Private key I own right now the most important access to it?
So, there is no way I can lose it when my laptop crashes or something.

AFTER LAUNCH:
Ideally you should remove all traces of that private key in cleartext after you've imported it into a password protected wallet. After that your wallet is the most important thing and you should have multiple backups of it on different drives.
All NEM wallets are encrypted and password protected by default which is why it's a much safer way to keep your private key than to have the cleartext lying around.

[Fatih87SK]

When the distribution is complete and I have my NEM.

Is the Private key I own right now the most important access to it?
So, there is no way I can lose it when my laptop crashes or something.

AFTER LAUNCH:
Ideally you should remove all traces of that private key in cleartext after you've imported it into a password protected wallet. After that your wallet is the most important thing and you should have multiple backups of it on different drives.
All NEM wallets are encrypted and password protected by default which is why it's a much safer way to keep your private key than to have the cleartext lying around.

Ok.

But when you lose the backups as well. Is it still possible to enter your wallet with the Private key I have stored?

[freigeist]

When the distribution is complete and I have my NEM.

Is the Private key I own right now the most important access to it?
So, there is no way I can lose it when my laptop crashes or something.

AFTER LAUNCH:
Ideally you should remove all traces of that private key in cleartext after you've imported it into a password protected wallet. After that your wallet is the most important thing and you should have multiple backups of it on different drives.
All NEM wallets are encrypted and password protected by default which is why it's a much safer way to keep your private key than to have the cleartext lying around.

Ok.

But when you lose the backups as well. Is it still possible to enter your wallet with the Private key I have stored?

I think if you loose or delete your wallet you need to create a new one
and then import the same private key you have stored in it to access the accounts (funds) tied to this private key.

Also I would suggest you for security reason to make a copy of the private key
also on paper or some other storage device to not loose it in case your PC or laptop stops working.

[Come-from-Beyond]

That would basically be another round of redemption and that takes months. I don't think we have the time for that. You could have suggested that half a year ago

The proposed method doesn't need months. Majority of nemsters are waiting for the launch, so they will read an announcement and install the software. The rest will take a week. Why do you think about months here?

[patmast3r]

That would basically be another round of redemption and that takes months. I don't think we have the time for that. You could have suggested that half a year ago

The proposed method doesn't need months. Majority of nemsters are waiting for the launch, so they will read an announcement and install the software. The rest will take a week. Why do you think about months here?

roughly 1400 people have to have their client running at the same time. That's like waiting for some special stellar constellation
Not to mention that a huge chunk of stakeholders only drop by once a month so it would have to be at least 1 month after the announcement which even if the announcement was made right now would be later than what we hope to be launch.

[Come-from-Beyond]

roughly 1400 people have to have their client running at the same time. That's like waiting for some special stellar constellation
Not to mention that a huge chunk of stakeholders only drop by once a month so it would have to be at least 1 month after the announcement which even if the announcement was made right now would be later than what we hope to be launch.

Not running at the same time. Launching it one day before and leaving it working.

Why you can't postpone the launch a little?

[makoto1337]

roughly 1400 people have to have their client running at the same time. That's like waiting for some special stellar constellation
Not to mention that a huge chunk of stakeholders only drop by once a month so it would have to be at least 1 month after the announcement which even if the announcement was made right now would be later than what we hope to be launch.

Not running at the same time. Launching it one day before and leaving it working.

Why you can't postpone the launch a little?

Assuming we are still on track for launch, there's no time left to do this.

[patmast3r]

roughly 1400 people have to have their client running at the same time. That's like waiting for some special stellar constellation
Not to mention that a huge chunk of stakeholders only drop by once a month so it would have to be at least 1 month after the announcement which even if the announcement was made right now would be later than what we hope to be launch.

Not running at the same time. Launching it one day before and leaving it working.

Why you can't postpone the launch a little?

I think there are about 500 people that would kill us if we postponed because of anything other than technical reasons.
If people were like "Well that's worth it let's postpone for that" then I'd personally consider it (no idea what the rest thinks) but I don't think that's the case at all.

[Come-from-Beyond]

Ok, looks like I came here too late. This was my fault and I'll fix it by myself.