Meta tracking for web E2E Dapp MVP -
infrastructure:
parity/js JS folderethereum-json-rpcparity.js LIBRARYsignerFirst run:
Account creation
.catchAccount list
Accounts details, e.g. funds, tokens https://github.com/ethereum/EIPs/issues/20 (???):
Address book
Balances
Transact and sending
.catch errors (as per import, generic)--chain testnet doesn't show up as test transactionsTokens
Contracts (developer-tool, not for general public, they have dapps)
Signer
Topbar
Apps
GAVcoin
Tokenreg
Registry
Status page
Potential, UX extensions
parity.jsGeneral
.catch everywhereGeneral availability, 1 Nov 2016
[ EDIT/@jacogr - Added all issues to the list above to allow checking them off, a couple addressed, a number remaining ]
NITPICKS FOR TODAY(chrome & firefox):
Wallet App UI wishlist:
the supplied address is an invalid network addressthe supplied address has no checksum formatting &the supplied address has failed the checksum formattingSigner UI (not sure how far you've thought about this)
[ EDIT/@jacogr - Added all issues to the list above to allow checking them off ]
NITPICKS/Bugs:
Adding transaction data reduces gas to zero (deliberate?)
Occasionally losing Gavcoin...returns on refresh
I am not seeing testnet transactions even though that feature is ticked off above?
Signer thoughts:
Now is probably the time to think about how we handle transaction records which have been sent by this instance of parity... Mist keeps them in a separate db so users can view their history. I don't think we will want to rely entirely on getting info from etherscan (or something better) so its definitely worth doing.
UI:
[ EDIT/@jacogr - Added all issues to the list above, except the first 2 - already fixed on Thu ]
NITPICKS:
Address book: Optional contract description:
Gavcoin:
Signer:
Wishlist:
Closing. this meta issue became a bit unwieldily, split out all the issues as per their relevant sections into separate/smaller meta-issues.