The Priime Stack

One verifiable stack, from the metal up.

Why a stack?

Priime is a stack: the Processor at the base, composable modules above it, and the apps you use on top. This page is how each layer works, and why every action it takes is provable, not something you have to trust.

The Priime Processor // 01

A Processor you do not have to trust.

The Priime Processor runs your strategy off-chain and brings the result on-chain, provably. It monitors every block and acts only when something needs to change, doing three things: fetch, compute, settle. The difference from a trading bot is one word: verifiable. A set of distributed operators each run it, and the chain only accepts a result a quorum of them produced, matched, and signed.

Exogenous Risk01
Dependenciesall clear
ORAVENUEBRIDGESTABLEFUNDINGRPC
watched as one stack
Actions
Hold
De-risk
Dynamic Leverage02
Leverageon target
2.4×
leverage vs target
Actions
Lever up
Hold
Deleverage
Dynamic Hedge03
Net deltaneutral
0.00 ETH
hedge vs LP
Actions
Hold
Resize short
Endogenous Risk04
Health factorin band
EmergencyTargetLever-up
health factor
Actions
Deleverage
Hold
Lever up
Module inputsVerifiable compute
Priime ProcessorPR∞● Live
Live · every block
Operators 7 / 7
operators run the WASM · a quorum signs the result
Fetch
Compute
Settle
Settled on every chainVerified ✓
EVMSVMMOVE
01FetchAny data, on-chain and off. Contract events, prices, oracle feeds, and off-chain APIs. Triggered by an event, a cron schedule, every block, or an external feed.
02ComputeAny strategy, as sandboxed WebAssembly. Runs off-chain with no on-chain gas ceiling, in a sandbox that only touches what you permit. Deterministic by design.
03SettleVerified, on-chain. Operators run the same logic and sign. Once a quorum of matching signatures arrives, one transaction settles and the chain validates the signatures.
Verifiable // proof

Every action, provable by design.

How is it made provable?

A registered, weighted set of operators each re-runs the same deterministic logic on the same inputs. The aggregator only proceeds when enough produce identical results and sign them. The on-chain verifier checks those signatures against the operator set. An insufficient quorum is rejected by design, so no single party can move your position.

PRIIME MODULETRIGGERcontract · event · cronPRIIME PROCESSORoperators run the WASMOPERATOR 1runs the WASMOPERATOR 2runs the WASMOPERATOR 3runs the WASMOPERATOR 4runs the WASMAGGREGATORquorum reachedk of n signatures ✓CHAINverified
VerifiableProvable execution by design, not trust me.
Block-timeMonitors at chain cadence, acts before problems land.
Multi-chainOne stack, across EVM, SVM and MOVE.
Non-custodialYour keys, your vault.
OpenAuditable, no black box.
Go deeper: verifiable execution →
The modules // 02

A module is one Observe, Reason, Act loop.

What is a module?

A module is one unit of automation: a trigger, a piece of sandboxed WebAssembly, and a submission. Something to watch, logic to run, an action to take. Modules are composable, so an app is just a set of modules running together, and because a module can return nothing, it acts only when its condition is met.

A
Observe
the trigger

A trigger watches for the condition that matters: an on-chain event, a cron schedule, every block, or an off-chain feed.

B
Reason
the logic

The module logic runs off-chain as sandboxed WebAssembly. Deterministic, so the same inputs always produce the same result.

C
Act
the submission

If action is needed, operators sign the result and a quorum settles one verified transaction. If not, the module returns nothing and holds.

Core modules

Each module watches one signal, and acts only when it must.

How do they fit together?

A strategy is an arrangement of these. The screen is what a module sees; the keys are what it can do, lit the moment it fires. They patch into one another, and into the Priime Processor.

Exogenous Risk01
Dependenciesall clear
ORAVENUEBRIDGESTABLEFUNDINGRPC
watched as one stack
Actions
Hold
De-risk
Dynamic Leverage02
Leverageon target
2.4×
leverage vs target
Actions
Lever up
Hold
Deleverage
Dynamic Hedge03
Net deltaneutral
0.00 ETH
hedge vs LP
Actions
Hold
Resize short
Endogenous Risk04
Health factorin band
EmergencyTargetLever-up
health factor
Actions
Deleverage
Hold
Lever up
↓ to Priime Processor
Go deeper: the modules in depth →
The Priime advantage

Off-chain speed. On-chain trust. Priime Processor.

How does it work?

Priime is verifiable off-chain compute. Your code runs in fast WASM sandboxes across a set of distributed operators, each re-runs the exact same deterministic logic and signs the result. A thin on-chain contract accepts it only when a quorum agrees. The verifiability of a distributed operator set, settled with the trust and finality of the chain, without paying to run your logic on-chain.

What you're weighing
Centralized serverLambda
On-chain contractEVM
Priime
Cost to fake the result
Compromise 1 box, nothing proves it ran your logic
Beat the whole chain
Collude a quorum of distributed operators, in the open, against sigs the chain rejects
Where trust comes from
Trust 1 company
The chain itself
Both: verifiability from a distributed operator set + finality from settling on-chain
On-chain verifiable?
“Trust me”
Native
Thin contract verifies the M-of-N operator signatures
Compute speed (per run)
~100ms cold start
Block-bound, ~15–30 TPS (L1)
µs cold start, ~5–50% of native (WASM sandbox)
Time to settle on-chain
Lowest, no consensus
Block time
Quorum signing + 1 settlement tx (small latency tail)
Cost
Cheapest (but unverified)
Gas per op (SSTORE ~20k)
More than 1 Lambda, but orders of magnitude cheaper than the same compute on-chain. The premium is the trust
Your code
Any language, floats, heavy
No native floats, ≤24KB (EIP-170)
Any language (Rust/Go/C++/TS), floats OK, no size cap, must be deterministic
Build difficulty
Deploy in minutes
Solidity + gas/size golf
Write one WASM component containing the logic, ship it
Single point of failure?
Yes
No
No execution SPOF, a quorum, not one party

Off-chain speed, on-chain trust, no compromise: distributed operators in WASM sandboxes agree, and a quorum of their signatures settles on-chain.

Try the stack

Same modules, assembled differently.

How are apps built?

Priime Pools and Priime Loop are different combinations of the same modules, running on the same Priime Processor. A new app is a new arrangement of modules, not new infrastructure.