You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
With a few O's being hacked on their O wallets it puts the O in a position where they have to abandon the orchestrator completely and start over. This has happened to O's such as myself and a few others.
Describe the solution you'd like
I would like to propose that ownership of the registered O is tokenized into an NFT which can be transferrable (similar to ENS ownership) or just transferrable (like contract #18 transferBond) and apply a 7 day reversable cooldown similar to the unstaking function.
Describe alternatives you've considered
Generate an NFT signaling ownership of the O that can be transferred.
Implement a contract function to transfer ownership with a locking period that can be reversable (similar to the withdraw stake locking mechanism)
The text was updated successfully, but these errors were encountered:
Thanks @RyanC92. That's a really nice feature request. Since it's a big one and related to the protocol changes, how about creating a post on the Livepeer Forum. There we can discuss, create LIP and follow up on this topic.
Is your feature request related to a problem? Please describe.
With a few O's being hacked on their O wallets it puts the O in a position where they have to abandon the orchestrator completely and start over. This has happened to O's such as myself and a few others.
Describe the solution you'd like
I would like to propose that ownership of the registered O is tokenized into an NFT which can be transferrable (similar to ENS ownership) or just transferrable (like contract #18 transferBond) and apply a 7 day reversable cooldown similar to the unstaking function.
Describe alternatives you've considered
The text was updated successfully, but these errors were encountered: