When this post is about 10 minutes old, your browser will start sending some of the requests to bchd.fountainhead.cash
, instead of rest.bitcoin.com
.
EDIT: It is live. Seems to be working.
EDIT2: All of the browser functions are migrated away.
EDIT3: Our backend is now also using bchd.fountainhead.cash
This is a first experimental step, we want to see how well (or poorly) it works.
The problem is that about 80% of our support requests are somehow related to rest.bitcoin.com. You can see it here, here, in our mailbox and there are also problems with Tor browser.
We're trying to respond to all of the requests, but we're just not fast enough!
The bigger problem is that we can't do much about it. We don't know why rest.bitcoin.com blocks some of these requests and trying to debug it using three-way communications (we ↔ user ↔ bitcoin.com) isn't really a productive use of our time.
So, we'll do a two-step migration, as a first first we'll use bchd.fountainhead.cash
for some functions, slowly replacing all of the rest.bitcoin.com
calls with calls to bchd
, then we'll start our own node at read.cash
, thereby (hopefully) getting rid of all of CORS
-related problems (CORS is a call that your browser makes before trying to access rest.bitcoin.com
, like "Am I allowed to connect to you?", to which occasionally rest.bitcoin.com answers: "No")
However, bchd uses a very different technology for connections (grpc), which wasn't really created for the web use. It was mostly created for use in "server-to-server" communications. We've never used it in browsers, so we don't know how well it is supported.
There's only one way to find out:
Deploy it and see if anyone complains! :)
If you are having problems using the site (especially, if you see your balance as $0.00), please let us know in the comment section.
Kudos to bchd.fountainhead.cash for providing this service!
Kudos to BCDH team for the development of BCHD!
Kudos to bitcoin.com for providing rest.bitcoin.com for free! It is still immensely helpful (especially due to the great integration with the BITBOX library), it's still great for the first iteration of any project.
Well, all I can say is...
GREAT JOB.
I mean, uhm, "so this is why my wallet started working again?"