feat: update default Electrum server from Fulcrum to Electrs#388
Merged
Conversation
This comment has been minimized.
This comment has been minimized.
ovitrif
force-pushed
the
claude/issue-367-20260122-1118
branch
from
0633425 to
dc464c4
Compare
ovitrif
force-pushed
the
claude/issue-367-20260122-1118
branch
from
dc464c4 to
f1fb57f
Compare
Contributor
|
Seems to work fine, but the original issue that led to us switching from Fulcrum still persists.
It usually happens right after opening a channel. I wasn't able to reproduce it on staging yet but on mainnet I got it first try. |
Collaborator
Author
|
Validated on REGTEST ✅ |
Collaborator
Author
I wonder if we might still get the issue that JC experienced seeing his onchain balance not updating / app not acknowledging an incoming onchain tx until reset & restore: Otherwise I am a bit less worried because even on old Fulcrum, this issue never reoccurred and almost nobody really had onchain issues during our extensive mainnet testing. Very odd that we never saw this on REGTEST to my knowledge… but I suppose as long as it's just a logging entry, it's not an issue, FWIW. Curious what input we could get from Spiral, given that, to my knowledge, we're now using an electrum server implementation on which ldk-node was tested, but for some reason we still see this error in the logs issue 🤔 . Going to inquire for feedback 🤞🏻 . |
Collaborator
Author
|
Can we merge this?! The issue is to be forwarded to Spiral |
ben-kaufman
approved these changes
Jan 22, 2026
Collaborator
Author
|
@piotr-iohk Can you help me understand what is happening with the e2e and why they seem not to run? 🤔 |
Collaborator
It is because we have only one hosted mac-os GH agent, and it is shared. The run is queued and waiting until the agent is free. It is a bottleneck recently because of high activity on the repo... On the side I've been trying to pralalelize tests similar to android by running some tests on regtest and using GH hosted macos-latest/macos-15, but unsucessful so far... test/try-run-tests-on-regtest |
BitcoinErrorLog
pushed a commit
to BitcoinErrorLog/bitkit-ios
that referenced
this pull request
Feb 7, 2026
…260122-1118 feat: update default Electrum server from Fulcrum to Electrs
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #367
This PR updates the default Electrum server configuration to use Esplora-based servers.
Description
ssl://bitkit.to:9999ssl://electrs.bitkit.stag0.blocktank.to:9999Preview
N/A - configuration change
QA Notes
Build and run on mainnet flavor
Build and run on dev (regtest) flavor ✅