pull down to refresh

Rough day for my Eagles as well I guess. ;)
BTW did you zap this 1000 CCs?
Yeah it was expected that the Eagles would lose some of their big time defensive players.
I zapped it 1k sats. Not sure why it converted to CC's. Came out of my attached wallet not my SN wallet. I only have 110 cc's.
reply
I zapped it 1k sats. Not sure why it converted to CC's.
I'm sorry to say but this is not good something's odd. Most of the times zapped sats are being turned into CCs.
The wallet logs say fees are too high. Fees to send (withdrawal) I guess, I should increase? It was set to 10 sats. Noe I've done it 100. Maybe the withdrawals now process and I don't get CCs.
reply
20 sats \ 5 replies \ @Cje95 11 Mar
This is a good time to bring in @k00b and @ek for help!
reply
20 sats \ 4 replies \ @k00b 11 Mar
It says what’s wrong. The fees are too high for us to pay. We will pay up to 30 sats (3%) of the amount in fees. The route costs 36.7 sats - more than our limit.
We are not in control of the route and cannot control the fees. In the future we will let the receiver pay the fees out of their own pocket, but this is not how it currently works.
reply
So, even if I've set the withdrawal fees to 100 sats it won't work for now? Also 30 sats isn't the 3% for 700 sats, do we base this on the zap amount, not the invoice amount?
reply
40 sats \ 1 reply \ @ek 11 Mar
So, even if I've set the withdrawal fees to 100 sats it won't work for now?
Yes, because it’s not a withdrawal where you could pay fees yourself but a zap that needs to include the fee to arrive in your wallet.
Also 30 sats isn't the 3% for 700 sats, do we base this on the zap amount, not the invoice amount?
It’s 3% of the zap: 1000 sats x 0.03 = 30 sats
20 sats \ 0 replies \ @Cje95 11 Mar
Thank you for quickly clearing it up!
reply