Six specialized node types, each optimized for a specific workload. Validation runs consensus. FHE crunches encrypted workloads on GPUs. Web nodes serve dApps. API nodes bridge external systems. Batch settles millions of operations. Storage holds distributed blobs.
One network, six specializations, maximum performance.
Unlike homogeneous networks where every node does everything, ATSHI assigns the right hardware and software profile to each workload class.
The backbone of the network. Run ARCH consensus, validate transactions, maintain canonical chain state, enforce protocol rules. Optimized for CPU efficiency and low-latency networking.
Dedicated to Fully Homomorphic Encryption workloads. High-end GPUs accelerate FHE operations by orders of magnitude. Process encrypted computations without ever seeing plaintext.
Serve websites and dApps stored on the blockchain. HTTP/HTTPS throughput with SSL/TLS termination, caching, and GeoDNS. Turns the chain into a content-addressed global CDN.
Bridge between blockchain and external systems. Expose ATSHI data through familiar REST and GraphQL APIs. Rate limiting, auth, transformation, caching built in.
Designed for high-throughput workloads — mass distributions, data migrations, bulk attestations, IoT ingestion. Aggregate, generate Merkle proofs, settle with a single root.
Persistent, distributed storage for large files, media, documents, dataset blobs. Content-addressed with erasure coding for durability. Keeps the main chain lean and fast.
From ingestion to on-chain settlement — how batch nodes process millions of operations with a single Merkle proof.
High-volume operation streams hit dedicated endpoints. IoT data, mass distributions, bulk attestations. Buffers absorb burst traffic and queue for processing.
Operations validated, transformed, organized into batches. Invalid ops rejected with detailed errors. Business logic executes against current state.
A Merkle tree is constructed over all state transitions. The root is a cryptographic commitment to the entire batch — every op is verifiable.
Merkle root and metadata submitted via a single transaction. One settlement, potentially millions of individual operations.
Each node type is optimized for its workload. FHE nodes have GPUs. Web nodes have caching. Batch nodes have high-throughput ingestion. No compromise hardware, no bottleneck from mixed workloads.
Optimized · Purpose-BuiltRun only the node types you need. An enterprise runs validation + API + storage. A DeFi protocol adds FHE compute. A content platform adds web hosting. Scale each type independently.
Modular · Independent ScalingBatch processing handles mass operations that would overwhelm traditional chains. API gateways provide familiar REST/GraphQL interfaces. Storage handles large files. Deploy without rethinking architecture.
Batch · API · StorageFHE operations that take minutes on CPU execute in seconds on GPU. NVIDIA A100/H100 acceleration makes confidential computing practical for real-time applications.
A100/H100 · 100× FasterMillions of operations settle with a single Merkle root transaction. IoT data streams, mass distributions, bulk attestations — workloads that are economically impossible on per-tx chains become trivial.
Millions/Tx · MerkleWeb hosting and API nodes deploy worldwide with GeoDNS routing. Storage uses erasure coding for durability across regions. The network adapts to geographic demand.
GeoDNS · Erasure-CodedGeographically aware node organization for optimized replication, routing, and sovereignty enforcement.
Nodes grouped by physical location and region for optimized replication and intelligent routing.
Transaction chains replicated across multiple geographic zones. Data is never concentrated in a single region.
Requests automatically routed to the closest geo-patch. Paris, Tokyo, São Paulo — all reach the nearest available nodes.
Data constrained to specified regions for GDPR / local regulations. Geographic sovereignty is a protocol-level guarantee.
On-chain hosting served from the geographically nearest nodes — load times drop worldwide.
Enterprises specify which chains must remain in which jurisdictions. Enforced at the replication level, not by policy.
GPU-accelerated FHE. Native web hosting. REST/GraphQL APIs. Batch settlement. Distributed storage. All as first-class network participants.