Hello everyone,
I’m a retail investor who purchased CFG on OKX exchange and withdrew it to my self-custody SafePal wallet via the ERC20 network. The exchange listed it as “CFG (ERC20)”, but when the tokens arrived in my wallet, they appeared as wCFG (which was standard practice for ERC20 withdrawals at the time).
The amount and value displayed correctly in my wallet, so I didn’t realize there was a migration issue until recently when wCFG stopped displaying in my wallet UI.
My situation:
I hold legacy wCFG on Ethereum (ERC-20), fully self-custody.
I missed the main migration window (closed Nov 30, 2025) and the case-by-case review (until Apr 10, 2026).
My balance is still visible on Etherscan at the old wCFG contract.
I have read the threads “Late to the migration party” and “Alternative Migration Path for Legacy CFG Holders”. I fully understand the governance process (CP141/CP149) and the deadlines.
My question to the team and community: as of August 2026, is there any official path for late self-custody holders to migrate legacy wCFG to the new CFG (e.g., a manual claim procedure, a new swap contract, or a treasury process)? I’m ready to provide my address and sign a message to prove ownership.
Context: I followed OKX’s withdrawal instructions correctly (withdrew “CFG” via ERC20), but received wCFG tokens that are now stuck post-migration. Many retail users likely faced the same issue when withdrawing from exchanges during the migration period.
Wallet:0x1c891676032472F5Bef3430ed6D2D7a3ee6c5e8A Etherscan:Address: 0x1c891676...3ee6c5e8A | Etherscan
Thank you!
Legacy wCFG holder (ERC-20, self-custody) — is there still a path for late migration in August 2026?
Same issue here! I am late to the migration and still own them in my self-custody wallet.
Any update on this?
What are you talking about? OKX supported the automatic migration back then. And when you mentioned Ethereum, that would mean holding wCFG, wouldn’t it?
I don’t remember clearly whether it was on Polkadot or the Centrifuge chain at the time. Either way, what you’re doing here seems pretty off. You should probably sort out the timeline and the actual migration process first.