"Checking status of verification request xxxx" forever, stuck there.
See original GitHub issueHey guys,
Started experiencing this today after migrating my truffle contract to the BSC testnet.
I run truffle run verify myContract --debug --network bsc_testnet and it just gets stuck on “Checking status of verification request xxx”.
The xxx hash will change every time I CTRL-C and run a new verification attempt.
Hadn’t experience any problems with truffle-plugin-verify before that and it’s one of my favourite little tools.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:14 (2 by maintainers)
Top Results From Across the Web
VSCode extension shows forever "verifying" - how to diagnose?
My .dfy file opened in VSCode causes it to forever show a "Verifying" message (with circling arrow) in the status bar. There is...
Read more >Common IRS Where's My Refund Questions and Errors
Ask the caller to check their records and call back. Name – as it appears on the tax return (for the tax year(s)...
Read more >SOLVED - AutoSSL stuck in pending - cPanel Forums
2:15:19 AM The system has completed the AutoSSL check for “user”. It's now sitting in the pending queue again and in cpanel it...
Read more >8841 stuck on detecting network - Cisco Community
Try to go and see the status messages, go to: Admin Settings -> Status -> Status Message, and see if there are any...
Read more >CSLB Application Investigation Unit - Contractors License Guru
Check out the information about CSLB Application Investigation Unit, and CSLB Processing times. CSLB's Criminal Background Unit reviews all criminal ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Hey everyone - This should be sorted now - Please do give it another shot if your contracts are not verified yet, and let us know if there are issues?
Thanks and sorry for the trouble!
Hey, since so many people are suddenly experiencing this, I do assume that there’s some downtime on the Etherscan/BscScan side that causes it. @Enigmatic331 do you know if there’s any issues with the verification API right now?