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

# Vexanium Toolchain

Vexanium platform provides a number of components and libraries which are used to operate blockchain nodes, collect blockchain data, to interact with these nodes, and to build smart contracts.

The VEXANIUM blockchain is made up of the following components and toolchain.

1. `nodeos`: the core VEXANIUM (VexChain) node daemon that can be configured with plugins to run a node. Example uses are block production, dedicated API endpoints, and local development.
2. `cleos` or `clivex`: (CLI + VEX = `clivex`), the command line interface to interact with the blockchain and to manage wallets.
3. `keosd`: the component that securely stores VEX keys in wallets.
4. `VEX.CDT`: the Contract Development Toolkit is a C/C++ toolchain targeting WebAssembly (WASM) and a set of tools to facilitate development of smart contracts written in C/C++ that are meant to be deployed to the VEXANIUM blockchain.

The basic relationship between these components is illustrated in the following diagram.

<figure><img src="/files/4ZHLj9q2JwDUftHZX017" alt=""><figcaption><p>VEXANIUM Development Lifecycle</p></figcaption></figure>

{% hint style="info" %}

#### Note

VEXANIUM also provides a library for javascript development called `vexaniumjs` together with Swift and Java SDK for developing mobile applications natively.
{% endhint %}

### **Node OS** <a href="#nodeos" id="nodeos"></a>

`nodeos` is the core VEXANIUM node daemon. Nodeos handles the blockchain data persistence layer, peer-to-peer networking, and contract code scheduling. For development environments, `nodeos` enables you to set up a single node blockchain network. `nodeos` offers a wide range of features through plugins which can be enabled or disabled at start time via the command line parameters or configuration files.

You can read detailed documentation about `nodeos` at here.

### **Cleos/Clivex**

`cleos` or `clivex` is a command line tool that interfaces with the REST APIs exposed by `nodeos`. You can also use one of them to deploy and test Vexanium smart contracts.

You can read detailed documentation about `cleos` at [here](broken://spaces/CZNVNWNLqWkyBEBOg8PH).

### **Keosd**

`keosd` is a key manager daemon for storing private keys and signing digital messages. `keosd` provides a secure key storage medium for keys to be encrypted in the associated wallet file. The `keosd` daemon also defines a secure enclave for signing transaction created by `cleos` or a third party library.

{% hint style="info" %}

#### **NOTE**

`keosd` can be accessed using the wallet API, but it is important to note that the intended usage is for local light client applications. `keosd` is not for cross network access by web applications trying to access user's wallets.
{% endhint %}

You can read detailed documentation about `keosd` at here.

### **VEX.CDT**

VEX.CDT is a toolchain for WebAssembly (Wasm) and a set of tools to facilitate contract writing for the Vexanium blockchain. In addition to being a general-purpose WebAssembly toolchain, VEX-specific optimizations are available to support building VEXANIUM smart contracts. This new toolchain is built around Clang 7, which means that VEX.CDT has most of the current optimizations and analyses from LLVM.

You can read more about `VEX.CDT` at here.

### **VEXANIUMJS**

A Javascript API SDK for integration with the VEXANIUM blockchain using the VEXANIUM RPC API.

#### **What's Next?**

Core Concepts: Learn about VEXANIUM's core concepts.


---

# 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.vexanium.com/overview/vexanium-toolchain.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.