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
More full node coverage #1148
Comments
I briefly spoke to @luke-jr about this on IRC, and I think this is an excellent idea, and it sounds very flexible---a couple hours work for a simple page listing the alternatives or many hours of work to provide something more comprehensive. I'm tagging this as Help Needed, which is our flag that help from outside the regular site contributors would be especially appreciated here. If anyone wants to volunteer, please comment here and we can help you figure out what will work well. Relevant links: |
ACK, good idea! My RBF release is pretty bare-bones, so it's probably better to present it as evidence that there are alternative views of policy, rather than necessarily something that an average end-user would ever want to mess with. Probably doesn't belong on the standard "choose-your-wallet" page, but may belong on some kind of advanced view of it. |
malt-ego has nodes to map the whole network :) |
It would be nice if someone with web design skills could extend the Bitcoin Core page(s) or at least the wallet directory to cover more full nodes. At the very least, Bitcoin LJR is available for the end user market. @petertodd's RBF forks may also be popular. @btcdrak has an addrindex fork, but I'm not sure how useful that is to end users. Probably should consider if btcsuite has any end user friendly options (I don't know).
The text was updated successfully, but these errors were encountered: