Node Performance
Introduction
Skilled Node Operators who don't individually have enough $RUNE to run a node themselves can use the Bond Provider feature to bootstrap bond from other $RUNE holders. Or several nodes can pool together as a single node to maximise their payouts.
Node Operators can define up to 6 THOR addresses as bond providers. These addresses will be able to Bond and Unbond to the node, and earn rewards based on the amount of bond they contribute. Node Operators take a fixed fee of 2000 basis points (20%) on all rewards from the Bond Providers' bond. In the future this fee may be configurable per node. Link
Method
In the current dashboard I tried to find the the transactions count and sum of Slash point to classic and pooled pools, also count the node addresses for each of them by use of lipside_prod_db.thorchain.bond_events table and the hint on here as mentioned in bounty’s question.
:telescope: Findings:
The following charts begin in March 2022, which is when pooled validators were first deployed to THORchain.
Classic validators consistently have a larger number of active nodes than Pooled validators.
In the middle of March of 2022, a record high number of THORChain nodes were online.
Pooled validators are growing in popularity while traditional validators are on the decline.
There were 178.9k less points on the 15th of November, 2021. The months of April and May of 2022 also feature significant increases.
May 9, 2022 saw the most daily reduction in points for Pooled validators (93.8K).
✍🏻 Conclusion
- Classic Validators have a greater total and average slash score than Pooled Validators.
- The number of transactions using pooled validators has increased on THORChain, while the number using traditional validators has decreased.
- There are more nodes with high scores in the Classic validator than in the Pooled validator.
About:
-
Author: HaM☰d
\
-
Discord: 0xHaM☰d#8391
\
-
Twitter: @arjmandi_hamed
\
-
Email: h_arjmandi2012@yahoo.com
Add Text Here
What is the performance of pooled validators re: slashes and slash points v. classic validator ops? (possibly implies newer people entering the playing field?)
\n
Hint: Use the memo from thorchain.bond_events and thorchain.slash_points
Hey there 👋!
Firstly, I appreciate you sticking with it until the conclusion.
I'm Hamed, a civil engineering Ph.D.
student interested in data analysis.
I've made many similar dashboards and visualizations since I started at Flipside in January.
Please take a look at my various contact details and let me know what you think.
:telescope: Findings:
Above, we have PIE charts that break down node kinds by transaction volume and Slash point value.
More than 35% of the nodes in the state are ready to go at any time, while another 33.4% are in standby, 31.2% are now active, and fewer than 0.5% are disabled. A similar development was depicted in the right bar chart.
As can be seen on the left graph, the bulk of both validators' nodes are located between 1,000 and 5,000 Slash.
Classic validators, in contrast to Pooled validators, have a higher concentration of nodes with high slash points (over 20,000).
\
:telescope: Findings:
Based on the above charts, number of nodes in Classic validators is way more than the nodes in Pooled validators. So, its obvious that the count of transactions and total slash point of classic validators nodes (2.57M) is also way more than pooled ones (282.708k).
The right side bubble chart shows the slash point against transactions count, and can be seen that when transactions count increased more than 50 the congestion was disappeared.
On the following charts, we can see also the Average/Median/Max/Min slash point of a node in Classic validators (191.8k) is more than average slash point of nodes in Pooled validators (114.2) but in other metrics like Median/Max/Min slash point of a node in Pooled validators is more than average slash point of nodes in Classic.