Stay in the know


Blockchain Connectivity

IN3 Client

The value of public blockchain networks is limited if we cannot easily access them securely. Operating a separate node (a device – like a computer – containing an entire copy, or a portion/state, of the blockchain) within a blockchain’s peer-2-peer (p2p) network is challenging or even impossible for many mobile and web applications as well as internet of things (IoT) devices. While centralized remote nodes exist and feel resource-efficient, the client cannot validate the results independently and the access point becomes a single point of failure.

Blockchains IN3 Client


Earning its name as a minimal verification client, IN3 (INcentivized Node Network, pronounced “in-cubed”) is the smallest client only needing 300kb of storage, making it easy to integrate into IoT and mobile or web applications. The IN3 client is a crypto-economic, non-synchronizing, and stateless blockchain client with minimal resource requirements.

How Does it Work?

The IN3 embedded client connects in a fully decentralized manner to the Ethereum blockchain and can verify and validate information without being part of the blockchain’s p2p network. IN3 is a decentralized network, meaning, responses are verified by proofs delivered by other nodes, or computers, in the network. Other nodes within the network will confirm the correctness of the proof. As an added security measure, watchdog nodes test the veracity of other nodes’ actions; a malicious node will be punished. Because the client is stateless – does not need to sync with, or download all the data from – the live blockchain network, minimum bandwidth is required for the transmission of information and the interaction with the blockchain can happen immediately (no wait time).


  • IoT-ready. IN3 is highly optimized for small devices and microcontrollers (running with only 128 KB of RAM).
  • Chain-agnostic. A single IN3 client can connect to several blockchains simultaneously.
  • Secure and decentralized. Responses will be verified based on proofs delivered by nodes within a decentralized network.
  • No login. No central server - all permissions are managed by cryptographic keys.
  • Stateless. The client does not need to sync, which means you can turn on your device and immediately start using it.
  • No single point of failure. IN3 will be based on a decentralized network, meaning zero downtime.



graph of Incubed Client and node interactions


comparitive chart of in3 Client, remote client, light, client, pruned node, and full node

Resources for Developers