Context and evidence
BCH has improved, but its main websites have not kept up. bitcoincash.org mentions CashTokens and ABLA, but does not explain the 2025 and 2026 upgrades or improvements to tools such as CashScript. bch.info is also sparse. Newcomers can miss much of what BCH can do today.
These sites already receive attention. On 22 October 2026, Ahrefs estimated monthly worldwide organic search clicks of 23,400 for bitcoincash.org ↗ and 833 for bch.info ↗, including subdomains. Similarweb's September report ↗ estimated that organic search supplied 50.82% of bitcoincash.org desktop visits. These are separate estimates, not measured total visitors or lost conversions.
CoinGecko ↗ links to both domains. CoinMarketCap ↗, Coinbase ↗ and CoinDesk ↗ link to bch.info; Wikipedia ↗ links to bitcoincash.org. The links are verified; their click volumes are unknown.
Updating these established sites could be a high-return, low-cost way to help people understand and use BCH. The main obstacle is agreeing with their owners on what to build, who can publish it and who will keep it current.
Proposed approach and scope
Agree with the website owners
Contact the people who control bitcoincash.org and bch.info. Find out whether they will support an overhaul and how changes can be published. One open-source site could serve both domains if the owners agree, with a plan for search indexing and translations.
BCH-1 can bring together a small group of people who have already built good BCH websites. Choose someone to lead delivery, someone to review the work and people to maintain it. None are appointed yet. The goal is a main BCH landing page with broad support.
Show what BCH can do today
Explain the 2025 and 2026 protocol upgrades, improvements to CashScript and other developer tools, and applications people can use now. Include wallets such as Paytaca ↗, Selene ↗ and Cashonize ↗, DEXes such as Cauldron ↗, and DeFi protocols such as ParyonUSD ↗. Explain what people can do with them, beyond listing links. Explain why those changes matter, with links to the developers' documentation and working examples. Clearly distinguish live features from future plans.
Give visitors useful next steps: get a wallet, use or accept BCH, research its fundamentals, build an application, or join the community. Link to good existing resources rather than duplicate them. Keep the writing clear and the design professional. vm.cash ↗, Zcash ↗ and Monero ↗ are useful references.
Preserve and improve existing traffic
Check which pages, searches and referring sites bring people in. Ask the owners for analytics and Search Console data where available. Audit missing content, broken links, indexing, translations and redirects. Preserve useful tools and existing URLs.
The public traffic estimates are a starting point. Use owner data to establish actual traffic and useful actions such as wallet, research and developer-documentation clicks.
Build, launch and keep it current
Agree a simple site plan and prototype, then build and test it on desktop and mobile. Ask newcomers to try the main tasks. Check accessibility, speed, links and redirects.
Launch on the agreed domains and name the people responsible for content, upgrades and technical maintenance. If domain access is blocked, report it and agree what happens next. A prototype or another disconnected website does not complete the planned launch.
How does this benefit Bitcoin Cash?
People already researching BCH should see what it can do today and know where to go next. Updating established websites can make better use of attention that BCH already receives and send visitors to useful ecosystem projects. Research must establish the cost and likely benefit; no conversion increase or return is guaranteed.
Expected outcomes and evaluation
Deliver an agreed site plan, current content, a tested open-source website and a maintenance handover. Launch on the established domains where permission is secured.
Check that newcomers can find the latest upgrades, developer tools and a useful next step. Test mobile usability, accessibility, speed, links and redirects. Compare search traffic and useful outbound clicks before and after launch, allowing for market conditions. Record missing data and domain-owner blockers.
Open questions and research needs
- Will the domain owners support the work and provide publishing access?
- Who will lead, review and maintain the site?
- Which upgrades, tools and applications need to be explained?
- Which existing resources should each visitor be directed to?
- What traffic and visitor-action data can the owners provide?
- Which URLs, tools and translations must be preserved?
- Can both domains use the same site, and how should search indexing work?
- What will the build and ongoing maintenance cost?
- What happens if agreement on a domain cannot be reached?
Supporting artifacts
Developer tools and documentation to include in the content review.
Primary technical documentation; verify current upgrade specifications and activation status during research.
Delivery plan
milestones
Driver details: A small group of experienced BCH website builders working with the domain owners. BCH-1 may coordinate. The delivery lead, reviewer and maintainers will be agreed during research.
Four proposed checkpoints are below. Research sets dates, costs, responsible people and payment terms. Delivery acceptance and payment are separate; a checkpoint need not have its own payment.
Agree ownership and scope
Speak with the domain owners, choose a proposed team and review current content and traffic.
Delivery criteria: Owner positions, publishing access, content gaps, available traffic data and proposed scope are documented.
Review the site plan and prototype
Draft current content and clear routes for users, investors, developers, merchants and contributors.
Delivery criteria: The owners and reviewer have reviewed the prototype, including 2025/2026 upgrades, CashScript, current wallets, DEXes, DeFi and useful next steps and the maintenance plan.
Build and test
Build the agreed site and check it with newcomers on desktop and mobile.
Delivery criteria: Content is checked against primary sources; key tasks, accessibility, speed, links, translations and redirects have been tested.
Launch and hand over
Publish on the agreed domains and hand over maintenance.
Delivery criteria: Agreed domains are live, launch checks pass and maintainers are named. Report unresolved domain access; a prototype or substitute domain alone does not complete this checkpoint.
Research confirms the delivery plan and costs.