ok try edit bitcoin.conf or regtest equivalant
proxy=172.31.32.200 ( server ip address)
Topic: Remote wallet.dat and bitcoind (Read 151 times)
Ah, see the -disablewallet option for bitcoind ... that will disable the wallet and allow bitcoind to be a proxy for all rpc requests as desired ... the only question then have is how do we run a client that has just the wallet management capability and proxies requests via bitcoind
Thanks for the response ... just want to clarify - dont want to share the wallet.dat ... want bitcond just to be a rpc server while have the wallet on another node
Hello all;
Was able to setup bitcoind in a local test mode (regtest) to explore the bitcoin json-rpc protocol. Starting bitcoind also creates/manages the wallet.dat. Is it possible to setup/create/manage the wallet.dat on another node (remote) and setup bitcoind as just a json-rpc proxy to send/receive bitcoin requests ?
Thanks in advance
Was able to setup bitcoind in a local test mode (regtest) to explore the bitcoin json-rpc protocol. Starting bitcoind also creates/manages the wallet.dat. Is it possible to setup/create/manage the wallet.dat on another node (remote) and setup bitcoind as just a json-rpc proxy to send/receive bitcoin requests ?
Thanks in advance
Jump to: