An implementation in the Bitcoin Lightning network will allow the creation of multiple payment channels in the same transaction thanks to the development of a new technology that makes use of PSBT or partially signed transactions.
The development of this new enhancement to the Lightning network was led by programmer Oliver Gugger, the current developer of the Lightning Labs company. He has been working on this implementation since June 3rd, when the first proposals were published in the Lightning Network Daemon (LND) client repository. The implementation referred to here was officially included
in the source code on September 3rd.
The implementation would mean an improvement in terms of the creation of payment channels, since it would allow the creation of different channels through a single transaction, without leaving aside security and privacy aspects. The advantage of this tool would lie in the waiting times and low commissions. By creating different channels in a single transaction, the user will have more liquidity within the Lightning network in less time, and will not have to pay a commission for each different channel he/she wants to open.
A payment channel, on the other hand, according to the CryptoNews Cryptopedia
definition, is a means that allows the exchange of BTC outside the blockchain, in which two people pledge funds as collateral or backing for the exchange. This allows for peer-to-peer transactions to be possible, without the need to wait for confirmations within the Bitcoin blockchain. Programmer Alex Bosworth was the first to propose a solution to this issue of batch creation of payment channels. Source: Github.
According to Gugger himself in a thread
on Github, the project solves a problem of how to use PSBTs to improve the funding and batch creation of payment channels. Previously, the problem was raised, but this did not give a solution that could be considered secure, as is the case of the one implemented by Gugger through partially signed transactions or PSBT.
It should be clarified that, for this functionality to be used directly from the Bitcoin Lightning wallets, it would still need to be adopted by each of the different wallets. This is because its activation in the source code does not necessarily mean that users can make use of it immediately.
The latter usually applies to any recent development that is adopted.
within the protocols either Lightning or directly in Bitcoin, as is the case of Taproot, which will be active in mid-November, but would still lack the activation by the nodes of the network, as reported by CryptoNews.