DIP #14- Spoof Assets

Aperta
#14 8 commenti 3 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
20/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Ferma
Ambito
blockchain

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
Nessun dato sulla lingua
Stelle
11
Fork
7
Nessuna PR unita negli ultimi 30g

Guida per i contributori

Nessuna guida per i contributori indicizzata per questo repository

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di dev-protocol/DIPs

Tutte le issue di dev-protocol/DIPs

Issue simili

Altre issue su Blockchain

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.