Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

IF: Consider changes needed for downstream dependencies related to IF transition #94

Closed
Tracked by #39
bhazzard opened this issue Jan 16, 2024 · 0 comments
Closed
Tracked by #39

IF: Consider changes needed for downstream dependencies related to IF transition #94

bhazzard opened this issue Jan 16, 2024 · 0 comments
Labels
triage

Comments

@bhazzard
Copy link

Starting lightweight with a list of downstream dependencies that may be affected.

  • Block Explorers (show finalizers, determine active BPs from active proposer policy)
  • Customized Trace API (like Robovorsky)
  • Deep Mind (and firehose / substreams)

Probably not impacted:

  • Wallets
  • PowerUp
  • SHiP providers
  • Trace API
  • Prometheus
  • API providers / consumers
  • Vert testing framework
  • DappRadar

Other Thoughts:

  • Node Operators might be more likely to want to run in irreversible mode
  • Node Operators may want to update failover scripts
  • Node Operators may need additional key lifecycle management
  • May consider suggesting that Exchanges run in irreversible mode after transition to IF.
@bhazzard bhazzard mentioned this issue Jan 16, 2024
Open
@arhag arhag transferred this issue from AntelopeIO/leap Apr 29, 2024
@bhazzard bhazzard closed this as not planned Won't fix, can't repro, duplicate, stale Oct 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
triage
Projects
Team Backlog
Archived in project
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bhazzard @enf-ci-bot