pull down to refresh
10 sats \ 6 replies \ @SimpleStacker 5 Jan \ on: What have ya'll learned since SN non-custodial transition? meta
I haven't learned anything. Everything has gone according to how I would've predicted :)
reply
It was fairly predictable that half the users wouldn't be ready for the rollout. It was also predictable that there would be technical issues with people setting up wallets and getting confused between the role of sats and CCs.
This is not the fault of the SN team. They did everything they could to ensure a smooth transition. But it's just human nature. In any large group, you are going to get some people who did not pay attention, or did not prepare adequately for a change. It's not a judgment on them either, maybe SN is just not a big priority in their lives.
But whatever the reason, the rocky rollout was entirely predictable.
Hopefully, though, this can be the catalyst for onboarding many new people to the lightning network. And everyone should open a channel to SN. That will make zapping so much smoother.
I don't know if SN has a minimum channel capacity. If it does (I heard 1M?) they should definitely lower it so that more people can open a direct channel.
reply
This is related to something I was wondering about -- if lots of people opened channels w/ SN, would there be interesting consequences that came from that, either good or bad? For instance, it ties up a lot of capital from SN; or, it turns SN into an important LN hub.
reply
Not sure. I think if all the nodes just had the single channel to SN and are not routing to other nodes, there should be very minimal impact on the broader lightning network. Channel capacity will just go back and forth between Stackers zapping each other.
If most of these nodes are routing to other nodes, then it's harder to predict what might happen.
But one thing I will say, SN is a huge source (in contradistinction to sink) for routing demand. On my routing node, which is connected to SN, every time I increase my inbound capacity to SN, it gets routed back almost immediately, so I almost never have any inbound capacity on that channel.
The node I use for zapping is different from my routing node. My zapping node has only one channel and that's to SN.
reply
reply
I don't. My inbound capacity on my SN channel is sitting at some minimal number right now.
There are probably things I could do like loop more capacity through that channel, and thereby earn myself more routing fees, but my routing node was more of an experiment / personal learning project. I don't really intend to do any serious routing with it.
I would've loved to increase fees to use that channel, but I think you can only set the fee for outbound usage of your channels. Since the routing demand is inbound through SN, I can't deter that with fees unless I simply increase my fees on all the other outbound channels, which I don't want to do.
reply