4 Matching Annotations
  1. Sep 2021
  2. May 2021
    1. Increased Channel Routes In the Lightning Network protocol, Hashed Time Locked Contracts (HTLCS) are used in the construction of channels. A new HTLC is required per route that the channel is serving in. In BOLT #2, this maximum number of HTLCs in a channel is hard limited to 483 as the maximum safe size to prevent the transaction from being too large to be valid. In common software implementations such as LND, this limit is set much lower to 12 HTLCS. This is because accepting a larger number of HTLCS makes it more difficult for transactions to confirm during congested periods as they must pay higher fees. Therefore, similarly to how congestion control is handled for normal transaction, lightning channel updates can be done across an CHECKTEMPLATEVERIFY tree, allowing nodes to safely use many more HTLCS. Because each HTLC can have its own relative time lock in the tree, this also improves the latency sensitivity of the lightning protocol on contested channel close.

      Lightning implementations limit the number of HTLCs because otherwise the commitment transaction becomes too expensive.

      This trick would make the redeeming of these HTLCs more expensive, just the expenses would happen across the time instead of all at once.

      Doesn't seem like an improvement to anything. Just adds cost and complexity.

      And most HTLCs are not economical to redeem anyway.

  3. Jun 2020
  4. Jan 2020
    1. Lightning Platform allows you to build employee-facing apps to customize and extend your Salesforce CRM. With Heroku you can go even further, building pixel-perfect applications for your customers in open-source languages like Java, Ruby, Python, PHP, JavaScript, and Go.

      Lightning: internal apps, employee-facing<br> Heroku: non-internal open-source apps, taking advantage of organization infrastructure and data

      Of course, if not all employees are Salesforce users/licensed, then a "non-internal" app could still be an organizational app, but without having to secure expensive Salesforce licenses. Also, if one wanted to build an external "customer" engagement community it could be done without needing a Salesforce Community and associated community licenses.