bitcoinunlimited / cashnodes-frontend

Cash nodes front-end

Website | Download | Setup | Miner | ElectronCash | UnconfirmedChains

What is Bitcoin Cash?

Bitcoin Cash is an experimental new digital currency that enables instant payments to anyone, anywhere in the world. Bitcoin Cash uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. Bitcoin Unlimited is the name of open source software which enables the use of this currency.

For more information, as well as an immediately useable, binary version of the Bitcoin Unlimited software, see https://www.bitcoinunlimited.info/download, or read the original whitepaper.

What is Bitcoin Unlimited?

Bitcoin Unlimited is an implementation of the Bitcoin client software that is based on Bitcoin Core. However, Bitcoin Unlimited has a very different philosophy than Core.

It follows a philosophy and is administered by a formal process described in the Articles of Federation. In short, we believe in market-driven decision making, emergent consensus, and giving our users choices.

Installing

For info on installing Bitcoin Unlimited see INSTALL.md

Building

For info on building Bitcoin Unlimited from sources, see

• Dependencies
• Unix Build Notes
• Unix Build Notes (RPM)
• Windows Build Notes
• OpenBSD Build Notes
• macOS Build Notes
• Deterministic macOS DMG Notes
• Gitian Building Guide

They are not complete guides, but include notes on the necessary libraries, compile flags, etc.

Running / setup

• Running large unconfirmed transaction chain limits
• Running an electron cash protocol server
• Getting the most out of Xtreme thinblocks
• Setting up an Xpedited Relay Network
• Tor Support
• Init Scripts (systemd/upstart/openrc)
• Using Bitcoin Unlimited for Mining

Development

• Developer Notes
• Contributing
• BUIP, BIP and Bitcoin Cash Specifications
• Bitcoin Unlimited Improvement Proposal Archive
• Multiwallet Qt Development
• Release Notes
• Release Process
• Translation Process
• Translation Strings Policy
• Unit Tests
• Unauthenticated REST Interface
• Shared Libraries
• Assets Attribution
• Files
• Fuzz-testing

Online resources

• Issue Tracker
• The Bitcoin Forum
• Reddit /r/btc
• Reddit /r/bitcoin_unlimited
• Slack Channel

License

Bitcoin Unlimited is released under the terms of the MIT software license. See COPYING for more information. This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. This product includes cryptographic software written by Eric Young ([email protected]), and UPnP software written by Thomas Bernard.

cashnodes-frontend's Issues

Minor layout improvements to deploy in 0.0.2

• Stats table: on page load get the "COUNTRIES" table selected so that it would be more clear that also the node distributions by NETWORK and USER AGENT are available, i.e.
• Pie chart legend should be horizontally aligned with the graph.
• Put the timestamp in bold and add total number of nodes (in bold) on the same line.
• For the the text at the bottom use centered alignement
• Horizontally aligned "Powerd by Bitcoin Unlimited" with the bitcoin cash log and maybe add also BU logo
  https://www.bitcoinunlimited.info/img/bitcoin-unlimited.png
• nodes table column width partitioned like this 35%,30%,17.5%,17.5%
• mv "Showing 2647 out of 2647." up, so thta we can have the table nodes bigger
• make nodes list more compact (less padding between nodes line)
• mv user agent as first column of the stats table
• put the gradation of the map to green only
• use green for the shading/background of stats header

Things to be done in the short term

ver 0.0.1

• Put the block height on same line as NODE_* in order to reduce line count
• fix other possible layout glitches
• mapping network names (#11)
• alternate row colors on table that displays nodes (#13)
• sort nodes according to the last time we connect to them (ascendant) (#12)
• makes search case insensitive (#14)

ver 0.0.2

• Add main statistics to the dashboard (nodes count, nodes by region, nodes by network)
• tailor the layout for mobile view (responsive design)
• minor layout improvements (#15)
• split content: graph and stats on the landing page; list of nodes and search on another one

ver 0.0.3

• pie chart representing nodes composition by client type
• export data in csv format (optional)
• provide the script to install a new BUCash node.

[Feature Request] Add 4th tab after "Network" for "Services Offered"

I think it would be interesting to see a breakdown of how many nodes are offering each of the service bit flagged services. Just a static number of rows based on the number of currently defined/supported service bits with the node count for each.

As an extension to this, would also be interesting to see a sub-table view listing the break down of the total number of nodes offering a service by agent (or at least the top 4 or 5).

As another extension, and this I think could apply to each of the tabs on the main statistics page, is that clicking on a row in one of the tables could take you to the node summary table but with a pre-applied filter that only shows the nodes that were the source of the totals for the row clicked. This likely means expanding the filter capabilities as currently you can only search on address or agent.

Next set of features

• add some APIs, especially a leader board
• add a form to check if a particular server is currently on line
• add historical data (#nodes vs time)
• specify search parameter via URL
• node status page (uptime, latency, etc, etc)
• node breakdown per service bit (see #30)

Lots of nodes listed as serving Graphene, which don't when connected with BUCash client.

With the graphene service bit now turned on, it looks like the cashnodes.io site is showing way more nodes as offering NODE_GRAPHENE services than actually are when connected via a BUCash client (with graphene enabled via the bitcoin.conf file of course).

Compared the first 5 or 6 in the list that would connect with my node by using addnode cli. When displaying the services offered in the debug window (Qt client) none of them were serving graphene. Out of 28 BUCash1.3.0.1 nodes connected to me, only 1 has graphene turned on and that wasn't one I connected to via addnode

Accuracy of the "top ten" counts

The top ten are prominent numbers for viewers.
However, user-agent subversions can be variable depending upon user configuration, and this can make the raw totals misleading. For example, the search function reveals 40 instances of BUCash:1.3, when only 27 are shown in the top ten count because they have EB values different from the most frequent, which is the default.
I suggest truncating at the first parenthesis "(" when counting different implementations for the top ten. Not sure whether the names should be truncated, or the most common subversion shown.

Make API host configurable

test

test again if repo-lockdown is working

test

test

Descending sort for implementations

Suggest a descending sort on node count for implementation list and therefore the pie-chart slices.

[Feature Request] - Allow searching/filtering either by regex or by categories.

Currently it doesn't look like searching allows standard RegEx (or maybe I just don't know the regex syntax used by JS, and this is already supported). It would be useful to be able to search via regular expression and/or categories, similar to what you can do in most standard e-mail clients.

For example, "from:[email protected] hasattachments:yes" would find all e-mails from specific account with attachments. Here this could be applied as "agent:BUCash service:XThin" to search for only BUCash nodes with XThin enabled. Would want case-insensitive, partial string match anywhere in the category string.

This comes about because I wanted to be able to search for only BUCash nodes providing the Graphene service (and ignore the "Bitcoin Core SQ" nodes which don't seem to be accept inbound connections).

Configure deploy pipeline

Auto-detect new clients for pie-chart breakdown list

I propose an enhancement where this list is generated from the data.
Extract from text e.g. "XT" from /Bitcoin XT: possibly by removing just the word "Bitcoin" and spaces.
If the count is >1% then show slices, else collate as "others".
At present it appears to be hard-coded:
ABC
Bitcoin Unlimited
Others
XT