Market owner can de-authenticate specific properties.
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- authorization, blockchain, security
Research direction
Start by locating the onlyLinkedPropertyAuthor modifier and the market deauthentication function mentioned in the issue. Add or update tests for market-owner and property-author authorization, then verify that deauthenticated properties cannot be staked or rewarded but can have staking canceled.
Written by the indexing model from the issue text.
Description
References
不正なクリエイターの上場廃止機能(Ability to delist rogue creators.)
Sentence Summary
This problem solves the problem of not being able to unauthenticate with the market except for the property author.
Paragraph Summary
This DIP proposes a feature that allows the market owner to freely deauthenticate the property.
Component Summary
Modify the onlyLinkedPropertyAuthor modifier.
Currently, an error occurs unless the sender is an author of the property.
This will be changed so that the error will not occur if the "sender is the author of the property or the owner of the market".
Motivation
There have been cases where development repositories have been deleted or made private. We provide this feature to deal with this.
Specification
Proposed Code
I'll implement it now.
Test Cases
・Only the market owner and the property's author have the authority to execute the market deauthentication function.
・Check that the following conditions are met for the deauthenticated property.
・Staking cannot be performed.
・Staking can be canceled.
・Creator reward and staking reward cannot be obtained.
Security Considerations
Make sure that only the owner and the author of the property to be deauthorized are authorized to execute the Market deauthorization function.
(Author-based deauthentication has already been implemented.)
Copyright
Copyright and related rights waived via CC0.
- Dominant language
- No language data
- Stars
- 11
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dev-protocol/DIPs
-
priority - high tokenomics
Difficulty 5/5 Over a week Newbie friendliness 20/100
dev-protocol/DIPs#76 · 4 comments · 1 reaction ·
-
layers
Difficulty 5/5 Over a week Newbie friendliness 20/100
dev-protocol/DIPs#52 · 2 comments · 4 reactions ·
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
dev-protocol/DIPs#50 · 28 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
dev-protocol/DIPs#48 · 13 comments ·
-
core layers usability
Difficulty 5/5 Over a week Newbie friendliness 20/100
dev-protocol/DIPs#47 · 3 comments ·
All issues in dev-protocol/DIPs
Similar issues
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
AXERA-TECH/ax-llm#75 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
gitbutlerapp/gitbutler#15998 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·
-
clawsweeper:needs-product-decision clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:security impact:ux-friction issue-rating: 🦞 diamond lobster P2
Difficulty 2/5 1-3 hours Newbie friendliness 84/100