Welcome to Incubed’s documentation!

Reference

• Getting Started
  • TypeScript/JavaScript
  • As Docker Container
  • C Implementation
  • Java
  • Command-line Tool
  • Supported Chains
  • Registering an Incubed Node
• Downloading in3
  • in3-node
  • in3-client (ts)
  • in3-client(C)
• Running an in3 node on a VPS
  • Side notes/ chat summary
  • Recommendations
• IN3-Protocol
  • Incubed Requests
  • Incubed Responses
  • ChainId
  • Registry
  • Binary Format
  • Communication
• Roadmap
  • V2.0 Stable: Q3 2019
  • V2.1 Incentivization: Q4 2019
  • V2.2 Bitcoin: Q1 2020
  • V2.3 WASM: Q3 2020
  • V2.4 Substrate: Q1 2021
  • V2.5 Services: Q3 2021
• Benchmarks
  • Setup and Tools
  • Considerations
  • Results/Baseline
• Embedded Devices
  • Hardware Requirements
  • Incubed with ESP-IDF
  • Incubed with Zephyr
• API RPC
  • in3
  • eth
  • ipfs
  • btc
  • zksync
• API Reference C
  • Overview
  • Building
  • Examples
  • How it works
  • Plugins
  • Integration of Ledger Nano S
  • Module api
  • Module core
  • Module pay
  • Module signer
  • Module transport
  • Module verifier
• API Reference WASM
  • Installing
  • Building from Source
  • Examples
  • Incubed - from Typescript to WASM
  • How to migrate?
  • IN3 Module
  • Package index
• API Reference Python
  • Python Incubed client
  • Examples
  • Incubed Modules
  • Library Runtime
• API Reference Java
  • Installing
  • Examples
  • Package in3
  • Package in3.btc
  • Package in3.config
  • Package in3.eth1
  • Package in3.ipfs
  • Package in3.ipfs.API
  • Package in3.utils
• API Reference Dotnet
  • Runtimes
  • Quickstart
  • Examples
  • Index
• API Reference Rust
  • IN3 Rust API features:
  • Quickstart
  • Crate
  • Api Documentation
• API Reference CMD
  • Usage
  • Install
  • Environment Variables
  • Methods
  • Running as Server
  • Cache
  • Signing
  • Autocompletion
  • Function Signatures
  • Examples
• API Reference Node/Server
  • Command-line Arguments
  • in3-server-setup tool
  • Registering Your Own Incubed Node
• API Reference Solidity
  • NodeRegistryData functions
  • NodeRegistryLogic functions
  • BlockHashRegistry functions

Concept

• 1. Concept
  • 1.1. Situation
  • 1.2. Low-Performance Hardware
  • 1.3. Scalability
  • 1.4. Use Cases
  • 1.5. Architecture
  • 1.6. Scaling
• 2. Ethereum
  • 2.1. Blockheader Verification
  • 2.2. Proof of Work
  • 2.3. Proof of Authority
  • 2.4. Ethereum Verification
• 3. Bitcoin
  • 3.1. Concept
  • 3.2. Security Calculation
  • 3.3. Proofs
  • 3.4. Conviction
• 4. Incentivization
  • 4.1. Decentralizing Access
  • 4.2. Incentivization for Nodes
  • 4.3. Connecting Clients and Server
  • 4.4. Ensuring Client Access
  • 4.5. Deposit
  • 4.6. LoadBalancing
  • 4.7. Free Access
  • 4.8. Convict
  • 4.9. Handling conflicts
  • 4.10. Payment
  • 4.11. Client Identification
• 5. Decentralizing Central Services
  • 5.1. Incentivization
  • 5.2. Verification
• 6. Threat Model for Incubed
  • 6.1. Registry Issues
  • 6.2. Network Attacks
  • 6.3. Privacy
  • 6.4. Risk Calculation

• Index