-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ElectrumX server doesn't support fee estimation #3590
Comments
We are running ElectrumX server with The Unfortunately, Bcoin RPC API is inconsistent with the Bitcoin Core RPC API, and instead of returning the estimate under I reported the problem in Bcoin repo (bcoin-org/bcoin#1153). We should consider switching Bcoin to Bitcoin Core as our full node. According to Fulcrum documentation. What is interesting Bitcoin Core is specified as the only full node that is supported (https://github.com/cculianu/Fulcrum#requirements) by Fulcrum which is an alternative Electrum server implementation we may consider running in the future. We used to run Bitcoin Core node ( Resources:
|
After switching ElectrumX server to use Bitcoin Core the initial problem was solved - please see passing integration tests in #3589. We need to update the production setup to use the Bitcoin Core. |
This PR adds Kubernetes manifests of bitcoin node and electrumx server. The configuration is based on the V1's config: https://github.com/keep-network/tbtc/tree/main/infrastructure/kube/keep-test with some improvements. For V1 we were running bcoin, now we switch to bitcoind, due to bcoin-org/bcoin#1153 Bitcoind and Electrum servers are running in dedicated kubernetes namespaces: - for keep-test: `bitcoin-testnet` - for keep-prd: `bitcoin` We started with one replica for each server and after sync was done, we created snapshots that were used for PVC creation for other replicas. Closes: #3590
ElectrumX server instance we're running failed integration tests for fee estimation:
We need to investigate and fix the problem.
Pull Requests
The text was updated successfully, but these errors were encountered: