不正なクリエイターの上場廃止機能(Ability to delist rogue creators.)

(English version is described at the bottom)

概要

不正なProperty(クリエイター)をMarketから除外する機能を実装しようと思います。

詳細

もともとMarketの認証を解除するのは、Propertyのauthorしかできませんでした。
今回、ユーザからの通報があり、GitHubのリポジトリが削除(もしくはprivate化)されているPropertyが見つかりました。
クリエイターに継続して開発する意思がないと思われます。
なので、author以外によるMarketの認証を解除機能を実装しようと思っています。
今のところ、Marketのowner(deployer)のみがそれを実行できるようにするつもりですが、実行可否の判断はガバナンス投票でコミュニティに委ねるべきだと考えています。
なお、Marketから除外されると
・ステーキングができなくなります
・ステーキングの解除はできます
・ステーキング報酬が引き出せなくなります
・クリエイター報酬が引き出せなくなります
ので、ご注意ください。

この機能のDIPを記述しようと思います、ご意見あればいただけませんでしょうか。

===========================================================================

description

I’m going to implement a function to exclude invalid Properties (creators) from the Market.

details

Originally, the ability to deauthenticate Market could only be performed by the Property’s author.
This time, we received a report from a user and found a Property that had been removed (or made private) from the GitHub repository.
So I’m planning to implement a feature to remove Market authorization by non-authors.
For now, we are going to allow only Market owners (deployers) to do that, but we think the decision on whether to do it or not should be left to the community in a governance vote.
If property are excluded from the Market
・Staking will be disabled
・You can remove the staking.
・Staking rewards cannot be withdrawn
・You will not be able to withdraw your staking reward.
Please be careful.

I’m going to write a DIP for this feature, if you have any suggestions.

Even if a Property is in an unauthenticated state, any staking users can cancel their own staking, with the existing contract, right?

An unauthenticated Property will result in a staking reward of 0 by the following code.

Subsequent codes do not throw an error, even if the staking reward is 0.

*_amount is the number of stakings requested to be cancelled, not rewards.

Hi, maybe we can discuss this further as I see the following case:

  • I stake on a valid project all my DEV tokens
  • the project after a few months goes private
  • I’m not aware of that
  • I go to vacation and don’t bother with DIP notifications or just decide to get back to DEV in an year
  • the project is delisted and all my DEV tokens are basically gone
1 Like

Yes, you can cancel the staking.
I’ll rewrite the details.

Yeah, this problem obviously happens. However, I think there are multiple patterns of how to think.

  1. Do not stake on projects that I should be wary of
    For projects that you should be wary of, such as lack of credit, you can choose not to stake from the beginning. This is a deterrent, and each project may be motivated to perform regular maintenance and build credit. However, it is personally disappointing that the motivation works to avoid “negative incentives”. (But I think it makes sense to have it)

  2. Protecting staking users
    Only the target creator’s reward will be reduced to 0, not the staking reward. This is a generous spec for staking users, but I have no idea right now if this is the right thing to do.

1 Like

I misunderstood the details of the specifications.
Staking release is possible.

So, your DEV will not be lost. You won’t receive any reward, though.

2 Likes

Thank you for your review :slight_smile:

This is extremely important, projects can’t just delete their repos and still abuse the system to be funded when they’re doing nothing.
Yeah, I think removing those rewards that were accrued during after this type of behavior is also necessary unfortunately.

This completely fixes the problem imo, when deleting their repos or doing something unethical, the Creators should first aware the team, if they don’t, this should be done. Stakers, most of the time won’t be checking Creator’s activity and repo daily, so they should be able to claim their Rewards, since its not their fault.

この機能を実装しようと思います。

・Marketオーナーは、特定のpropertyの認証を解除することができる機能

これでよければ投票に移りたいと思います。
どうでしょうか。

I would like to implement this feature.

the Market owner can deauthenticate a specific property.

If this is OK, I would like to move on to voting.
What do you think?

Can you write a DIP?

It should use the template-technical-dip.md as that template

1 Like

今からDIPのテンプレートに従って、DIPを作っていきます。

Now we will follow the DIP template to create the DIP.