"MerkleMine for your friend" dApp / MetaMask

[chrishobcroft]

This issue defines a product to simplify the process of MerkleMining Livepeer Tokens (LPT) on behalf of a specific eligible address using a browser with MetaMask installed.

That means to submit a proof transaction from the user's address to Ethereum Blockchain which has the effect of releasing a portion of the Livepeer Tokens (LPT) assigned to the eligible address at the genesis of Livepeer's protocol, as well as releasing a portion of those LPT to the user's address.

What is an eligible address?

When Livepeer's protocol was launched to Ethereum mainnet, ~63% of the 10,000,000 tokens were made available to ~2.6m eligible addresses - any address with >0.1 Ether at block 5,264,265.

Why focus on MetaMask?

The reason that MetaMask is being focussed on here, is to leverage MetaMask as one of the most accessible, easy-to-use and widespread ways to interact with Ethereum via a standard browser.

Inputs:

• ETHAddress of account eligible for LPT

Interface:

• text field: ETHAddress
• button: "claim LPT" for this ETHAddress

Process:

• user enters ETHAddress
  • ability to scan a QR code is a "nice to have"
• user clicks "claim LPT" button
• dApp validates the following, showing progress indicator and "success" or "failure" of each validation:
  • whether ETHAddress is eligible (i.e. that it had >0.1 ETH at block 5,264,265)
  • whether ETHAddress still has LPT to be claimed
  • whether user has MetaMask installed
    • if not, provide link to MetaMask
• if everything is valid, the dApp should open MetaMask and populate the transaction for final approval and submission.
• user submits transaction in MetaMask
• once the transaction has been mined, the dApp should show:
  • summary of how many LPT have been transferred to which addresses
    • a nice to have would be some kind of pie chart showing a total of 2.44LPT and how it was split between the user's
  • links to txns in etherscan.
  • would you like to mine for another address?