-
Notifications
You must be signed in to change notification settings - Fork 5.5k
Closed
Milestone
Description
High Level
- Making Dapps work in Chrome
- Key pair management (generic identity management)
- Basically done already by lightwallet
- Includes UI component
- Ethereum Client
Most of the problem (>=80%) - web3 injected from Chrome extension
Fairly trivial
- Key pair management (generic identity management)
- Launch Prep
Ethereum Frontend JS Client
A light-client that doesn't need to climb the merkle tree, just trusts its provider. Maybe later on we'll move to a lite-client, but those aren't ready yet.
- Provider engine (Caching layer, mostly done)
- Provider engine should handle forks:
- Requires responding to fork announcements on the protocol and cleaning up the cache appropriately.
- Will need to recognize when a block is broadcast with the same # as another block, verify authenticity (same parent).
- Need to replace "what is the newest block" with "what is the next block after X", to avoid skipped blocks
- Provider engine should handle forks:
- In theory, this could maybe be replaced by some kind of webRTC light-client.
- Add toggle between test & main blockchains.
Backend
- Need to have scalable logging solution.
- Some recommendations: @ketux had some tips
- Fix occasional dropped connections from caching/whitelist server in front of the RPC.
- Called eth-rpc-wrapper. Uses node/express
- Finish eth-rpc-wrapper
- Filters out some types of requests, like sleep node, that we shouldn't allow.
- Provide methods the RPC does not provide
- Mapping from account to transaction history
- Provided from etherscan for the time being, but we might want to implement ourselves.
- Mapping from account to transaction history
- Set HTTPS via probably LetsEncrypt for automatic SSL renewal etc.
Frontend Interface
- Allow creating new accounts
- Allow exporting accounts
- Allow importing accounts
- Allow deleting accounts
- Allow nicknaming accounts
- Integrate uPort account flavoring
- Add per-domain configuration
- Allow selecting what accounts the current dApp can see.
- Add friendly first-time user experience flow
- Dapp store integration
Launch Preperation
- Add nice intro to main page
- Compose email to blast out to email list
- Compose reddit post
- Compose Medium post
- Look into using Consensys's Medium account
- Compose HackerNews post
- Pretty up the home page
- Create chrome app store page
- Screenshots
- Description
- Create list of dApps that work with Metamask at launch
- Create simple dApp for Metamask tutorial
- Create software licenses for all components
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels