Good morning laolu,
Sorry for the late reply.
> > A random, possibly-dumb idea is that a leased channel should charge 0 fees
> > initially.
> > Enforcing that is a problem, however, since channel updates are
> > unilateral, and of course the lessee cannot afford to close the channel it
> >
Hi Z,
Thanks for such kind words!
> Is there a documentation for the client/server intercommunications
> protocol?
Long form documentation on the client/server protocol hasn't yet been
written. However, just like Loop, the Pool client uses a fully-featured gRPC
protocol to communicate with the
Good morning laolu,
Thank you for your hard work!
Is there a documentation for the client/server intercommunications protocol?
How stable is this protocol?
A thought occurs to me:
* The payment of the lease effectively shifts risk from established forwarding
nodes to those purchasing
Hi y'all,
We've recently released a new system which may be of interest to this list,
Lightning Pool [1]. Alongside a working client [2], we've also released a
white paper which goes deeper into the architecture of the system.
Pool builds on some earlier ideas that were tossed around the ML
