pull down to refresh
Yes, I forgot to mention this. Forward posts can only receive CCs currently, because we can't do a 3-or-more non-custodial split on lightning.
For non-custodial zaps, it's a two-way split to SN and the OP which is already fairly "cutting-edge" for lack of a better term.
I think we will eventually make these work with real sats, but in the background we'll need to do an independent zap for each forward and one for the OP.
Good to know. Nice catch, @grayruby. All these little quirks should be collected in a post until we all become more experienced with cc's
Documentation is probably how I'll spend next week.
He wasn't able to receive sats for some reason so he received CCs, that's what you see.
Since you didn't have CCs, it used sats on your end.
I see. Could he not receive sats due to the forward?
Ohh, right. Forwards always use CCs because we cannot split payments to multiple receivers on the lightning network. This makes us very sad but it's a limitation of the lightning network. Maybe this will change but I am not aware of any ideas how to fix this that don't require some intermediate custody of funds.
I am not aware of any ideas how to fix this that don't require some intermediate custody of funds
The only way to do this with the tech as it is, is to do an independent zap per forward in the background ... basically it'd require its own paid action and its own special retry logic.
ah, right, the "show multiple QR codes" solution if we didn't have attached wallets
Yep, UX nightmare.
"This qr is for OP ... This qr is for Forward0 ... and all the little satoshis went wee wee all the way home"
Hey @k00b @ek here is an interesting one for you.
When you scroll over the sats on Siggy's post #836419 it says zero sats and I see (200 CC's) from me but I didn't have 200 CC's in my SN wallet and I checked my attached wallet and it showed the sats being zapped.
Is it because it has a forward?