I note you added support to view send and receive other assets. Thumbs up!! I can now view balance and send other assets like FUNT with this wallet. But I noted one more thing I didn't notice before. It seems federation lookup is not supported yet? I tried sacarlson*funtracker.site as a destination address and I got invalid destination address. I checked on another wallet and it seems the federation server was working at the time.

Other than that this wallet is looking nice.

You are so good at making cool user interfaces that maybe you can also come up with a user interface to also some day add remote signing of transaction so that we don't have to fully trust this site with our secret key. Maybe some QR-code or something that an android or other device might read to get a transaction envelope to signed and feed it back. My attempt of adding remote signing to my branch of stellarterm is a poor example that hopefully people like you can improve upon.

Good work

    sacarlson Hey! Yep I'm working on the federation server - writing one in php (but you already know from slack ?)

    Regarding the remote signing, perhaps I understood wrong but, wouldn't this require another wallet (unless doing the signing thing etc. by yourself but this would require the user to be an advanced stellar user)? implying using the secret key elsewhere and so having to fully trust another website?
    But maybe I have not understood what you meant?

    Thank you for your feedback on the interface/design! Being in front of it all day nor night makes it difficult for me to evaluate it ?

      Yes remote signing requires another wallet that is trusted to be the signer as an option. In my example on my branch of stellarterm https://www.funtracker.site/stellarterm/#account it's optional to login with your public ID or your secret key. For remote signing I provide stellar laboratory as a trusted point that can be used to sign the transaction. Stellar labs can also be used to view the transaction that is being signed before signing it. I also provide my_wallet as an option that also is able to sign transaction envelopes and submit them. I think dzham was working on adding a QR-code interface to sign transactions with his stargazer wallet that might also be working by now as an option.

      But the point is as you said this is an advanced feature and as difficult as the user interfaces we now have are now, most people won't find it easy or even possible to use.

      So I guess what is needed is an easy way to both input your public ID into the wallet we use to generate the transaction with QR-code or copy paste or auto fill ?? and a simplified view of the transaction that will be signed on the signing wallet when it does the signing. And both those parts need to be made very simple and easy with an android phone and qr-code or just URL links to a web wallet. or maybe some kind of hardware wallet dongle at some point.

      The option is not only that your wallet can be the wallet that has options to remote sign but also be the optional wallet to be the trusted signer for transactions of others web apps. We just need an agreed protocol to allow this.

        Hey.

        I was looking for a clear, simple Lumen Wallet, so I gave yours a try. And I think I will stick on him. Easy to use, no log-in, fast and minimalist. After all, we're not here for design, but for efficiency, and Blackwallet does good job on both aspects.

          sacarlson Hey, yeah it might complicate things, but I may add a such feature in the future - for now I'll stick to my roadmap and will see what be can done then ?

          Mail sending is almost ready and will be released in the next (huge) update, this is what the mail will look like:
          mail sending

          MathisDmm , BlatteMure , NicolasSperduto thanks for the kind words! hope you will give feedbacks of the next update as there will be many new things to test!

                  5 days later

                  Huge update

                  blackwallet v0.1.4
                  - merge account operation is now suppported, if you try to send more Lumens than you own, a window will appear asking if you want to send ALL your lumens instead
                  - fixed a bug that was preventing non-existing accounts to be funded.
                  - minor bugfixes
                  - changed some animations, loading will popup instead of notifications for trust lines & inflation
                  - improved holdings display, issuer is now displayed too.
                  - fixed a bug that was preventing the wallet from loading
                  - federated addresses are now supported
                  - sending to emails is now supported
                  - you can now link your public key to a blackwallet.co federated name (in receive money > federated name)
                  - when receiving lumens from a mail, you can choose to link your email to your account id (federated address)
                  so that next time someone send lumens to your email from blackwallet, you will directly receive them (+added security to prevent users to link email they do not own to their account id)
                  - icon changes (now more intuitive)
                  - transaction's date is now displayed in the transaction history
                  - fixed a bug with "auto-refresh"
                  - improved page performances/loading speed (gzip) (~ -200ko)
                  - other minor improvements
                  - fixed IE/Edge problems

                  Hope you will enjoy them! And if you're not yet using blackwallet, I hope this will convince you!

                  I am currently updating the get started page with documentations for the new features - docs should be updated in the night!

                  Updated getstarted & home pages!
                  Also, blackwallet will be opensourced before the end of the week! (on github)

                  Great job, the wallet is very nice.

                  As an improvement, I recommend to translate also the interface in french.
                  As french is your mother tong it should not be very hard to do.

                    QuasarK Hey, thanks!

                    Regarding the translation thing, I should have chosen angular to develop blackwallet... ? (maybe I'll migrate to it later) - but well I think I can write a translation extension! Will work on it ?

                      Backwallet supports the new meta info for the anchor's assets

                      tonaira
                      tonaira
                      tonaira3

                      Also added 2 languages : italian & french

                      Hope to deploy the update today!

                      A new update has been deployed!

                      blackwallet v0.1.5
                      - blackwallet is now in 3 languages: english, french & italian! (thanks to nekrataal for the italian transaltion)
                      - Anchors assets can now be added easily, just enter the anchor's domain name to get the available assets
                      - added LupoEx in the exchanges list!
                      - we now support the update on assets meta infos
                      - some minor changes & improvements
                      - bugfixes (loading window not closing etc.)

                      blackwallet in french on ios!
                      screenshot of blackwallet in french, running as a web-app on ios!

                      Cool. You are making a lot of improvements. Few issues

                      • Where are the secret keys saved? You should make this clear on the screens you enter in the secret key.
                      • Why do you have the ripple price chart in there?
                      • In recent txs the accountID is a link to stellarcahin.io but seems better to have it just open this "inspect" screen you made and have the "inspect" screen have a link to "more info" which is to stellarchain.io or steexp.com
                      • the send form isn't doing path finding. For example you should be able to send XLM to <phone number>*coins.asia and have the receiver get PHP. Checkout how stargazer is doing it.
                      • it doesn't seem to support sending to payment addresses (things like bob*domain.com) ,at least it doesn't display the accountID it gets back or an error if you give it a bogus one.

                        jed Hey jed! Thanks for your message!
                        I've deployed v0.1.6 in accordance to your remarks!

                        Where are the secret keys saved? You should make this clear on the screens you enter in the secret key.

                        It depends, if you are using blackwallet.co without enabling the mobile mode, then the secret key is stored in a javascript variable.
                        If you enable the mobile mode, then your secret key(s) will be stored in the localStorage - I am currently working on a PIN encryption system!

                        I've added a "security concerns" popup on the wallet's page after the unlock button!

                        Why do you have the ripple price chart in there?

                        As many people claim there is a price correlation between XLM and XRP, I thought that adding it for prevision purposes could be a plus - removed it as it could be confusing! (perhaps i'll add a checkbox in the settings for that if people want it)

                        In recent txs the accountID is a link to stellarcahin.io but seems better to have it just open this "inspect" screen you made and have the "inspect" screen have a link to "more info" which is to stellarchain.io or steexp.com

                        Good idea, had not thought about it! It's now working that way ? (added both stellarchain & steexp link)

                        the send form isn't doing path finding. For example you should be able to send XLM to <phone number>*coins.asia and have the receiver get PHP. Checkout how stargazer is doing it.

                        Not sure about that one, I checked stargazer and has not found a difference with blackwallet, perhaps I'm missing something?
                        I think the difference is that stargazer is displaying the address before you click the send button - while blackwallet is displaying everything once you clicked the send button (before sending, there is a confirmation window that shows up details like federated name, account id, amount, memo, message etc.)

                        I've changed the "SEND" button's text to "CONTINUE"

                        it doesn't seem to support sending to payment addresses (things like bob*domain.com) ,at least it doesn't display the accountID it gets back or an error if you give it a bogus one.

                        It works for valid federated addresses ?
                        Regading bugus ones, you're right - I've noticed that Federation lookup function in the stellar sdk wasn't returning an error when a lookup failed so the .catch() function was never called has it stopped working - I now use an ajax trick to handle bugus destinations ?

                        So now, trying to send to a invalid federated address will display an error: "Domain not found"

                        Changelog

                        v0.1.6 changelog
                        - fixed a bug with federated address lookup on non-federated domains (now display a: "Domain not found" message)
                        - removed the XRP from the charts list
                        - clicking on a public address in the transaction history will now display more infos about that address in the inspect tool
                        - some files minification to increase loading speed

                        working on:
                        - use a pin system for secret keys encryption

                            wow so many screen shots.

                            For sending are you using this: https://stellar.github.io/js-stellar-sdk/Server.html#paths ? This is what I mean when I say it doesn't seem to be supporting path finding

                            I've changed the "SEND" button's text to "CONTINUE"

                            "CONFIRM" is probably better

                            Also you might have to do the federation lookup before this confirm screen since if the federation comes back with a memo then you can't allow the user to enter their own.

                              jed Nope, I'm not using it yet! I'm not sure to understand it btw, will look into it and add it asap then, thanks ?

                              Yeah I thought about "CONFIRM", "CHECK UP" etc. but was not sure of the best word, will change to "CONFIRM" (+ I will change the federation lookup to work a bit like stargazer, disabling the confirm button while the lookup is not finished and then display the address & memo if set)!

                                Little update:

                                • changed "CONTINUE" text to "CONFIRM"
                                • inspect tool now support federated addresses
                                • fixed an asset loading issue