Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reactflow Graph - AutoScaling when loaded #9

Open
ArinNigam opened this issue Oct 2, 2024 · 0 comments · Fixed by #8
Open

Reactflow Graph - AutoScaling when loaded #9

ArinNigam opened this issue Oct 2, 2024 · 0 comments · Fixed by #8

Comments

@ArinNigam
Copy link

Description:

We need to enhance the existing React Flow graph visualization to better track and display user transactions on the Solana blockchain. The goal is to provide a clear and intuitive way to represent payments sent and received between users, offering insights into the flow of funds between different wallets/contracts.

image

Auto-Scaling and Positioning:

  • Ensure the graph auto-scales and centers when loaded, displaying all users and transactions clearly, regardless of the number of users or transactions.

Some changes that can be made

  1. Introduce a Balanced or Hybrid Node Color:
    Create a third color (e.g., yellow or blue) to represent users who both send and receive payments.
  • Red: Primarily a sender (sends more than they receive).
  • Green: Primarily a receiver (receives more than they send).
  • Yellow/Blue: Balanced or hybrid, where the user both sends and receives a similar amount of transactions.
  1. Transaction Volume-Based Coloration:
    Instead of a binary classification (either red or green), calculate the transaction volume ratio of sent to received payments and adjust the color of the node accordingly:
    Example:
  • If the user sends more than 70% of their total transactions, they remain red.
  • If they receive more than 70%, they are green.
  • If the sent/received ratio is roughly balanced (within a 30-70% range), the node can be marked yellow.
@tanish35 tanish35 linked a pull request Oct 2, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants