Author: l0k1 2023-02-23 11:11:49
Published on: 2023-02-23T11:11:49+00:00
The context is split into two parts.Part 1:The first part discusses the use case of Indranet, where channel sizes are smaller than normal to transport small payments. The Lightning Network (LN) instance is integrated with the Indra service, and semi-automated creation of channels between relays requires three optimal channels to ensure message layers include special nodes called "seeds." These seeds allow clients to open zero conf, one-way channels for very small balances. The LN mesh in this network is expected to be vast, with all nodes having at least three peers with channels to them. Payments between peers require low latency and do not have fees to simplify route selection.Part 2:The second part talks about the issue of input being signed by one participant, who can sign a different transaction that spends that input differently and bribe a miner to include it in a mined block. This problem cannot be resolved entirely as some confirmed transaction is required to commit the funds to the three participants. ZmnSCPxj signs this message, which includes a public key and digital signature attachments. Furthermore, the discussion aims to explore the use of LN as an anti-spam and anti-sybil rate limiting scheme in a separate peer-to-peer network system. This application could be relevant for various monetized p2p networks where users can anonymously pay other relays to host and deliver content for designated user identities. It also enables this to become a distributed service rather than relying on the trustworthiness of relays.
Updated on: 2023-06-03T12:08:25.008893+00:00