make-software / casper-account-info-standard Goto Github PK

Summary

The proposal is to expand the type - i.e., the entity type array in the Casper Account Info. Standard Schema Specification.
Please find below the proposed new additions to the existing type array;

["bridge", "cloud-storage", "collectable", "defi", "education", "explorer", "game", "gateway", "launchpad", "marketplace", "nft", "on-ramp", "off-ramp", "oracles", "partner", "sdk", "staking", "tool", "wallet", "software-house", "marketing-agency", "security"]

Motivation

We would like to utilize Casper Account Info. Standard to introduce a self-certification process on Casperecosystem.io. Casperecosystem.io is the Casper Association's official Casper Ecosystem website, which hosts information about projects and providers. It serves as the definitive source of truth for the Casper community to understand the projects and providers working on the Casper Network.

Currently, project and provider data are listed based on a curated list maintained by the Casper Ecosystem. We recently launched a self-service portal for new projects/providers to add their entries to Casperecosystem.io. To ensure the accuracy and integrity of the data submitted to Casperecosystem.io, we are introducing a self-certification process.

This process will function as outlined in the process flow below. In brief, projects and/or providers will be encouraged to self-certify their data. The self-certification will leverage the Casper Account Info. Standard, requiring projects/providers to complete the Casper Account Info. Standard process.

Upon completion of their Casper Account Info. Standard, the Casperecosystem.io backend will query the Casper Account Info Standard API endpoint using the project's/provider's account hash. Based on the API response, their entry on Casperecosystem.io will be categorized as Self-certified

Please refer to the process flow diagram here for more details.

Guide-level explanation

Upon approval and implementation of this proposal, the type field in the Casper Account Info. Standard Schema Specification will be expanded to include a broader array of entity types. This expansion is designed to accommodate a wider variety of projects and providers within the Casper ecosystem, particularly those that are emerging or have specialized functions.

Examples:

• A new project categorized under cloud-storage can register itself on Casperecosystem.io and complete the self-certification process by providing detailed information according to the Casper Account Info. Standard.
• An sdk developer can use the standardized form to ensure all necessary details are provided for better clarity and transparency for community members accessing the ecosystem website.
• Once a game developer submits their certification, their entry on Casperecosystem.io will be tagged as Self-certified, providing users with confidence in the legitimacy and self-validated status of the project.

Reference-level explanation

The proposal involves adding the following new entity types to the type array in the Casper Account Info Standard Schema Specification: ["bridge", "cloud-storage", "collectable", "defi", "education", "explorer", "game", "gateway", "launchpad", "marketplace", "nft", "on-ramp", "off-ramp", "oracles", "partner", "sdk", "staking", "tool", "wallet", "software-house", "marketing-agency", "security"].

Detailed Explanation:

• API Interaction: Upon completion of the Casper Account Info. Standard form by a project or provider, Casperecosystem.io's backend will automatically query the Casper Account Info Standard API using the provided account hash. The response will confirm the entity type and categorize the entry accordingly on the website.
• UI Updates: The user interface on Casperecosystem.io will display a new badge or marker indicating that an entry is Self-certified, enhancing the visibility and perceived credibility of self-certified projects or providers.

Example Case Study:

A provider categorized under security submits their standard form through the self-service portal. The backend processes this data and updates the listing on Casperecosystem.io with a Self-certified tag once the API validation is complete.

Drawbacks

The primary drawback of expanding the type array could be the complexity and potential confusion arising from the broad range of categories. Users and new entrants might find it challenging to select the appropriate category or might misuse categories due to overlapping characteristics between them.

Rationale and alternatives

Rationale: The expansion of the type array is designed to reflect the growing diversity and specialization within the Casper ecosystem. This change aims to provide a more granular and precise classification of projects and providers, enhancing the ecosystem's structure and navigability.

Alternatives Considered: One alternative could have been to keep a more generalized set of categories and rely on tags or keywords for further specification. However, this approach was not chosen due to the lack of formal structure and potential for inconsistency in tagging.

Impact of Not Doing This: Not implementing this proposal could result in a less organized ecosystem, making it harder for community members to find relevant projects or providers. It may also slow down the adoption of the Casper platform by new and innovative projects that do not feel adequately represented.

Unresolved questions

• How will we handle cases where a project or provider feels that none of the available type categories accurately represent their operation?
• What measures will be put in place to prevent the misuse of the type category during the self-certification process?

Future possibilities

• Future enhancements might include the introduction of sub-categories or additional layers of categorization to accommodate even more specific types of projects and providers.
• Another possibility could be the integration of AI-driven tools to assist projects and providers in selecting the most appropriate categories based on their inputs during the self-certification process.