-
Notifications
You must be signed in to change notification settings - Fork 302
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
Hide outdated / old / redundant assets #445
Comments
Thanks for documenting this, Kai. |
I followed the discussion in #452 and I would like to add that this "unlist" feature might get additional priority due to regulatory concerns. During April and May the German Authorities are working on a new law regarding tokenized assets. This might lead to the need to unlist assets that do not comply with regulatory requirements. I would love to have this feature rather sooner than later. |
what happens when there is pool and people have liquidity ? if we "retire" the asset, it's not going to be visible. |
This could work as in purgatory. All people invested in it can still access it and remove liquidity, but interactions from new participants would be impossible. But I see a problem with people actually owning datatokens and do not know if they are actually able to interact with / discover a dataset in purgatory right now. Those have datatokens should have the option to change them to liquidity / get rid of their tokens. |
This can be revisited with v4, as the Data NFT includes a new Still pending to be defined which component does what with which state. |
https://docs.oceanprotocol.com/concepts/did-ddo/#state Updating the state to 1,2,3 will remove the asset from |
As discussed with @trentmc during the last DAO town hall meeting I would like to request to hide a dataset / data service from the market interface once it is outdated or migrated to another chain.
This would require the same functionality as for the purgatory with slight modifications:
a. The publisher should not be put into purgatory
b. There should not be any attribution to purgatory because this would impact the reputation of the publisher
This feature would be all about cleaning the marketplace interface up and allow for better visibility of "good" datasets and -services.
I would request to hide i.e. this one: https://market.oceanprotocol.com/asset/did:op:10b1CfF754bE22181a5bE5c2825F1bBC56473DFE
It has been created and due to an error in the process it has been made obsolute by creating a new dataset.
In my opinion it is necessary, that publishers and LPs and token holders still have the option to interact with "hidden" pools as they might want to remove the last bit of liquidity later on.
Looking forward to a discussion and implementation.
The text was updated successfully, but these errors were encountered: