Newton Explorer

Newton Explorer: https://explorer.newton.xyz/

Definitions

Term	Definition
Task	The atomic unit that the protocol validates. It includes an intent and a reference to the policy.
Policy	User-specific policy with parameters set by a user when they choose to use it.
Compliant	When a task meets the criteria defined by a policy.
Non-compliant	When a task does not meet the criteria defined by a policy.

Term	Definition
Current Status	Information on the stage a particular task is in. See section below for possible values.
Sender	The address of the wallet that initiated the transaction to the protocol.
Policy Client Address	The address of the policy-guarded smart contract. This could represent a vault for an end-user.
Evaluation Result	Indicates whether a policy is passed or not. Possible values: compliant or non-compliant.
Date Created	The date the task was first recognized by the protocol.
Last Updated	The date the task last changed status.
Intent	The actual EVM transaction for which the policy is being evaluated.

Term	Definition
Policy address	A generic policy written by a developer. Policies can be customized by end-users as used by a task for evaluation
Policy ID	Unique identifier representing a user-specific policy.
Date Created	The time at which a policy was created for the user.
Time of Evaluation	The time at which the task was evaluated as compliant or non-compliant.
Evaluation Result	Indicates whether a policy is passed or not. Possible values: compliant or non-compliant.
Intent	The actual EVM transaction for which the policy is being evaluated.
Policy Data	Offchain data produced by the data oracle as defined in the policy.
Policy Params	User-specific parameters used to customize a policy.
Policy Code	The Rego code that defines the logic of a policy.
Policy Simulation	A local browser evaluation of an intent, used to keep operators honest.

Intent evaluation requested: The task is sent to an AVS operator for evaluation.
Intent evaluated: The AVS operator has evaluated the task against the policy to determine compliance.
Proof consumed / Proof expired: Once a proof is generated by the protocol and provided to the developer, it can be used by the policy client to complete the transaction. If the proof is used, it is “consumed”. If the expiration window passes, as defined by the policy, it is “expired”.