Attributes
- Author(s): @beezy
- Parameter: Maximum Chains
- Current Value: 15
- New Value: 30
Summary
Currently , the maximum amount of chains a node is allowed to stake for servicing is limited to 15. This causes the operator to have to pick and choose the chains they will support usually based upon the ones that have been getting the most relays.
In order to help facilitate the teams goal of 100 chains by the end of 2023, each servicer will need to be able to support new chains as they are onboarded. I propose increasing the MaximumChains parameter to 30 (arbitrary wanted to open to discussion on the optimal setting for this to ensure steady growth and service availability to new chain partnerships). Increasing this will help keep idle nodes busy, move towards the goal of onboarding more chains and allow increased flexibility to node runners.
Abstract
The MaximumChains parameter is pretty straightforward and is defined as The amount of chains a node can be configured for in one stake.
Motivation
While adding backends supporting Moonriver and Moonbeam earlier this week; I also added BSC backends for our nodes. Today when trying to stake BSC; I received the error “Too Many Chains” thus having to remove Goerli from our stake list and adding BSC.
With rewards and relays decreasing due to market conditions, WAGMI and other factors I chose to stake BSC in place of Goerli due to the ever increasing relay count for the chain in comparison to Goerli. Also because I had to in order to support more chains.
Rationale
I chose double the default value as a starting point and to open discussion on what this should be configured to. I think 30 will help give people more options of investigating, deploying and staking new chains on the network for a few months and it can be revisited as Triforce and general demand continue to grow. This proposal will benefit more engaged runners that are looking to diversify their servicing portfolio and aligns the incentive more towards providing diverse relay infrastructure rather than stacking pocket nodes.
There are currently 5941 staked nodes servicing less than 10 chains, 8949 servicing less than 13 chains and 22448 currently at 15 MaximumChains staked.
Dissenting Opinions
1.) We are trying to reduce overall infrastructure costs for node runners now and this is the opposite of our near term goals.
- Yes. This would increase costs of node runners as they scale into new chains and technologies. It will also give them they ability to directly weigh the cost vs benefit of supporting different chains., Thus replacing other chains they no longer wish to support on existing hardware. While short term it will increase node runners cost(voluntarily by adding more chains) in the long term it aligns with the teams goals.
2.) This proposal exaggerates the economies of scale that larger node providers enjoy.
- While this could increase cost of larger node providers; it would be their own decision whether it was economically viable to expand their current relay offerings. This could also allow smaller runners a better chance to pick up more relays to stay competitive and diversify. Providers and runners do not have to stake more than 15 chains, this would just give them the option to.
Analyst(s)
N / A
Copyright
Copyright and related rights waived via CC0.