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

feat(docs): added FAQ question for AVS deregistration #2808

Merged
merged 2 commits into from
Jan 21, 2025
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions docs/content/operate/faq.md
Original file line number Diff line number Diff line change
Expand Up @@ -109,6 +109,16 @@ Validators must stake native **\$OMNI**. Validators can also opt into receiving

Omni currently has a validator whitelist. The whitelist applies to both native **\$OMNI** staking and **\$ETH** staking via the Omni AVS. A future network upgrade will enable permissionless validator registration.

### How can I deregister from the old AVS contract?

To deregister from the old AVS contract, you must first retrieve a copy of the Omni CLI from GitHub from commit [`ead6061`](https://github.com/omni-network/omni/commit/ead606159fd0724376f1f12a2ab0d34560ab677f) to [`latest`](https://github.com/omni-network/omni) in the main branch. Alternatively, you can wait for release `v0.12.0 (commit: ead6061)` of the Omni CLI, which will support AVS deregistration.

Once you have an updated version of the Omni CLI, you can deregister from the old AVS contract by running the following command:

```bash
omni operator deregister --config-file ~/path/to/operator.yaml
```

### What are the planned staking upgrades?

There will be several network upgrades to enable various validator / staking features. Some of these features include:
Expand Down
Loading