Skip to main content
Events are the atomic units of a machine’s financial history. The EventRegistry stores them ; the scoring pipeline reads them to compute credit ratings.

​
Two event types

TypeValueDescription
Revenue0The machine earned money. value carries the amount as a minor-unit integer (cents for USD/HKD, whole units for JPY/KRW) in the event’s currency; the MCR scoring pipeline normalizes to USD cents via FX at the event timestamp. Single-event submitEvent resolves an omitted currency to "USD" for revenue and "" for activity; batch submit requires an explicit currency per event.
Activity1The machine performed an action (telemetry, data generation, task completion). value may be 0. currency must be empty (""); non-empty currency on an activity event reverts InvalidCurrencyShape.
Both SDKs export these as constants: 
import {
  EVENT_TYPE_REVENUE,  // 0
  EVENT_TYPE_ACTIVITY, // 1
} from "@peaqos/peaq-os-sdk";

​
MachineEvent schema

Every event stored in the EventRegistry follows this structure: The expose the stored struct as MachineEvent (with dataHash / data_hash as a 32-byte keccak256). The SDK input type SubmitEventParams takes rawData / raw_data bytes instead; the SDK computes the hash for you before the call.
FieldTypeDescription
machineIduint256Machine identity from IdentityRegistry. Primary key linking event to machine.
eventTypeuint80 = revenue, 1 = activity.
valueuint256Amount earned (revenue) or metric value (activity). May be 0 for activity events. Revenue events express value as an ISO 4217 minor-unit integer (cents for USD/HKD, whole units for JPY/KRW) in the event’s currency.
currencystringRevenue events: 3-10 char uppercase alphanumeric ISO 4217 code (e.g. "USD", "HKD", "JPY"). Activity events: empty string "". Validated on-chain.
timestampuint256Unix timestamp when the event occurred, not when it was submitted.
dataHashbytes32keccak256(raw_data). Raw data stays off-chain; hash proves integrity.
trustLeveluint80 = self-reported, 1 = on-chain verifiable, 2 = hardware-signed.
sourceChainIduint256Chain where the original activity occurred (e.g., 3338 for peaq, 8453 for Base). 0 for off-chain events.
sourceTxHashbytes32Transaction hash on the source chain. Combined with sourceChainId, creates a verifiable cross-chain link. Null for off-chain events.
metadatabytesArbitrary bytes stored on-chain alongside the event (4096-byte cap). The MCR API server parses JSON metadata into the event_data[].metadata object surfaced on /machine/{did} for machines with data_visibility: onchain; the SDK only writes raw bytes.

​
Cross-chain revenue accounting

sourceChainId and sourceTxHash together form a cross-chain audit trail. When a machine earns revenue on , the proxy submits the event to the EventRegistry on with sourceChainId = 8453 and the Base transaction hash. Any verifier can look up the on the source chain and confirm the event happened.
ScenariosourceChainIdsourceTxHash
Revenue earned on Base8453Base transaction hash
Revenue earned on peaq3338peaq transaction hash
Off-chain telemetry0null (bytes32(0))

​
Data integrity via dataHash

Raw event data stays with the project (in their database, behind their API). The dataHash stored onchain is keccak256(raw_data), computed by the SDK before submission. This keeps costs at 32 bytes per event regardless of payload size, while anyone can fetch the raw data from the project’s data_api (set in the machine’s ) and verify keccak256(fetched_data) == dataHash. 
import { computeDataHash } from "@peaqos/peaq-os-sdk";

const rawData = new Uint8Array([1, 2, 3]);
const hash = computeDataHash(rawData);
// hash === "0x..." (keccak256)

​
Authorization

EventRegistry reads IdentityRegistry to verify submit authority. msg.sender must be one of:
PathAddressUse case
NFT ownerIdentity NFT holderThe account that holds the Identity NFT submits directly.
Machine walletmachineWalletOf(machineId)The machine’s registered wallet submits. Typical for self-managed flows where the machine signs its own transactions.
OperatoroperatorOf(machineId)Assigned operator submits on behalf of the machine. Only valid when an operator has been set (non-zero).
All three paths produce identical on-chain records: the machineId in the stored event always identifies the machine, regardless of who submitted.

​
Validation

The JS SDK exports validateSubmitEventParams, which checks all nine fields before any interaction: 
import { validateSubmitEventParams } from "@peaqos/peaq-os-sdk";

validateSubmitEventParams({
  machineId: 1,
  eventType: 0,
  value: 100,                  // $1.00 in cents
  currency: "USD",
  timestamp: Math.floor(Date.now() / 1000),
  rawData: new Uint8Array([1, 2, 3]),
  trustLevel: 1,
  sourceChainId: 8453,
  sourceTxHash: "0xabc...def",
  metadata: new Uint8Array([]),
});
Key validation rules:
  • eventType must be 0 or 1
  • value must be a non-negative integer (subunit, per ISO 4217 minor units)
  • trustLevel must be 0, 1, or 2
  • sourceChainId must be a supported chain (0, 3338, or 8453)
  • When trustLevel is 1 (on-chain verifiable), sourceTxHash is required
  • rawData must be non-empty when provided (null is allowed, empty array is not)
  • currency on revenue events must match ^[A-Z0-9]{3,10}$; on activity events it must be ""
  • timestamp must be a positive integer; the EventRegistry contract additionally rejects timestamp > block.timestamp (FutureTimestamp revert)
  • metadata is capped at 4096 bytes on-chain (MetadataTooLarge revert above the limit)