Would you like to introduce yourself and give the readers some background on why you created Nanollet?

My name is Lucas and I’m from Brazil. I don’t have any formal programming education, but started teaching myself when I was 9 years old. A few years ago, I became interested in cryptography and when I learned about Nano at the end of last year, I began to build Nanollet. When I’m not developing Nanollet, I run my own website which is unrelated to crypto. I’ve been working on the wallet since the beginning of this year and actually released it back in March alongside NanoFY, but at that time the wallet required a back-end server. I’m now spending my weekends improving the wallet.

Your wallet is best known for not requiring a back-end server, how does that work?

With the release of version 15, you are able to retrieve the pending blocks of an account. The Nanollet just request blocks of your account, nothing else. Since the block are signed, they are unable to be forged, however, it also ask votes for your last block. If the last block is valid, all previous are too. To receive one transaction, the Nanollet listens to the network like a common node, but without having to synchronize and download all the blocks. If the block has you as the destination and is not pocketed yet, it asks for votes and then receives the transaction. Everything without a main server.

Even aside from not using a back-end server, Nanollet has several features unique to it, including NanoFY, NanoAlias and SeedFY.

NanoFY allows you to verify if a user has signed any data using Nano. This is done by using the hash of a document as the public-key, letting us know the user themselves wrote the signature. SeedFY acts by combining a password with the seed of an account. So it’s not an encryption, which fails on wrong password, and it’s not a plain-text seed, as is used in most wallets. When a user creates a SeedFY, it outputs a string of random-looking data, which can’t be can’t be predictable by an adversary. If you do not know the password it is impossible to use. NanoAlias offers users a way to create an on-chain alias. Unlike other alias services, it does not rely on a trusted third-party, instead relying on Nano’s dPoS system. The system works by taking advantage of the fact that accounts can only have one open-block which can’t be replaced. The user assigns an alias by creating a public key with the private Ed25519(Key = 5BitASCII("ALIAS")) . The features that I personally most like is the NanoAlias and the SeedFY.

I know the community and our team have enjoyed the unique features you are developing, are there any more you are working on that you can share?

NanoAlias was the last major feature I have planned for now. I have some ideas for Nano (and Nanollet), such as creating a wallet using a FPGA, which will be open-hardware, because I really want to learn VHDL. For Nanollet, the priority is releasing mobile versions (iOS/Android) and just improving the current features. I’m a big fan of the “dPoW” system and am interested in incorporating it into slower devices.

Thank you, Lucas, for developing the wallet and sharing your progress. I know the community is looking forward to what you have in store. For more information on Nanollet, visit https://nanollet.org/.