Overview
T3N is a confidential-computing network. TEE contracts and data run inside hardware-secured TEE nodes. Data are stored in a shared key-value (KV) store, and that store is divided into namespaces so tenant data and T3N data stay isolated. A namespace is a prefix on a map name. T3N uses that prefix to route each KV operation through the right access policy. There are two main worlds of namespaces:- Tenant-owned namespaces (
z:) — open-ended. Tenants create maps and TEE contracts at runtime (i.e., register new maps and contracts while the cluster is running; do not need to be built into the T3N node ahead of time), and access is governed dynamically by tenant identity, contract identity, and map policy. - T3N-owned namespaces (everything else) — fixed. These are system maps such as
users,auth,dids,scripts,outbox_*, andidx:_tenant_*, with strict built-in rules.
Canonical format
As an external developer, your TEE contracts and data belongs in z-namespace. Every z-namespace resource uses this canonical name:z:<tid>:<tail>
Example:
z:8f3a0123456789abcdef0123456789abcdefc91d:secrets
Use the full canonical name when documenting, debugging, or reading audit output. High-level SDK helpers may ask only for the tenant-local tail.
Access model
T3N enforces tenant-map policy in the governed transaction path before writes commit. By default, a tenant contract can access only maps allowed by that map’s policy:- Writers controls which tenant contracts may write.
- Readers controls which tenant contracts may read.
- If readers is omitted on map creation, it defaults from writers.
- Cross-tenant access is denied unless the map owner explicitly grants another tenant contract access.