# Welcome to the I/O Coin Wiki!

This wiki has been made by to community for the community to provide information and documentation about the I/O Coin blockchain and how to use its many features.

Do you have any feedback or suggestions for this wiki? [Contact us](https://i-o-digital-foundation.gitbook.io/ioc/contact-us) here and let us know!

## Technical Specifications <a href="#technical-specifications" id="technical-specifications"></a>

| Network            |                             |
| ------------------ | --------------------------- |
| Genesis Block      | Fair Launch July 24, 2014   |
| Consensus          | POS CiPher                  |
| Max. Block Size    | 4MB                         |
| Max Data Per Block | 1MB                         |
| Block Time         | \~Variable 60 to 15 seconds |
| P2P Port           | 33764                       |
| RPC Port           | 33765                       |

| Coin                                          |                                      |
| --------------------------------------------- | ------------------------------------ |
| Current Supply                                | 21,767,656                           |
| Staking Rewards                               | 1.5 IOC per block + transaction fees |
| Number Of POW Coins                           | 16,000,000                           |
| 1 Year Inflation per 60 sec Blocks            | 788,400                              |
| 30 Year Max Supply per Constant 60 sec Blocks | 42,376,480                           |
| 30 Year Max Supply per Constant 15 sec Blocks | 107,419,480                          |

## Project History <a href="#project-history" id="project-history"></a>

After years of PoS proof-of-concept testing and blockchain penetration testing, the I/O Coin development team, lead by its founder Joel Bosh, devised a unique approach to Proof-of-Stake and they started working on I/O Coin. The team opted for a Fair Launch which meant that there would be no ICO and that there would be no coins reserved for the development team. To ensure fair distribution, I/O Coin was launched via X11 Proof-of-Work mining and after 12815 blocks (14 days) the blockchain successfully transitioned to its unique Proof-of-Stake mechanism. The Genesis Block was mined on July 23rd 2014 and for the first 30 blocks the mining reward was 625 IOC, after which the block reward was doubled to 1250 IOC per block, totalling to exactly 16 million PoW I/O Coins. To keep the launch of I/O Coin fair, the dev team did not participate in the mining period.

Since then and over the las 6 years, the development team managed to add several features to the I/O Coin blockchain code without the need of any smart contracts and thus maintaining the high level of security and privacy. Some of these features are:

* Shade Addresses (Optional Private Send & Receive)&#x20;
* DIONS (an alias "DNS" system which can be used instead of the long hex addresses)
* Private & Public Alias
* Encrypted AES 256 Single Messaging
* Encrypted AES 256 Group Messaging
* RSA Key Exchange via Encrypted Tunnels
* Encrypted 1MB File Storage & Transfer

The team is currently working on the development of I/O Coin's Dions 2.0 and side chain with Abstract Smart Contract platform enabling an entropy based graph ledger [Chameleon](https://www.chameleongraph.com)

**IOC DEV TEAM Bitcoin Conference Keynote**

{% embed url="<https://youtu.be/r1TEnqrhfJA>" %}

**IOC DEV TEAM Bitcoin Conference internview**

{% embed url="<https://youtu.be/C8ASLy2xQr8>" %}


---

# 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://i-o-digital-foundation.gitbook.io/ioc/master.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.