System Architecture

The BitCache system architecture aims to maintain a cache layer of all your blockchain transactions (regardless of which wallet or application interface you use). The idea is to create the cache at the time of transaction creation/settlement to avoid having to filter through every single network transaction. Note that network scanning/indexing can still be done to repopulate your BitCache in the case of disaster recovery.

Using Bitcoin without a cache layer is like using a computer without a cache or RAM layer. The CPU has to read from and write to the hard disk (blockchain) without any "working memory" - painfully slow and expensive.

With your onchain data, you have two options:

1. scan all network transactions after they are settled onchain, then filter and index the ones you need (EXPENSIVE - needs to scale as blockchain scales)

2. cache transactions you need as they get settled onchain (CHEAP - only scales with your data usage)

As shown in the diagram above, all of the interfaces you use to create new Bitcoin transactions - whether they are different wallet interfaces, different devices, or different Bitcoin applications - notify your BitCache of those transactions so that they are saved/cached to be used whenever and wherever you want, seamlessly.

Data Dashboard

Since you now have all of your onchain transactions in one place, for the first time, you can have the ability to view (without necessarily controlling) all of your transactions in one dashboard or screen.

In this dashboard, you can now see for instance that today you've created and/or received 24 payment transactions, 15 token transactions, 11 lockup transactions, 9 bSocial transactions, etc.

This allows for the ability to view your data (transactions) from an "admin dashboard" where you can control everything in one place, as well as a "watch-only dashboard" where you can view everything but not control anything, or even go as granular as you like with difference permissions for different interfaces.

This changes the paradigm from transactions being platform-based into being function-based. What this means is that since you can view and use your transactions from any interface, it doesn't matter that these transactions are "HandCash" or "RelayX" transactions, it only matters what function they serve, such as payment or token transactions.

Function-Based Vs. Platform-Based Wallets

In addition to moving towards function-based transactions, we will shift towards function-based wallets as opposed to platform-bassed wallets. This is a paradigm shift since I will no longer think of my wallets as my "HandCash wallet" or my " ElectrumSV wallet" and instead think about my "mobile wallet" or my "savings wallet" or my "social media wallet" etc.

Open Protocol

BitCache is released as an open protocol so anyone can run their own BitCache instance or use a hosted instance.