Anyone from the Base team can help with a failing Basename transfer?

Trying to transfer megapot.base.eth from a cold wallet to 0x278BFb830b8C0b33B23abF0589c4a8d8aF52a150. 3/4 steps succeeded, but the last one (I think transfer NFT?) failed. 

I think it's resolving correctly now, but have no idea the status of the transfer, and why there's a "Claim name" button there. 

Goal is when we send users a reward, it clearly shows up from Megapot. `megapot.eth` also resolves to this 0x278B address. My guess is TBA uses Basenames, but wanted to cover all bases

building world's largest jackpot @megapot • ex @uniswap • 🟪 #45, FID #1575

Just to be clear, we issue prizes from address 0x278B. I just want in the TBA wallet activity for it to show from Megapot so users know where that money is coming from. Currently it shows that base name as associated with the address. I’m not sure if it fully completed though.

I don’t think it’s actually possible to set a reverse resolution ENS name for a contract without adding special methods to the contract but will confirm for you tomorrow