Re: Bitpay Generating Invalid BTC Address (URL addy) Any Ideas?

Quote from: Bourguiba on January 28, 2018, 10:06:26 PM

Any ideas on how to fix that? Or maybe really it s a problem on BitPay side?
Because as i understand from reading the code (https://github.com/spesmilo/electrum/blob/master/lib/paymentrequest.py ) and comments -
of the coders, it s the message u get for trying to put an invalid format of adress (# Guard against `bitcoin:`-URIs with invalid payment request URLs).
Can anyone try to open this invoice on his end (just like HCP showed) in a wallet that supports this format?
Here is the invoice : bitcoin:?r=https://bitpay.com/i/T8qnej63zHSwNLKtmurLKx

The problem is on BitPay's side:

Code:

$ wget -S --spider https://bitpay.com/i/T8qnej63zHSwNLKtmurLKx
Spider mode enabled. Check if remote file exists.
--2018-01-28 22:36:21-- https://bitpay.com/i/T8qnej63zHSwNLKtmurLKx
Resolving bitpay.com (bitpay.com)... 104.20.80.236
Connecting to bitpay.com (bitpay.com)|104.20.80.236|:443... connected.
HTTP request sent, awaiting response...
HTTP/1.1 403 Forbidden
Date: Sun, 28 Jan 2018 22:36:26 GMT
Content-Type: text/html; charset=UTF-8
Connection: close
Set-Cookie: __cfduid=d7127900092ab197a3196cd5b45c6c7fe1517178986; expires=Mon, 28-Jan-19 22:36:26 GMT; path=/; domain=.bitpay.com; HttpOnly
CF-Chl-Bypass: 1
Cache-Control: max-age=2
Expires: Sun, 28 Jan 2018 22:36:28 GMT
X-Frame-Options: SAMEORIGIN
Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
Server: cloudflare
CF-RAY: 3e476e393b3c7229-AMS
Remote file does not exist -- broken link!!!

The server is behind Cloudflare, which sometimes (or always if you use Tor) requires you to solve a CAPTCHA to connect to the site, which obviously won't work with programs that aren't web browsers (such as Bitcoin clients). BitPay knows about this problem, but doesn't seem to be in any hurry to fix it.