Documentation

This page provides a professional overview of Lockrion’s execution model, architectural separation, and compliance posture. It summarizes the strict implementation profile: fixed reserve, full pre-funding, immutable smart-contract execution, and deterministic settlement on Solana.

Protocol Overview

Lockrion is a commercially governed deployment platform for autonomous, time-locked reserve issuances implemented as immutable smart contracts on Solana. Governance exists only prior to deployment. After deployment, execution is controlled exclusively by on-chain logic.

Each issuance is an independent instance with immutable parameters, strict reserve funding requirements, deterministic accounting, and post-maturity settlement. Issuances are structurally isolated and do not share escrow accounts or accounting state.

Lockrion does not provide investment advice, does not guarantee yield, and does not manage participant assets after deployment.

Architecture

Layer Separation

  • Governance Layer (off-chain): issuer admission, parameter screening, fee determination, and deployment decisions prior to deployment only.
  • Issuance Layer (on-chain): immutable execution, accounting, escrow control, and settlement after deployment.
  • Interface Layer (UI): non-authoritative interface; users may interact directly with issuance contracts.

Issuance Independence

  • Each issuance maintains isolated state and isolated escrow accounts.
  • No pooled reserves exist.
  • Failure or inefficiency in one issuance does not affect others.

Execution Model

Immutable Parameters

Issuance parameters are fixed at deployment and cannot be modified. The v1 profile includes fixed reward asset (USDC), fixed reserve_total, fixed start/maturity timestamps, and fixed claim window configuration.

Reserve Funding Gate

Participation is disabled until the reward reserve is fully funded on-chain. Partial funding is rejected. Funding must occur strictly prior to the participation window.

Time Window Rules

Deposits are permitted only during the participation window. Deposits after maturity are rejected. Withdrawals before maturity are prohibited by design.

Deterministic Accounting

Accounting and distribution are deterministic, integer-based, and reproducible. No floating-point arithmetic is used. Overflow/invalid states must fail transactions rather than produce ambiguous outcomes.

Escrow Model

Deposit Escrow

Participant deposits are held in a dedicated deposit escrow account (lock asset). Deposits remain isolated and are not used for reward funding. Deposit release is permitted only by immutable post-maturity withdrawal logic.

Reward Escrow

The full USDC reward reserve is held in a dedicated reward escrow account. The reserve cannot be increased after deployment. Reward funds can move only through predefined claim/sweep/reclaim paths.

Non-Commingling Guarantee

Deposit escrow and reward escrow are strictly segregated. No commingling is permitted under any circumstances.

Settlement

Maturity Transition

At maturity, participation ends permanently. No new deposits are accepted. Accounting stops accumulating new participation weight beyond the defined window.

Claim Phase

Reward claiming is available within a predefined claim window after maturity. Claims are computed deterministically and are bounded strictly by the fixed reserve.

Deposit Withdrawal

Deposits remain withdrawable after maturity. Withdrawal is not dependent on reward claiming.

Unclaimed Reward Handling

Unclaimed rewards follow predefined immutable rules after claim window expiration. This handling does not modify historical accounting and does not recalculate results.

Immutability

Post-Deployment Finality

  • Program upgrade authority is revoked at deployment.
  • No administrative keys are retained for changing issuance behavior.
  • No pause, emergency override, or discretionary intervention mechanisms exist.
  • Parameters and execution logic remain immutable for the lifetime of the issuance.

Reproducibility

Outcomes are reproducible from public on-chain data. Any observer can verify reserve funding, escrow balances, timestamps, and settlement outcomes.

Compliance & Risk

Platform Role Limitation

  • Lockrion provides deployment infrastructure and a convenience interface.
  • Lockrion does not act as an asset manager, custodian, broker, or investment advisor.
  • Lockrion does not guarantee yield, profitability, or economic performance.

Participant Risk Allocation

  • Participants bear market, liquidity, volatility, and opportunity risks of the locked asset.
  • Reward outcomes are bounded strictly by the declared reserve and proportional rules.
  • Participation is voluntary and governed exclusively by public on-chain rules.

Issuer Risk Allocation

  • Issuers bear responsibility for fully funding the reward reserve prior to participation.
  • Issuers cannot access participant deposits and cannot modify the issuance after deployment.
  • Any reclaim/sweep paths are strictly predefined and are not discretionary.

Compensation Framework

Lockrion v1 does not implement on-chain compensation mechanisms. Compensation, if any, is external, discretionary, and must not modify on-chain accounting, state, or results.

Reserve Commitment Theory (RCT) Basis

Lockrion implements Reserve Commitment Theory under a strict implementation profile intended to maximize predictability and eliminate discretionary behavior. Issuances are fixed commitments with time-discrete accounting, bounded reserves, proportional deterministic distribution, and structural independence.

Constitutional Principles

  • Fixed Commitment
  • Reserve Non-Extractability
  • Absolute Issuance Immutability
  • Temporal Discreteness
  • Proportional Distribution
  • Issuance Independence
  • Reproducibility
  • Compensation Boundaries

Lockrion v1 Implementation Profile

  • Reward asset is fixed to USDC.
  • Reward reserve must be fully funded before participation begins.
  • Reserve increases are not permitted after deployment.
  • Settlement occurs through a post-maturity claim phase with a predefined claim window.
  • Arithmetic is deterministic, fixed-width, and integer-based.
  • No administrative or governance intervention is possible after deployment.