inco-primary-sources-2026-04-26

Inco primary-source snapshot

Fetched: 2026-04-26 UTC

1) Official site / positioning

Source: https://inco.org/

Selected excerpts from the official site:

Bring privacy to users where they are.

Works with the tools you already use.

Wallets (e.g, MetaMask, Coinbase Wallet, Phantom)

Smart contract languages (e.g, Solidity, Rust)

Networks (EVM, SVM)

The new privacy standard

Inco leverages isolated hardware environments and cryptography to deliver high performance and institutional-grade security.

Non-custodial

Enables users to keep complete control over their funds, with force-exit path.

Additional signals from the homepage:

• The site is positioning Inco as compatibility-first confidentiality infrastructure rather than as a new privacy chain or standalone wallet
• The official marketing language emphasizes TEE-backed execution plus cryptography, broad developer compatibility, and private application design space
• The homepage claims are broader than the currently documented beta deployment status, so the docs are important for grounding what is actually live

2) Introduction / current product reality

Source: https://docs.inco.org/introduction.md Source: https://docs.inco.org/introduction.md?ask=What%20is%20Inco%20Lightning%2C%20what%20chains%20or%20environments%20are%20currently%20supported%2C%20and%20does%20it%20require%20a%20new%20chain%20or%20wallet%3F

Selected excerpts from the docs:

Inco Lightning is currently available on Base Sepolia in beta testnet.

Inco (short for “incognito”) is the confidentiality layer for existing blockchains.

Inco Lightning uses Trusted Execution Environments (TEEs) to deliver verifiable confidential compute at lightning-fast speeds.

No new chain, no new wallet. Just import our Solidity library and start building privacy-preserving dApps today.

Additional signals from the intro docs:

• The current live environment appears narrower than the homepage’s broad compatibility framing, with Base Sepolia beta called out explicitly
• The docs consistently frame Inco as an add-on confidentiality layer for existing chains rather than as a new execution environment
• TEE-backed confidential compute is central to the present product identity

3) Architecture / trust model / missing whitepaper

Source: https://docs.inco.org/architecture/overview.md Source: https://docs.inco.org/architecture/overview.md?ask=What%20are%20Inco%27s%20main%20architectural%20components%20and%20what%20kind%20of%20trust%20or%20execution%20model%20does%20it%20use%3F

Selected excerpts from the docs:

Inco is a confidentiality layer for blockchains that enables privacy-preserving smart contracts without modifying the underlying blockchain.

Unlike monolithic privacy solutions, Inco follows a modular approach similar to how SSL/TLS provides security for internet protocols.

Whitepaper coming soon!

Inco’s architecture consists of three main components that work together to provide confidential computing capabilities:

1. Smart Contract Library
2. Confidential Compute Server
3. Client-side JavaScript Library

Additional signals from the architecture docs:

• The “SSL/TLS for blockchains” analogy is a strong clue that Inco should be cataloged as middleware, not as an L1/L2 in the ordinary sense
• The architecture page explicitly says no whitepaper is available yet
• The three-part split between contracts, compute service, and client SDK is the clearest current description of the real system boundary

4) Attestation and decryption flows

Source: https://docs.inco.org/architecture/decryption-mechanisms.md

Selected excerpts from the docs:

Inco provides three types of decryption mechanisms:

• Attested Decrypt
• Attested Compute
• Attested Reveal

Used when an authorized user needs a cryptographic proof of decryption that can be selectively revealed on-chain

Used when you need to perform computations on encrypted data completely off-chain and get a decryption attestation

Additional signals from the decryption docs:

• The attestation model is central to understanding how Inco bridges offchain confidential compute with onchain verification
• ACL checks and signed attestations appear to be core operating primitives, not optional extras
• These docs make Inco look like confidential-compute middleware and verification infrastructure rather than generic privacy branding

5) Developer onboarding surface

Source: https://docs.inco.org/js-sdk.md Source: https://docs.inco.org/quickstart.md Source: https://docs.inco.org/llms.txt

Selected excerpts from the docs:

incoJs is a javascript library that enables developers to interact with the Inco protocol.

Get started with Inco Lightning in minutes.

We recommend getting started using our template.

Additional signals from the SDK and quickstart docs:

• The official docs expose a practical developer surface with templates, test flows, and SDK guidance rather than a research-only narrative
• The llms.txt index shows breadth beyond a single demo: architecture pages, access control, attestation verification, wallet integrations, and confidential-token tutorials
• This is a strong indicator that the project is actively trying to become a usable application-layer stack

6) GitHub organization / shipped surface

Source: https://github.com/Inco-fhevm

Selected excerpts from the GitHub org surface:

Dapp Development Kit (DDK) for Inco Lightning

nextjs template for building encrypted dapp on solana

Additional signals from GitHub:

• The public repos show active starter kits and example applications across both EVM- and Solana-oriented workflows
• GitHub makes it easier to see that Inco is shipping templates and integration surfaces, not only concepts
• The repo inventory is useful for confirming that the project’s ambitions extend beyond a single demo chain environment

Notes

• No public standalone whitepaper was found in official sources during this pass.
• The architecture docs explicitly say “Whitepaper coming soon!”, so the docs portal is currently the main technical source of truth.
• Inco appears best cataloged as confidentiality middleware / confidential smart-contract infrastructure for existing chains, with TEE-backed execution and attestation flows as the core operating model.