-
Notifications
You must be signed in to change notification settings - Fork 7
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
Add Firo peers #9
base: master
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -7,5 +7,18 @@ DAEMON_URL = http://username:password@hostname:port/ | |
|
||
# COIN = Bitcoin | ||
|
||
# Peer Configuration | ||
PEER_HOST = electrumx01.firo.org | ||
SERVICES = ssl://electrumx01.firo.org:50002, tcp://electrumx01.firo.org:50001 | ||
|
||
PEER_HOST = electrumx02.firo.org | ||
SERVICES = ssl://electrumx02.firo.org:50002, tcp://electrumx02.firo.org:50001 | ||
|
||
PEER_HOST = electrumx03.firo.org | ||
SERVICES = ssl://electrumx03.firo.org:50002, tcp://electrumx03.firo.org:50001 | ||
|
||
PEER_HOST = electrumx.firo.org | ||
SERVICES = ssl://electrumx.firo.org:50002, tcp://electrumx.firo.org:50001 | ||
Comment on lines
+11
to
+21
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 💡 Codebase verification Based on the code analysis, I can now provide the final response: Multiple PEER_HOST entries are not supported - use REPORT_SERVICES instead The codebase shows that PEER_HOST is actually obsolete. The configuration should use REPORT_SERVICES for peer announcement. The current configuration format is incorrect because:
Correct configuration should look like:
🔗 Analysis chainVerify peer configuration format and DNS resolution
Consider consolidating the peer configurations into a single REPORT_HOST setting or using environment-specific configuration files to avoid potential conflicts. Let me gather more information about the configuration format by checking the ElectrumX codebase for how PEER_HOST is handled. Let me check the actual configuration handling code to understand how PEER_HOST is processed. 🏁 Scripts executedThe following scripts were executed for the analysis: Script: #!/bin/bash
# Description: Verify DNS resolution and TCP/SSL port accessibility for the new peers
echo "Checking DNS resolution for peer hosts..."
for host in electrumx01.firo.org electrumx02.firo.org electrumx03.firo.org electrumx.firo.org; do
echo "Resolving $host..."
host $host
done
# Search for any existing peer configurations in the codebase
echo -e "\nChecking for existing peer configurations..."
rg -l "PEER_HOST|REPORT_HOST" --type conf
# Check if these hosts are already defined in coins.py
echo -e "\nVerifying peer definitions in coins.py..."
rg "firo.org" --type py
Length of output: 1805 Script: #!/bin/bash
# Search for PEER_HOST handling in the codebase
echo "Checking PEER_HOST handling in the code..."
rg "PEER_HOST" -A 5 --type py
# Check for any documentation or examples about peer configuration
echo -e "\nChecking for configuration documentation..."
fd README -t f -X cat {}
Length of output: 1369 Script: #!/bin/bash
# Search for configuration handling in the server setup
echo "Checking server configuration handling..."
ast-grep --pattern 'class Env {
$$$
}'
# Look for specific configuration parsing
echo -e "\nChecking configuration parsing..."
rg -l "class.*Env" --type py | xargs cat
# Check for any sample configuration files
echo -e "\nChecking sample configurations..."
fd -e conf -e cfg -e sample -X cat {}
Length of output: 11986 |
||
|
||
# See http://electrumx.readthedocs.io/en/latest/environment.html for | ||
# information about other configuration settings you probably want to consider. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add explicit COIN setting for Firo
The commented out
COIN = Bitcoin
setting needs to be updated for Firo. This might be causing the peer validation issues reported in the logs.Apply this change:
📝 Committable suggestion