ZmnSCPxj via Lightning-dev
writes:
> Good morning Alejandro,
>
> I was about to ask Christian this myself.
>
> There is another technique:
>
> Use a sequence of `nSequence`d transactions off-chain. For example,
> to get an 2-bit counter, you would have:
ZmnSCPxj via Lightning-dev writes:
> Suppose, rather than implement a splice-in/splice-out ("channel
> top-up", etc.) we instead implement a more general "cut-through" for a
> channel close transaction.
>
> Normally a channel close spends a single input
Do (should) channels have the option of publicizing their balances, so as
to improve routing performance / scalability in a large network, and for
competitive differentiation among competing routes? This would allow
channel owners to balance privacy with efficiency, and where the incentive
to
ZmnSCPxj writes:
>> This also allows domain operators to have one or more public nodes,
>> but many private ones with channels open to their public nodes to
>> better manage their risk. For example, the private nodes could be
>> behind a firewall.
>
> I am not sure how
Good morning Alejandro,
I was about to ask Christian this myself.
There is another technique:
Use a sequence of `nSequence`d transactions off-chain. For example, to get an
2-bit counter, you would have:
funding -> kickoff -> bit1 -> bit0
Only funding is onchain. kickoff, bit1, and bit0
Good morning Alejandro,
>> No, channel balance of each peer on the channel is not revealed on node
>> gossip.
>>
>> Logically, invert the question: do you want to report how much you
>> spend/receive on each of your channels to the network? Do you want to report
>> how much you own on
Hi ZmnSCPxj,
No, channel balance of each peer on the channel is not revealed on
node gossip.
Logically, invert the question: do you want to report how much you
spend/receive on each of your channels to the network? Do you want to
report how much you own on Lightning to be reported to
Good morning Tyler,
> I will continue to approach the problem of securely advertising
> human-understandable node names, and I hope someday soon I will have a
> solution Lightning can use that retains the open, decentralized properties of
> the technology and the underlying blockchains.
I