My setup is simple, I have a laptop and a raspberry pi on the same network. I installed parity on my raspberry pi and successfully connected to it, e.g., with
geth attach http://192.168.1.:8545. All is well, I can get the most recent block number through the geth console, so obviously, that parity node is working well! I also see no accounts under web3.eth.accounts, obviously because there's no keys on that parity node.
Now I'm about to setup Mist so it uses that rpi web3 provider, and see the following instructions on the mist github:
Connecting to node via HTTP instead of IPC This is useful if you have a node running on another machine, though note that it's less secure than using the default IPC method. $ electron . --rpc http://localhost:8545
How exactly is that setup less secure? My understanding (probably wrong), is that I'm only using that parity node to get latest blockchain info, and to broadcast transaction. None of the keys are even accessible from my parity node (rapsberry pi on same LAN in this case).
What I'm looking for is an experience where I can just open an app on my laptop, and I can transact and see blockchain info right away. There's no light wallet yet, so I feel like this setup with the raspberry pi remote node is the closest I can get. Maybe something more clever?