BOLT#2 states the beneath as one rationale to restrict a Lighting Community channel to 483 HTLCs:
It additionally ensures {that a} single penalty transaction can spend your complete dedication transaction, as calculated in BOLT #5.
In different phrases: we’re constrained by the utmost measurement (based on standardness guidelines) of the penalty transaction. With a P2WSH output being 43 bytes, the dedication transaction may accommodate a considerably larger variety of outputs (and thus, HTLCs) and keep inside the max (standardness) measurement of 400,000 WU. Are there any vital hurdles stopping us from utilizing a number of penalty transactions, the place the nth penalty transaction spends HTLCs [n*483; (n+1)*483[ from the commitment transaction? At first sight, it seems like quite a straightforward upgrade.
To keep the questions focused, let’s ignore the other rationale of 483 signatures fitting in a single commitment_signed message.
Related question (and very useful answer): Lightning Network: How was the maximum allowed HTLCs in flight computed?
