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

Adding new dashboards to the TON Stat service #779

Open
3 of 18 tasks
seriybeliy11 opened this issue Aug 31, 2024 · 0 comments
Open
3 of 18 tasks

Adding new dashboards to the TON Stat service #779

seriybeliy11 opened this issue Aug 31, 2024 · 0 comments
Labels

Comments

@seriybeliy11
Copy link
Contributor

seriybeliy11 commented Aug 31, 2024

Summary

There is a great service for visualization and analytics of key metrics on our blockchain: https://tonstat.com/

We would like to add the following components:

  • 1. Average Transaction Confirmation Time: The time it takes for a transaction to be confirmed on the network.
  • 2. Average Transaction Size: The average size of transactions on the network.
  • 3. Number of Unique Addresses Participating in Transactions: The number of unique addresses that sent or received transactions.
  • 4. Token Distribution: Information on how tokens are distributed among different wallets (e.g. number of whales, small holders, etc.).
  • 5. Average Transaction Fee: The average fee charged per transaction.
  • 6. Number of Smart Contracts: The total number of deployed smart contracts on the network.
  • 7. Number of Active Smart Contracts: The number of smart contracts that are actively being used.
  • 8. Daily Gas Used: The total amount of gas used per day to execute transactions and smart contracts.
  • 9. Average Gas Per Transaction: The average amount of gas used to execute one transaction.
  • 10. Transactions Rejected Due to Insufficient Gas: The number of transactions that were rejected due to insufficient gas.
  • 11. Transactions Rejected Due to Other Reasons: The number of transactions that were rejected due to other reasons (e.g. insufficient funds, smart contract errors, etc.).
  • 12. Number of transactions between different types of wallets: Information on how many transactions are taking place between different types of wallets (e.g. between user wallets, between user and smart contracts, etc.).
  • 13. Number of DeFi-related transactions: The number of transactions related to DeFi protocols.
  • 14. Number of NFT-related transactions: The number of transactions related to NFTs.
  • 15. Number of DNS-related transactions: The number of transactions related to TON DNS.
  • 16. Number of liquid staking-related transactions: The number of transactions related to liquid staking.
  • 17. Number of validator-related transactions: The number of transactions related to validators.
  • 18. Number of transactions related to other asset types: The number of transactions related to other asset types (e.g. tokens issued on the TON platform).

Context

The metrics we offer allow you to dive deeper into our monitoring and provide accessible, fast, deep and open analytics.

Learning goals

This information provides a more complete and detailed picture of the health and activity of the TON Blockchain network. Here's what each of the above points gives us:

  1. Average Transaction Confirmation Time:
  • Performance Metric: Allows us to evaluate the speed and efficiency of the network.
  • User Experience: Important for users who want to know how quickly their transactions will be confirmed.
  1. Average Transaction Size:
  • Activity Analysis: Helps us understand what types of transactions are prevalent on the network (small or large).
  • Economic Trends: Can indicate economic trends and user behavior.
  1. Number of Unique Addresses Participating in Transactions:
  • User Activity: Shows how many unique users are actively using the network.
  • User Growth and Retention: Important for assessing user growth and retention.
  1. Token Distribution:
  • Token Concentration: Helps to understand how tokens are distributed among users (e.g. number of whales and small holders).
  • Risks and Stability: Important for assessing the risks and stability of the network.
  1. Average Transaction Fee:
  • Network Economics: Shows how much users pay on average for transactions.
  • Competitiveness: Important for comparing with other blockchains and assessing competitiveness.
  1. Number of Smart Contracts:
  • Ecosystem Development: Shows how many smart contracts are deployed on the network.
  • Innovation and Usage: Important for assessing the level of innovation and usage of smart contracts.
  1. Number of Active Smart Contracts:
  • Real Usage: Shows how many smart contracts are actively used.
  • Efficiency: Important for assessing the efficiency and real-world usage of smart contracts.
  1. Gas Used Per Day:
  • Network Activity: Shows the total amount of gas used per day.
  • Performance: Important for assessing network performance and activity.
  1. Average Gas Per Transaction:
  • Transaction Efficiency: Shows how much gas is used on average per transaction.
  • Optimization: Important for optimizing and improving transaction efficiency.
  1. Transactions Rejected Due to Insufficient Gas:
  • Gas Issues: Shows how many transactions were rejected due to insufficient gas.
  • Optimization: Important for optimizing and improving user experience.
  1. Number of transactions rejected due to other reasons:
  • Errors and issues: Shows how many transactions are rejected due to other reasons (e.g. insufficient funds, errors in smart contracts, etc.).
  • System improvement: Important for identifying and fixing problems in the system.
  1. Number of transactions between different types of wallets:
  • Transaction types: Shows how many transactions are happening between different types of wallets.
  • Activity analysis: Important for analyzing user activity and behavior.
  1. Number of DeFi-related transactions:
  • DeFi activity: Shows how many transactions are related to DeFi protocols.
  • DeFi development: Important for assessing the development and activity in the decentralized finance sector.
  1. NFT Transactions:
  • NFT Activity: Shows how many transactions are related to NFTs.
  • NFT Development: Important for assessing the development and activity in the non-fungible token sector.
  1. DNS Transactions:
  • DNS Activity: Shows how many transactions are related to TON DNS.
  • DNS Development: Important for assessing the development and activity in the decentralized domain name sector.
  1. Liquid Staking Transactions:
  • Staking Activity: Shows how many transactions are related to liquid staking.
  • Staking Development: Important for assessing the development and activity in the liquid staking sector.
  1. Number of transactions associated with validators:
  • Validator activity: Shows how many transactions are associated with validators.
  • Validation development: Important for assessing the development and activity in the validation sector.
  1. Number of transactions associated with other types of assets:
  • Other asset activity: Shows how many transactions are associated with other types of assets (e.g. tokens issued on the TON platform).
  • Ecosystem development: Important for assessing the development and activity in other sectors of the TON ecosystem.

This data provides a more complete and detailed picture of the health and activity of the TON Blockchain network, which helps in making informed decisions and improving the user experience.

References

My team already had experience creating similar dashboards: https://github.com/seriybeliy11/Grants-Bounty-Tracker

Therefore, we ask you to select the most important additions and assign us as executors

Stack:

  • Next.js
  • Tremor Framework React

We will present our solution in the form of sets of components with programs for collecting and sorting data. Thanks for your attention!

Estimate suggested reward

1700-3000 USD (solid price after agreement)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant