502 error when searching for BSC Testnet contract

[wfkhrrzi]

The error is depicted in the below image.

Steps to reproduce: https://louper.dev/diamond/0x9d27b9413138EEDa955CD65A8dEfcb2a01Ff6f8c?network=bscTestnet

Im also wondering if louper.dev works for BSC mainnet and testnet contracts?

Would appreciate your help on this @ezynda3. thank you!

[ezynda3]

So this has started happening recently and only for diamonds that contain facets with unverified contracts. I haven't yet been able to identify why this is because there is never any error in my logs. If anyone else has some experience with sveltekit and has an idea of what might be happening, please chime in. Until then I would make sure that every single one of your facets including the diamond is verified.

[wfkhrrzi]

So this has started happening recently and only for diamonds that contain facets with unverified contracts. I haven't yet been able to identify why this is because there is never any error in my logs. If anyone else has some experience with sveltekit and has an idea of what might be happening, please chime in. Until then I would make sure that every single one of your facets including the diamond is verified.

i have verified the diamond contract as per the explorer, same goes to all facets. Why is louper still unable to fetch the contract though?

[ezynda3]

What is the address of this diamond?

[wfkhrrzi]

What is the address of this diamond?

Diamond address: 0x9d27b9413138EEDa955CD65A8dEfcb2a01Ff6f8c

Here is the contract reference in testnet.bscscan: https://testnet.bscscan.com/address/0x9d27b9413138EEDa955CD65A8dEfcb2a01Ff6f8c

[ezynda3]

502 error is fixed. Once viem merges this fix your BSC Testnet contracts should show as verified. wevm/viem#2729

[wfkhrrzi]

Yep, it's working now. Thanks for the help!