# Vexanium Protocol

### Core[​](https://docs.eosnetwork.com/docs/latest/protocol/#core) <a href="#core" id="core"></a>

`VEXCHAIN Core` provides the basic building blocks for the `system` layer and because they are not implemented as smart contracts they do not provide the same level of flexibility. Nevertheless, the `core` implementation is also open source and thus it can be modified as well to suit custom business requirements.

The core protocols are:

1. Consensus Protocol
2. Transactions Protocol
3. Network or Peer to Peer Protocol
4. Accounts and Permissions

### System[​](https://docs.eosnetwork.com/docs/latest/protocol/#system) <a href="#system" id="system"></a>

The VEXANIUM blockchain is unique in that the features and characteristics of the blockchain built on it are flexible, that is, they can be changed, or be modified completely to suit each business case requirement. Core blockchain features such as consensus, fee schedules, account creation and modification, token economics, block producer registration, voting, multi-sig, etc., are implemented inside smart contracts which are deployed on the blockchain built on the VEXANIUM blockchain. These smart contracts are referred to as `system contracts` and the layer as the `VEXANIUM system` layer, or simply `system` layer.

VEXANIUM Network Foundation implements and maintains these `system contracts`, as samples only, encapsulating the base functionality for an VEXANIUM based blockchain and they are listed below:

1. eosio.bios
2. eosio.system
3. eosio.msig
4. eosio.token
5. eosio.wrap

Also part of the `system` layer are the following concepts:

1. Account
2. RAM
3. CPU
4. NET


---

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