The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
balanced-network-interface	Ready	Preview, Comment	Apr 17, 2026 1:52pm

Looks good. Just confirming with the SODAX team that the current values should still reflect your initial migration amount.

Also wondering if we should keep the xSODA and current value in place during the unstaking process, so that line is only missing for SODA that hasn't been staked or is fully unstaked.

Also wondering if we should keep the xSODA and current value in place during the unstaking process

Both are 0 when unstaking

The SODAX team confirmed that the values should increase very slowly, so I think this is all working as expected.

Let's merge on Monday.

Some of my SODA has completed the lock-up time. Is it expected that it will still appear under the Migrate tab with the ability to stake it? Apparently it's not staked, yet it still has an xSODA value attached.

And if I click the Stake button, I see this modal:

I do have some SODA in my wallet, but it's unclear if it came from this.

Here's my wallet address: 0x9c7d2E8efA7e6885e90C0CFb8D1A8fa3dad57538

@parrot9design looked at the sonic tracker, nothing indicates that you received the migrated tokens automatically.

There is a method in the sdk that should claim the tokens, I've implemented it but I can't test it myself. My earliest unlock is on 27th. Have a look and let me know if it works please.

Also, the xSoda row should be hidden for all but staked migration items now.

Doesn't look like anything has changed. I can still see the xSODA balance and Stake button for the SODA that is now available, and there's no option to claim. 🤔

For migrations that are currently unstaking, it now shows the unstaking date twice. The top one should always be the unlock date, which won't always be the same.

When I tried to test staking/unstaking with other migrations, I got these errors:

I think for some, especially unstaking, it's because the unstaking transaction went through but the UI didn't update, so then when I try to unstake again I get the error.

For the modals, let's remove the message for SODA, so it just looks like this:

For xSODA, we could update the message to this:

And if unstaking has begun, we could use this:

I claimed this migration twice, but it still shows in the UI and appears that it will let me continue to claim it as many times as I like.

Lol, apologies for this mess @parrot9design

main issue was that the transactions are using migration item index. Once I tested the claiming, the item got filtered out. That shifted the indexing in the app and broke all the other transactions - including the claim you were trying. You couldn't claim it multiple times since the tx was using wrong index, that's the reason it didn't disappear from the UI.

This looks much better, thank you!