Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"One-click" mobile-optimised MerkleMine dApp / WallETH #18

Open
chrishobcroft opened this issue Jul 25, 2018 · 1 comment
Open

"One-click" mobile-optimised MerkleMine dApp / WallETH #18

chrishobcroft opened this issue Jul 25, 2018 · 1 comment

Comments

@chrishobcroft
Copy link

chrishobcroft commented Jul 25, 2018

This issue defines a product to simplify the process of MerkleMining Livepeer Tokens (LPT) on behalf of an address using a mobile browser, and integrated with WallETH to sign the transaction.

That means to submit a proof transaction to Ethereum Blockchain which has the effect of releasing the genesis-minted Livepeer Tokens (LPT) to the address, as well as releasing LPT to the address being used to submit the transaction.

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 WallETH installed
  • if everything is valid, the dApp should open WallETH and populate the transaction for final approval and submission.
  • user approves transaction in WallETH
  • 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 addresses
    • links to txns in etherscan.
    • would you like to mine for another address?
@ligi
Copy link

ligi commented Jul 30, 2018

Process:

user enters ETHAddress
ability to scan a QR code is a "nice to have"

that sounds like horrible UX - users should only enter addresses manually in very rare situations - ideally never.

But I need to understand the use-case better first - what is the reason for the whole process?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants