# 6.1. Protocol & Smart Contract

The 4IR Token will be created and presented for the Public Presale on the “Bitbond” token tool platform (<https://www.bitbond.com/>) on the Ethereum Protocol. The Ethereum protocol has provided popular and sound software frameworks for the creation of crypto-tokens, their so-called token standards, which BlockchainValley’s native and general-purpose crypto-token, the 4IR Tokens will be based on. The 4IR Token will be built on top of the Ethereum blockchain using the ERC-20 open source smart contract framework for token standards. This token standard has become the industry standard for the issuance of tokens and has proven to be the best solution, because of the robustness of the software and the variety of existing support tools such as wallets, exchanges and additional smart contract frameworks.&#x20;

The 4IR Token will be launched and therefore being usable on Uniswap just after the end of the Presale in IDOs using several Dex exchanges and deployed in a multi chain approach, being the Public Presale the first one, up to eight different Blockchain platforms. All subscribers on the Presale Period will be able to use their 4IR Tokens once they are listed and launched from the first IDO.

There will be a smart contract which will manage the distribution of the tokens.

The 4IR Tokens may switch from Ethereum to 4IR Blockchain Protocol, in the conditions described in Section 3.6.2 “[OBJECTIVE: Blockchain technology of the 4IR Blockchain Protocol](https://docs.google.com/document/d/1E_5uCXKo9JJh4b_XJlL9clAxnxx4niFH/edit#bookmark=id.3gnlt4p)”.

<br>


---

# 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://4irtoken.gitbook.io/blockchainvalley/6.-the-technical-procedures/6.1.-protocol-and-smart-contract.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.