How We Deal With Blockchain (Hard) Forks – In Light of the Upcoming BCH Hard Fork

Bitcoin Cash fork

Bitcoin Cash fork

In light of the upcoming Bitcoin Cash (BCH) hard fork on November 15th, we want to share how we handle forks at Decentral, and our plan around the decision to suspend transactions for the BCH wallets in Jaxx Legacy and Jaxx Liberty on the day of the fork.

Before we get into how we deal with hard forks, let’s first understand what a hard fork is.

What Is A Hard Fork

A Hard Fork is a blockchain software update (new rules) that, when applied, will override all blockchain activity initiated by earlier versions of said blockchain software.

Blockchain activity on the Bitcoin Cash network mainly consists in mining transactions and all miners handling the transaction data and packing it into blocks run the blockchain software. A hard fork is mainly an update to the software miners run on their computers (e.g. nodes).

There are two types of forks:

  1. Consensual – also known as soft forks, where the update is assumed to be applied by all nodes on the network – e.g. consensus is achieved over the fork
  2. Contentious – also known as a hard fork, where the update has not achieved consensus within the community and the expected consequence will be resulting in two blockchains or more, each following their own rules.

Bitcoin Cash fork

Confusion appears when consensus is not achieved over a fork as this may have some unexpected results. The risks with hard forks may be:

  • Multiple blockchains: Causes confusion for holders of the main coin and raises questions of how to manage the mirrored (forked) coins
  • Replay attacks: Since the software base is the same for any duplicated chains, a malicious party may copy a transaction code from the main chain and send it (re-play it) on a mirrored chain, thus creating unwanted results for the owner
  • Temporary transaction suspension: As a best practice, many exchanges and wallet providers will be stopping the users’ ability to transact a certain coin until the fork is applied and the resulted blockchain(s) are working safely. This is one of the best measures to stop replay attacks.

How We’re Handling Forks

A look at the details of the fork to understand the impact it will have on our users:

  • On November 15th, a contentious Hard fork will occur.
  • There are currently three major implementation proposals for the Bitcoin Cash network: Bitcoin ABC, Bitcoin Unlimited, and Bitcoin SV
    1. Bitcoin ABC will add new features such as smart contract abilities, oracle services, and scaling improvements to the Bitcoin Cash network;
    2. Bitcoin Unlimited will implement both changes of Bitcoin ABC and Bitcoin SV enabling miners to vote for the features they want;
    3. Bitcoin SV will replace Bitcoin ABC’s scripts with its own and expand Bitcoin Cash’s block size from its current 32MB to a maximum size of 128MB.

Actions We Will Take

  • Stop Jaxx users ability to transact Bitcoin Cash through the Jaxx wallet for approximately 24h around the fork. The timeframe may change depending on the outcome of the fork.
  • We will start this a few hours before the expected time, until the dust settles, so we can plan the next action. All users digital assets are safe during this process. 
  • Issue warnings to our users via our communication channels (blog, Social media, in-app bulletins)
  • Enable the Bitcoin Cash service when we believe it is safe for our users. We plan to support the chain that has the most hashpower following the fork. At this time, we do not plan to support any of the additional chains.
  • Ensure our servers and apps are updated with the needed upgrades to support the fork
  • If major backend updates are required, transacting Bitcoin Cash following this fork may not be available in Jaxx Legacy and only be available in the new Jaxx Liberty. At that point we may ask all our Jaxx Legacy users to migrate over to the new Jaxx Liberty, a process that takes less than two minutes.

Alternative Options

With Jaxx Legacy and Jaxx Liberty, we strive to empower our users to have full control of their digital life. This means that there are options available for all our users in case they don’t agree with the actions we will take during the Bitcoin Cash fork or any other future forks.

  • You can send all your Bitcoin Cash out of Jaxx Legacy and Jaxx Liberty wallet before the fork happens.
  • Since we follow a standard protocol in the industry for the security information (BIP 39), any of our users can choose to import their wallet into any other third party wallet that supports the fork.
  • At all times you have full access to your wallet security information: wallet seed  (Jaxx Legacy and Jaxx Liberty) and private keys (Legacy and Jaxx Liberty)

Remain vigilant! There will be many attempts online trying to persuade Jaxx Legacy and Jaxx Liberty users into claiming their forked coins and asking for the wallet backup phrase or the private keys of your Bitcoin Cash address. DO NOT share any of your wallet’s security information with anyone unless you want them to have full access to your digital assets on all blockchains.

Typosquatting, Angler Phishing, and Immutable Theft

The Internet changed  our world. Blockchain is changing it even more, moving things to new terrain all over again. That new terrain has amazing possibilities for decentralizing power and empowering the masses. But it also has dangers. This blog post is about one kind of online danger: phishing and mistaken-identity attacks.

It’s Not Just You

Feel like there are more of those attacks than ever? It’s not just you. And, really, it’s not too surprising. Digital asset transactions on the blockchain are more private, and more permanent, than real-life transactions. Assets are transferred with minimal personal information — and there’s no easy way to take them back. That keeps things simple and portable. But it ups the rewards for anyone who can get assets transferred to them through fraud.

Anyone who’s spent time on public-facing social media like Twitter, Instagram, or the open Web knows how that happens.  “Typo-squatting”, also known as “angler phishing”, is a fraud tactic fuelled by small typographical errors in an account or domain name. Think in-thread replies by a deceptively-similar account on Twitter. Or pro-active Instagram follows by a handle whose image is familiar — maybe the phisher has “borrowed” a brand icon — but whose name is just a bit off.  Or a surprisingly friendly “help desk” reaching out on Telegram to solve all your problems.

An example is included below. Note how the user copies our logo, handle, and cover image, yet the account name is not ours.

Expecting one website, and landing on another one just waiting for that typo, is irritating. But typo-squatting becomes more than just irritating when applied to blockchain assets. Once you’ve been taken in by a scammer’s fake use of a brand logo, slightly misspelled handle, or in-thread reply, it can be impossible to walk the mistake back.

The Trend Hasn’t Exactly Gone Unnoticed

Every social media landscape is now cluttered with fake accounts built from real people’s profile pictures, recognizable brand logos, and nearly-familiar names or handles.  More and more “blue checkmark” personalities add phrases like “doesn’t give away cryptocurrency” to their account names, to set themselves apart from scammers piggybacking on their identities. Last March, Twitter told online publication The Verge it would begin preventing accounts “from engaging with others in a deceptive manner.” Last August, security researchers at Duo Labs published a “case study detailing a large botnet of at least 15,000 bots spreading a cryptocurrency scam”, showing how to identify the scheme.

Three Tips to Help Identify and Avoid These Situations
  1. We never ask for your secret identifiers like your private keys or personal information.  If someone is asking for such things pretending to be us, call them on it. It’s not us.
  2. Our official brand accounts are: @jaxx_io, @jaxx_support, and @DecentralCA, and our Web sites are at and — spelled with just those letters.  All of our accounts are verified, so look for the blue checkmark next to our account names. Check the source, and make sure the Twitter handle or domain name has the correct spelling.
  3. When a phisher solicits you to respond in private — don’t respond. Do report.

We see phishing posts and imposter accounts frequently. We flag them and ask that they be taken down. It can take a few days before these fake accounts are removed, though.  If there are doubts, please don’t engage. If you see a tweet, or profile you know is a scam — consider reporting it and letting us know, too: [email protected] .

Jaxx Does Not Offer Phone Support

We take great pride in offering one of the best, free, multi-platform, multi-currency digital asset wallets in the industry, and with it comes a world-class support system, but we do not offer and have never offered phone support. The Jaxx User Success team believes our written support channels deliver high-quality, responsive help in a way that is fast and clear. This means that our User Success team works around the clock to rapidly assist users through written support channels like email, web tickets and social media.

As such, anyone posing as a member of the Jaxx User Success team with a phone query is not us, so please be aware that is a tell-tale sign of an impostor. Beyond that, please be on the lookout for anyone calling you, pretending to be a member of the Jaxx User Success team. We do not call our users to offer wallet recovery services.

Jaxx Liberty bitcoin wallet ethereum blockchain
Jaxx offers industry-leading world-class support services for free

It is a fact that we cannot actually offer any wallet recovery services as all the wallet security information is only saved locally, on your device, there is nothing saved on any Jaxx server for us to recover for you. Your Jaxx Wallet master seed is generated randomly through an industry standard protocol (BIP39) and by keeping a copy of it safe, you are guaranteed full ownership management of your digital assets.  Please be safe and guard your wallet information and digital assets. Nobody on the Jaxx User Success team will ever request your 12-word Backup Phrase or your Private Keys, which should be stored safely and not shared with anyone you do not want to grant direct access to your digital assets.

We decided to stick to written support only because one clear advantage is that it’s efficient and transparent for a global user base. The Jaxx team does not offer phone support, but it does offer 24-hour free help through written channels if you request it. If you need help, you can choose one of the following options:

  1. Go to and click on Support (in the upper-right-hand corner of your screen) then click on Submit A Request (also in the upper-right-hand corner of your screen)
  2. Tag @Jaxx_Support on Twitter
  3. Post in our subreddit

We have chosen to offer these written communication methods for a reason, and that is to provide users with the very best support experience possible. The Jaxx team does not offer phone support and we have a system in place that serves users well, based on your feedback and best practices. In addition, we have carefully selected the teams that make up the Jaxx User Success department to ensure a rapid and robust solution-focused approach.

Thank you for your continuing trust and support,

Andrei Daniliuc

Jaxx Support Team Manager

Decentral Inc.

Jaxx bitcoin wallet ethereum blockchain iphone
The Jaxx Liberty App

Our team is working on the Bitcoin Cash upgrade in the Jaxx wallet following the May 15th network upgrade

Bitcoin Cash (BCH) is a fork of Bitcoin that supports larger blocks and different opcodes. It is incompatible with the main Bitcoin blockchain and has been diverging from the Bitcoin codebase. On May 15th there was a network upgrade that created a situation where BCH is not compatible with some software that was previously compatible. More specifically, the new version of the bitcoin-abc node software that we use for the infrastructure that powers Jaxx became incompatible and our system is now unable to display new transactions from the Bitcoin Cash network.

The network upgrade for BCH occurred at block #530361. The day after the upgrade we held our “United by Decentral” event for our partners and friends in New York as the official after-party to Consensus Blockchain Summit. At the event,  we announced that on July 1st we will be releasing a new version of Jaxx that we have been developing since the Fall. We’re calling the new version “Jaxx Liberty” and we look forward to getting into the hands of our users as quickly as possible. Although our engineers originally thought that the May 15th change would be a minor upgrade, it has turned to be a bigger challenge than expected. We are working diligently to fix it.  

Bitcoin Cash BCH cryptocurrency digital wallet Jaxx orange decentralization
We are dedicated to resolving the BCH situation in the Jaxx wallet as soon as possible.

The challenge we face is due to the way that Jaxx interacts with blockchains, as opposed to how a user interacts with their own node, with their own wallet on that node. The Jaxx backend infrastructure uses a combination of official daemons and various blockchain indexers, including a proprietary system used for most coins and the Bitpay Insight API service for Bitcoin Cash. We need these indexers to take the data from the official blockchain client and push it into a large database that can be easily accessed by other programs that ultimately serve the data to Jaxx users.

The new version of BCH is not compatible with the Bitpay Insight system that we use for BCH, and new versions have other compatibility issues, so this has required us to investigate a few different approaches: upgrading to the newer beta of Insight, moving to ElectrumX (or another open-source server), moving to a new proprietary system for Bitcoin Cash and adapting our existing proprietary system to BCH. At the moment we don’t have an expected time for delivering this upgrade but we hope it will be within the next week and that we’re able to migrate to a newer version of Insight.

We are working hard to fix this situation so that we can deliver on the promise of Jaxx: a unified blockchain interface for digital assets. We’ve diverted about 20 percent of our development team to work on the BCH issue. In the meantime, your private keys remain safe in Jaxx and once our backend infrastructure is made compatible again with the Bitcoin Cash network you will be able to send and receive BCH again. If you need to transact with BCH immediately you can always export your private keys or mnemonic (found in the MENU > Tools > Backup Wallet > View Backup Phrase) and then import them into another wallet program such as bitcoin-abc. A long-standing tenet of Jaxx has been that your private keys belong to you and we will never lock our users into our platform.

Like many companies in our space, we’re dealing with unexpected challenges, an evolving technical landscape and ever greater demands on our infrastructure. We continue to hire more people to help out with Jaxx development and if you think you’re one of those people we would appreciate you reaching out to [email protected]. We know that we need more people to help deal with the many chains (including Bitcoin Cash) and many tokens in Jaxx, and our ambitious plans for Jaxx Liberty.

Please accept my apologies on behalf of the Jaxx team at Decentral Inc. We’re working hard to bring BCH back online as well as to meet our timeline to bring you Jaxx Liberty on July 1st.


Addison Cameron-Huff

President, Decentral

Jaxx Development Update: version 1.3.8 released on all platforms

Jaxx Version 1.3.8

Jaxx Development Update: version 1.3.8 released on all platforms

Earlier this morning Jaxx v1.3.8 went live on Android, Chrome, Windows, Mac, and Linux. The update to our iOS client has been sent to Apple for their approval. This release includes new features and a few bug fixes of note. Be sure you have your 12-word backup phrase written down before you update Jaxx. New features you’ll find in Jaxx include:

  • ETH Gas Limit Control: you now have more flexibility setting ETH transaction gas limit maximums and minimums. This feature is particularly helpful when participating in ICOs.
  • Paper Wallet: simple functionality has been included to allow you to transfer paper wallets into Jaxx.
  • Pricing Data: we’ve updated the way we manage coin and token prices to be faster and more frequent.

The Jaxx 1.3.8 release includes fixes to a handful of bugs in earlier releases. Those updates include:

  • BTC History: transaction histories for BTC wallets display correct balances.
  • ETC Spendable: spendable balance is checked before allowing a send-transaction. attempt. This forces confirmation available funds match the send request.
  • ETH Balances: ETH wallets now show accurate balances. The bug causing balances to display the actual value divided by 10 has been resolved.
  • ERC20 Spendable:  spendable balance is checked and verified before attempting a send transaction for all ERC20 tokens.
  • ShapeShift Unavailable Message: new pop-up notice in Jaxx on tokens Shapeshift has made “temporarily unavailable” in their service.

You can upgrade your Jaxx client on your favourite platform by visiting our download page today. We value your input – reach out to us on twitter or register a request with our Support team. And always remember: you should write down your 12-word backup phrase and keep it in a safe place.

We will no longer support  devices running Android 4.4 and older.  Users on Android 5.1 or older who have not backed up their 12-word backup phrase and who have also not ever paired their wallet on any of the other platforms Jaxx supports – iOS, Mac, Linux, Windows and Chrome Extension – should reach out to our support team for help.

And always remember: you should write down your 12-word backup phrase and keep it in a safe place.



Jaxx Development Update: Android 5.1

Jaxx Support - android 5.1

Jaxx Development Update: Android 5.1

An announcement from our Development team: Jaxx will no longer be available on devices running versions older than 5.1 of the Android OS. The Android OS releases known as Lollipop were released as early as 2014. Devices running Android OS versions that predate Lollipop (5.1) do not have the ability to handle the latest version of our Jaxx Wallet.

Users on Android 5.1 or older who have not backed up their 12-word backup phrase and who have also not ever paired their wallet on any of the other platforms Jaxx supports – iOS, Mac, Linux, Windows and Chrome Extension – should reach out to our support team for help.


Jaxx Development Update for December 1st 2017

Jaxx iOS

The Jaxx development team here at Decentral Inc. has been busy this Fall. We’re proud of our work offering our application across eight platforms and supporting dozens of exciting blockchain projects. We’ve made significant progress on our mission to deliver the best HD wallet in the world.

Infrastructure: We’ve increased and improved the infrastructure we use to operate nodes on the variety of blockchains we support. This added capacity makes Jaxx faster and more reliable than ever. We’ll continue rolling out new infrastructure (servers and systems) in December as expand to meet & exceed demand for Jaxx wallets.

Security Improvements and User Education: We’ve implemented an optional pin code to more strongly protect our user’s assets. This pin secures access in Jaxx to the screens that display the 12-word Masterseed “backup phrase” (BIP39). Users new to the world of blockchain and cryptocurrencies often do not understand the power of the 12-word Masterseed structure we use in Jaxx. We never hold or control our user’s assets; those assets remain on their respective blockchains and the Masterseed is a powerful tool for controlling them. Adding pin functionality has been a great way to help new users understand how to use their Masterseed to pair their wallets across devices and to understand the Masterseed should be backed-up.

Asset Swapping with Shapeshift: We’ve made UI changes to make the swapping of tokens easier and more intuitive. Control of gas prices and clear confirmations have helped make Shapeshifting assets inside Jaxx easy.

Tokens and Coins Supported:

Several of the tokens supported in Jaxx are not available in any other wallet available on iOS. Tokens and Coins currently live in Jaxx include:

AION / Nuco CVC / Civic EOS GUP / Match Pool
ANT / Aragon CFI / CoFoundIt ETH / Ethereum MLN / Melon
REP / Augur CRB / CreditBit ART / Maecenas MCO / Monaco
BNT / Bancor DPP / DA Powerplay ETC / Ethereum Classic MCI / Musiconomi
BAT / Basic Attention DASH / Dash 1ST / Firstblood PPP / PayPie
BCAP / Blockchain Capital DGD / Digix FUL / Fuel POE /
BTC / Bitcoin DOGE / Dogecoin GNO / Gnosis PRE / Presearch
BCH / Bitcoin Cash DRT / DomRaider GNT / Golem QTUM
LTC / Litecoin EDG / Edgeless ICN / Iconomi RSK Testnet
BCP / Blockmason ENJ / Enjin RLC / iExec RLC ROUND
SLT / Salt STX / Stox UKG / Unikrn
SAN / Santiment SWM / Swarm WINGS / Wings
SNT / Status PAY / TenX WRC / Worldcore
STO / Storm TKN / TokenCard ZEC / Zcash

Looking Forward to 2018: we expect the cryptocurrency and blockchain communities will continue their growth in 2018. The Decentral team will continue to expand the Jaxx platform to support the best and brightest blockchain projects. If you would like to see a certain project supported in Jaxx, do add your voice to others on our social media communities to cast your vote. Find us on or

An Update on BCH in Jaxx


The decentral & blockchain ecosystem has been growing rapidly this year and we’ve been working hard to stay right on its forefront. There are so many tokens & projects we are eager to support. The innovation and creativity we see in this industry are inspiring. This past Spring we began planning a significant expansion of our own infrastructure to support our rapid growth and to facilitate much more rapid integration of new tokens in the future.

Jaxx uses Insight Server – the same service used by several other major platforms. Insight, you may be aware, decided not to support Bitcoin Cash. This left us with a rather lot of work to sync and reindex the BCH blockchain on a completely new system.

This process has taken longer than expected. The BTC blockchain is quite large.

We’re quite close to being complete with BCH integration. We spent most of this past week testing and, as of the end of day Friday, still see performance issues. I promise that when we do release BCH support in our wallet that it will be reliable. User experience & user control are our highest priorities here at Jaxx. The masterseed, the interface and the nodes we run are the source of that empowerment; our team is proud of our platform & we’ll always hold ourselves to these high standards.

We’re not just employees here – we’re users, too, and we’re also anxious to be able to control our BCH in our own Jaxx wallets. We’ll be ready soon. In the meantime, if you received BCH in the August 1st fork and have not moved it off to a different address, that BCH is safe and will be accessible in Jaxx next week.


#BCHinJaxx Update for September 14th:

An update from Nilang, our CTO, and the back-end dev team: Today we’re continuing our work from yesterday in verifying information from our current indexer. We’ve discovered that our method has some limitations due to the amount of data we’re requesting from the client, which is a new issue we’ll need to address, ASAP. It’s likely we will be testing late tomorrow.


#BCHinJaxx Update for September 15th:

Today’s update on BCH in Jaxx: Our efforts yesterday verifying data from the indexer progressed well. We’ve not had any new surprises or challenges and have been able to move forward strongly. We’ll be testing this afternoon.



#BCHinJaxx Update for September 18th:

Today’s update from Nilang, our CTO: “We are continuing testing &  validating transaction data on the BCH chain. Testing on Friday went well but we’re not yet at a point to be confident enough to take it live. Testing continues.”
#BCHinJaxx Update for September 19th:
Yesterday’s testing went well in that we have been able to move through several significant items on our list to confirm. Parsing & indexing has been a challenge. There still remain four significant hurdles for us to clear before we can call ourselves ready to take this code to production. Specifically (our largest issue) surrounds blocks with broken transaction data – how we manage this. Testing continues.



#BCHinJaxx Update for September 20th:

Testing will continue later today after we finish debugging work from yesterday related to our indexing process. We’ve made progress from yesterday but are still not in a place to deploy this code.



#BCHinJaxx Update for September 21st:

Debugging the broken transaction issue in our indexing process continues. We’re well past half-way through the list. We’re still not in a place to take our code to production but we have moved closer from where we were yesterday. We’ll continue sweating today.

#BCHinJaxx Update for September 22nd:

Though we’re not done the debugging work on the indexer we do continue to move forward towards the finish line. In preparation to actually go live we’ve begun testing new transactions and shapeshifting. Our eye is on edge cases & on identifying potential bugs. We continue.

#BCHinJaxx Update for September 25th:

In our edge-case work from last week we’ve identified a new “show-stopping bug” that’ll get our attention today. We’ve a clear path to resolving this one and expect to square it away and be back to testing, pronto.


#BCHinJaxx Update for September 27th:

We’ve deployed a significant upgrade to the Jaxx platform, our version 1.3. This version includes significant backend improvements that the process of integrating BCH into our v1.2 series exposed as necessary. 1.3 removes the largest roadblocks to BCH integration – we do, however, need to do the integration & test it still. This work will begin late in the day today.


#BCHinJaxx Update for September 28th:

Testing of BCH on our new (1.3) release has begun and is progressing well. We’ll not be through it all today and we’re not going to tempt fate by releasing this on a Friday. Could you imagine? We’ll continue testing tomorrow & likely into early next week. Stay tuned, we’re moving forward.

#BCHinJaxx Update for September 29th:

We pick up today right where we left off yesterday. Regardless of how well it goes we’ll not be releasing it on a Friday afternoon. We’ll keep pushing and update you again Monday morning with out plans for the week.



#BCHinJaxx Update for October 2nd:

Good Monday morning – we didn’t get ourselves to a testable release on Friday – we continue our work here today with that goal.



#BCHinJaxx Update for October 3rd:

Testing BCH in our 1.3 continues well. We’ve completed testing on the server side and have moved to our front end tests. Progress.



#BCHinJaxx Update for October 4th:

Testing has gone well enough that we’ll be starting a build that includes BCH. This build won’t be released today – but assuming it goes well, we will release BCH in our Chrome & Android versions, tomorrow.



#BCHinJaxx Update for October 5th:

In order to initialize your BCH wallet in Jaxx you will need to update your instance of Jaxx to the most recent 1.3.2. BCH will not be supported in older versions of Jaxx. We have included code dependencies necessary for BCH support in our 1.3.2 release but we have not enabled BCH YET. We have a small amount of testing remaining before flipping that switch. Depending on how those last tests go tomorrow, we may be in a position to enable BCH before the weekend. If not – we will inform you – we will look to make this release next week.



#BCHinJaxx Update for October 6th:

It will have to be next week; for now we’ll wish you a happy (Canadian) Thanksgiving. We’ll be back in our office and working towards BCH releases Tuesday 10th October.


#BCHinJaxx Update for October 10th:

We’re back in the saddle after a long holiday weekend. We’ll continue pushing to test and verify BCH in our 1.3 release. We’ll keep this post updated as work progresses through the week.


#BCHinJaxx Update for October 17th:


It’s been a week since we last posted our daily update; we’ve been quiet but we’ve been working. We’ve got BCH completed and incorporated into the front end of our 1.3 releases. Before we will activate it in your wallet, however, we still have work to do on the back end BCH nodes. That work is ongoing – see below for specifics on what we’re doing, right from the keyboards of our developers on the project.

In plain language, we are pursuing two development solutions concurrently to solve our problems indexing and parsing the BCH chain.

*10th October:*
– Writing a tool that will repair BCH addresses that incorrectly show zero-balance due to bad indexing
– Address diagnostics for correct balance verification addresses.


*11th October:*
– Writing a tool for converting addresses between BCH and BTC formats, which is the main reason for addresses giving no balance.
–  Writing a parsing tool for the blockchain to have a functioning parser.


*12th October:*
– Created base utility which makes rpc calls against the BCH blockchain and maximum number of blocks.
– Added logic for converting block index into block hash and reading the block. Parsed result to create a cache for both block details and transactions. Worked on inserting the cache into MySQL, having an issue with BLOB inserts.


*13th October*
– Resolved binary/BLOB conversion issues; working on bulk MySQL updates.
– Resolved MySQL bulk insertions and ran through insertion tests. Hit an RPC timeout issue.
– After team discussion, we put retry logic into the new tool and it started processing; this isn’t returning all the transaction details. Trying a REST API call instead.  

– Investigated call and will experiment further once first experiment completes.
– Turned on the REST API and started updating the indexer to extract the transaction details.

*16th October*
– Updated schema to reflect changes made on Aurora; removal of 32 byte hash transaction and BLOBs.  Tested REST API block call, started to add support for vin and vout entries.
– Writing parsing routines for vin and vout.
– Completed vin/vout code, rewrote and tested caching system (for MySQL updates) and started import.
– Working on empty vout values, code currently errors and skips over.



#BCHinJaxx Update for October 18th:

Work continues in earnest on our two production solutions surrounding the indexing of, and interacting with, BCH. We’ve also begun a third, experimental, approach. Notes from our dev teams on these projects:

– Input indexing and tests
– Modified indexer to account for new data model from yesterday
– Checking addresses on BCH Insight to see how they’re built
– Working on tool to build addresses according to different formats

– R&D on indexer infrastructure
– Developing Performance Profiler
– Multithreaded I/O scheduler




#BCHinJaxx Update for October 19th:

We’ve been updating our cloud architecture to use Insight’s bch implementation api.  Specifically we’ve been compling their api and the necessary supporting libraries. We’ll then be building the bch blockchain such that we can do indexing & query the blockchain in a more useful manner.

A more specific rundown from one of our devs: “Looked into what is required for Insight configuration to support BCH. Continued with Insight configuration; modified configuration but decided to wait on re-indexing for the moment while I copied BTC blockchain to a separate directory in order to experiment with Insight. Had unexpected “stat” issues when copying the files but was finally able to copy and verify. As requested, looked into removing blocks after BCH, found a possible solution but will need further work. Bottom line parse the block files, look for height 478558 and delete everything after (including 478558). As a backup, started compressing my local copy of BCH. Received docker file and started to look at Insight integration – wasn’t able to find direct docs.




#BCHinJaxx Update for October 20th:

With respect to the Insight implementation mentioned: node is running but API not responding correctly. Suspect configuration issue – will address this today. Other specifics:

– Output spending: verification of outputs, will go more in depth tomorrow once the master list of addresses is on-hand.
– Modified stored procedures according to data model changes
– BTC/BCH address adapter (this is work in progress)

With respect to R&D:

1. R&D on indexer infrastructure
1.1. Refactoring
1.1.1. Tooling
1.1.2. Architecture/cleaning
1.2. Benchmarking
1.2.1. Current RPC offering (slow)
1.2.2. Direct reading




#BCHinJaxx Update for October 23rd:

– Running address tests and Working on the algorithm for BTC -> BCC address conversion
– Tooling, Benchmarking, and Profiling; reviewing mathematically formal cases

We’ve been preparing end-to-end test cases for tomorrow. We’re excited and looking forward to the outcomes of those tests.




#BCHinJaxx Update for October 24th:

We’ve begun testing BCH in the wallet. In our primary production solution for BHC: Indexing is complete and we left the tester running overnight to get a good batch of results to review this morning. In today’s tests we’ve been seeing transaction mempool conflicts and another issue in the front end where a GET to the tx/send endpoint doesn’t update transaction history.

Development of our secondary production system continues. From our lead developer on the project: “Verified BCH state – completed 70% of the blockchain loading; very slow. Then resolved BCH Claim issue when still attempting to claim after a successful txn, added transactions messages and removed commented code.”




#BCHinJaxx Update for October 25th:

* AWS Volume expansion for staging: researched best practices for AWS Volume resizing; worked out a series of steps to update the AWS staging volume. Started to shutdown the staging instance but found the “delete-on-termination” flag was set to TRUE. Found an article that describes how to update an already running instance but the tone suggested it “should” work. Decided to do the snapshot without bringing down the instance. Instead of resizing the root volume, will create a new volume from the snapshot and mount it to staging instead; this is the preferred approach. Created new volume from snapshot, updated mount point and restarted BCH Insight daemon. Finally, end-to-end Insight BCH testing.

* Testing BCH transactions send receive process, Coding transactions parser, confirmations counter, Balances updater.




#BCHinJaxx Update for October 26th:

Today we have been:

– Made utxo call not return utxos that are spent in a transaction in the mempool
– Included unconfirmed txs in transaction list call
– Working on unconfirmed transaction details call more fully (this remains in-progress)
– Reviewed BCH Claim process and raised points regarding the reason we decided to query BTC instead of only from BCH. Will explore this deeper tomorrow.
– Spent time going through BCH performance changes for claim calculation. Still need to confirm on waiting until restore history completes before starting the next.
– Preparing for further BCH Insight end-to-end testing. (BCH Insight responds to all queries; however, all the values are zero. The Bitcoin_ABC version of the blockchain does contain the correct values but unsure why Insight isn’t picking it up – more work here is required.
– Wallet-side will need some code changes to handle emergency switch overs (once Insight is working stably). More importantly will need to discuss changing the version byte to prevent users from unintentionally sending BCH to a BTC wallet or BTC to a BCH wallet. Continuing to looking Insight BCH to determine why the queries are having an issue.




#BCHinJaxx Update for October 27th:

– resolved the UTXO / mempool issues
– resolved unconfirmed transaction issues
– explored BCH claim process; preparing for exception testing next week
– explored “The zero problem” from yesterday; despite Insight indicating the synchronization was finished, it wasn’t. So test cases were referencing data from yesterday which wasn’t available yet. Planned management of this and set re-testing plans for Monday.




#BCHinJaxx Update for October 30th:

Today we’ve been pursuing BCH in Jaxx with:

– R&D on indexer infrastructure with byte-level parsing of the blockchain.
– Benchmarking REST API
— Testing REST API block call, doing some basic initial benchmarking and looking into possible parsing solutions
– Discussing possible parsing solutions, including the byte-level experiment.
– Looking into mempool failure issue, causes, possible solutions and approaches
— Determined to increase memory for the moment and possibly use a stream to parse the resulting JSON. This will be tested ASAP.
– Checked status of BCH Insight, read up on November 13 target changes for Bitcore ABC and spun up a new instance to test Bitcore ABC 0.15.1




#BCHinJaxx Update for October 31st:

– Solved the mempool failure issue;
– Completed front-end test cases;
– Rolling out new Insight instance compliant to BCH 13th November changes (will continue this, tomorrow)
– Completed benchmarking REST API; update discussions of parsing solutions held with key team members; adjusted and outlined next-steps for work here.




#BCHinJaxx Update for November 1st:

– Documentation; prep’ing for new-hire onboarding
– BCH version update (see this news site for details on 13th november updates  )
– Testing transaction sending; unconfirmed balance fluctuation during/after send. Found the problem with data inconsistency; developing solution to this bug will be straightforward




#BCHinJaxx Update for November 2nd:

– We believe we’ve got our primary solution to a BCH back end operating smoothly enough to take it to production.
— To that end we have begun both user acceptance testing and regression testing on all eight platforms users can interact with Jaxx on. We will be thorough with this before we push live into production.




#BCHinJaxx Update for November 3rd:

– User acceptance testing continues to go well – we’re half-way through these tests. Work will continue Monday.
– Regression testing across all 8 platforms we support also has progressed well and without errors today. We’re not-quite to half-way through these tests.





#BCHinJaxx Update for November 6th:

We’re excited to announce that both Front-end and Back-end testing has gone well and we are progressing with a staged roll out of BCH to our user base.

The roll out will occur in stages to help us manage the load we expect to see created from the over 400,000 Jaxx users. The stages will progress as follows:

November 6th: a large block of Chrome and Android users will see BCH support in Jaxx.

November 7th & 8th: increased numbers of Chrome and Android users will see support for BCH in Jaxx. All users of the Mac, Windows and Linux Desktop Jaxx Applications will see support for BCH.

November 9th: all users on Desktops, Android and Chrome will see BCH support in Jaxx.

An update to the Apple App Store will be made shortly; at the time of this post we have yet to submit the iOS update to Apple for approval.

Recall: you are in complete control of your assets through their private keys. You should back-up your 12-word Masterseed to be sure you never lose access those assets. Your keys, your funds, and your wallets are all in your control; we do not have access, ever. You should write down your 12-word Backup Phrase found by touching Menu > Tools > Backup Wallet and store that phrase in a safe and secure place. Conveniently, this phrase is all you need to pair your wallet from one platform to another.




#BCHinJaxx Update for November 7th:

We can report that the staged roll-out of BCH in Jaxx is proceeding as planned. Another large group of Android and Chrome users have access today; all users of Mac, Windows and Linux desktop users have access today. Further roll-out to Android and Chrome will follow tomorrow.




#BCHinJaxx Update for November 8th:

We’ve rolled out BCH to another large block of Android and Chrome users. The staged roll out process is going well – we’ve not had any significant issues.

You might see issues claiming BCH in Jaxx if you have a PIN active protecting the wallet. A hotfix was built today and will be released this afternoon; the workaround is to temporarily disable the PIN on your wallet and claim the BCH without the PIN active. Touch: MENU > Settings > Setup Security PIN




#BCHinJaxx Update for November 9th:

We’ve expanded the roll out per our plan, again. Most users of Jaxx have access to BCH now. Three items to be aware of:

– the hotfix solution to the security PIN preventing BCH claims has been implemented and works. This is no longer an issue.

– an update to our iOS app for Apple users is pending approval with Apple. This will be available to download shortly – keep an eye on your App Store updates section.

– You need to be running the latest version of Jaxx (that’s v 1.3.6). Once you are running 1.3.6, simply touch Menu / Wallets / BCH to initialize your BCH wallet. Once initialized you will be able to view your wallet and touch ‘claim’. Wait for a few moments for the balance to show up – approximately 3 minutes.




#BCHinJaxx Update for November 10th:

We’ve continued our roll out of BCH to new block of users. We’ve been keeping a close eye on our BCH backend as transaction load has increased. BCH transaction volume is up – we’re paying close attention this weekend and will continue our roll out Monday.




#BCHinJaxx Update for November 13th:

Good morning – a short note to confirm that we are 100% rolled-out with BCH on our Chrome Extension, Android, Mac, Windows and Linux desktop versions. iOS will follow shortly.

Recent Issues with the Chrome Extension and New Fix Live

To meet the Civic token distribution window, we pushed an update to our Chrome Extension and Android users that enabled the Civic wallet in Jaxx on Sunday afternoon. Following that release, we started receiving feedback from our users regarding balance issues on a number of coins (LTC, ZEC, DOGE) where their balance was showing up as zero but the crypto to fiat exchange conversion was displaying correctly. This was just a display issue and all funds were unaffected.

Being able to replicate the issue, our development team dived into research and a potential fix and eventually decided to temporarily rollback the Civic integration so that our users could see their correct balances again. That was an all night endeavor (research, potential fix, decision to rollback) and on Monday morning, we pushed the new fix.

The Android app worked as expected but we started seeing issues with the Chrome version being completely unusable and automatically disabling itself from our users’ browsers. We did not experience this during our QA process and to this moment, we have not identified the reason as to why we are seeing this issue on Chrome. Again, during our internal testing, everything worked as expected.

This brought us to the point where everyone trying to use the Chrome extension was unable to do so due to the unknown Chrome Webstore propagation issue. Our users would see this message when checking their extensions list (by typing chrome://extensions in the address bar):

Some of our users might have tried to fix the Chrome extension by clicking the Repair button (as shown above) that their browser was offering or completely uninstalled and reinstalled the extension. Both of these processes erases Jaxx so do not click Repair in your Chrome settings. If you clicked ‘Repair’ and uninstalled your app, you will need to Pair / Restore Wallet via their 12-word Backup Phrase to regain access to their wallet.

We have issued announcements throughout our support platform and social media channels as soon as we understood that this could impact our users (even before the actual update was pushed yesterday) in order to prevent our users from being disconnected from their wallets.

We have since pushed out a temporary fix to the Chrome Webstore. Once the update is downloaded, the Jaxx Wallet should be fully functional and previous information restored.

If you are still seeing version number 1.2.20 and an error message in your chrome://extensions page you will need to force an update by enabling the Developer Mode and clicking the Update extensions now button at the top of the page:

If you uninstalled the extension and re-installed it, you will experience the same issue unless you update to v. 1.2.21. When deleting an extension, the related information is cleared as well, so the wallet needs to be restored / paired via the 12-word Backup Phrase.

If you clicked on Repair, a re-download process would have happened just as above, and Pair / Restore Wallet via the 12-word Backup Phrase is needed as well.

If you happened to only use Jaxx on the Chrome Extension and do not have a copy of your 12-word Backup Phrase please reach out to our support team here.

Jaxx 1.0.5 released with adjustable BTC fee for added flexibility

If you’ve been paying attention to Bitcoin network activity over the last couple of days, you’ve undoubtedly noticed that it’s spiked to levels not seen in over two years. That’s great news for BTC holders, but a pain for wallet users who have seen their transactions take longer and longer. With the release of Jaxx 1.0.5, this will no longer be an issue.


Jaxx 1.0.5 adds the option to select a “Slow,” “Average,” or “Fast” fee level, all of which are dynamically adjusted based on the level of current network activity. Now, users who are unconcerned with speed don’t have to face heftier transaction fees, while power users can ensure that their transactions will be accepted by the network very quickly.


What we have in place is not a perfect solution, but we felt it was important to update our current options so that current Jaxx users won’t be faced with interminable wait times for BTC transactions. In future, we will also be adding Custom fee option, allowing users to specify their fee well above or below even Jaxx’s recommendations. 


Previously, we had a floating fee rate based on the current transaction filesize, but this new solution is more effective for handling the current state of the Bitcoin network.


As per usual, iOS users will have to wait a little longer for Jaxx 1.0.5 due to Apple’s length app review process. If there was anything we could do about it, we would!
Get all versions of Jaxx at