SIGHASH_NINPUT Development Ethereum and its location on lightning network
In the early days of the Lightning Network, the original Joseph Poon white paper offered an essential feature: sighash_ninput (sighash) had to be used as a condition for a commitment transaction that indicates another operation without acting. However, this approach has made significant changes in the development of the network.
Original intention
In the original Lightning Whitepaper Poon, “The first commitment should be able to rely on the TXID funding transaction without actually incorporating it.” This condition was designed to create a commitment that could verify the authenticity and integrity of the transaction, while indicating its origin. Using sighash_noinput, operations should not be introduced from the network, which would simplify the process and reduce the complexity of the network.
evolution
However, over time, the lightning network has developed significantly. 2017 Implemented Funding Transactions (FTX) Function 2017 Marked an important stage in creating sighash_ninput. By enabling FTX obligations to not require the network input, developers could simplify the process and reduce the complexity of the operations approval.
sighash_noinput in contemporary Ethereum
In the modern Ethereum Sighash_Noinput, still used for certain purposes. However, his role declined significantly compared to his initial intent. In fact, most Lightning network operations now use other mechanisms such as the “commit” field or “sequence number” to achieve similar goals.
For example, when creating a commitment transaction that indicates another operation without actually excluding it, the developers may use the following method of the following methods:
- The obligation field: This is used to indicate a specific range of operations.
- Sequence numbers: They are assigned to each operation and can be used to check the sequence of events.
- FTXS (fund operations): As mentioned earlier, FTX enables operations to perform without a network deposit.
Conclusion
Although the Sighash_Noinput is still used in certain contexts of Ethereum, its initial intention has mainly changed more efficient and simplified mechanisms. The lightning network continues to develop, and developers are exploring new ways to simplify the approval of the operations and reduce complexity. As you move forward, it will be interesting to see how sigh_ninput develops or changes these alternative solutions.
Sources:
- Lightning Network White Paper (2017)
- Ethereum WhitePaper: Ethereum 2.0 Testnet and Lightning Network (2020)
Leave a Reply