# Bitcanna

<figure><img src="https://pbs.twimg.com/profile_images/1455116847024586757/T9o06sNM_400x400.png" alt="" width="188"><figcaption></figcaption></figure>

BitCanna aims to solve a problem that has plagued the cannabis industry from its inception. Companies like Visa and MasterCard deny cannabis companies access to their services due to the legal status of marijuana. Since the legality of the herb is regulated differently in European countries, the industry leaders operate in gray areas. BitCanna wants to solve this problem by providing a decentralized blockchain network that is specifically designed for the cannabis industry and provides much-needed services to both consumers and businesses.

***

## [STAKE WITH INDONODE](https://explorer.indonode.net/bitcanna/staking/bcnavaloper1603vvkelz5e54lqleya8kzcf7lydx98v5tcusp)

***

### Links

[Website](https://www.bitcanna.io/) | [Twitter](https://twitter.com/BitCannaGlobal) | [Discord](https://discord.gg/XDUSpFn6rN)

***

<table data-full-width="false"><thead><tr><th>Version</th><th>Chain-id</th><th>Wasm</th><th data-hidden>WASM</th></tr></thead><tbody><tr><td>v2.0.3</td><td>bitcanna-1</td><td>DISABLED</td><td>DISABLED</td></tr></tbody></table>

<details>

<summary>More Summary</summary>

* Binary Name : bcnad
* Binary Home : $HOME/.bcna
* Denom : ubcna
* Exponent : 6

</details>

Peer

```sh
d068226de69f0e14ff34e393a199137a44b0398d@rpc.bitcanna.indonode.net:11656
```

Endpoint

* rpc.bitcanna.indonode.net
* api.bitcanna.indonode.net
* grpc.bitcanna.indonode.net:11090

Addrbook

```sh
curl -Ls https://snapshots.indonode.net/bitcanna/addrbook.json > $HOME/.bcna/config/addrbook.json
```

***


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.indonode.net/mainnet/bitcanna.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.