Often I’m sorry
If it contains a ‘_’ in the name space,
Properly address can not be set.
Is the specification of which is also ‘Aliases’?
Ex ):
@godtanu
→ OK (TB235J-LAOGAL-DATDJC-7LXDMZ-SDMFBU-MDVIBF-VQPF)
@team_udon
→ NG (invalid NameSpace ‘teamudon’)
Get an ‘team_udon’ is ‘teamudon’ and displayed error messages.
Going to fix that and add better validation for the namespace name, I forgot to do it ^^. Thanks
Apostille did not work.
Do I need to purge my account?
There is a need to read again .wlt File?
I am using the Firefox.
The collectively 3 file Apostille (image, image, add text)
It will remain throughout the run
You need to purge the nty data in local storage. To do that open your browser console (help: http://webmasters.stackexchange.com/a/77337), you’ll see some kind of “>” at the bottom of the console, there you need to paste:
localStorage.removeItem(“ngStorage-nty”);
Then press enter and reload the page.
I was posted ’issues16’.
Garbled characters Multibyte character File (Apostille).
Source code is now available: https://github.com/QuantumMechanics/NanoWallet
I’ll write the readme and publish documentation during week-end
Hi
I have a problem creating a new mosaic with Levy feature enabled. It’s not possible to select current mosaic from the dropdown list.
I’m trying to create new mosaic, say “test-mosaic”. I check the “Levy” checkbox. Dropdown selector with available mosaics appears. But I can choose only XEM as the Levy mosaic. Therefore I can’t set levy in my newly created asset.
I’d like to set up some levy to make sure that target account will receive equivalent portions of my asset and XEMs to make further transactions.
Not sure if it is NanoWallet or core API issue.
Hi,
In Nano you can only use Mosaics you own as Levy. Do you already have some ? If not there is no problem, you can only choose XEM
As far as I know, technically any transferable mosaic can be a levy for any other mosaic. It also use to be that a mosaic could be a levy of itself, but I haven’t tested that recently. Right now NanoWallet only supports adding a mosaics you already have in the dropdown to choose from as that is easier for most people than seeing a dropdown of all mosaics on NEM.
OK, I’ll try to explain this case in details.
Imagine that you are creating new mosaic. Name it, i don’t know, VirtualUSD (divisibility 0, total 1 000 000). To make it transferable we should send some XEMs in transactions alongside with our VUSD. Otherwise, end users will receive only VUSDs. They can not transfer it further because each transaction implies at least 2 XEM fee.
OK, we can make our newly created mosaic trully transferable if we include enough funds for the endpoint users to pay the fee. So, we need to add 200 XEMs to transfer 100 VUSDs in order to allow our recipient to make up to 100 further transactions with 1 VUSD each. But all 200 XEMs will be spent on these transactions. Therefore, again, the 2-tier recipients will not be able to transfer funds further because they will receive only 1 VUSD each and no XEMs at all.
We can add some levy to balance transactions. In our case if we set levy amount to 1 VUSD all the fees will be compensated.
For example,
It looks like the easiest and the most natural way to organize transfers from the scratch. In this case wallet for our VUSDs can be easily implemented.
Not a bug, when clicking on levy checkbox you can see that “right now, only owned mosaics can be used as a levy”.
To be honest I thought that the mosaic needed to exists to use it as levy… But I tried and it worked.
Added it to my to do list
This archive is certified using Apostille
Onwer: NAMOAVHFVPJ6FP32YP2GCM64WSRMKXA5KKYWWHPY
File hash: 4e54590357e43a1a29691a781d667d22ca7e79aefcf0f81b3c00cd46f0451dbbb3be3c8d
Transaction hash: bc1ed5db9f2e53cf03c6ee17ec87d50b58e4d4972dfae606bc279f1246851e1a
Regarding Apostille, 3 new modules have been added:
The above 3 modules are only accessible via the Apostille history. There you can also import, backup or purge notary data from your local storage (it’ll only affect data stored for the network you are using).
Thanks @Quantum_Mechanics it is really nice to have so much packed into NanoWallet now and especially the enhanced support for Apostille. We now have dedicated update, message, make QR, and transfer/split ownership sections of Apostille to make the process easy for users!
I also like the new block explorer which will give you info on accounts, apostilles, namespaces and mosaics.
How do I put an already existed acount to Nanowallet? only by importing other wallet with the account in it?
here you go https://blog.nem.io/ncc-to-nanowallet-export/
you can also get your private key and make a new wallet by using the private key
Thank you. I think we need to change that. Some countries use decimal and comma differently like Germany. I think we need to change it to more of the America style.
The QR code displayed by “Account info” of “Export to mobile”
It is incompatible with the latest mobile wallet.
However, the QR code of “Andoroid and iOS” operates normally.
At this time, since the official version of mobile wallet has not appeared, I do not know which is wrong.
Somehow, I feel that the QR code version of “Account info QR” is 1 and it is not 2.
