Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
This branch is 9 commits ahead, 1485 commits behind MyEtherWallet:mercury.

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time

Chrome Extension

Download the Latest Release

  • is the smaller package containing the gh-pages branch aka
  • is the chrome extension package
  • source code is the full source for developers to get started with (although cloning or forking the mercury branch is probably a better choice)

MEW Around the Web

mercury is the development branch. gh-pages contains only the smaller dist folder only and is served to

  • Our infrastructure ("node") is on AWS. You can also use your own node.
  • We also provide access to & nodes. Use the drop-down in the top-right.


  • MyEtherWallet is a free, open-source, client-side tool for easily & securely interacting with the Ethereum network. As one of the leading providers of Ethereum services, MyEtherWallet equips users with an easy-to-understand and accessible suite of tools for their needs.
  • It was created and is maintained by kvhnuke and tayvano.


Our Philosophy

  • Empower the people: Give people the ability to interact with the Ethereum blockchain easily, without having to run a full node.
  • Make it easy & free: Everyone should be able to create a wallet and send Ether & Tokens without additional cost.
  • People are the Priority: People are the most important & their experience trumps all else. If monetization worsens the experience, we don't do it. (e.g. ads)
  • A learning experience, too: We want to educate about Ethereum, security, privacy, the importance of controlling your own keys, how the blockchain works, and how Ethereum and blockchain technologies enable a better world.
  • If it can be hacked, it will be hacked: Never save, store, or transmit secret info, like passwords or keys.
  • Offline / Client-Side: User should be able to run locally and offline without issue.
  • Private: No tracking!!! No emails. No ads. No demographics. We don't even know how many wallets have been generated, let alone who / what / where you are.
  • Open source & audit-able

Users (non-developers)

  • It is recommended you start here.
  • You can run on your computer. You can create a wallet completely offline & send transactions from the "Offline Transaction" page.
  1. Go to
  2. Click on
  3. Move zip to an airgapped computer.
  4. Unzip it and double-click index.html.
  5. is now running entirely on your computer.

In case you are not familiar, you need to keep the entire folder in order to run the website, not just index.html. Don't touch or move anything around in the folder. If you are storing a backup of the MyEtherWallet repo for the future, we recommend just storing the ZIP so you can be sure the folder contents stay intact.

As we are constantly updating, we recommend you periodically update your saved version of the repo.


If you want to help contribute, here's what you need to know to get it up and running and compiling.

  • Both the Chrome Extension and the are compiling from the same codebase. This code is found in the app folder. Don't touch the dist or chrome-extension folders.
  • We use angular and bootstrap. We used to use jQuery and Bootstrap until it was converted in April 2016. If you wonder why some things are set up funky, that's why.
  • The mercury branch is currently the active development branch. We then push the dist folder live to gh-pages, which then gets served to
  • We use npm / gulp for compiling. There is a lot of stuff happening in the compilation.
  • Old node setups can be found in in json_relay_node (node.js) & json_relay_php (php). These are great resources for developers looking to get started and launch a public node on a $40 Linode instance.

Getting Started

  • Start by running npm install.
  • Run npm run dev. Gulp will then watch & compile everything and then watch for changes to the HTML, JS, or CSS.
  • For distribution, run npm run dist.

Folder Structure

  • fonts and images get moved into their respective folders. This isn't watched via gulp so if you add an image or font, you need to run gulp again.

  • includes are the pieces of the pages / the pages themselves. These are pretty self-explanatory and where you will make most frontend changes.

  • layouts are the pages themselves. These basically take all the pieces of the pages and compile into one massive page. The navigation is also found here...sort of.

  • You can control what shows up on vs the Chrome Extension by using: @@if (site === 'cx' ) { ... } and @@if (site === 'mew' ) { ... }. Check out sendTransaction.tpl to see it in action. The former will only compile for the Chrome Extension. The latter only to

  • embedded.html is for embedding the wallet generation into third-party sites. Read more about it and how to listen for the address generated here.

  • The wallet decrypt directives are at scripts/directives/walletDecryptDrtv.js. These show up on a lot of pages.

  • The navigation is in scripts/services/globalServices.js. Again, we control which navigation items show up in which version of the site in this single file.

  • As of September 2016, almost all the copy in the .tpl files are only there as placeholders. It all gets replaced via angular-translate. If you want to change some copy you need to do so in scripts/translations/en.js folder. You should also make a note about what you changed and move it to the top of the file so that we can make sure it gets translated if necessary.

  • styles is all the less. It's a couple custom folders and bootstrap. This badly needs to be redone. Ugh.

Use Your Own Servers / Node Guide


How to Help Translate

A couple of notes:

  • Everything on the entire site is broken down into lines and in this one file. The uppermost items are the highest priority and the further you go down, the less of a priority it is.
  • You can add comments anywhere by wrapping it in /* Your Comment Here */. If you want to leave a note for yourself or someone else, do so in this format. That way it doesn't screw up the code or show up somewhere on the site.
  • Don't delete any lines. Just leave it in English if you don't know how to translate it.
  • Always make sure each line ends with ',. So the format is NAME: ' your text here ', You only need to change the your text here part - try not to touch anything else.

If you are NOT a developer and have no idea how this works:

Anyone can help out and it looks way more complicated than it is! If you would rather not deal with Github, please send us an email to and I'll email you the file and you can make changes and send it back to us and I'll make sure you don't screw anything up. If you feel like experiencing something new, read on!

  1. Sign into your Github account or make a new Github account.
  2. Go to
  3. Click on the language file you want to update.
  4. Look in the upper right. Click the pencil icon. This will then tell you, "You’re editing a file in a project you don’t have write access to. We’ve created a fork of this project for you to commit your proposed changes to. Submitting a change to this file will write it to a new branch in your fork, so you can send a pull request." Ignore it all.
  5. In your browser, start translating. Translate as little or as much as you want.
  6. Scroll down to halfway to the translator's section. Enter your name/username, donation address, and any comments you would like to leave.
  7. When you are done, tell us what language you updated. You can also leave any notes about problems you had or things you'd like us to know.
  8. Click the green "Propose File change" button.
  9. This next page is a review of what you did.
  10. Click the "Create Pull Request" button.....twice. Screenshot.
  11. That's it. You successfully made a new pull request! Tell all your friends.
  12. We will now review it and pull it in and it will be made live on the site. We may also ask you questions if something is confusing for whatever reason.

If you are a developer and familiar with GitHub, Pull Requests, and know how to save a JS file as a .js file rather than a Word Doc:

  1. Clone the mercury branch.
  2. Go to /app/scripts/translations/.
  3. Open the language you want to translate.
  4. Translate as much or as little as you wish.
  5. Add your name/username, donation address, and any notes you would like on in the translator's section, about halfway down.
  6. Open a PR and leave us a brief description of what you did and any issues you ran into or comments you have.

Read more @ Help us translate into ALL THE LANGUAGES!


If you can think of any other features or run into bugs, let us know. You can fork, open a PR, open an issue, or support at myetherwallet dot com.

Announcement History & MyEtherWallet CX are licensed under The MIT License (MIT).


Temporary fork of MyEtherWallet with Slovenian translation







No packages published


  • JavaScript 74.5%
  • HTML 13.0%
  • Smarty 10.1%
  • CSS 2.1%
  • PHP 0.3%