reply on: SN release: not custodians \ stacker news ~meta

pull down to refresh

42 sats \ 6 replies \ @k00b OP 4 Jan \ parent \ on: SN release: not custodians meta

For that zap, the lightning network fees to your wallet were too high.

cowboy credits, dead or alive (Bon Jovi)

Ok I see, thanks. So the error message shows sats in msats I guess, should I read 1029 msats > 630 msats hence the transaction failed? What would be the maximum network fee? I thought it would be left to the user in the configuration (I set the max fee rate to 5 sats)

33 sats \ 2 replies \ @k00b OP 5 Jan

We pay the outbound fee on zaps and will pay a max of 3% (which we take from the sybil fee on a zap). That fee for that zap would've cost 7%.

In the future we will allow you to pay the fee yourself if you want, but this is how it works currently.

0 sats \ 0 replies \ @john_doe 5 Jan

Let me ask an other related question. For the sending case I always had a log showing success on Stacker News, furthermore on my wallet I had 21 sats spent plus 1 sat for the fee so it looked ok to me. However is it possible that although the log shows success on my side, on the receiving side it gets converted to CC (so assuming logs show success on sending side and the receiving side has a wallet connection setup)? In this case, would you recommend to double or triple the amount to avoid a failing zap? (e.g.: like sending 42 sats instead of 21) Or use a node/custodial wallet which has a direct channel to Stacker News' node?

0 sats \ 0 replies \ @john_doe 5 Jan

Ok thanks