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.

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

OperatorsRegistry & middleware contracts #4

Closed
4 tasks done
mempirate opened this issue Jan 7, 2025 · 0 comments
Closed
4 tasks done

OperatorsRegistry & middleware contracts #4

mempirate opened this issue Jan 7, 2025 · 0 comments
Assignees

Comments

@mempirate
Copy link
Contributor

mempirate commented Jan 7, 2025

Context

Even with this off-chain registry, we'll still have to deploy an OperatorsRegistry eventually for integration with restaking protocols, which require on-chain entrypoints for restaking & operator registration etc. The choice to do this now comes from:

  1. The fact that we'll need it eventually
  2. We have most of these contracts already, just need to adapt it
  3. It would actually allow us to integrate with real collateral and restaking protocols immediately
  4. We'd have an on-chain source of truth for the amount of operators & amount of collateral that everyone can monitor

High-level Tasks

Preview Give feedback
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants