... I didn't think the node made a difference...except to my CPU and bandwidth.
Yes it does
If you make a txn that isn't confirmed, your local node will send it out again, I think once every few hours or so ... (I'm not sure how often)
Basically the issue is that standard bitcoind has a habit of throwing away transactions after a while if they aren't white-listed.
Adding a txn via the RPC white-lists it i.e. creating the txn on your node.
If you aren't using the node for your wallet, then get the txn from your wallet:
On the wallet:
bitcoin-cli getrawtransaction txnid....and the long hex output, go to your node and:
bitcoin-cli sendrawtransaction longhex....Well...at least my intuition was good on that one...
Thanks, Kano...makes sense. Yup, my wallet is the Core, so I don't think I need to do anything else at this point. It has worked well, with the exception of that episode last month when someone spammed the blockchain...but even then all my tx's came back.
Anyway...I'm blessed in that I have no data cap, a 100mbps connection, a high-end workstation with a backup, and free power...all 30 amps of it.
I can open 8333 on the modem straight through, and handle the security with my own router on my end. Right at the moment, Core says I've got 63 active connections. Macheen workee.
Mine on...