Asset ScamList
current project status
Current Project Status
unfunded
Total
amount
Received
$0
Total
amount
Requested
$21000
Total
Percentage
Received
0%
$ Received out of $21000
Solution
A github repository containing all tokens identified as scam, rugpulls. A program with set of rules that automatically categorize potential spam and add into repository. A manual revalidation process
Problem
Today, with more than 5,000,000 assets created on the cardano network, we also have a proliferation of copies, imitations that aim to deceive users.
Impact alignment
Feasibility
Value for money

Équipe

  • download
  • download

[IMPACT] Please describe your proposed solution.

Today at the beerhouse.io project, we felt the need for a shared repository where any developer can report a scam.

We internally developed 4 rules to identify common scams (similar names, similar image, similar description, bot that captures the policyId of the originating site and is identical to the current site) and modified our cardano-db-sync to behave and ignore these tokens created for only deceive and deceive the

user.

The idea is to create a shared repository (similar to cardano-token-registry) and together with this a validation process, partly automated and partly carried out by a capable responsible team.

This repository may be available for consultation by everyone in the community, thus facilitating the

The asset can have several flags:

  • No Flag = All OK with the Token.

  • OK = Token verified and everything OK with the Token.

  • ALERT = Something abnormal was identified (infringed some of the rules) and needs to be reviewed to be reclassified.

  • SCAM = It has been alerted and is identified as a scam.

    [IMPACT] Please describe how your proposed solution will address the Challenge that you have submitted it in.

We will develop documentation and present it to the community. After reviewing, suggesting improvements, we will deliver a finalized documentation, with the processes of inclusion and review of assets and the functioning of the bots capable of mapping and monitoring possible irregularities.

  • We will create a public repository on github.
  • We will modify our bots to interact with this repository, including the tokens with the alert flag for review.

We will have a team dedicated to solving possible problems and for a period of 6 months. (included in cost)

[IMPACT] What are the main risks that could prevent you from delivering the project successfully and please explain how you will mitigate each risk?

The main risk is not in the development of the project, but in the adoption of the shared database by the developer community.

The minimization of this risk will be to have transparency in the creation and maintenance of this bank, as well as in the wealth of data.

[FEASIBILITY] Please provide a detailed plan, including timeline and key milestones for delivering your proposal.

  • Integration of the team that will develop.

  • Creation of documentation with the processes.

  • Creation of documentation with data architecture standards.

  • Creating the repository on github

  • Inclusion of the integration manual

  • Adaptation of current bots to run and interact with the github repository.

  • feedback report on the performance and growth of this database.

    [FEASIBILITY] Please provide a detailed budget breakdown.

We are thinking of 4 stages divided into 2 stages:

  • First stage ( Planning, Development and Implementation ) - We will have 3 people involved. The project leader and 2 programmers. It should take 2-3 months to complete and will cost $15,000.

  • Second stage ( Maintenance and Analisys ) - We will have 1 people full time. will run for 6 months after delivery of the first phase and will cost $6,000.

    [FEASIBILITY] Please provide details of the people who will work on the project.

For development we will have 1 project leader and 2 developers.

Once implemented, we will have 1 developer responsible for maintaining, approving, generating reports and insights for the community.

As it is a project that we are very interested in incorporating into beerhouse.io, we must use the project's internal developers, not having to hire an exclusive contract for this development

[FEASIBILITY] If you are funded, will you return to Catalyst in a later round for further funding? Please explain why / why not.

No. For this project we will probably not need further funding.

The current financing includes all development and a maintenance team for 6 months.

After this period, with the adoption and use by the community, the community itself should maintain it, without the need for other contributions.

[AUDITABILITY] Please describe what you will measure to track your project's progress, and how will you measure these?

The project is divided into 4 stages:

  • Planning
  • Development
  • Implementation and Maintenance
  • Improvements

Each step will be measured with the production of documents and in a qualitative way

[AUDITABILITY] What does success for this project look like?

Have a membership similar to https://github.com/cardano-foundation/cardano-token-registry, being a trusted database with an active developer community benefiting

[AUDITABILITY] Please provide information on whether this proposal is a continuation of a previously funded project in Catalyst or an entirely new one.

The project is brand new but can be incorporated into other projects. We even want to share this shared database in our developments.

Avis des conseillers communautaires (1)

Comments

close

Playlist

  • EP2: epoch_length

    Authored by: Darlington Kofa

    3 min 24 s
    Darlington Kofa
  • EP1: 'd' parameter

    Authored by: Darlington Kofa

    4 min 3 s
    Darlington Kofa
  • EP3: key_deposit

    Authored by: Darlington Kofa

    3 min 48 s
    Darlington Kofa
  • EP4: epoch_no

    Authored by: Darlington Kofa

    2 min 16 s
    Darlington Kofa
  • EP5: max_block_size

    Authored by: Darlington Kofa

    3 min 14 s
    Darlington Kofa
  • EP6: pool_deposit

    Authored by: Darlington Kofa

    3 min 19 s
    Darlington Kofa
  • EP7: max_tx_size

    Authored by: Darlington Kofa

    4 min 59 s
    Darlington Kofa
0:00
/
~0:00