Bridge SPL keeps failing on devnet-alpha with error `0x3`

[ScapeXYZ]

Hi team,
I’ve been testing the bridge on devnet-alpha and I keep running into the same problem. I created my own SPL token (using spl-token create-token), minted some supply into my wallet ATA, and then tried bridging with:

npm run tx:bridge-spl -- devnet-alpha --mint <myMint> --amount 100
But the transaction always fails with:
custom program error: 0x3 Logs: Account not associated with this Mint

I also tried dumping the bridge state account (`

7Mgida4KEymRV7t7BWjyH3P9yQYJLGw5pifEvN5da63J`) and parsing it, but the “mint” value I pulled out doesn’t behave like a real SPL mint account (the token program rejects it).

So my question is:

Which SPL mint is this bridge program actually configured to use on devnet-alpha?

Should I be using a pre-deployed mint, or is it possible to deploy my own and point the bridge to it?

Any guidance would be super helpful — I think I’m just missing the right mint address to work with.

Thanks!

[jackchuma]

Hey! Apologies for the headaches - we'll definitely be working to improve our documentation. For starters, I recommend using the devnet-prod bridge instead of alpha. Alpha is like our development environment so is not guaranteed to always be working.

Can you share more about exactly how you created the SPL mint you're using?

[ScapeXYZ]

Got it, thanks for the clarification. What I did was simple — I just created a new SPL mint with spl-token create-token, set up an account for it, minted tokens into it, and then tried running the bridge command with that mint. The tokens showed up fine in my wallet, but the bridge kept failing with 0x3

I haven’t tried with devnet-prod yet, I was only testing on alpha. I can switch over and retry there if that’s the recommended setup.

[ScapeXYZ]

@jackchuma
Can you airdrop me some test tokens for the devnet-prod SPL mint (8KkQRERXdASmXqeWw7sPFB56wLxyHMKc9NPDW64EEL31)? My wallet is 9wE5bNPQB3qxNAHbuJo2RxB4cdyH2FKQUnPiwb8PVFvb and my ATA is 5CN4yhSieisBt5YLSju6NR6me2ZAvKQ1VUYHvu5fZc9A.”

[ScapeXYZ]

@jackchuma I'm still waiting