Skip to content

Optimize Chain State Query Logic: Switch from User Dimension to Token Dimension #49

Description

@sssning121

Expected Behavior

The optimized Chain state query logic should perform queries based on the Token dimension to provide more precise state information related to Tokens, rather than relying on the user dimension.

Specifications

As a developer, I want to optimize the Chain state query logic by switching from a user-based dimension to a Token-based dimension. This will improve query efficiency and make the results more targeted.

Features:

  1. Modify the existing query logic to use the Token dimension for Chain state queries.
  2. Ensure the query results include Chain state information related to each Token, rather than focusing on user-related states.

Development Tasks:

  • Modify the Chain state query interface to switch from user dimension to Token dimension.
  • Update database queries or data storage logic to support Token dimension queries.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions