lbcdblocknotify: support multiple stratum server #100
No reviewers
Labels
No labels
ci
claimtrie
consider soon
Epic
good first issue
hacktoberfest
help wanted
mempool
mining
peer
priority: blocker
priority: high
priority: low
priority: medium
rpc
runtime
test
type: bug
type: discussion
type: improvement
type: new feature
type: refactor
type: task
ux
wallet
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: LBRYCommunity/lbcd#100
Loading…
Reference in a new issue
No description provided.
Delete branch "peterpan0708/lbcdblocknotify-support-multi-stratum-server"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
support notify to multiple stratum servers
@ -43,3 +53,1 @@
log.Fatalf("ERROR: %s not found: %s", cmd, err)
}
b.customCmd = *run
// Start the eventt handler.
LGTM.
Ideally, we'd like to fan out with multiple stratum connections(or clients), not multiple bridges.
But the current codebase is not friendly to extend it that way.
So I think we can have this working feature merged now and update it in future iterations.
A minor preference is to update the
stratum
flag to a list style as shown in those inline comments.This has been requested by multiple pools. So, thanks a lot for the contribution :-)
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.