[bug] cannot verify Second Level Domain through /.well-known/walletconnect.txt

[Revolution1]

Link to minimal reproducible example

N/A for this is a pure server side issue.

Summary

I'm debugging walletconnect on a blockscout. The domain name is like: www.example.com I don't have control of the DNS, but I have controll of the HTTP server. I setup the verification code and tested it OK:

$ curl https://www.example.com/.well-known/walletconnect.txt
76b2ab15-3907-49b8-xxxx-c49d68fe77a5=10424409466a39733b063c6a147847b0d15847f0980003b874feedeee881c037

Then I wen to the dashboard, trying to verify the domain and failed: It seems it's not trying to get the code from HTTP, or it's getting from example.com instead of www.example.com

Can you help me to solve this issue? Email me if you need the actual domain.

List of related npm package versions

"wagmi": "2.9.2"
"@web3modal/wagmi": "4.2.1"

[minapham17]

any update on this issue? I had the same issue

• I can access our site /.well-known/walletconnect.txt with curl or on browser correctly
• but on Verify domain site, it said DNS TXT Not found as well

[rtomas]

This problem is resolved.