Title: Best practices for sending BTC and dealing with fees Post by: randomuser543 on May 10, 2016, 03:55:42 PM I've got a fully functioning web service working with my bitcoin daemon, which I'm pretty happy with. When a withdrawal is requested, I'm doing the following -
settxfee = 16 satoshis / per byte (this seems pretty safe, however I may switch to using 'estimatefee 6') sendtoaddress (I'm terrified about attempting rawtransactions) I'm now thinking how to best handle fees so that they won't eat in to any potential profits. Sending to many isn't an option at this point. Withdrawals will come from warm storage.
I'm still thinking how to best handle things. Should I eat the tx fees or pass them on. Should I deduct a static fee from all withdrawals or a tiny percentage. Title: Re: Best practices for sending BTC and dealing with fees Post by: cloverme on May 11, 2016, 03:37:28 AM I've got a fully functioning web service working with my bitcoin daemon, which I'm pretty happy with. When a withdrawal is requested, I'm doing the following - settxfee = 16 satoshis / per byte (this seems pretty safe, however I may switch to using 'estimatefee 6') sendtoaddress (I'm terrified about attempting rawtransactions) I'm now thinking how to best handle fees so that they won't eat in to any potential profits. Sending to many isn't an option at this point. Withdrawals will come from warm storage.
I'm still thinking how to best handle things. Should I eat the tx fees or pass them on. Should I deduct a static fee from all withdrawals or a tiny percentage. All things considered, fees are pretty low. Calculate the transaction size before sending, calculate the txfee, then deduct total fee from the amount your sending before you send it. Check out this post: http://bitcoin.stackexchange.com/questions/22313/fees-for-bitcoind-sendmany-limits-for-number-of-end-addresses |