API - Better UX

[RafilxTenfen]

Summary

• Create an API to retrieve the in-memory information about peggo

Problem Definition

• We need this feature so that the frontend is able to retrieve which transactions are being crossed and give a better UX

Proposal

• Add a new flag

  • To define if the API will be available
  • Maybe another flag to define the base URL (if possible do this with only one flag)

• The endpoints needed for each side like (ETH -> UMEE & UMEE -> ETH) we need to know the information from both sides

  • Txs waiting to be batched
  • Txs in a batch not processed yet
  • Txs that are successful

---

For Admin Use

• [ ] Not duplicate issue
• [ ] Appropriate labels applied
• [ ] Appropriate contributors tagged
• [ ] Contributor assigned/self-assigned

[0xshogun]

@khoerling we can currently see this by querying by address, but we need to be able to monitor the process overall. So instead of putting in an address, we need to see if there's any transactions stuck in the process (and in what stage of the process they're in)

[khoerling]

Started work branched off main, using a single status port flag for now, listens on all interfaces if enabled: https://github.com/umee-network/peggo/tree/342-api-better-ux