Update: just added the link to the standalone version in the OP.
Hello!
Something goes wrong with my test wallet.
My computer worked as a node all days of beta testing. I've got my 50 000 000 for test and transfered most of it to other people. Yesterday I left my wallet opened. There were more than million NEMs.
Some minutes ago I came to computer and wanted to send some NEMs to somebody. But when I refreshed the page - It suggested to enter my wallet again. I entered login and password and entered to wallet. But it seems not my wallet 
There are no NEMs. It's not harvesting, importance - 0. No transactions, And it's not my number of wallet
I tried to exit and enter - the same. I tried to stop NCC and start again - the same.
NIS seems working properly. GUI says that NIS synchronized, Local Node booted.
I tried to enter again private key, received from Bloody Rookie, but it says, that "Wallet already contains this account."
What happened? And what to do now?
UPD: Fixed All I had to do - is to click on wallet number and there was another wallet - right wallet. I click it and now it's ok. Sorry
Yes you can manage more than 1 account inside your wallet.
decimal digit issue with 0.2.9 UI :
When sending NEMs, if the Fee has more than 6 digits, e.g. 14.14145611,
then comes an error note "Oops ...".
The entered values remained in the dialog, so no harm done.
Maybe the UI can prevent the user to enter too many digits after the decimal point?
When writing "many enough" numbers to the Fee field, all the numbers are not shown.
Still problems with the number fields:
- trying to set the NEM amount to be sent to 33333.333333
and the fee to 33.33
While wrote the fee, the amount is changed to 33333333.333.
When going to change that decimal point back, the fee is changed to 1 333 340.00
(is this the minimum fee for 33 million?)
Well, I admit that I have earlier (alpha) pushed the decimal points to their limits by using all the 6 digits, but is this now the revenge of the numbers or what ? :(
Edit: now started sending first without decimal points and then increasing the digits on the right side of the decimal points. All were sent but not when there is 6 digits after the decimal point.
Edit2: while writing the fee, the amount field automatically changes the
decimal point "33 333.333333" to "33 333 333.333"
But the confirmation note says: "You're going to send 33 333.333333 NEM".
Has there been some change in the number policy or am I remembering another alpha SW? :) The transaction details do show only 2 digits after the decimal points.
decimal digit issue with 0.2.9 UI :
When sending NEMs, if the Fee has more than 6 digits, e.g. 14.14145611,
then comes an error note "Oops ...".
The entered values remained in the dialog, so no harm done.
Maybe the UI can prevent the user to enter too many digits after the decimal point?
When writing "many enough" numbers to the Fee field, all the numbers are not shown.
Still problems with the number fields:
- trying to set the NEM amount to be sent to 33333.333333
and the fee to 33.33
While wrote the fee, the amount is changed to 33333333.333.
When going to change that decimal point back, the fee is changed to 1 333 340.00
(is this the minimum fee for 33 million?)
Well, I admit that I have earlier (alpha) pushed the decimal points to their limits by using all the 6 digits, but is this now the revenge of the numbers or what ? :(
Edit: now started sending first without decimal points and then increasing the digits on the right side of the decimal points. All were sent but not when there is 6 digits after the decimal point.
Edit2: while writing the fee, the amount field automatically changes the
decimal point "33 333.333333" to "33 333 333.333"
But the confirmation note says: "You're going to send 33 333.333333 NEM".
Has there been some change in the number policy or am I remembering another alpha SW? :) The transaction details do show only 2 digits after the decimal points.
I confirm this. While writing the fee - amount changed!
My beta NEM wallet is getting loads of test NEM, but every time I try to send NEM to someone I get an error message saying the timestamp is too far in the past or too far in the future. Changing the number of hours for submission doesn't help.
I think this has to do with synchronizing the time between my beta account and the blockchain, but I can't find any settings that would address this. I've had my beta account up for about 12 hours nows. I would have thought that everything would be in sync by now.
@SwapperMalll: It's a known bug. Leave NIS running and restart NCC, wait for a minute then it should work.
well, I had client running on firefox but a 'real' account is not 'copy and pasting'…so I have started on Chrome…surprise surprise…not working…a green box shows for a couple of seconds…ok I am following the instructions on chrome now but i need to navigate to a site with JNLP files…does anybody know of such a site?..maybe its our site but im not getting a pop-up box.
I tried INT.EXP but the client showed up on the firefox page…works but still couldnt copy and paste…so now trying chrome
Im not getting a 'dowload prompt'…should I adjust chrome settings?
what about simple tutorial on how to set up the wallet, for noobs?
This is something you may want to look at. But a big warning. It will eat up your entire CPU resources.
http://localhost:8989/ncc/web/sigma-graph/nemgraph.html
Enjoy. 
This is something you may want to look at. But a big warning. It will eat up your entire CPU resources.
http://localhost:8989/ncc/web/sigma-graph/nemgraph.html
Enjoy. ;)
Hmmm ... in this pic I'm green, but here https://bitcointalk.org/index.php?topic=654845.msg9312234#msg9312234 orange.
Maybe the pic sets the centre node always as green (it works "properly" from its own view of point) ...
https://bitcointalk.org/index.php?topic=654845.msg9312827#msg9312827
"you might need to go into your firewall settings and make an allowance for port 7890. When creating the allowance you may need to open that port to all pc's and not just home/shared network."
If that port is opened and NCC/NIS is not running, can it be somekind of "risk" ... ?
https://bitcointalk.org/index.php?topic=654845.msg9312827#msg9312827
"you might need to go into your firewall settings and make an allowance for port 7890. When creating the allowance you may need to open that port to all pc's and not just home/shared network."
If that port is opened and NCC/NIS is not running, can it be somekind of "risk" ... ?
good question actually.. :/ i couldnt get it working for love nor money until i opened the port to all pc's.. there are many other allowances in my firewall(mcAfee) for microsoft stuff and a few other things and they are mostly all open to all computers.. this is a new machine too so it came like that stock.. so i didnt think it would be that much of an issue..
Before I copy and paste my real nem information, is there a fixed amount of characters for
Address
Public key
Private key
And how many for each? ......and has everyone the same number of characters?
Can a dev answer this please?
[B]Address:[/B] addresses always have the same length. The first character is the network version. Right now it can be "T" for test network or "N" for live network (will be used after launch). The second character is always "A", "B", "C" or "D". The length of an address is 40 characters (not counting the "-")
Example: TASSSR-OMJE3L-6ZUN6L-SW76Y2-FCIH3H-HULADH-PPUL
[B]Public key:[/B] public keys are always 64 characters long when using the hexadecimal writing.
Example: b5c6ade9ccb21f62de4f5b49ba63464d198226c4707460c11e1fe0604dd7f041
[B]Private key:[/B] private keys can be 64 or 66 characters long when using hexadecimal writing. If 66 characters in length, it begins with "00" (double zero).
Example: 00d4a0f7f34144086f232e39ee0ef6f3321ea570cc481a1de1d6587df0087a02fb
https://bitcointalk.org/index.php?topic=654845.msg9312827#msg9312827
"you might need to go into your firewall settings and make an allowance for port 7890. When creating the allowance you may need to open that port to all pc's and not just home/shared network."
If that port is opened and NCC/NIS is not running, can it be somekind of "risk" ... ?
good question actually.. :/ i couldnt get it working for love nor money until i opened the port to all pc's.. there are many other allowances in my firewall(mcAfee) for microsoft stuff and a few other things and they are mostly all open to all computers.. this is a new machine too so it came like that stock.. so i didnt think it would be that much of an issue..
Maybe it is not any risk ...
what can be done through an opened port, if there is nothing behind of it?
Question for security specialists or Ead* ... :)
If that port is opened and NCC/NIS is not running, can it be somekind of "risk" ... ?
Opening a port means there is yet another way for outside entities to "present" data to your computer. If the OS has a vulnerability then it could be dangerous.
If that port is opened and NCC/NIS is not running, can it be somekind of "risk" ... ?
Opening a port means there is yet another way for outside entities to "present" data to your computer. If the OS has a vulnerability then it could be dangerous.
It would be dangerous if ...
for example, someone had succeeded to install his malware program to the pc and it knows that port 7890 will be open?
If that port is opened and NCC/NIS is not running, can it be somekind of "risk" ... ?
Opening a port means there is yet another way for outside entities to "present" data to your computer. If the OS has a vulnerability then it could be dangerous.
There is always risk if you open up ports. ;)
That's why I was reluctant to open up my port at the firewall. I tried to check if my system works and then when I found it worked, I closed it back.;)
Kodtycoon, if I were you, I wouldn't do what you did. What you did was port triggering. Try and find NAT and do a specific map to a particular machine that has a static IP inside your home network. That is a much better way than to do a blanket opening.
If you have a DMZ, it would be much better to connect that machine there.
I have an question regarding the NIS.
If I check my node with http://chain.nem.ninja/checknis/ the site tells me
"We were not able to reach your node 
Make sure port 7890 is open in your router configuration!"
What is understandable, since I did not open that port.
My NEM client however tells me, my Importance is 0.16% with 1.86mil NEM and I harvested 1 block already (0.00NEM :'( ).
Is the importance higher if I open that port? If not, is
i am getting this error when try to send NEM. "The time stamp of the transaction id too far in the past."
Time and Date is correct on my computer ???
i am getting this error when try to send NEM. "The time stamp of the transaction id too far in the past."
Time and Date is correct on my computer ???
Is your computer clock set to internet time?