chore: document guidance on transaction resubmission during congestion for users

[jcstein]

Summary

Users need clear guidance on handling transactions that aren't included within 75 seconds, as this indicates the need for transaction resubmission. Especially during network congestion, transactions with relatively low fees might not be included, even after congestion subsides. This documentation update is necessary, particularly in light of changes from celestiaorg/celestia-core#1089.

Details

When transactions aren't included within 75 seconds, users must resubmit them. It’s important to note that transactions, whether originating from celestia-app or celestia-node, won't be regossiped unless there's a new peer, even by nodes with longer TTLs. All transactions are also sorted and pruned based on fees by default.

Tasks

• Update celestiaorg/docs to incorporate the guidance for users about transaction resubmission during periods of congestion.
• Clearly mention that transactions not included within 75 seconds should be resubmitted.
• Explain that during congestion, transactions with low fees might not be processed, even when the network eventually clears up.
• Specify that this applies to all types of transactions, regardless of whether they come from celestia-app or celestia-node.
• Clarify the implications of celestiaorg/celestia-core#1089 and the use of CAT on transaction gossiping and inclusion.

Notes

• All transactions, regardless of origin, are subject to being sorted and pruned based on fees.
• Transactions need to be monitored and possibly resubmitted by the users if not included within the 75-second window.

Related Issues & Pulls

celestiaorg/celestia-core#1089
celestiaorg/celestia-app#2577 (comment)

This issue was generated by gpt-4