Automation-native Layer 1

SET THE RULE.
OREUM DOES THE REST.

Oreum Network is designed as an EVM-compatible Layer 1 built around reliable transaction automation. Create scheduled, recurring and conditional actions with bounded permissions, transparent rules and user-controlled revocation.

Explore Autopilot ↓ Read whitepaper ↗

Oreum Rule 2,500 ORM to Payroll Vault

Frequency Recurring 1st · 09:00 UTC

Authorization Approve once bounded + revocable

Schedule →

SCHEDULED TRANSACTIONS●PAYROLL●SUBSCRIPTIONS●DEFI AUTOMATION●TREASURY●PROGRAMMABLE TIME●

01 / The network

Define the outcome once.
Oreum executes the Rule.

Most chains process immediate transactions well, but future and conditional execution is usually delegated to bots, keepers, backend servers or repeated manual signatures.

Oreum Autopilot turns automation into a first-class network capability. Oreum Rules define exactly what may happen, when it may happen, how much may be spent, how fees are funded, and when permission expires.

02 / Oreum Autopilot

Set the Rule.
Autopilot does the rest.

Autopilot supports protocol-recognized Rules for scheduled and recurring actions at MVP, with event, state, oracle and multi-condition triggers introduced in later phases.

01 — CREATE

Create the Rule

Define the transfer or application action that should happen onchain.

02 — TIME

Define the trigger

Set a date, time, interval, or recurring cadence for execution.

03 — AUTHORIZE

Authorize + fund

Confirm the schedule through a clear wallet or application flow.

04 — EXECUTE

Execute + settle

The network processes the scheduled action when its conditions are met.

03 / What it unlocks

Schedule
what matters.

Oreum’s automation stack is designed for repeatable workflows including payroll, subscriptions, vesting, rewards, AutoStake, DCA, escrow, revenue sharing, treasury Rules and security automation.

Global payroll

Recurring contributor, salary, and contractor payments.

↗

Subscriptions

Recurring memberships, services, creators, and commerce.

↗

DeFi automation

Scheduled deposits, strategies, and time-aware execution.

↗

Treasury operations

Planned distributions, recurring flows, and grants.

↗

Vesting

Time-based token and contributor distributions.

↗

04 / Oreum Autopilot

Automation-native
by design.

Oreum organizes user applications, smart accounts, the automation layer, EVM execution and PoS BFT consensus inside one security domain. The Scheduler, Rules Registry and Automation Gas Lane form the principal automation path.

LAYER 01

Execution Layer

Processes normal smart-contract transactions and scheduled actions under the network’s execution rules.

LAYER 02

Scheduling Layer

Registers time conditions, recurring intent, execution windows, and the lifecycle of scheduled transactions.

LAYER 03

Application Layer

Wallets, dApps, businesses, and developer tools compose Oreum scheduling into products users already understand.

05 / Developer experience

Intent.
Rule.
Execute.

Oreum AI converts natural-language intent into a structured Rule or OneTap action for validation, SafeSign simulation and user approval. Oreum Forge is the later no-code environment for building from verified modules.

Developer architecture ↗

Oreum AI + ForgeAI + Rules

Prompt

Create a payroll dApp that sends ORM to 20 contributors on the first day of every month.

✓ Payroll contract structure
✓ Recipient registry
✓ Recurring schedule configuration
✓ Wallet authorization flow
✓ Frontend transaction state

06 / Whitepaper

The official
v1.0 whitepaper.

Read the complete 24-section Oreum Network Whitepaper covering Oreum Autopilot, Oreum Rules, the Scheduler, Automation Gas Lane, Smart Accounts, OneTap, FlexGas, SafeSign, products, Oreum AI, Forge, security, $ORM utility, governance, roadmap and risks.

24 Sections Key diagrams August 2026 Official v1.0

Read Whitepaper ↗ Download PDF ↓