Skip to main content

​
A

​
Attestation

A cryptographic proof (BLS aggregate signature) that Newton operators evaluated a policy and approved or rejected an Intent. Contains the taskId, policyId, evaluation result, and expiration block. See also: Core Concepts.

​
AVS (Actively Validated Service)

An EigenLayer service that leverages restaked ETH for economic security. Newton Protocol operates as an AVS, meaning its operators have staked assets that can be slashed for incorrect behavior.

​
B

​
BLS (Boneh-Lynn-Shacham)

A signature scheme that allows multiple signatures to be aggregated into a single compact proof. Newton operators produce individual BLS signatures that are aggregated by the Aggregator into a single consensus proof.

​
C

​
CID (Content Identifier)

An IPFS content-addressable hash used to reference policy files, schemas, and metadata stored on IPFS. Generated by newton-cli policy-files generate-cids.

​
G

​
Gateway

The JSON-RPC 2.0 endpoint that receives tasks and coordinates operator evaluation. All SDK and CLI interactions with the Newton network go through the Gateway. See also: RPC API.

​
H

​
HPKE (Hybrid Public Key Encryption)

The encryption scheme (X25519/ChaCha20-Poly1305) used by Newton’s privacy layer to encrypt sensitive data before submission to operators.

​
I

​
Intent

A proposed transaction submitted for policy evaluation. Contains EVM fields: from, to, value, data, chain_id, and function_signature. See also: Core Concepts.

​
O

​
Operator

An EigenLayer node registered with the Newton AVS that independently evaluates tasks. Operators fetch PolicyData, run Rego policies, and produce BLS signatures that are aggregated into consensus proofs.

​
P

​
Policy

A Rego program that defines the conditions an Intent must meet to be approved. Policies are stored on IPFS and referenced by CID. They access data.params (configuration) and data.data (runtime oracle data). See also: Writing Policies.

​
PolicyClient

A smart contract that validates Newton attestations before executing transactions. Created by inheriting the NewtonPolicyClient Solidity mixin. See also: Smart Contract Integration.

​
PolicyData

A WASM data oracle that fetches or computes external data at evaluation time. The output is fed to the Rego policy as data.data. See also: Writing Data Oracles.

​
R

​
Rego

The policy language used by Newton Protocol (originally from Open Policy Agent). Rego policies define declarative rules that evaluate to true or false. See also: Rego Syntax Guide.

​
T

​
Task

The atomic evaluation unit in Newton — pairs an Intent with its Policy and configuration. Each Task is either compliant or non-compliant. See also: Core Concepts.

​
W

​
WASM (WebAssembly)

The compilation target for PolicyData oracles. JavaScript, Rust, or Python code is compiled to WASM components that implement the newton-provider WIT interface.

​
WIT (WebAssembly Interface Types)

The interface definition language used to define the contract between WASM components and the Newton runtime. The newton-provider.wit file specifies the run function and http.fetch import.