-
Notifications
You must be signed in to change notification settings - Fork 912
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
Remove "Legacy key" part from Handbook #375
Comments
This issue is open for a while now, does anyone else have any opinions on this? |
I agree with OP (a very unlikely scenario, but if anyone who does need it has other ways to do so) |
Since Priyank has confirmed, I am confident it can be removed. Would be great if you can do that @os11k |
Hi! I'm bit busy this week, I will try to work on this next week on during weekend. Cheers! |
No rush, sir. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I propose to remove "Legacy key" part from Operate a Stake Pool - Handbook. Do we still need it there?
I found that on 3 pages. 2 of them are in Handbook, so I'm pretty sure nobody needs legacy keys at least for creating a pool. No? If this is ok, I will create PR.
The text was updated successfully, but these errors were encountered: