IBC Milestone #5 needs validation

[jeffwerner00]

• Who should validate?

• Should each of the BPs provide their initial emergency contact person + alternate to populate the alert mechanism contacts now, before considering the feature done? Or, OK to just add names as we move forward?

[jeffwerner00]

Ted to ask NS James to validate milestone 5. Need to determine his backlog before a commit date.

G to message chain heads to get info re: TG channels

[jeffwerner00]

Nathan approved with these comments:

Went over the IBC monitoring solutions with Guillaume. It hits all the marks laid out in the milestone description.

Here are some notes from the call:

Entities running IBC that might be willing to also run monitoring:

• EOS USA
• EOS Nation
• Boid
• EOS Titan (already running it)

Finished elements:

• Each chain has contracts that can be stopped (enable/disable) in the case where something bad happens (like an over-mint). BPs are required to make an msig to enable or disable them. They are going to make a proposal to reduce the requirement for disabling to prod.minor to allow for faster reactions in the case of a problem.

• There are 2 Telegram bots that raise alerts:

  • Token alerts — Raises alters on discrepancy between destination and origin transfers/mints (minted more than was transferred)
  • Technical alerts — Infra alerts
    • History provider down
    • Out of sync
    • Etc

The monitoring UIs are rudimentary but the outputs are good and we can use them for various purposes internally as well (marketing)

[jeffwerner00]

Vote to release payment: EOS: Yes Telos: Yes WAX: Yes UX: Abstain