It seems that the technology does not match the intentions. Even if lighting is faster, you need to keep open state channels, and many coins are stuck in staking as I understand it.
Stakenet activated segwit (p2sh and bech32) in summer 2018. Right after they enabled the lightning network and finally made their first atomic swap due to the lightning network a few weeks ago. The mainnet guide for the average linux operator was published a few days ago.
The decision to use segwit addresses is based on the previous risk of badly formatted transactions by bundling of micropayments in lightning channels which could cause different tx IDs for the same transaction. By avoiding this risk with the use of segwit addresses it is possible to upgrade the current masteenodes in so called watchtowers. These watchtowers are a combination of masternodes and lightning nodes and multi-payment-provider. Stakenet believes, that masternodes can be much more than just coinmixer, instant sender and governance provider. Therefore, we modify our masternoders (which already become watchtowers) again and empower them as lightning-channel manager and liquidity provider by using their colloteral to fund the lightning channel. Each masternodes will be a fullnode and lightning channel for at least stakenet with the possibility to add other fullnodes and lightning nodes on top of it for any other lightning compatible currency of your choice. In the end, every masternodes with the same fullnodes will act as a failover node for any other masternodes with the same specs. The result will be a highly liquid lightning network with no risk of coin hostage or delays of a pending channel opening/closing.
Best regards
JStarhead | X9 Dev