Features we would like to see in a wallet

Most wallets enable you to see balances either in BTC or in a regular (“fiat”) currency. We would like to be able to see both at the same time.

When preparing to receive Bitcoin, we would like to be able to create easily many ACCOUNTs, and deliver all of them to the sender individualizing the payment request for each. Example: If we are to receive 0.75 BTC, and expect that the funds will stay on cold storage for a while, we would like to be able to set the maximum denomination to 0.1BTC. This would create 8 ACCOUNTs at once, and send them all to the payer requesting 0.1 BTC for the first 7, and .05 for the 8th. It would be nice if we could copy all 8 ACCOUNTS and the bitcoin request for each as a data rectangle of 8 rows each with 2 tab-separated columns (ACCOUNT-tab-amount), so it can be pasted anywhere - and if a spreadsheet, everything will go in a distinct cell. It would be nice if wallets would be able to receive as inputs such data rectangles, like an HTML textarea. It would be nice if the wallet's transaction screen reported confirmations for each of 8 simultaneously until the agreed-upon confirmations have happened.

It would be nice if the online transaction screen reported confirmations for all 8 until the agreed-upon number of confirmations have happened.

When sending Bitcoin we would like the option of choosing which unspents to use. The unspents could be pre-sorted in a configurable choice (by ascending or descending value; by ascending or descending timestamp; by source, this source being able to be labeled before and/or after the receipt), but this choice to be explicitly overridable at transaction time.

We would like the wallets to facilitate safekeeping by chopping up the PASSWORDs (or SEEDs!) into two pieces, where the left halves can be stored separately from the right halves, and obviate the process to the users.

We would like the wallets to obviate and facilitate the multi-signature process. Here is an example of what is called “2 of 3” (denoted 2:3) multi-signature implementation:

A PASSWORD can be split to 3 segments: Left, Middle, Right.

Person A safeguards the Left and Middle parts.

Person B safeguards the Middle and Right parts.

Person C safeguards the Right and Left parts.

No one person can spend the bitcoin.

Any 2 of the 3 people can reconstruct the PASSWORD and spend it.

And if the Bitcoin has been split to many ACCOUNTs, then they only spend what they need, without having to create new keys for the rest.

While the segments need not be contiguous, if they are contiguous then it is easier for users to reconstruct them.

Must have usability switch: the interface users technical terms vs non-technical terms (or both!)

Must be able to export to/import from tab-separated files.

Must be able to group ACCOUNTs - perhaps a good term might be FUNDs.

Must have a connector to MS*Excel. Since most people use MS*Excel, they would arrange information in a way that is best for them.

Suggested feature: budgeting, as inspired by http://www.mvelopes.com/

Advanced feature: SEEDs created from pre-SEEDs and user-defined transformation algorithms (all of this off-line of course).

Example transformation algorithm: TA1: augment every m-th digit by n

Simplified example implementation:

pre-SEED=Brave new world

TA1/m=7; n=-1

calculates SEED=Brave mew workd

all off-line... so that users do not have to strain too hard to come up with brainwallets.

More topics