RIFT ENGINE VAULTS

Engine Activity. Verified.

Engine Activity. Verified.

Independently inspect the activity behind the RIFT Engine.

Transparency should not require trust.

RIFT Engine activity is designed around publicly verifiable records. Eligible trades and pool transfers displayed through the platform are connected to Hyperliquid Layer-1 transaction hashes, giving users a direct path from what they see inside RIFT to the underlying public blockchain record.

No private dashboard is required to verify the transaction.

No special permission is required.

The record exists independently of RIFT.

What Engine Activity Shows

What Engine Activity Shows

Engine Activity provides a live view of completed profitable executions produced across the Engine vault network.

Each displayed execution includes the information needed to understand and independently check the trade.

Rift-Dont-Trust-Verify

Field

What It Represents

Asset / Direction

The asset traded and whether the vault bought or sold

Price / Size

The executed price and the size of the fill

Time

When the execution occurred

Realized P&L

Profit realized when the position was closed

L1 Receipt

The Hyperliquid transaction hash linking the activity to its public record

The transaction receipt is the bridge between the RIFT interface and independent verification.

Go Beyond the Activity Feed

Go Beyond the Activity Feed

Engine Activity is only the starting point.

Each vault provides a broader performance and activity view so users can evaluate more than a single execution.

Vault information can include:

Performance history across multiple time periods

Trading volume

APR

Total Value Locked

Current open positions

Depositor information

Trade history

The Insights layer also records transfers between the pool and participating vaults, with those movements connected to their respective on-chain receipts.

Rift-Dont-Trust-Verify

How Independent Verification Works

How Independent Verification Works

Verification is designed to be straightforward.

01 — Choose an Execution

Open Engine Activity inside RIFT and select any displayed trade.

02 — Open the Receipt

Select the transaction receipt. Inspect the public Layer-1 transaction associated with that execution.

03 — Match the Execution Details

Compare the public record with RIFT.

Check:

Asset

Direction

Position size

Execution price

Timestamp

Execution price

Timestamp

04 — Review the Vault

Open the corresponding vault and confirm that the execution appears within its recorded trading history.

05 — Evaluate the Bigger Picture

Individual trades provide limited information.
A stronger assessment comes from reviewing performance and execution over longer periods rather than judging a vault by one isolated transaction.

Reading an Engine Vault

Reading an Engine Vault

A vault contains several different data points.

Each answers a different question.

APR

APR represents an annualized rate implied by recent performance.

It should be viewed as a performance indicator rather than a guaranteed future outcome.

TVL — Total Value Locked

TVL shows the capital currently deployed within the vault.

It provides context around the scale and depth of the environment.

Realized P&L

Realized P&L reflects profit already locked in through closed positions.

This is the type of execution surfaced through Engine Activity.

Open Positions

Open positions show current live exposure.

Users can review:

Assets

Position sizes

Current unrealized results

This provides context beyond completed trades.

Monthly History

Longer-term history helps place short-term performance into context.

The operating model prioritizes consistency across changing market conditions rather than isolated periods of performance.

The RIFT Verification Standard

The RIFT Verification Standard

RIFT applies several principles to the Engine Vault environment.

Performance Must Be Maintained

Vaults are expected to sustain the required performance standard to remain displayed.

If a vault no longer meets that standard, it may no longer remain visible within the Engine environment.

Capital Movements Are Receipted

Pool capital can rotate through Engine vaults.

Transfers are recorded with on-chain receipts and reflected within the Insights environment.

Displayed Fills Must Be Verifiable

Only fills connected to a verifiable Layer-1 transaction hash are displayed through this verification framework.

Executions without an individual verifiable receipt are excluded rather than presented as independently verifiable activity.

Data Follows the Public Record

Displayed information is designed to update shortly after the associated public blockchain activity becomes available.

Verify First. Decide Second.

Verify First. Decide Second.

RIFT is built around a simple principle:

If activity cannot be independently verified, it should not be presented as verified activity.

Review the trade. Open the receipt. Inspect the vault. Study the history. Make your own assessment.

Open RIFT Engine Vault

Next-generation multi-asset trading infrastructure where your Vault becomes the foundation for trading, investing, capital allocation, and intelligent execution.

Resources

Blog

COMMUNITY

© 2026 RIFT. All rights reserved.

Built for the future of markets.

Next-generation multi-asset trading infrastructure where your Vault becomes the foundation for trading, investing, capital allocation, and intelligent execution.

Resources

Blog

COMMUNITY

© 2026 RIFT. All rights reserved.

Built for the future of markets.