> For the complete documentation index, see [llms.txt](https://docs.smartbch.org/smartbch/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.smartbch.org/smartbch/developers-guide/intro.md).

# Introduction

Currently, there are no toolkits dedicatedly designed for smartBCH. Please use the tools from Ethereum's ecosystem (Remix, truffle, waffle, ganache, etc) to develop the source code and compile the EVM bytecode. After the DApp works fine on ganache, you can start testing it with smartbchd (the executable of smartBCH's full node client), which can [start a single node private testnet](/smartbch/archives/runsinglenode.md), or a [multi-node testnet](/smartbch/archives/runmultinode.md)

Through a compatible Web3 API, smartbchd interacts with the wallets (such as MetaMask) and DApp's backend, just as an infura node does. We try our best to make it behave the same as infura for compatibility, but there are still missing features and bugs.

For a list of supported RPC endpoints, please see [here](/smartbch/developers-guide/jsonrpc.md).

We also provide a [backend design](https://github.com/smartbch/BasicExplorer/tree/main/backend) of blockchain explorer for smartBCH. It just has basic functions and is not so powerful as etherscan. If you wants to add a frontend to build a complete explorer, this [API document](https://github.com/smartbch/docs/blob/master/developers-guide/browserapi.md) may help you.

If you find a mistake in the document, please tell us by create an issue at <https://github.com/smartbch/docs/issues>. If a missing feature blocks you, we are sorry but you need to modify your application to bypass it.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.smartbch.org/smartbch/developers-guide/intro.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.