Remove hardcoded 24h order expiration and use expiration_hours

[Catrya]

Currently, when an order is published, the confirmation messages state that it will be published for 24 hours, but this value is hardcoded. It should display the correct duration based on expiration_hours from event 38383.

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🔗 Similar Issues

Possible Duplicates

• Error displaying when an order was created #358

Related Issues

• The pending order countdown timer shows more than 24 hours. #249
• Inconsistencies in event timing and status changes mostro#506
• Improve the timer and clock when the order is in waiting-buyer-invoice, waiting-payment, and Active statuses. #155
• When an order is republished in pending status, the maker doesn't see the remaining time countdown. #387

🔗 Related PRs

MostroP2P/mostro#507 - Fix: Set event expiration time to 24 hours, improved time to check or… [merged]

👤 Suggested Assignees

• Catrya

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord or schedule a call!

[kufre19]

hello @Catrya was wondering if i could be assigned this issue

[Catrya]

Hello @kufre19 great, welcome! I already assigned it to You. If you have any question ask here

[Catrya]

completed via #392