High Value Bep-2 to Bep-20 BNB Migration Failure. Please Escalate. Requesting Recovery!

[Ethereum2]

I have ~5,000+ BNB stuck on BNB Beacon Chain at:

bnb17myfc5zz2d52kg2lefjfztrm3dty6jv8wk4gsc

I own the original seed and can derive the raw private key (Ledger legacy BEP2 path ≈ m/44'/714'/account/index/change). The official Token Recovery flow (https://www.bnbchain.org/en/token-recovery) and supported wallets, however, do not allow custom derivation paths or direct Beacon private-key import, so my actual address is never detected and I cannot start recovery.

I first attempted migration in 2022 and have pre‑sunset email records showing ongoing attempts. The blocker is purely a tooling limitation, not key ownership.

I am requesting:
– Internal review of this edge case, and
– Any supported option (temporary private-key import, updated recovery tool, or as a last resort, manual recovery) that would let me use my existing key to complete recovery and get my funds back.

Previous Discord ticket: Ticket-4080

[buddh0]

resolving

[Ethereum2]

So far this is the only message I have received about this issue. How is it being resolved? Is the recovery tool going to be adapted so that it can work with custom derivation paths? This would solve the issue for everyone (I know there are others out there as well with similar issues).

[clydemeng]

@Ethereum2
can you submit a support ticket through the official channels:

Discord: https://discord.gg/bnbchain
Telegram: @bnbchain_official_bot

[Ethereum2]

I already created many tickets over the last several months and this is not being resolved. The Discord support from BNBChain said to come here to this GitHub and open an issue in order to get this looked at and resolved. I had at least 7 tickets (many of them connected to ticket 4080 - the original ticket) and they always end up expiring due to lack of response from the BNBChain team after several days or weeks.

What would you suggest I do from here to get this issue escalated and resolved finally? This is not even the first issue I posted on GitHub regarding this... The last one the people here told me to go back and do a discord support ticket (Where I had literally just been sent from and told to come here) and then after I made another ticket I got entirely ghosted on that ticket and it closed unresolved. This is getting very tiring since I have been dealing with some form of this issue for 3 years now and it is going on 4. Can someone please just escalate this to the proper party so that a fix can be made to the recovery tool? It needs to support additional derivation paths because I am not the only one with this issue and even if I was, it still needs to be addressed even if just for my sake.