The name of the Send ETH button and the title of the modal dialog should be configurable from the admin settings

The Ethereum address is recorded in a custom record, which is fetched with a GET /u/USER.jsonrequest as a part of the profile data retrieved when another user clicks on the user's icon. This custom data is always visible to all logged-in users in the forum. So anyone can see all user's ETH addresses.

What this means is that the security settings discourse_ethereum_groups and discourse_ethereum_all_user are enforced client-side but not server-side. This just brings false sense of security to the forum admins.

The best fix is to figure out a way to make those security restrictions work server-side. If Discourse's architecture makes this impossible, then the security-related settings must be removed.

If I don't have any tokens in my account I should still be able to make a transfer with 0 tokens. One can imagine that this call could have some meaning to some contracts

I get the following error when i add this discourse plugin and the app fails to rebuild.
If i dont include the plugin app rebuilds fine.

According to this article the way we currently connect to Metamask will not be supported anymore after November 2nd:
https://medium.com/metamask/https-medium-com-metamask-breaking-change-injecting-web3-7722797916a8

Sent from my Galaxy A3 using FastHub

After I sucessfully send ETH on Kovan via metamask the Discourse UI hangs. The console shows the following error message:

Uncaught TypeError: Cannot read property 'hash' of null

The error appears at the following line:

Apparently web3.eth.getTransaction returns null when the transaction is still pending. This is a known bug: web3/web3.js#1679

The Send ETH button is disabled when I click on my own user. It should not be disabled. There are valid use-cases for sending tokens to oneself.

As the title says, the address field cannot be populated. After filling the form and hitting "SAVE" you get the "Saved" message even though the field remains unpopulated.

It seems that the address shown under the sender is the address that they have submitted in their settings. It should show the current address in Metamask instead.

This is happening after I deployed latest discourse with latest commit on procourse master branch. The following might be relevant: https://meta.discourse.org/t/cryptocurrency-tip-system/92531/8