Dumb question no doubt, but I haven't tried to install the wallet for a long time. It's insisting on 64 bit Java. It won't run on my 32 bit machine. What's the workaround?
Tried the 32 bit Version?
Topic: NEM (XEM) Official Thread - 100% New Code - Easy To Use APIs - page 1329. (Read 2985503 times)
Tried the 32 bit Version?
Dumb question no doubt, but I haven't tried to install the wallet for a long time. It's insisting on 64 bit Java. It won't run on my 32 bit machine. What's the workaround?
My NEM real address, public and private keys are absolutelly OK, checked and fine, however i just wanted to be fully sure that the same name of currently used testing-wallet in beta versions where i redeemed my stake few months ago will not affect real version data after the launch. Currently im getting error 121 when accessing older testing wallets.
Old wallets don't work with the newest version.I repeat: The verification tool in the NCC works completely independent and has nothing to do with the wallet or account which is currently used in your NCC!
The idea to use a machine where the NEM-wallet hasnt been installed yet is a good idea. The remains of older versions are not in registry but in AppData\Roaming\ folder (win7 system).
The remains of older versions are not in registry and not in AppData\Roaming. It is in C:\Users\%YOUR-USERNAME%\nemSorry for fail info, in AppData-Roaming folder was only one shortcut in roaming - microsoft - windows folder. The rest is as you said in nem folder.
LOL. Everyone paniiiiiiiiiiic!!!!! c[[]].
Already released?
My NEM real address, public and private keys are absolutelly OK, checked and fine, however i just wanted to be fully sure that the same name of currently used testing-wallet in beta versions where i redeemed my stake few months ago will not affect real version data after the launch. Currently im getting error 121 when accessing older testing wallets.
Old wallets don't work with the newest version.I repeat: The verification tool in the NCC works completely independent and has nothing to do with the wallet or account which is currently used in your NCC!
The idea to use a machine where the NEM-wallet hasnt been installed yet is a good idea. The remains of older versions are not in registry but in AppData\Roaming\ folder (win7 system).
The remains of older versions are not in registry and not in AppData\Roaming. It is in C:\Users\%YOUR-USERNAME%\nem
My NEM real address, public and private keys are absolutelly OK, checked and fine, however i just wanted to be fully sure that the same name of currently used testing-wallet in beta versions where i redeemed my stake few months ago will not affect real version data after the launch. Currently im getting error 121 when accessing older testing wallets.
The idea to use a machine where the NEM-wallet hasnt been installed yet is a good idea. The remains of older versions are not in registry but in AppData\Roaming\ folder (win7 system).
The idea to use a machine where the NEM-wallet hasnt been installed yet is a good idea. The remains of older versions are not in registry but in AppData\Roaming\ folder (win7 system).
So what happens after the deadline? Launch day announced? 
Checked again, all ok!
The deletion of testnet wallets will NOT harm your stake accounts!
The verification tool in the NCC works completely independent and has nothing to do with the wallet or account which is currently used in your NCC!
The verification tool in the NCC works completely independent and has nothing to do with the wallet or account which is currently used in your NCC!
I have the latest Java installed but I'm getting this:
I think you have 32bit java installed, you can try standalone version for 32bit java http://bob.nem.ninja/ . If not install 64bit Java https://www.java.com/es/download/manual.jsphttp://nem.ghost.io/windows-installation-guide-stand-alone/
I have the latest Java installed but I'm getting this:
I think you have 32bit java installed, you can try standalone version for 32bit java http://bob.nem.ninja/ . If not install 64bit Java https://www.java.com/es/download/manual.jsp
I have the latest Java installed but I'm getting this:
Safest way to check is as follows:
1. Download the installer to a system(trojan and key-logger free) on which NEM has never been installed before.
2. Install it.
3. Create a wallet and boot a node.
4. Disconnect from the internet.
5. Verify real account information.(Everything seems to be good......COOL!!) If all is not well, Create new real account info. Save the address,public key and private key. Send the new account details to makoto or patmast3r asap.
6. Close program. Go to control panel and uninstall the NEM software and delete all the shortcuts.
7. Go to c:\users\your-pc-name\ and delete the NEM folder.
This way nobody will even know that anything related to NEM ever happened in the pc.
(NOTE: -There is no need to download the whole blockchain to verify real account info.
-If you do not wish to copy paste the real account info, you could always take a screenshot and save the picture for better security. And then you can type in the real account info on launch. At least I have done it this way
)
1. Download the installer to a system(trojan and key-logger free) on which NEM has never been installed before.
2. Install it.
3. Create a wallet and boot a node.
4. Disconnect from the internet.
5. Verify real account information.(Everything seems to be good......COOL!!) If all is not well, Create new real account info. Save the address,public key and private key. Send the new account details to makoto or patmast3r asap.
6. Close program. Go to control panel and uninstall the NEM software and delete all the shortcuts.
7. Go to c:\users\your-pc-name\ and delete the NEM folder.
This way nobody will even know that anything related to NEM ever happened in the pc.
(NOTE: -There is no need to download the whole blockchain to verify real account info.
-If you do not wish to copy paste the real account info, you could always take a screenshot and save the picture for better security. And then you can type in the real account info on launch. At least I have done it this way
) I made one my testing wallet corrupted some way after installing a new version, or this is made by incompatibility with new versions and not by my machine's registry?
An incompatiblity was created when addresbooks were introduced. I don't think it has anything todo with the registry as that should all be handeld by the installer/uninstaller.
Without erroe messages noone can help you.
I made one my testing wallet corrupted some way after installing a new version, or this is made by incompatibility with new versions and not by my machine's registry?
Will the keeping, deleting or breaking my wallet now in beta have any impact on functionality or compatibility of real XEM account after launch?
Almost at the same PC, because the system seems to be still keeping some files in registry after uninstalling the old versions of NEM client so i need to avoid every possible trouble.
Almost at the same PC, because the system seems to be still keeping some files in registry after uninstalling the old versions of NEM client so i need to avoid every possible trouble.
What do you mean with files in registry ? What exactly ?
Will the keeping, deleting or breaking my wallet now in beta have any impact on functionality or compatibility of real XEM account after launch?
Almost at the same PC, because the system seems to be still keeping some files in registry after uninstalling the old versions of NEM client so i need to avoid every possible trouble.
Almost at the same PC, because the system seems to be still keeping some files in registry after uninstalling the old versions of NEM client so i need to avoid every possible trouble.
Hello,
I think I did something wrong, but I don't know what...
Months ago, I sent my NEM steak and my NEM address through NXT to receive the NEM, but i never received the NEM.
I'm listed here: https://chain.nem.ninja/stakes/registered/
>>> NXT-EDLZ-9ZKY-9GLS-7UBCL : NAOD7K-SVV6JT-...
I just add my private key to a new wallet, and I notice my address changed a little.
From: NAOD7K-SVV6JT-RFGZEA-IZ32EA-Z6GEAR-ZP63PQ-EVUH (the address I sent through NXT with the steak)
To: TAOD7K-SVV6JT-RFGZEA-IZ32EA-Z6GEAR-ZP6ZZW-ANTS (the address I see in the NEM client after restoring my private key)
Is someone know what I missed?
Thanks
I think I did something wrong, but I don't know what...
Months ago, I sent my NEM steak and my NEM address through NXT to receive the NEM, but i never received the NEM.
I'm listed here: https://chain.nem.ninja/stakes/registered/
>>> NXT-EDLZ-9ZKY-9GLS-7UBCL : NAOD7K-SVV6JT-...
I just add my private key to a new wallet, and I notice my address changed a little.
From: NAOD7K-SVV6JT-RFGZEA-IZ32EA-Z6GEAR-ZP63PQ-EVUH (the address I sent through NXT with the steak)
To: TAOD7K-SVV6JT-RFGZEA-IZ32EA-Z6GEAR-ZP6ZZW-ANTS (the address I see in the NEM client after restoring my private key)
Is someone know what I missed?
Thanks
check this, ...
Double Check Your Private Keys
The core developers wish to “lock in” the NEM NEMesis accounts, after which addresses may not be changed so we strongly urge everyone to double and triple check that their private key, public key and address are all correct by utilising the “verify real account data” function in the NEM beta client. It is of utmost importance that all users be sure to check that their keys are correct and secure, otherwise XEM will be lost and it will not be possible to recover once the NEM addresses are locked in.
When you open the beta client, which you can download here, you will see a “cog” symbol next to your address which opens an options menu. Within this menu you will see the “verify real account data” option which you will need to select. Upon selection, a window will open requesting that you enter your real account address (Nb: starts with an “N”), public key and private key. If they match, or if unfortunately they don't, a message will display letting you know the outcome. If the information you entered does not match after a number of attempts, you have to recreate your real account data, test that it matches and submit your new address to a Patmast3r or Makoto asap. The deadline for submitting a new address is now set as the 22/3/2015 @ 23:59:59. After this date it will no longer be possible to change your address. Please do not take chances with your real account data as everyone only gets one chance at this!
The core developers wish to “lock in” the NEM NEMesis accounts, after which addresses may not be changed so we strongly urge everyone to double and triple check that their private key, public key and address are all correct by utilising the “verify real account data” function in the NEM beta client. It is of utmost importance that all users be sure to check that their keys are correct and secure, otherwise XEM will be lost and it will not be possible to recover once the NEM addresses are locked in.
When you open the beta client, which you can download here, you will see a “cog” symbol next to your address which opens an options menu. Within this menu you will see the “verify real account data” option which you will need to select. Upon selection, a window will open requesting that you enter your real account address (Nb: starts with an “N”), public key and private key. If they match, or if unfortunately they don't, a message will display letting you know the outcome. If the information you entered does not match after a number of attempts, you have to recreate your real account data, test that it matches and submit your new address to a Patmast3r or Makoto asap. The deadline for submitting a new address is now set as the 22/3/2015 @ 23:59:59. After this date it will no longer be possible to change your address. Please do not take chances with your real account data as everyone only gets one chance at this!
currently the "real-Network" haven´t lauchned, so you only se your test-Net adress (starts with "T") in your client.
Thanks Lyricz!
Thus I just need to wait the official launch
Hello,
I think I did something wrong, but I don't know what...
Months ago, I sent my NEM steak and my NEM address through NXT to receive the NEM, but i never received the NEM.
I'm listed here: https://chain.nem.ninja/stakes/registered/
>>> NXT-EDLZ-9ZKY-9GLS-7UBCL : NAOD7K-SVV6JT-...
I just add my private key to a new wallet, and I notice my address changed a little.
From: NAOD7K-SVV6JT-RFGZEA-IZ32EA-Z6GEAR-ZP63PQ-EVUH (the address I sent through NXT with the steak)
To: TAOD7K-SVV6JT-RFGZEA-IZ32EA-Z6GEAR-ZP6ZZW-ANTS (the address I see in the NEM client after restoring my private key)
Is someone know what I missed?
Thanks
I think I did something wrong, but I don't know what...
Months ago, I sent my NEM steak and my NEM address through NXT to receive the NEM, but i never received the NEM.
I'm listed here: https://chain.nem.ninja/stakes/registered/
>>> NXT-EDLZ-9ZKY-9GLS-7UBCL : NAOD7K-SVV6JT-...
I just add my private key to a new wallet, and I notice my address changed a little.
From: NAOD7K-SVV6JT-RFGZEA-IZ32EA-Z6GEAR-ZP63PQ-EVUH (the address I sent through NXT with the steak)
To: TAOD7K-SVV6JT-RFGZEA-IZ32EA-Z6GEAR-ZP6ZZW-ANTS (the address I see in the NEM client after restoring my private key)
Is someone know what I missed?
Thanks
check this, ...
Double Check Your Private Keys
The core developers wish to “lock in” the NEM NEMesis accounts, after which addresses may not be changed so we strongly urge everyone to double and triple check that their private key, public key and address are all correct by utilising the “verify real account data” function in the NEM beta client. It is of utmost importance that all users be sure to check that their keys are correct and secure, otherwise XEM will be lost and it will not be possible to recover once the NEM addresses are locked in.
When you open the beta client, which you can download here, you will see a “cog” symbol next to your address which opens an options menu. Within this menu you will see the “verify real account data” option which you will need to select. Upon selection, a window will open requesting that you enter your real account address (Nb: starts with an “N”), public key and private key. If they match, or if unfortunately they don't, a message will display letting you know the outcome. If the information you entered does not match after a number of attempts, you have to recreate your real account data, test that it matches and submit your new address to a Patmast3r or Makoto asap. The deadline for submitting a new address is now set as the 22/3/2015 @ 23:59:59. After this date it will no longer be possible to change your address. Please do not take chances with your real account data as everyone only gets one chance at this!
The core developers wish to “lock in” the NEM NEMesis accounts, after which addresses may not be changed so we strongly urge everyone to double and triple check that their private key, public key and address are all correct by utilising the “verify real account data” function in the NEM beta client. It is of utmost importance that all users be sure to check that their keys are correct and secure, otherwise XEM will be lost and it will not be possible to recover once the NEM addresses are locked in.
When you open the beta client, which you can download here, you will see a “cog” symbol next to your address which opens an options menu. Within this menu you will see the “verify real account data” option which you will need to select. Upon selection, a window will open requesting that you enter your real account address (Nb: starts with an “N”), public key and private key. If they match, or if unfortunately they don't, a message will display letting you know the outcome. If the information you entered does not match after a number of attempts, you have to recreate your real account data, test that it matches and submit your new address to a Patmast3r or Makoto asap. The deadline for submitting a new address is now set as the 22/3/2015 @ 23:59:59. After this date it will no longer be possible to change your address. Please do not take chances with your real account data as everyone only gets one chance at this!
currently the "real-Network" haven´t lauchned, so you only se your test-Net adress (starts with "T") in your client.
Jump to: