Ed’s post from Discord on Dec. 24
@odeac: and I had a good discussion just now. Looks like the mechanism for a wallet dApp to get the history of a user's Rev sends and receives might be best implemented with a new Account contract abstraction that stores its own history. The existing BasicWallet and Purse contracts and other block/DAG mechanisms obscure that type of audit trail (which could be considered a feature). However, for the adoption of RChain, a user must be able to see their conventionally transacted Rev Send and Receive history from a co-op provided dApp (e.g. a command-line wallet). WalletCheck will likely need some enhancements. I'm hoping that @odeac: or others will arrange a meeting for himself and some subset of @dckc: @kayvan: @kellyfoster: @Ned: @Kent: and me later this week to discuss how some of the requirements will be implemented.
User stories proposed for Mercury
Dan and Ed ideas for command line wallet
Related Jira issues
Higher abstraction of a wallet
Contract for wallet is not so difficult
Ovidiu discussed with Kent
What is difficult is preparing the Rholang infrastructure and test and debug the contract
IDEA a wallet could be encapsulated in a single contract
Naming conventions for wallets
Concern the RChain wallet is not aligned to the industry. It will confuse users
Recommendation for nomenclature
design an account and an account contract
How important is it to leverage ETH style for signing transactions (Dan)
How to address mulitsig?
How from a client perspective do we predict the unforgeable name?
What platform does the coop-provided wallet app run on?