Skip to main content
Version: 3.0.0

ICICLE libraries

ICICLE is composed of two main logical parts:

  1. ICICLE device library
  2. ICICLE template core library

ICICLE device

The ICICLE device library serves as an abstraction layer for interacting with various hardware devices. It provides a comprehensive interface for tasks such as setting the active device, querying device-specific information like free and total memory, determining the number of available devices, and managing memory allocation. Additionally, it offers functionality for copying data to and from devices, managing task queues (streams) for efficient device utilization, and abstracting the complexities of device management away from the user.

See programmers guide for more details. C++, Rust, Go

ICICLE Core

ICICLE Core is a template library written in C++ that implements fundamental cryptographic operations, including field and curve arithmetic, as well as higher-level APIs such as MSM and NTT.

The Core can be instantiated for different fields, curves, and other cryptographic components, allowing you to tailor it to your specific needs. You can link your application to one or more ICICLE libraries, depending on the requirements of your project. For example, you might only need the babybear library or a combination of babybear and a Merkle tree builder.

Rust

Each library has a corresponding crate. See programmers guide for more details.

Supported curves, fields and operations

Supported curves and operations

Operation\Curvebn254bls12-377bls12-381bw6-761grumpkin
MSM
G2 MSM
NTT
ECNTT
Vector operations
Polynomials
Poseidon
Merkle Tree

Supported fields and operations

Operation\FieldbabybearStark252
Vector operations
Polynomials
NTT
Extension Field

Supported hashes

HashSizes
Keccak256, 512

Backend

Each backend must implement the device API interface. Each backend may implement

  • One or more ICICLE library. For example implement only bn254 curve.
  • One or more APIs in this library. For example MSM only.

See CUDA backend and Build Your Own Backend for more info about implementing a backend.