<commit_before># *insight API*

*insight API* is an open-source bitcoin blockchain REST
and websocket API. Insight API runs in NodeJS and use LevelDB for storage. 

This is a backend-only service. If you're looking for the web frontend application,
take a look at https://github.com/bitpay/insight.

*Insight API* allows to develop bitcoin related applications such as wallets that 
require certain information from the blockchain that bitcoind does not provide.

A blockchain explorer front-end have been developed to top of *Insight API*, it can
be downloaded at [Github Insight Repository](https://github.com/bitpay/insight).

## IMPORTANT: Upgrading from  v0.1 to v0.2
In order to optimize some queries, the key-value layout in Level DB has been changed.
If you are running v0.1.x, a total resync needs to be done, running `$ util/sync.js -D`. This
needs to run while *insight-api* is shut off. See details at: **Synchronization**.


## IMPORTANT: v0.2 Caching schema

In v0.2 a new cache schema has been introduced. Only information from transactions with
INSIGHT_SAFE_CONFIRMATIONS+ settings will be cached (by default SAFE_CONFIRMATIONS=6). There 
are 3 different caches:<commit_msg>update readme 2<commit_after># *insight API*

*insight API* is an open-source bitcoin blockchain REST
and websocket API. Insight API runs in NodeJS and uses LevelDB for storage. 

This is a backend-only service. If you're looking for the web frontend application,
take a look at https://github.com/bitpay/insight.

*Insight API* allows to develop bitcoin related applications such as wallets that 
require certain information from the blockchain that bitcoind does not provide.

A blockchain explorer front-end have been developed to top of *Insight API*, it can
be downloaded at [Github Insight Repository](https://github.com/bitpay/insight).

## IMPORTANT: Upgrading from  v0.1 to v0.2
In order to optimize some queries, the key-value layout in Level DB has been changed.
If you are running v0.1.x, a total resync needs to be done, running `$ util/sync.js -D`. This
needs to run while *insight-api* is shut off. See details at: **Synchronization**.


## IMPORTANT: v0.2 Caching schema

In v0.2 a new cache schema has been introduced. Only information from transactions with
INSIGHT_SAFE_CONFIRMATIONS+ settings will be cached (by default SAFE_CONFIRMATIONS=6). There 
are 3 different caches:
{'fraction_non_alphanumeric': 0.06798153587914393, 'fraction_numerical': 0.01049097775912715, 'mean_word_length': 4.505773672055427, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 4, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '153984', 'n_tokens_mistral': 709, 'n_tokens_neox': 677, 'n_words': 331}