Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

DIP #14- Spoof Assets

Open
#14 8 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
blockchain

Research direction

No repository files, tests, or entry points are identified. Start by reviewing the issue's Kleros Curate references and listed risks, then determine the required asset-approval flow and record a resolved design decision; the issue is done when the proposal has an agreed implementation scope.

Written by the indexing model from the issue text.

Description

core priority - low security

What is a spoof asset?
A spoof asset is an authenticated asset that has no intrinsic value and is meant to deceive the community and protocol in order to generate rewards. For example, currently, a "creator" could generate npmjs repos with one line of code and become an authenticated asset on Stakes Social.

Why are spoof assets bad?

  • Create artificial minting
  • Take away from other creators

Potential solution for spoof assets?
A potential solution to mitigate spoof assets is to implement Kleros Curate. Kleros Curate uses the Kleros protocol to organize information. Other uses cases for this product are exchange listings, fake news, or marketplace products. For more information on how it works click here --->: Kleros Curate blog post. Verified assets/creators will receive a badge once Kleros' network of jurors approve the submission.

Potential Issues?

  1. Kleros requires submitters to deposit ETH for the submission. If they are accepted then they will get the ETH back. If they lose then the ETH is used as a fee to pay for the jurors. If creators apply then this decreases the UX experience and creates more gas prices. If the Dev Protocol paid for the ETH then this could open an attack vector to drain company finances.

  2. Submitters will have to interact with the Kleros protocol to submit evidence

  3. All assets must get approved in Curate before being listed on Dev Protocol which will increase the time to launch for creators.

Unpopular Solution?
Admin keys.

Dominant language
No language data
Stars
11
Forks
7
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dev-protocol/DIPs

All issues in dev-protocol/DIPs

Similar issues

More Blockchain issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.