Analysis and Proposals on dYdX Chain and DYDX Tokenomics: Reduce the active set from 60 to 30 validators

[nethermind]

Introduction

Since the genesis of dYdX Chain on October 26, 2023, dYdX Chain has generated $232B in trading volume and distributed $39M in USDC to dYdX Chain validators and stakers.

On August 12, 2024, dYdX Trading announced the dYdX Unlimited software featuring significant improvements to the dYdX Chain open-source software, such as permissionless market listings, MegaVault, the potential for revenue sharing, and an Affiliate Program, among other things.

Despite product achievements, the DYDX token has been facing challenges due to high inflation and a significant amount of token unlocks. We believe that dYdX Unlimited presents a unique opportunity to optimize dYdX Chain and DYDX tokenomics for the protocol’s long-term viability and success. Our proposals aim to (1) improve liquidity on dYdX Chain markets, (2) increase the attractiveness of the DYDX token, and (3) encourage holding and staking DYDX, all with a view to increasing the security of the dYdX Chain and driving sustainable growth in the dYdX ecosystem.

To achieve this goal, we recommend implementing revenue sharing, enhancing DYDX token utility, and reducing DYDX emissions, all while supporting the immediate growth requirements of the dYdX Chain. Implementing these changes will significantly enhance dYdX’s competitiveness and reduce DYDX inflation. This will turn the DYDX token into a more robust asset, therefore benefiting the overall security and resiliency of the network.

We published our Analysis and Proposals on dYdX Chain and DYDX Tokenomics on the dYdX Forum on 22nd October 2024 which has garnered constructive participation and discussions.

Our extensive analysis of the proposal can be found in our research report.

Based on the community’s feedback, we are splitting up the proposals based on subject matter. The four separate proposals (and threads) are as follows:

1. Reduce the Trading Rewards “C” constant from 0.90 to 0.5.
2. Protocol Revenue Distribution:
   a. 50% of all protocol revenue routed to the MegaVault.
   b. 10% of all protocol revenue routed to the Treasury subDAO.
   c. Recommendation that above an $80M level of annual protocol revenue, the Treasury subDAO could consider a Buy & Stake program.
3. Reduce the active set from 60 to 30 validators.
4. Cease support for the wethDYDX Smart Contract (i.e., the Bridge) on the dYdX Chain side.

Summary of Recommendations

1. Reduce the active set from 60 to 30 validators.

Reduce the active set from 60 to 30 validators

The current active validator set on the dYdX Chain consists of 60 validators. At the current fee level, over 17 active validators are unprofitable after accounting for a fixed infrastructure cost of $1,000 per month at their respective commission rates. The proposed MegaVault and dYdX Treasury subDAO revenue shares would further reduce staking yields and, therefore, the funding validators receive from their respective commission, exacerbating unprofitability.

Of the total revenue, 50% is allocated to MegaVault and 10% to the Treasury subDAO. At current commission rates, in a set of 60 validators, 34 would incur losses, while in a 45-validator set, 19 would remain unprofitable. Meanwhile, increasing validator commission to boost profitability would lower staking APR. This could potentially encourage unbonding while discouraging staking. The equilibrium bonded ratio to achieve the current staking APR would decline and thus, impact dYdX Chain security.

We proposed reducing the active validator set from 60 to 30, ensuring that all validators in the active set have a chance to remain profitable after accounting for MegaVault and Treasury subDAO revenue shares at current commission rates. We have conducted a thorough analysis of the proposals. For more details, please refer to our research report.

@nethermind

3. Network performance and reducing the active set from 60 to 30 validators

We appreciate that validators could decide to operate at a loss with the hope that volume and revenue increase on dYdX Chain, but we think it is in the best interest of the dYdX ecosystem to reduce the active set.

The proposed reduction of the active validator set from 60 to 30 takes into account the impact on validator profitability, assuming the approval of a 50% revenue share towards MegaVault and 10% towards the Treasury subDAO. At the time of the analysis, 17 validators were unprofitable with 100% of protocol revenue directed to stakers and validators, assuming a fixed infrastructure cost of $1,000/month (which, again, we acknowledge may not be representative in all cases but, in our opinion, serves as a good proxy). With the proposed revenue share, over 34 (of 60) validators could face unprofitability, accounting for 57% of the active validators. This concern has been raised by comments suggesting that some validators have been operating at a loss since the genesis of dYdX Chain. Validator financial health is important to the chain’s security and overall success.

We do not think there are significant impacts on validator network decentralisation from reducing the active set by 50%. The top 30 validators have been delegated 86% of the total stake, with the top 4 accounting for 36%. The report notes that the Nakamoto Coefficient would remain at 4, and the HHI would increase slightly to 552 if the active set reduction is implemented. We strongly advocate for decentralization, and recommend the community adopt a delegation policy framework that encourages a more even distribution of stake, particularly supporting validators with lower delegations. Additionally, we propose reassessing the active validator set in the future, potentially increasing it once dYdX Chain achieves sufficient unincentivized volume. This should occur alongside the stabilization of DYDX price and the bootstrapping of new initiatives, which could allow for a reduction in the revenue share allocated towards them.

This proposal emphasizes the importance of maintaining a lean, agile, financially healthy validator set to ensure dYdX Chain’s security, leaving the final decision to the community.

Additionally, reducing the active validator set could improve network performance. We have not done any technical analysis, but we assume that decreasing the active set will result in less network traffic.

Community feedback indicated strong interest in exploring potential latency and performance improvements from reducing the validator set.

@nethermind

We appreciate all the feedback and acknowledge that our initial research focused on validator profitability, which was an issue raised by validators while discussing the Treasury subDAO proposal. It’s clear there’s also interest in discussing the potential latency improvements from reducing the active validator set from 60 to 30 on the dYdX Chain. Beyond profitability, we believe this reduction could drive meaningful improvements to the speed and reliability of dYdX Chain for the following reasons:

Network Efficiency: A larger validator set requires messages (like new orders) to travel farther across the network, often in multiple steps to reach all validators. This can slow down the network and introduce unpredictability. By reducing the validator count, messages can take more direct routes, minimising delays and enhancing both speed and reliability.

Faster Order Processing: For a competitive trading platform, rapid order processing is essential. Fewer validators mean fewer steps for orders to reach the proposer, which results in faster and more consistent processing times, improving the overall user experience to more closely match centralised exchanges (CEXs).

Faster Consensus: Fewer validators means fewer number of prevotes/precommits required for consensus to reach finality.

Node Location: Several validators have suggested that prioritising validators operating within Japan would be the most effective way to reduce latency. While we agree that this could improve latency, validator node location should not be seen as an alternative to the current proposal. Rather, validator node location and reducing the active set should be seen as two levers that the dYdX community could leverage to improve speed and reliability of dYdX Chain. We strongly encourage all dYdX Chain validators to align with the MEV committee’s guidelines and urge ecosystem participants to consider node location when choosing validators to stake to.

We believe a smaller validator set would enable a faster, high-quality trading experience, and maintain sufficient decentralization for the security of the dYdX Chain, while improving the financial health of the chain. Given that our proposal does not include the technical analysis around latency and focuses on the economics of the chain, we invite any technical teams without a direct stake in this proposal to share their perspectives and insights.

This was followed by valuable community input, highlighted below.

@eguegu

About the Validator Set

• Reducing the number of validators to 30 could alleviate the load on consensus mechanisms, thereby enhancing the UX for traders. Hyperliquid achieves its superior UX by operating with just 4 validators. Currently, there is virtually no demand from traders for greater decentralization, so this suggestion is intriguing in terms of improving product quality.
• However, it’s also important to recognize that this perspective largely aligns with the interests of the top 30 validators, so the community should consider this proposal with a balanced and careful approach.

@Cosmic_Validator

Secondly about @eguegu mention of consensus. dYdX already recommended Tokyo as the infra location for best latency and hence best trader experience so if you really want to improve trader experience you should eliminate all the validators not based on Tokyo, not the ‘smaller 30 validators’. Also your comment ‘there is virtually no demand from traders for greater decentralization’, of course users don’t care about the underlying tech, it was dYdX team that decided to decentralized all components of dYdX including the orderbook and matching engine (first DEX to achieve this) and that’s why they migrated from v3 to v4

@RoboMcGobo

Validator Set Reduction

I’m very strongly in favor of reducing the validator set, but not for the reasons proposed here. There’s been a lot of commentary here about validator profitability, even by the proposers.

To me, this is less of an issue of profitability (as noted in the report, on most chains validators seem happy to run unprofitably) and more of a performance issue. dYdX is a trading platform that relies heavily on optimizing trade execution speed and low-latency. The biggest bottleneck on this right now is the time that it takes for validators to come to consensus.

If traders lose value because of latency, they won’t trade here. Reducing the set to 30 will reduce instances of this occurring. It truly is that simple.

Further, and as I’ve repeated on numerous occasions, large validator set sizes do not have a meaningful impact on overall decentralization.

Note: In the event that this does pass, Stride will also have to adjust its delegation program for dYdX and move delegations around. We’re already thinking through what this could look like and expect to have a plan out in the coming weeks (subject to this passing).

@cryptoplaza

Validator Set Reduction

As we mentioned in the analysis, we found the reasoning behind the profitability to be very weak, and the only reason we could identify was improving the user experience. If the project deems it necessary to enhance the user experience, then this is certainly a very appropriate measure. However, the downside is the increased centralization, which we agree may not be significant, as well as the impact on governance, since it will also reduce participation in forums like this by half, along with contributions from these token holders. Another additional impact is the loss of these stakeholders, as it is very likely that they will sell the tokens they had purchased to engage in the activity

@carlbergman

Improving execution with networking performance

Through our work with the MEV Committee, we have repeatedly identified issues of inefficient order gossiping resulting in orderbook discrepancies. Orders submitted by traders don’t reach the relevant block proposer in time, resulting in worse pricing, slower execution, or both. This isn’t due to any malicious activity, but a result of networking problems.

It’s worth noting that practically every validator has, at some point in time, displayed issues with discrepancy. Even under optimal configurations, validators display discrepancies. This leads us to believe the network simply isn’t efficient enough to process trading demand at the expected performance level.

By halving the validator count, we effectively halve the network topology for an order to reach the next block proposer. We reduce peering requirements, allowing for more direct routes among validators and trading nodes. Theoretically, the reduction should allow orders to gossip more efficiently through a leaner network, improving discrepancies.

As far as I know, the number of validators at launch was chosen arbitrarily. There is no research or justification for why 60 is an optimal number of active validators. Instead, we’re learning from experience now that 60 is probably a sub-optimal amount. Why should we stick with a number that isn’t working? Reducing this number is a reasonable experiment to improve execution, making dYdX a more competitive trading venue. Thankfully, this is something we can continue to adjust or revert over time based on future learnings.

Obviously, as mentioned in the thread, we risk losing a number of high quality validator teams contributing to the protocol. It’s not an easy decision to make, but dYdX has to perform better on execution if it wants to compete with other venues.

@shellvish

Reduction of the Validator Set

I can’t directly speak to the profitability of validators, and whether or not validators want to run unprofitably on networks. However, I can speak to the importance of having a highly performant chain.

Traders, particularly quantiative traders, have a ~limitless appetite for transaction throughput. On venues where they are offered the chance, traders will spend millions to optimize throughput on the order of nanoseconds (e.g. NYSE). dYdX contributors and validators have done a truly spectacular job at optimizing the dYdX chain - block times are down to ~1.1s running a fully decentralized network. This is done through many technical optimizations on the chain-level, as well as social coordination among validators to optimize the geographic placement of their nodes.

However, the reality is that other decentralized perp markets, like Hyperliquid, operate in a pseudo-centralized manner with few nodes that are tightly colocated. This allows them to give extremely strong guarantees to traders around trade execution, which drives much more liquidity and volume to the venue.

I’ve heard from multiple liquidity providers that dYdX performance is still below other markets. Unfortunately, dYdX is still compared to fully centralized venues like Binance, Coinbase, etc, as well as psuedo-centralized venues like Hyperliquid. Having even 1-5% of transactions fail or not get processed in time is enough to convince HFT firms to stop supporting dYdX.

I view this as a critical issue for dYdX, and should be the protocol’s top goal. Market makers offboarding from dYdX would be catastrophic.

The long-term viability of dYdX is fully dependent on attracting the most competitive and efficient liquidity providers. I fully believe that reducing the validator set can only improve the performance of the chain.

As other contributors have mentioned, validators already mostly colocate their nodes, and we would achieve large gains by improving the technical setup of a few underperforming validators. I fully agree with this, and I believe any delegations done by the dYdX protocol or the Treasury SubDAO should only delegate to highly performant validators. I don’t disagree with this view at all, and also view the underperformance of large validators as a critical issue.

However, it’s certainly true that fewer validators will lead to faster blocks. Fewer validators means less gossipping on the p2p layer, and fewer nodes needed to reach 2/3 consensus. Even in a world where all validators are located in the same room, fewer nodes will still directly lead to faster blocks.

Carl highlights some empirical data about this here - it is a fact that the current dYdX network has performance issues. We need to increase the tx throughput of the network, or we risk losing meaningful liquidity.

I am aware that this reduction would be painful, but I do strongly believe it’s necessary for the long-term competitiveness of dYdX. I believe that one of dYdX’s core goals should be optimizing tx throughput for liquidity providers, otherwise all validators will be negatively affected in the long-term.

@AutoStake

We are have plenty of scope to optimise block times further as is with 60 validators based close together like DYDX recommends

Check out Injective, they have 60 geographically distributed validators across the world amf are still able to achieve 0.6s block times

Happy to share the config changes necessary to achieve this.

@thecryptostakr

Latency: it is necessary to analyze how it is possible to reduce latency and prove with technical data the number of validators, location and quality, as well as what (if any) technical alternatives are necessary to achieve this objective; It is equally important, for the sake of transparency, to prove to the community what the effective arguments are for reducing the number of validators. While reducing latency of the DYDX chain and higher profitability (per validator) corresponding to a smaller group of validators are justifiable objectives (always keeping latency reduction as the main objective). On the other hand, a possible reduction in the group of validators with the sole objective of increasing the profitability of DYDX’s largest current valuers to the detriment of the rest is a purely and simply predatory positioning of large validators in relation to smaller ones. I insist that this issue must be clarified without any doubt within the community.

@ttt_vn

Hi dYdX Community!

I’m wondering why we don’t reduce the validator set gradually, for instance, by decreasing it from 60 to 50 and reducing the block time from 1 second to 0.6 seconds to see how much the network speed of the dYdX chain improves. If we suddenly reduce from 60 to 30 validators without lowering the block time, would it actually be faster? Do you have any in-depth reports on how much speed would realistically change? We would like to have an in-depth discussion about your statement that reducing the validator set would increase speed by a certain percentage. The options are to reduce the block time to 500 ms while keeping 60 validators, or to keep the block time at 1 second and reduce the validator set to 30.

@EarlMontagu

→ That being said, there are valid reasons to adopt a smaller validator set and they should be considered in their own merit. This is why I think the community should start a separate discussion about increasing the chain’s performance as there are alternative solutions worth exploring (mentioned above) before halving the Set.
Better performance and low latency should be a priority but it’s important to remember that we’ll always lag behind CEXs and ‘semi-decentralized’ DEXs as decentralization ( dYdX’s competitive advantage) comes with its trade-offs.

@magmar-skip

Hey all, Mag from Skip here.

I understand that reducing the validator set would have harmful effects - namely validators would get cut out of the active set. I’m not here to comment on that (it makes me sad), only to comment on the technical side after years of working deep within the Comet codebase.

Reducing the number of validators would definitely speed up dYdX. There is no honest technical argument to believe otherwise. Centralized systems are the fastest, and as a network approaches a centralized system, it will speed up. The reality is that the gossip factor of Comet-based data (e.g. txs, votes, blockparts) is extremely high, so any additional data gets flooded around the network multiple times. With dYdX especially, which uses Skip:Connect (and therefore circulates heavy Vote Extension packets), there is a ton of data on the gossip network. The more validators there are, the more gossip there is, as each validator regossips the data it receives. This can throttle a network by preventing votes, proposals, and blockparts from reaching the selected proposer, who will effectively wait for the network to catch up.

Cutting down the number of validators will reduce the amount of traffic in the gossip network, will reduce the number of validators required to vote on committing blocks/proposals, and will concentrate stake into the remaining validators that are not cut. This will improve network latency in a couple ways:

1. On average, there will be a lower minimum number of validators from which votes are required to reach the 2/3 threshold, and so blocks will progress faster
2. If the validators are colocated, the latency between each peer will be much smaller, effectively increasing the gossip throughput of the network.
3. There will be significantly less data in the gossip network overall.
4. There is significantly decreased chance that the proposer selected is a non-functioning validator (the risk of which increases as there are more validators)

Now, there are many other ways to reduce the latency / block time of a network, that are currently being worked on by the Informal team (and the Skip team) - including mempool performance improvements, reducing the size of vote extensions, direct peering amongst validators, etc. These are not ready, but will be helpful to achieve the same thing. This does not change the fact that decreasing the number of validators and colocating them will definitively lower blocktimes and latency - it’s just a technical reality.

@Callen_Wintermute

Lastly, we sympathise with a lot of the Validators that are affected by the reduction in the Validator set and think it would’ve been better to frame this reduction with the purpose of increasing performance as no one is forcing a Validator to join the network and it’s their decision to operate at a loss. If we are truly wanting to improve performance (which i think should be the number 1 priority) then the 50% cut likely makes sense, however, if it’s about validator profitability it could then make sense to initially reduce it down to 45 and assess if profitability improves

[kaenoru]

Hi! The reduction of trading rewards down to 0.5 will make service fees unfavourable compared to other exchanges with more stable API and better liquidity.

Thanks.

[Cosmic_Validator]

@nethermind

At the current fee level, over 17 active validators are unprofitable after accounting for a fixed infrastructure cost of $1,000 per month at their respective commission rates.

Your analysis about profitability and recommendation is based on very wrong costs assumptions, and many already asked you to stop discussing profitability as a reason to eliminate validators given your incorrect assumptions for the analysis:

Analysis and Proposals on dYdX Chain and DYDX Tokenomics

If the geolocation of dYdX validators was very globally decentralized as well as the institutional users of dYdX you could then talk about randomly choosing 30 validators to eliminate, which could be the bottom 30. However, and this is key, the majority of institutional users of dYdX are near the Tokyo area as well as a good number of validators. In this situation to improve performance you CAN’T just randomly pick 30 validators to eliminate like the bottom 30, you must identify which validator…

Analysis and Proposals on dYdX Chain and DYDX Tokenomics

Thank you for your reply. To be clear, I agree with the goal of shifting revenue allocation to liquidity and improving chain performance. It is the most important factor in attracting the platform’s key customers - retail traders, market makers and institutional investors. On the other hand, I also believe it is important to get the message right. Just as validator profit and loss estimates complicate the discussion, Claims and rationales need to be carefully constructed. Why I mentioned t…

Not only your assumptions are very incorrect, but you also overlooked the fact that you would actually make latency much worse if the bottom validators are mostly based in Japan while the top ones no.

@nethermind

Community feedback indicated strong interest in exploring potential latency and performance improvements from reducing the validator set.

You are also overlooking the Optimistic Execution in CometBFT v0.38 with ABCI++ that will be introduced in a few days in the next dYdX upgrade and that it will already improve latency by a lot:

[DRC] Proposal for dYdX Unlimited (v7.0.0 Protocol Upgrade)

@dYdX_Ops_subDAO do you have estimations about the latency improvement? This is great news since it would allow dYdX to greatly improve latency while maintaining its current decentralization, and if more validators move the infra to Tokyo the latency could be improved even further @magmar-skip @nethermind

@nethermind

This was followed by valuable community input, highlighted below.

To summarize:

Nethermind suggestion: Based on very incorrect costs assumptions with no supporting research/data/surveys we suggest to remove the bottom 30 validators for profitability concerns

Community suggestion:
-Nethermind costs assumptions are very incorrect, hence profitability cannot be used as an argument to remove the bottom 30 validators
-Nethermind missed the main point and advantage to reduce validators which is latency improvement
-Nethermind missed that in the next upgrade latency will already improve by a lot thanks to Optimistic Execution
-Nethermind missed that for latency, validators being based in Japan is the most important metric and that to maximize latency improvement we would need to remove the validators not based in Japan
-If Nethermind was suggesting to remove validators not based in Japan to improve latency this could make sense, but this was suggested by community members, not Nethermind in their report. However, Nethermind still insists in removing the bottom 30 validators which not only makes no sense given their incorrect costs assumptions to reach that conclusion, but this would actually damage latency since validators based outside Japan is not equal to the bottom 30 validators

[michael_ns]

This is my personal view (not as Nansen):

Not going to mince my words on this, this is a great proposal to alienate your community ahead of one of your biggest competitor’s mainnet launch.

The north star metric for improving chain performance is to reduce latency, and that can be achieved by having nodes in close proximity (Japan) or centralizing the Valset (reduction). I’m no researcher but the extreme Valset change should be plan of last resort because of the significant logistics and relationships involved (redelegations, shut off of validator operations for validators who supported DYDX at a loss since genesis, etc.). We should only be explore this after geographical latency is optimized, and certainly not at 50% reduction (start small, test, step up).

Also, I cannot emphasize enough that reducing the Valset will not help with the PA or tokenomics - that is just redistributing the same emissions over a smaller set of operators.

The top 30 validators are definitely (incentivized) to vote in line with this so I expect this proposal to pass.

[samwise]

I still do not see any hard evidence or simulation on what kind of performance gains we are talking about here in terms of consensus times when we cut the valset by half.

I guess the cartel wants to increase profitability because removing half the valset will mean that thousands of stakers currently staked in the 31-60 validators are going to be forced to re-allocate their stake to the top 30 - ironically these stakers are the ones being punished for supporting decentralized validators not in the top half.

@antonio decision to lay off 35% of dydx staff coupled with this kind of move towards centralization speaks volumes about the ecosystem here.

[AutoStake]

Just going to reiterate my thoughts

1. There is already plenty of scope to increase throughput if this is a desired metric, we should do this first.
   I should also mention the original proposal had nothing to do with this metric, but was instead solely about imposing an economic business decision on validators.

2. It would be a massive fumble to have less validators than hyperliquid (39 on testnet as of right now)
   it would be embarrassing for dydx to suddenly be more centralised than hyperliquid.

[samwise]

Someone please enlighten me on why are we taking suggestions and proposals from @nethermind seriously when their report uses terms like inflationary staking rewards? And killing half of the chain’s infrastructure service providers?

[AutoStake]

There has been lack of communication around the concerns, and then trying to spin off it off from an economic decision to a performance suggestion, and then again ignoring all those suggestions (to how we can improve with simple configs changes).

Additionally Hyperliquid now has 41 validators…

[eguegu]

From a performance standpoint, reducing the number of validators to provide traders with a better experience is a logical approach.

However, failing to clearly justify the choice of 30 validators may lead to conflicts within the community.

I believe it would be more prudent to gradually reduce the number of validators—progressing from 60 to 50, then to 40, and so forth—by establishing a clear timeline. This would allow for a balanced assessment of performance improvements at each stage.

[Cosmic_Validator]

Following up on this @nethermind, you admit that originally you suggested to reduce the bottom 30 validators solely because of profitability concerns but the $1k monthly costs you assumed is very incorrect which invalidates your suggestion, please confirm this and remove/cancel already this original incorrect suggestion.

The latency improvement suggestion was not done by you, but by us, the community. And the latency has already been improved by a lot in the latest upgrade with Optimistic Execution, as you see below.

[DRC] Proposal for dYdX Unlimited (v7.0.0 Protocol Upgrade)

Hi @Cosmic_Validator, Indeed, Optimistic Execution (OE) was specifically introduced to reduce block latency. In a production-like environment, enabling OE has demonstrated a reduction in block execution time of approximately 70%. We highly recommend enabling this feature. For more information, please refer to the v7.0.0 Release Notes and this article on Optimistic Execution. Cheers,

To further improve latency, validators should be running from Japan/Tokyo. We would need to identify those validators not running from Tokyo (which are NOT the bottom 30) and target those specifically. Removing the bottom 30 validators was incorrectly suggested originally for your incorrect profitability analysis, it has nothing to do with latency. Extrapolating this bottom 30 validators for the latency argument makes no sense, because it is not like the top 30 are running from Japan and the bottom 30 no.

In summary: removing the bottom 30 validators for profitability concerns should be confirmed to be removed/cancelled by Nethermind since this was based on incorrect costs assumptions. Suggesting to remove the bottom 30 for latency improvement should also be cancelled because the validators not running from Japan is NOT equal to the bottom 30 validators. The only suggestion that could make any sense, made by the community, not Nethermind, is to identify the validators not running from Japan and either ask them to migrate to Japan for latency improvement and those not migrating could be removed

Moreover, what it is mentioned above it is very serious, recently both @karpatkey and @stride based their delegations decisions mostly on the assumed ‘top 30’ remaining validators assuming this proposal goes on-chain. This is serious for the following reasons:

-After the delegations from Karpatkey and Stride, the voting power is even more centralized and concentrated in the top 30, meaning even easier than before for the proposal to pass if the top 30 vote yes, which of course they will do to eliminate half of their competition, whether the arguments for the removal are flawed or not

-Even if Karpatkey and Stride don’t vote, now there is an even bigger bias by the top 30 validators to vote yes to remove the bottom 30 as to ‘align’ with what Stride and Karpatkey decided the top 30 to be

-Stride was the only supporter of the validator reduction together with Reverie, it seems a potential conflict of interest that they used their DYDX to further encourage their views by ‘pre-selecting’ a top 30 validator group and assuming and suggesting it is because this proposal could go ‘soon’ on-chain and might be approved

-They have centralized the stake so much that now the top 30 has almost 88% of the DYDX staked. This goes against the mission of both entities which is to delegate to increase the decentralization and security of dYdX, rather than the opposite, to centralize it even more

-They have created an artifical gap between the validator 30th and 31st, now not only they have greatly concentrated and centralized the stake in the top 30, but they also created a gap of around 1.5M DYDX between the validators 30th, and 31st. You can see that above 30th the DYDX increases smoothly, and below 31st also decreases smoothly, but between validators 30th and 31st there is a large artificial 1.5M DYDX gap

Validators have been since before v4 genesis supporting so much, trying to attract delegators. Now an entity comes with some flawed arguments to remove half of the validator set. And other entities with large DYDX allocations supposed to increase the decentralization and security of DYDX collude in a centralized way about who to ‘save’ and who to ‘eliminate’. Actually, this could be a potential attack vector for dYdX, a malicious actor could try in this way to keep centralizing the stake and eliminating validators, and then it would be easy to do a 1/3 attack to halt the dYdX Chain or even just take over the chain with a 2/3 attack. The whole point of dYdX v4 was about decentralization, 60 validators was already not too decentralized compared to most PoS networks, but now it is quite concerning concentrating so much the stake in 30 validators, putting the chain at higher risk and lowering a lot the security because of some ‘flawed proposal being discussed in the forum’. If this goes through, then nothing stops the process to be repeated and the stake centralizing even more and the security of the dYdX getting lower and lower. For the integrity of the dYdX chain and its security in the long term it is urgently needed to clarify all the above and put the situation in order

[samwise]

How much was @nethermind paid to produce a flawed report with “inflationary” staking rewards, and large parts of the report generated by AI GPT?

Why was there an agenda to cut the valset by half without any concrete evidence or modelling? Initially, this was because of economics, but they quickly changed their story to performance gains after their flawed assumption of $1k/month costs being utterly refuted and destroyed by the feedback of the validators.

Because of the reckless and irresponsible actions by nethermind, Stride and Karpatkey now refuses to delegate any stake to validators outside of the top 30 because of impending uncertainty.

The foundation also refuses to make any strong statement on whether the push to cut the valset in half will happen.

Every validator and infrastructure service provider in the 31-60 is left in a state of limbo and uncertainty, and has lost delegation.

@nethermind please declare any conflict of interest when you are pushing such a flawed agenda. How much economic rewards do you stand to gain when you pushed for such an agenda?

Every institution, investor and infrastructure provider should blacklist nethermind from interfering with critical governance functions on any chain in the future.

[SilkNodes]

@samwise definitely something fishy going on, I just left a comment on the Karpatkey delegation forum post as it has greatly effected us.

It feels like the stage is being set to hand pick the val set and get rid on lesser known validators like ourselves. I’m sure have seen their rankings change significantly recently but we have dropped a huge amount. A few weeks back we were ranked 19th then we lost what i think was a foundation delegation (I’m not 100% sure but it was a large amount) this dropped us to 25th then Karpatkey pushed out their delegations and although we received some we received the second smallest amount dropping us to around 33rd. Then we get informed stride is removing us from their delegation program as we are now outside of the top 30.

I’m finding it extremely hard to beleive that we aren’t being pushed out of the set for whatever reason I don’t know, we offer services and build tools and have good uptime with our validators in Japan to reduce latency so it really just seems to be down to popularity.