DFINITY Foundation

Internet Computer Association

Synapse.vote (formerly ICP Maximalist Network)

Arthur’s Neuron (used to be cycle_dao)

ICDevs.org

CryptoIsGood

Anvil

ICPL.app

The Fools' Court

ysyms

The Accumulators’ Neuron

RawTech Venture

Paul Young

ICPMANUAL

8yeargangDAO

John Wiegley

Isaac Valadez

Krzysztof Żelazko

Always Rejects

Nicolas.ic

Smaug’s Neuron for Retail Investors

# Bitcoin Integration: Install the `uploader` canister.

As mentioned on the [forums](https://forum.dfinity.org/t/direct-integration-with-bitcoin/6147/619), this is the first of three proposals to deploy the Bitcoin mainnet canister.


The [uploader canister](https://github.com/dfinity/bitcoin-canister/blob/launch/bootstrap/uploader/src/main.rs) is what we'll be using the upload the pre-computed Bitcoin mainnet state. Once the `uploader` canister is deployed, we can upload “chunks” of the bitcoin canister’s state using ingress messages. The uploader canister is initialized with the hashes of the bitcoin mainnet state to verify their correctness, meaning that this proposal fully controls the state that will be uploaded. [Here](https://github.com/dfinity/bitcoin-canister/blob/launch/bootstrap/uploader/src/chunk_hashes.txt) you’ll find the hashes of the chunks, which are [hard-coded](https://github.com/dfinity/bitcoin-canister/blob/a5fd086/bootstrap/uploader/src/main.rs#L21) in the `uploader` canister.


## How can I verify the Wasm hash of this canister?

* Clone the [bitcoin-canister repo](https://github.com/dfinity/bitcoin-canister).
* `git checkout fdfced51d002d7f16908642f29216a869ecd3627`
* Run `docker build -t canisters .` to build the canisters and output their Wasm hashes.

You should then see the following in the output:

```
20b7866d8a4eb6ee53caaa21b2a531b7541c83500f09d91d750e7aca733973c1  uploader-canister.wasm
```

## How can I verify the state that will be uploaded?

If you’d like to compute the Bitcoin canister’s state for yourself to verify the correctness of these hashes, please follow the instructions [here](https://github.com/dfinity/bitcoin-canister/tree/master/bootstrap), setting the `HEIGHT` to `764684`. Note that the computation takes around 24 hours. At different points in the computation process, the checksums of various files are emitted. If everything is working as expected, you should see the following checksums:

```bash
sha256sum unstable_blocks
c62e653e80c11c5463cfd24af8d26eef4392d6b9600ab6278d61f29f159c1e1a unstable_blocks

sha256sum block_headers
b7047039bccb1eb81c7df97ba4dcd04ae6163277909bcded7789b73512e29544 block_headers

sha256sum utxodump.csv
ec09112894aad807b90f9991be76105e41e9038687b59dce5a1aaadcedf52ddc utxodump.csv

sha256sum utxodump_shuffled.csv
9730fddcf70afc60bfb94d0bcddd82b2e807cf57842733176dec1d31b0dedc05 utxodump_shuffled.csv

sha256sum canister_state.bin
1cf90cc7abdd859be021f35e1066965b7d1f23add33ddc4650ff3d27663211ec canister_state.bin
```

Once you’re done with the instructions, you’ll have a file called `chunk_hashes.txt`, which should be identical to the hard-coded `chunk_hashes.txt` file in the `uploader` canister.

```bash
git switch launch # switch to the launch branch.

# The chunk hashes you computed and the ones hard-coded in the uploader canister
# should be identical.
diff chunk_hashes.txt ./uploader/src/chunk_hashes.txt
```


Upgrade Nns Canister: ghsi2-tqaaa-aaaan-aaaca-cai to wasm with hash: 20b7866d8a4eb6ee53caaa21b2a531b7541c83500f09d91d750e7aca733973c1