I have a bunch of wallets for which I expect to cold-sign transactions when required. I have set these up as watch-only hot wallets using monero-wallet-cli
--generate-from-view-key
, but would prefer not to have multiple wallet daemons running at the same time: after all, my node daemon (monerod
and its data.mdb
) is the real aggregator and data store!
Any suggestions on how I can manage multiple wallets(hot or cold) please? How are businesses / DNMs currently managing these(multiple wallets per customer) ?
Asked
Active
Viewed 212 times
2

kumarz
- 307
- 2
- 10
1 Answers
2
One daemon instance is enough. It can service multiple wallets simultaneously. The data stored by the daemon in the .mdb is all public knowledge (the blockchain), anyway.
Wallet-specific data is stored in the cache file. See here for more details. So really, you can keep the daemon running and have few instances of the wallet running and talking to the same daemon. Each wallet stores only some data relevant to it, while the daemon stores the entire public ledger (blockchain).
Popen PIPE
s, but was hoping just the onemonero-wallet-cli
rpc could be pinged by a solution that updates the required wallet file accordingly, coz after all the (wallet)rpc is able to accept multiple calls: so restrictingmonero-wallet-cli
to one wallet only sounds a bit, well, 'restrictive' :p – kumarz Feb 08 '17 at 22:10