I think this should be a layer above in a separate tool(s).

Maybe bash scripts which use the on-disk filesystem to organize keys,
provide encryption .etc Then you can even have a wallet with a menu to
perform actions which works by decrypting and piping keys to different
tools.

On 08/01/14 18:41, Thomas Hartman wrote:
> I think what is really wanted is the notion of an account.
>
> You want to know the balance of an account, where an account could be
> defined various ways
> -- a single address
> -- a group of addresses
> -- a group of addresses under a deterministic public key(s)
> -- some arbitrary collection of unspent transaction outputs
> -- just something with a name, and no addresses/inputs associated with it yet
>
> I think if we get the notion (or notions) of account right, the
> balance logic is easy.
>
>
>
>
>
>
> On Wed, Jan 8, 2014 at 2:44 AM, Amir Taaki <genjix@???> wrote:
>> sx history implements this, by allowing you to pass multiple arguments
>> in on the command line. I would simply copy this code over to
>> sx-balance. Feel free to just commit it straight to the repo.
>>
>> https://github.com/spesmilo/sx/blob/master/src/history.cpp
>>
>> On 08/01/14 10:30, Grazcoin wrote:
>>>
>>> sx balance shows the balance of a single Bitcoin address, and I would
>>> like to enable multiple addresses:
>>> https://github.com/spesmilo/sx/issues/34
>>>
>>> Any suggestions on how to implement it? I have noticed that
>>> https://github.com/spesmilo/sx/blob/master/src/balance.cpp implements it
>>> using history fetch of the address. Would it require a modification on
>>> the obelisk side?
>>>
>>> Grazcoin
>>>
>>> _______________________________________________
>>> Libbitcoin mailing list
>>> Libbitcoin@???
>>> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/libbitcoin
>>>
>>
>>
>> _______________________________________________
>> Libbitcoin mailing list
>> Libbitcoin@???
>> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/libbitcoin
>>