ULASafe is an open-source chrome/firefox/Opera plugin that allow to store Stellar wallets.
It is currently under development.

Current features:
- real-time balance of Stellar accounts (Public, private keys or federation addresses) (in XLM)
- XLM/BTC rate in many currencies*
- translated in many languages**
- multiple accounts
- account creation
- account merge
- send XLM (Public keys / Federation addresses)
- join custom inflation pool
- print account
- export account by email
- export account by QR code
- protect your data with password
- detect public keys / federation addresses on all websites
- Provide transaction signature

.* currencies currently available: AUD, BRL, CHF, CNY, EUR, GBP, JPY, PHP, USD
** language supported: English, French, Spanish, Portugese

The sources are available on Github -> https://github.com/HerveKoener/ULASafe
The plugin is publicly available:
- For firefox: https://addons.mozilla.org/fr/firefox/addon/ulasafe/
- For chrome: http://quasark.dorefy.com/ULASafe/add-ons/ULASafe.crx
A user guide is available here: http://quasark.dorefy.com/ULASafe/

Here are the future features that I have currently in mind:
- Brain wallet -> IN PROGRESS
- Transaction history
- Budget management
- [Your idea here]

If you have other ideas or information that you want to have in the plugin don't hesitate to post it.
Edit [21/10/2017]: XLM/BTC rates are in AUD, BRL, CHF, CNY, EUR, GBP, JPY, PHP, USD
If you want more currencies, you can ask ?

Edit [24/10/2017]: The plugin is available here: https://addons.mozilla.org/fr/firefox/addon/ulasafe/

Edit [30/10/2017]: Source code available on github: https://github.com/HerveKoener/ULASafe

Edit [03/11/2017]: You can now protect your data with password and the private keys can be encrypted on the browser.

Edit [01/11/2017]: You can now merge accounts

Edit [11/11/2017]: A user guide is now available on http://quasark.dorefy.com/ULASafe/ and the chrome version of the plugin is now public.

Edit [13/11/2017]: ULASafe now support federation addresses:
- You can add federation addresses;
- You can send lumens to federation addresses;
- ULASafe can detect federation addresses on visited website;

    GbolahanEthanOnadeko: The security comes from the browser. If you update frequently the security issues are low.

    bkolobara: yes I was thinking about "auto-detection" of public key or stellar QR Code.
    I will also provide a way to print the accounts (private/public keys).

    bkolobara

    I experimented with chrome extensions last year but hit a cul-de-sac when I realized that custom protocol handlers basically don't work, since they must use a "web+" prefix for all non-standard protocols.

    I tried intercepting horizon requests, and adding signatures for private keys stored in the extension.

    Injecting an API into pages would work, but then again, do we need even more fragmentation than we already have?

      As much as I like the idea, I don't install any more extensions with access to websites I visit after being ripped for some BTC

      12 days later

      I think this would be great. If it handles the signing of transactions too like Metamask does it'd be preferable to copying and pasting keys around and trusting/reading the code of multiple DApp sites .. If the plugin shows you every transaction and requires a manual approval click (or a pin code or passphrase) before signing then your in control. Well hopefully! Need to check the plugin itself carefully and trust it too of course.

      Another approach could be the way Ethereum Mist Browser does it. Instead of bringing keys and wallet to the browser you bring the browser to the desktop wallet. If Stellar Desktop Client for example, embedded a browser you could navigate to StellarTerm, LuPoEx or some app that looks for the standard injected API.

      a month later

      I have updated the developement status.
      I will upload the source on github and provide a link in order to download the plugin soon.

      I'm currently testing the interactions with the stellar network

      I don't like the name, "ULASafe" is not good at all. "Ula"?

      ULAS comes from the name of the highest redshift quasar known these days (ULAS J1120+0641).
      It's also the most distant yet found.
      https://en.wikipedia.org/wiki/ULAS_J1120%2B0641

      If you have a better name, you can propose it.
      I don't have issue to change the name of the plugin.

      The XLM/BTC rate is now available in the following currencies: AUD, BRL, CHF, CNY, EUR, GBP, JPY, PHP, USD.
      If you want another currency, don't hesitate to ask.

      5 days later
      4 days later

      You can now protect your data with password and the private keys can be crypted on the browser.
      The github page has been updated.

      You can now merge accounts.
      The plugin will be publicly available for chrome and opera soon

      hi QuasarK, looks great.

      maybe hide the secret key from view and replace it with a click to reveal link/button? because a good chunk of it visible everytime you navigate back to the home view.

      For me the Join Inflation Pool button worked on the network but it didn't update on the UI. It still shows the joining button.

      Hello,
      By default the private keys are visible on the UI and everybody using the browser can send XLM.
      But if you configure a password for ULASafe:
      1) In firefox menu click on Add-ons
      2) Click on the ULASafe preferences
      3) Set your password

      When the password is set, all the secret keys are encrypted on the browser store and a password is needed to access the following pages: Manage accounts, Account Setting and Send XLM.

      Here is the user guide of the plugin: http://quasark.dorefy.com/ULASafe/

      For the joining button, I see what you mean. In fact, the joining button doesn't disappeared because, you can also change the inflation pool on the ULASafe preferences.
      But for the next version of the plugin, I will check if the current account has already joined the "current" inflation pool and if it is the case, the button will not be displayed.

      Thank you for your feedback.

      Hi hatch,
      You remarks have been taken into account in the current version (1.2.1), ULASafe now check if the accounts have joined the configured inflation pool.

      ULASafe 1.2.1 now support federation addresses:
      - You can add federation addresses;
      - You can send lumens to federation addresses;
      - ULASafe can detect federation addresses on visited website;

      hi @QuasarK , I still just see the "Join Inflation Pool" button. In preferences I can see the inflation pool address is set though it doesn't show on the main UI.

      2 years later