You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reason: Ensure conformance with message-size limits on protocol level
Cause:
- Each HTLC may reference multiple asset UTXOs from funding output
- Each referenced input needs a signature, increasing transmission data
Alternative Solutions:
- Implement SIGHASH_NOINPUT on protocol layer
- Allows sending second-level signatures alongside HTLCs
- Requires stable pkScript for next commitment (achieved with per-commitment-secret)
- Limit total number of UTXOs within funding output
- Asset ID is not the limiting factor, but rather total UTXO count
Limiting UTXOs in Funding Output:
Reason: Ensure conformance with message-size limits on protocol level
Cause:
- Each HTLC may reference multiple asset UTXOs from funding output
- Each referenced input needs a signature, increasing transmission data
Alternative Solutions:
- Implement SIGHASH_NOINPUT on protocol layer
- Allows sending second-level signatures alongside HTLCs
- Requires stable pkScript for next commitment (achieved with per-commitment-secret)
- Limit total number of UTXOs within funding output
- Asset ID is not the limiting factor, but rather total UTXO count
[Original commentary]
The text was updated successfully, but these errors were encountered: