Validators running multiple identities and flipping commissions in same day

I’m updating the list of commission flippers with :evergreen_tree::deciduous_tree: Plant A Tree :deciduous_tree::evergreen_tree:

It increasingly appears that :evergreen_tree::deciduous_tree: Plant A Tree :deciduous_tree::evergreen_tree: and :fish: Bluefin Tuna :fish: are two identities managed by the same operator. What do you think?

Below is a set of on-chain evidence supporting this hypothesis:


1 - Transfers between​:evergreen_tree::deciduous_tree: Plant A Tree :deciduous_tree::evergreen_tree: and :fish: Bluefin Tuna :fish: / :sandwich: Sandwich :sandwich:
https://assethub-kusama.subscan.io/account/JFHtREewUeVy96gGDwMTxrGvQxBDz6jGL8E5LxnAnNbcNbh?tab=transfer

2 - Transfers from :evergreen_tree::deciduous_tree:Plant A Tree​:deciduous_tree::evergreen_tree: and :fish:Bluefin Tuna​:fish: to this account:
https://kusama.subscan.io/transfer?address=DiAwvbHdeFejTFYWVyBVxKYLu1J91DXd9ShusmShRVCv3cV&token_category=native&token_category=treasury

3 - Transfers from :evergreen_tree::deciduous_tree:Plant A Tree​:deciduous_tree::evergreen_tree: and :fish:Bluefin Tuna​:fish:to this account:
https://kusama.subscan.io/transfer?address=H7cqoGVP3oAGQ8UrrrxJYuoErkZnrSXQGmz1g1VkiL5y7xg&token_category=native&token_category=treasury

4 - Transfers from :evergreen_tree::deciduous_tree:Plant A Tree​:deciduous_tree::evergreen_tree: and :fish:Bluefin Tuna​:fish: to this account:
https://polkadot.subscan.io/transfer?address=16FHqbiiorxVCiiXnRxQ3EnLJmZNMb7sAbgjXFix4CwKzaKM

5 - Transfers from both operators to the same Kraken (user wallet):
This is the clearest evidence so far, since a user wallet is personal by definition.
What legitimate explanation is there for two supposedly independent validators sending funds to the same personal wallet?

https://polkadot.subscan.io/transfer?address=143Eok8cqoG8u56dBRbckSzQzTtGgi7vEdX4Zg5qnFAcDxA&token_category=native&token_category=treasury

6 - Transfers from both operators to the same Binance (user wallet):
The same pattern appears again here, this time involving a Binance user wallet.
Once more, two supposedly independent validators are transferring funds to the same personal account.
https://polkadot.subscan.io/transfer?address=12kWkKBiMDCZM8Yxep5vm3KTn1xKtbnFr3spkejPzAV8Ej5A&token_category=native&token_category=treasury


*****

At this point, it’s reasonable to ask whether Polkadot should take action against validators operating multiple identities, engaging in systematic commission flipping, and behaving in ways that are clearly detrimental to nominators.

Could mechanisms like Proof of Personhood be part of the solution to finally address this long-standing issue?

Looking forward to the community’s thoughts.

2 Likes

As far as I can tell, there is no approved Fellowship RFC that directly specifies or constrains how validator commissions are treated (the mechanics live in the staking runtime and are mostly surfaced via UI conventions, please correct me if I am wrong in this interpretation).

However, Proposed RFC-0162 is relevant in principle: it explicitly frames sybil splitting (multiple accounts), broker aggregation (off-chain consolidation), UI/coordination capture, and timing manipulation as part of the “economic/institutional adversary” attack surface. In other words, it treats these behaviors as market-structure vulnerabilities.

I would strongly recommend revisiting RFC-0162 and contributing amendments that make these specific staking-related surfaces first-class considerations (e.g., disclosure/observability requirements and UI invariants such as era-effective parameter history by default). Left unaddressed, these gaps can mechanically increase market concentration and manipulability, lowering the protocol’s market-structure maturity and the trustworthiness of nominators’ decision inputs.

RFC-0162’s Github PR Link.

1 Like

@Megadot You should go check the commission flippers from before the AH migration. So far what you’ve posted on this topic is nothing new and is honestly not even concerning compared to historical behavior.

Many validators are duplicates because they’re still riding the wave of nominations they received while active from the 1KV and DN programs. It was always my opinion that at least 50% of the 1KV participants were dupes.

The majority of the data available for this and by far the most offensive perpetrators – you haven’t even looked at yet. << Insert jurassic park that’s one big pile meme >>

5 Likes

Thank you. The more I investigate, the more dirt I find hidden under the rug.

I’ve now updated the list with 10 additional validators showing dishonest behavior against the interests of nominators.

It’s honestly shameful that no one is taking action so far, but if the system is to maintain any credibility, someone has to step up and take measures.

The best thing that could be done is to roll out PoP validators as soon as possible. There’s no point spending time on other solutions.

I want to stress (again) that this is a UI/UX issue, not an unsolved protocol problem.

The PAPI Staking DApp already avoids this pitfall by showing nominators the effective commission in the most recent eras, so users can make decisions based on what validators are actually charging:

Given there’s now an OpenGov proposal to fund the most widely used staking dashboard, we should require them to address this explicitly in scope and deliverables:
https://polkadot.subsquare.io/referenda/1831#1

3 Likes

That doesn’t resolve the issue of duplicate validators who operate who knows what % of the validators on the network. Yes, working as intended, but the entire model is broken because of assumptions made about the rationality of nominator behavior. The early 1KV validators were able to get in easily, create duplicate entities, and leverage low fees to collect nominations to remain in the active set permanently.

1 Like

This is, indeed, a real and very worrisome issue. Sorry, I hadn’t been paying close attention to the latest messages, and I wrongly assumed that the main discussion topic was the commission-flipping.

However, I agree that what you are pointing out is a much more worrisome and important issue, for sure.

It is deeply concerning to see validators operating under multiple identities.

I would like to present another case that suggests a strong link between dakkk and OpenBitLab, both identities currently operating active Polkadot validators.

—-

dakkk identity

According to Twitter, @dagide belongs to Davide Gessa

—-
OpenBitLab identity

Please note that its Davide personal email address, not OpenBitLab corporate domain

What is particularly alarming is that both accounts transfer funds to the same Kraken user wallet, despite the fact that user wallets are, by definition, personal accounts:

In addition to direct transfers between these two identities, there is also a transfer dated 13/08/2025 of 2,490 DOT originating from the following account.

A review of this account’s transaction history strongly indicates that it is controlled by OpenBitLab.

Given that OpenBitLab does not appear to be a legally incorporated entity, this seems to be a case of two identities that are apparently managed by the same operator. It is also concerning that OpenBitLab is operating validators on the Paseo network and across multiple system chains within the ecosystem.

Once again, this situation raises serious concerns regarding validator identity duplication, transparency, and the lack of effective enforcement within the ecosystem.

I am surprised by the extent to which the following operator identities, all running active Polkadot nodes, show such a significant intermixing of transactions between their accounts:

BESTVALIDATOR | ZURICH/p1
BUENO VALIDATORO/p1
BUENO VALIDATORO/p2
Chris-Staking
Chris-Staking/p1
Chris-Staking/p2
Encointer
POWERSTAKE POLKADOT/P1
STEAKCHEF/p1

Example 1
Example 2
Example 3
Example 4
Example 5
Example 6

It is also noteworthy that these operators chose to transfer 20 DOT to their sub-identities almost simultaneously on November 5, 2025, presumably for identity verification purposes:

Encointer transfer to sub-identities
BESTVALIDATOR | ZURICH transfer to sub-identities
BUENO VALIDATORO transfer to sub-identities
Chris-Staking transfer to sub-identities

The timing and coordination of these transactions further reinforce concerns about whether these identities are truly independent or instead managed in a coordinated manner.

This level of fund movement between supposedly independent operators raises legitimate questions around independence, transparency, and whether these identities are effectively controlled by the same entity.

With great sadness, I have to report that I continue to find rotten apples within the ecosystem. In this case, it involves the validator Mile and its other identity StakedTech, both operating active validator nodes.

To properly understand what is happening, let’s follow the chronology of events.

On 16/06/2020, the wallet that now shows as ‘Mile’ set its identity as ‘StakedTech’ : :thinking:

On 06/01/2021, a new wallet was created and set its identity with almost same branding:

Then, on 19/01/2021, just a few days after this second wallet established its identity as StakedTech, the identity of the first wallet that now shows as ‘Mile’ was suddenly changed:

Name: From StakedTech → To Mile
Email: From staked.tech@protonmail.com → To mherceg@protonmail.com
Matrix: @matherceg:matrix.org (unchanged)
Website: https://www.staked.tech (removed)

Additionally, by analyzing the transfer history of this account, it can be observed that on 29/09/2020, “Mile” sent 1,094.45 DOT to another account, and those funds ultimately ended up in a StakedTech controlled account.

What makes this particularly concerning is that both “Mile” and “StakedTech” have been identified for years as engaging in abusive practices, specifically commission flipping, extracting hundreds or even thousands of DOT from nominators over time.

Once again, this raises serious questions about multiple identities, abusive behavior, and the lack of effective enforcement within the ecosystem.

Expand your search criteria a bit more to look at any validator that changes commission to 100%.

If you don’t claim an era it’s possible to change your fee in the future and claim the previous era at the new fee. I’ve never tried this in practice myself to confirm it’s true but it was talked about somewhere in here before. The premise is that you run a validator, allow 100 eras to pass, flip commission to 100%, wait for it to apply, then claim all the eras. I do have some vague memory of looking at a few accounts that did this a few years back.

Like I said previously, while this is new for you, people have been annoyed by this for years. No one ever cared enough to act. I had to complain for months just to get W3F to implement a simple KYC. This is when they changed it from 1kv to DN.

The needing to complain or interact a lot to get anything done is a common theme and it’s a reason why people are angry.

Just look at this thread Discontinuation of ink: Rust smart contract language - #8 by Kratist0s

The W3F should have known already if ink was part of the new roadmap or not. Why did it take months for them to finally say that?

Just look at the DV and DN programs – there was no experimentation, no changes, no real oversight or management – no plan. As far as I can tell, they no longer have the capacity to meet the foundation’s stated mission. What do they even do? I’m trying to figure it out.

It’s the common theme you’ll find in a lot of issues around the ecosystem. People complain about stuff but those complaints don’t make their way into a task management system to be resolved. I just recently realized (last weekend) that even though there are all these duplicate identities that the DN program itself was massively beneficial for that thing for which we dare not speak.

I told a few people that the DN program should not be shut down because of its benefit to that thing for which we dare not speak – But I already know it will have 0 impact – and – I can prove it with math. It’s not subjective.

More rotten apples in the ecosystem.

A single operator appears to be running three different validator identities and has been observed transferring funds from those validators to the same personal Binance user wallet, where deposits are restricted to a single account holder.

The identities involved are:

  • GuruStaking​:person_wearing_turban:138tCNoHg9QbhjqanRS7R8ZC8547A6CdaSmrCtJCRLpjQk6r

  • Stake​:magnet:Magnet — 12uGsmXCJL1kGSozLS4vSX8nLGkX8DUKiWK1HdV8Zc6mcbwE

  • ProStakers.com​:gem_stone:12pnnD6kCBTLJkFkoKQ2knf1MTehyJNRvsSdDw4EJ9CYgE1z

This pattern strongly suggests common ownership and raises serious concerns about transparency, accountability, and validator concentration within the network.

We respectfully ask Polkadot and Kusama nominators, as well as nomination pool operators, to review and update their nominations accordingly. Some of these actors currently maintain active validator nodes on both networks, and continued vigilance is essential to protect delegators, preserve decentralization, and uphold the integrity of the staking ecosystem.

In the following article, you will find a comprehensive list of identified bad actors, which I will continue to update as new information becomes available.

1 Like

This is actually an interesting discussion, because it does not only affect Polkadot staking itself, but also, for example, the Nakamoto Coefficient calculation. I opened a discussion issue in their repo: Problems with the Polkadot NC: validators secretly run by the same party, and anonymous validators · Issue #79 · xenowits/nakomoto-coefficient-calculator · GitHub

2 Likes

More validators running multiple identities :scream:

:ewe: HODL.FARM :ewe: - Polkadot address
:office_building: MIDL.dev - Polkadot address

Example 1
Example 2
Example 3

Both operators currently have active validators.
Please review and update your validator and nomination pool selections accordingly.

You can find an up-to-date list of identified bad actors in this article.

1 Like

More bad actors running multiple identities with nodes in the active set:

NeNa :sunflower:- Polkadot address
CP287-CLOUDWALK - Polkadot address

Please note that when you check CP287-CLOUDWALK address it shows as Account index: 1abY8 instead but here you can verify the wallet belongs to CLOUDWALK validator by hovering over the stash account.

Both CLOUDWALK (aka 1abY8) and NeNa :sunflower: transfer funds to this this wallet:

Proof of both identities sending funds to this Bybit (user wallet)

Both operators currently have active validators.
Please review and update your validator and nomination pool selections accordingly.

You can find an up-to-date list of identified bad actors in this article.

1 Like

What is going on with all these validators?

***

Wallet 1 - mutiple tranfers between la_civeta, il_corvo, redpenguin

Wallet 2 - transfers between azimut, ondin, la_civetta

Wallet 3: Binance (user wallet) receives funds from both azimut and alfastake

What’s going on with all these validators?

We recently discovered Mile​:globe_showing_europe_africa: running another identity, StakedTech

Now we have discovered that he has also been running another identity: BEEFY :ox:
Here you can see Mile​:globe_showing_europe_africa: sent 10,000 DOT to a bridge account and from there to BEEFY :ox: wallet who was a Polkadot validator in the past.

*Proof*

This MEXC (user wallet) which is suposed to be personal, received transfers from BEEFY :ox: and this other account:
11AnciffJctDC28odTEjDVYP2yWyp6275WLbrAUHi2vJm9f

Here how the wallet 11AnciffJctDC28odTEjDVYP2yWyp6275WLbrAUHi2vJm9f is connected with Mile​:globe_showing_europe_africa:. You cann also check on subscan.

I just can’t believe Mile​:globe_showing_europe_africa: has been running Polkadot validators with 3 identities! :scream:

How is possible Mile​:globe_showing_europe_africa: is still running key Polkadot infra like system chains? @Karim @OliverTY

Please review and update your validator and nomination pool selections accordingly.

You can find an up-to-date list of identified bad actors in this article.

1 Like

old community members that does nothing to the community…