pull down to refresh

Sparrow does allow for fees lower than 1 sat/vB. You just need to connect it to a Bitcoin node that has a lower minrelaytxfee 😎
How does the node react if all peers have standard minrelaytxfee? Keep it in its pool and periodically try to send it? Or does it try to connect to peers with low minrelaytxfee?
reply
10 sats \ 5 replies \ @m0wer 4h
For some reason I always have peers that broadcast transaction with lower fees. Without even hardcoding any. You could force the connection to some specific peers if you want to make sure. I think transactions in the mempool are not rebroadcasted by default.
reply
What is the unit of that setting?
seems to agree that minrelaytxfee=100 means 0.1 sat/vB.
With minrelaytxfee=100 I see
[warning] -minrelaytxfee is set very high! The wallet will avoid paying less than the minimum relay fee.
Edit: and Electrum shows error 'min relay fee not met' when trying to publish a 0.3 sat/b transaction (through electrumpersonalserver).
reply
0 sats \ 3 replies \ @m0wer 3h
Yeah the units are a bit weird: BTC/kvB.
This is my conf. The second one is to raise data limits already, but this is more controversial nowadays.
# relay settings
# min relay fee of 0.01 sat/vB
minrelaytxfee=0.0000001
datacarriersize=1000000
reply
27 sats \ 2 replies \ @Scroogey 2h
I now set mine to
# in BTC/vkB, so 0.1 sat/vB is 0.000001
minrelaytxfee=0.000001
and successfully made a transaction with 0.3 sat/b in Electrum!
reply
0 sats \ 1 reply \ @Scroogey 2h
But it doesn't reach the miners or doesn't get picked... Not visible on blockchain explorer, either. Seems like it doesn't propagate.
reply
0 sats \ 0 replies \ @m0wer 2h
Some miners don't pick transactions under 1 sat/vb.
You can check if at least it propagated through the network. Checking https://mempool.space or similar.
reply