I'm not up to date with recent online wallet developments, but suspect they may not support the internal no-fee coin moves between wallet accounts that is crucial to us. Or do some?
You can use the "accounts" system which is built into bitcoind. Using that, you can query each account's balance before executing the command. Alternately, you can that keeps track of each user's balance in a separate database. In both situations, you'll need to write a custom RPC proxy. 
Topic: Bitcoind forwarder / proxy / wrapper (Read 1716 times)
Can't you use a online wallet for handling transactions?
That's possible, but the dependency from a third party web site would jeopardize branding and practical marketability wholly.I'm not up to date with recent online wallet developments, but suspect they may not support the internal no-fee coin moves between wallet accounts that is crucial to us. Or do some?
Do we need to write an RPC proxy "balance limiter" from scratch, or does there exist any such mediator software publicly or privately available?
As far as I know, such a proxy does not publicly exist.Note we cannot use the web wallets as access to our own bitcoind is required.
Can't you use a online wallet for handling transactions, and a bitcoind to get network info? What are you doing that requires bitcoind access?
We would need to grant customers partial access to our bitcoin daemon's RPC API. Partial meaning basically all RPC calls (at least those related to accounts), but with only a portion of the full wallet balance available.
Do we need to write an RPC proxy "balance limiter" from scratch, or does there exist any such mediator software publicly or privately available? Note we cannot use the web wallets as access to our own bitcoind is required.
Do we need to write an RPC proxy "balance limiter" from scratch, or does there exist any such mediator software publicly or privately available? Note we cannot use the web wallets as access to our own bitcoind is required.
Jump to: