Circular Documentation
  • Getting Started
  • Introduction
    • Introducing Circular
  • Circular's Mission
  • Circular's Technology
    • Certificates & Data Anchoring
    • Multi-Chain Architecture
    • Certified Nodes & Jurisdictional Deployment
    • HyperCode & GPU Accelerated Processing
    • Proof of Reputation Consensus Mechanism
  • Certified Intelligence
  • Developer Tools
    • Enterprise APIs
      • Javascript
        • CEP_Account.open()
        • CEP_Account.setNetwork()
        • CEP_Account.setBlockchain()
        • CEP_Account.update()
        • CEP_Account.submitCertificate()
        • CEP_Account.getTransactionOutcome()
        • CEP_Account.getTransaction()
        • CEP_Account.close()
      • Node.JS
        • CEP_Account.open()
        • CEP_Account.setNetwork()
        • CEP_Account.setBlockchain()
        • CEP_Account.update()
        • CEP_Account.submitCertificate()
        • CEP_Account.getTransactionOutcome()
        • CEP_Account.getTransaction()
        • CEP_Account.close()
      • PHP
        • CEP_Account.open()
        • CEP_Account.setNetwork()
        • CEP_Account.setBlockchain()
        • CEP_Account.updateAccount()
        • CEP_Account.submitCertificate()
        • CEP_Account.getTransactionOutcome()
        • CEP_Account.getTransaction()
        • CEP_Account.close()
      • Python
        • CEP_Account.open()
        • CEP_Account.set_network()
        • CEP_Account.set_blockchain()
        • CEP_Account.update_account()
        • CEP_Account.submit_certificate()
        • CEP_Account.get_transaction_outcome()
        • CEP_Account.get_transaction()
        • CEP_Account.close()
      • Java
        • CEP_Account.open()
        • CEP_Account.setNetwork()
        • CEP_Account.setBlockchain()
        • CEP_Account.updateAccount()
        • CEP_Account.submitCertificate()
        • CEP_Account.getTransactionOutcome()
        • CEP_Account.getTransaction()
        • CEP_Account.close()
  • SDK
  • CLI & Tooling
  • Core Concepts
    • Overview
    • Certificates
  • Accounts
  • Private Chains
  • Data Management
  • Fees
  • Nodes
  • Private Keys
  • Recovery Phrases
  • Tutorials & Examples
    • Circular Connect Guide
      • Create an Organisation Account
      • Create a Blockchain Account
      • Purchase Certificates
      • Using the Explorer & Viewing Certificate Details
    • Create Your First Certificate
  • Industry Use Cases
    • Industry Use Cases - Overview
    • Clinical Trials
    • Medical Devices
    • Public Health
    • Pharma Supply Chains
    • Research and Academia
Powered by GitBook
On this page
  • Overview
  • What is HyperCode?
  • Why GPUs?
  • Use Cases Enabled by GPU-Accelerated Processing
  • 1. Zero-Knowledge Signature Extraction
  • 2. Proof of AI
  • 3. Time-Bound Certifications
  • Determinism & Safety
  • Interfacing with HyperCode
  • Summary
  1. Circular's Technology

HyperCode & GPU Accelerated Processing

HyperCode enables deterministic, high-performance processing of certificate operations using GPU acceleration, unlocking scalable verification, zero-knowledge privacy, and AI-native workloads.

Overview

At the core of Circular’s performance and scalability is a system called HyperCode — a low-level execution layer that processes transactions and certificates using parallelized GPU computation.

Unlike traditional systems where every validation or verification is executed sequentially by a CPU, Circular leverages high-throughput graphics processors (GPUs) to execute actions like hashing, data fingerprinting, validation, and timestamping at massive scale.

This approach is particularly valuable in environments where:

  • Large volumes of data need to be certified in real time

  • Zero-knowledge proofs or signature extraction must be computed on-device

  • AI model training or validation processes require verifiable, high-speed attestations

  • Complex logical instructions must execute deterministically and reproducibly

What is HyperCode?

HyperCode is a deterministic execution engine built for Circular’s internal virtual machine. It allows logic instructions tied to a certificate (or system action) to be run with:

  • Parallel GPU processing

  • Controlled memory and instruction scope

  • Time-bound, verifiable outputs

  • Replayable, audited outcomes across nodes

Every HyperCode program must produce the same output across all nodes. If one fails to validate or disagrees, the action is rejected.

Why GPUs?

GPUs allow for dramatically more efficient processing of tasks such as:

  • File hashing and metadata extraction

  • Signature validation at scale

  • Time-sensitive verification logic

  • Proof generation for AI training workflows

  • Model hash attestation and dataset audit logs

This unlocks 10x to 100x speed increases in throughput compared to CPU-only chains or traditional databases.

Use Cases Enabled by GPU-Accelerated Processing

1. Zero-Knowledge Signature Extraction

Extract and certify signatures from confidential documents or patient data without exposing raw content. Enables privacy-compliant certification in healthcare and legal contexts.

2. Proof of AI

Certify the entire lifecycle of an AI model, including:

  • Hash of training data

  • Model architecture metadata

  • Training epoch logs

  • Output checkpoints

  • Embedded inference logic

This creates a tamper-proof lineage for AI deployments — essential for compliance in regulated AI systems.

3. Time-Bound Certifications

Handle high volumes of certifications during peak system demand (e.g., drug batch validation, clinical submission deadlines) without bottlenecking on CPU constraints.

Determinism & Safety

HyperCode execution is sandboxed and deterministic:

  • No random output allowed

  • No external system calls

  • Resource-constrained (memory, time, compute)

  • Output must match across all nodes before being accepted

This ensures reproducibility and removes the risk of divergence across nodes, even under complex or custom logic.

Interfacing with HyperCode

HyperCode programs can be authored using Circular’s SDK or integrated directly via certificate payloads. Inputs and outputs are hashed and signed during validation, ensuring full auditability.

No external programming knowledge is required — most developers interact with high-level tooling while HyperCode runs under the hood.

Summary

HyperCode powers Circular’s scalability and regulatory-grade performance through GPU-native execution of verification logic. By leveraging deterministic compute across a distributed node network, institutions can certify data, processes, and AI systems at scale — while maintaining privacy, integrity, and reproducibility.

PreviousCertified Nodes & Jurisdictional DeploymentNextProof of Reputation Consensus Mechanism

Last updated 27 days ago