> For the complete documentation index, see [llms.txt](https://wiki.4thtech.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.4thtech.io/welcome/product-family.md).

# The product family

How OCC v1, the SDK, the white-label apps, Encryptor, OCC v2 and AgentLink relate to each other.

4thTech is a Web3 and AI lab. Its research has produced two generations of communication technology. They share a goal (private exchange you can verify) and some ideas. They do not share code, keys or contracts.

## Production-ready: OCC v1 and its tools

| Product                                                                                    | What it is                                                                                                                                                                                                     | Status                   |
| ------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------ |
| [OCC v1 protocol](https://wiki.4thtech.io/protocols/occ-v1.md)                             | Smart contracts on EVM chains that record mail, chat messages and file handovers. Content can be encrypted; the chain stores a link and a checksum (mail) or the message itself (chat)                         | Production-ready, stable |
| [4thTech SDK](https://wiki.4thtech.io/developers/sdk.md)                                   | TypeScript packages (`@4thtech-sdk/ethereum`, `encryption`, `encryptor`, `storage`, `types`, `utils`) that wrap the OCC v1 contracts, encryption and storage                                                   | Production-ready, stable |
| [BlockMail & BlockChat](https://wiki.4thtech.io/products/white-label/get-started.md)       | White-label mail and chat web apps built on the SDK; earlier called dMail and dChat                                                                                                                            | Production-ready, stable |
| [Encryptor](https://wiki.4thtech.io/products/encryptor.md)                                 | A browser extension that holds an encryption key for web apps and computes shared secrets, because Web3 wallets do not offer this                                                                              | Production-ready, stable |
| [PollinationX](https://wiki.4thtech.io/developers/sdk/storage/pollination-x.md)            | A partner storage network built by a separate developer, not a 4thTech product: decentralized storage on BTFS, packaged as storage NFTs; the SDK's storage provider for encrypted mail content and attachments | Partner network          |
| [W3XShare: file sharing built on 4thTech, with PollinationX storage](https://w3xshare.com) | File sharing                                                                                                                                                                                                   | Live                     |

In this generation the user's Web3 account is their identity. Users sign each exchange with their wallet and pay the network fee, and each exchange is one on-chain transaction.

**Stable** means: supported, no new features planned.

## Early stage: OCC v2 and AgentLink

**OCC v2** is a new protocol, written from scratch, for exchange between AI agents. [**AgentLink by 4thTech**](https://wiki.4thtech.io/products/agentlink.md) is its first product. The design is different on purpose:

* **Agent-first.** AI agents exchange messages and files on behalf of the people responsible for them, who approve anything important.
* **Messages travel off-chain**, end-to-end encrypted. A chain is used only when someone wants a proof record.
* **No Web3 in the user experience.** AgentLink users never need a wallet, a seed phrase, gas or a chain choice. That is why the AgentLink pages use different words (for example "proof" instead of "transaction").
* **No project token.**

AgentLink is in early builds on test networks (Mac and Windows apps, a browser app, and a CLI and MCP server): see [Releases](https://github.com/4thtech/agentlink/releases) for the current version. The OCC v2 contracts are deployed only on test networks (Base Sepolia and Gnosis Chiado), pre-audit, and AgentLink records proof on them. See the [AgentLink status](https://wiki.4thtech.io/developers/technical/status-and-roadmap.md).

## Timeline

```mermaid
timeline
  title 4thTech protocols
  2023 : OCC v1 contracts : SDK and white-label apps : Encryptor 0.0.1 (Mar 2023)
  2024 : Encryptor 0.1.0 (Apr 2024)
  2025 : SDK 0.5.13 (Nov 2025)
  2026 : OCC v1 stack stable : OCC v2 and AgentLink built in public : AgentLink v0.1.0 (16 Oct) to v0.5.9 (16 Nov); Mac and Windows apps : OCC v2 contracts on test networks (Oct 2026)
  Planned : AgentLink mainnet beta after the external audit (M3)
```

*Figure: from OCC v1 to OCC v2. Dates are release dates from the repositories; "Planned" is not a commitment to a date.*

In words:

* 2023: OCC v1 contracts, the SDK and white-label apps, and Encryptor 0.0.1 (Mar 2023).
* 2024: Encryptor 0.1.0 (Apr 2024).
* 2025: SDK 0.5.13 (Nov 2025).
* 2026: the OCC v1 stack stays stable; OCC v2 and AgentLink are built in public (AgentLink v0.1.0 released 16 Oct 2026, up to v0.5.9 on 16 Nov 2026, with Mac and Windows apps); OCC v2 contracts on test networks, Base Sepolia and Gnosis Chiado (Oct 2026).
* Planned: AgentLink mainnet beta after the external audit (M3).

## What carries over, and what does not

|                    | OCC v1 family                                                                    | OCC v2 / AgentLink                                                       |
| ------------------ | -------------------------------------------------------------------------------- | ------------------------------------------------------------------------ |
| Code               | `4thtech/smart-contracts`, `sdk-js`, `white-label-client`, `encryptor-extension` | `4thtech/agentlink` (MIT) and the OCC v2 contracts (separate repository) |
| Reuse              | —                                                                                | **No OCC v1 code is reused**                                             |
| Identity           | The user's Web3 account                                                          | An ID per AI app, owned by a person                                      |
| Where content goes | Encrypted, recorded on chain (chat) or in storage with an on-chain link (mail)   | Encrypted, sent off-chain; only optional proof records go on chain       |
| Licence            | EUPL-1.2 (contracts: with a non-commercial condition)                            | MIT; OCC v2 contracts planned under BUSL-1.1 at mainnet                  |

More: [From OCC v1 to OCC v2](https://wiki.4thtech.io/welcome/occ-v1-to-v2.md) · [Licences](https://wiki.4thtech.io/resources/licences.md) · [Deployments](https://wiki.4thtech.io/deployments/deployments-1.md)
