pull down to refresh

21 sats \ 4 replies \ @0xbitcoiner 7 Mar \ on: deleted by author bitcoin
https://imgprxy.stacker.news/1cDCgDi3xlp_Os50_2-xOMsSm63qLEZRFbTCwoZnVS8/rs:fit:1920:1080/aHR0cHM6Ly9pbWFnZS5ub3N0ci5idWlsZC9hYTllN2I2Njg0Y2Y3NjllZmU0OTdjOTAxZDkyYzRkMjRlZWJhM2MxNDU0MThhYTZlNTYwZTAwYTI4MTE1M2JjLnBuZw
write
preview
0 sats \ 3 replies \ @chairman_pretense 8 Mar
I'm beguiled by your diagram and would like to know more. Can you describe your standard send and receive workflow? What software? (Assuming Core on each PC?) Is PC2 not connected to the internet?
reply
0 sats \ 2 replies \ @0xbitcoiner 8 Mar
you are right
reply
0 sats \ 1 reply \ @chairman_pretense 8 Mar
How does the 2nd PC keep a full node whilst staying offline? Just RPC to share block data?
reply
20 sats \ 0 replies \ @0xbitcoiner 8 Mar
PC2 is disconnected from the internet but communicates with PC1. This means that the only visible peer for PC2 is PC1. PC2 is a cold wallet.
in pc2 bitcoin.conf file
# Connect only to the specified node(s); can be set multiple times. Set to 0 to disable automatic connections.
connect=192.168.xxx.xxx:port
reply