WCT Series (IX): Evaluation Framework for Service Node Performance Metrics

The performance of WalletConnect network's service nodes directly determines the efficiency and user experience of the entire system. The evaluation framework mainly revolves around two core metrics: uptime and latency. Uptime (Ui) is the proportion of time the node is online, calculated as total runtime divided by the evaluation period; latency (Li) is the average response time, calculated as the sum of all request responses divided by the number of requests. Combining these two, a weighted formula calculates the performance coefficient U(i,t): Performance = (Wu · Ui) · (Wl · Li), where Wu and Wl are weights, adjustable according to network needs.

Why such detail? Because the network, transitioning from permissioned to permissionless, needs reliable verification. In the initial phase (Phase 1), trusted nodes are used as 'oracles' to measure performance; in the later phase (Phase 2), all nodes ping each other and report. Node status is also linked to performance: active nodes processing requests must maintain a high score; if the score drops, they enter confinement, returning to reserved status after 24 hours. Reserved nodes are backups, ready to take over; standby nodes must have machines ready, or they will be deactivated.

This framework not only measures, but also incentivizes. High performance yields greater reward bonuses; low performance triggers penalty mechanisms. Consider that the target total number of nodes is 21 (15 active + 6 reserved), creating intense competition, driving everyone to optimize hardware and software. On the user side? Wallet performance is also tiered: only wallets with over 100,000 connection signatures are eligible for rewards. Certified wallets can also participate in a larger pool, with non-linear allocation, rewarding better performance with more. This evaluation makes the network more resilient, avoiding single points of failure. In the long run, it encourages developers to continuously iterate, ensuring the efficient operation of the WCT ecosystem.

#WalletConnect @WalletConnect $WCT