Locksley
Locksley ProtocolDoc LP-09 · Rev 12026-07-09Chain 4663

The Charter

The public specification of the Locksley Protocol — its definitions, mechanics, and the adverse conditions, written as numbered clauses. Every figure below is enforced on-chain and independently verifiable. Where the design is still maturing, this document says so in the body, not the fine print.

§1Perpetual Compute Rights

§1.1

A Perpetual Compute Right (PCR) is a transferable ERC-721 deedto a fixed quantum of normalized network capacity, denominated in Compute Units (CU). It is pool-backed: the deed binds to the network’s live capacity, not to any single accelerator. Perpetual denotes a right, not silicon — the entitlement outlives the machine that first serves it.

§1.2

Acquisition is one-time. Capacity is purchased once, in tokenized USD, at mint. There is no subscription and no recurring protocol charge for holding the deed.

§1.3

The instrument coordinates three parties. (a) The holder pays once and holds capacity — usable directly, leasable on the spot market, or sellable as a deed. (b) The providerpledges hardware and staked $LOXLEY; the holder’s payment streams to it only for served uptime. (c) The network guarantees the two never diverge: sold capacity may not exceed what providers actually run, and failed hardware is reassigned with its remaining bond.

§1.4

Cashflow follows title. Whoever holds the deed at the moment of settlement receives spot-lease income and slash compensation. Selling the deed transfers every future entitlement with it.

§2Compute Units

§2.1

Heterogeneous accelerators are normalized to a single integer unit — the Compute Unit (CU) — so that one deed can be served by any qualifying hardware in the pool. CU is always an integer; there are no fractional units.

§2.2

Normalization is governed. The mapping below is the v1 normalization curve; $LOXLEY governance may revise it as hardware generations change. Existing deeds retain their CU count — revisions affect how new capacity is counted, never the size of rights already sold.

AcceleratorClassCU (v1)
H100 SXM 80GDatacenter16
A100 80GDatacenter8
RTX 4090 24GProsumer3
v1 normalization curve · governed by $LOXLEY
§2.3

A provider’s capacity in CU is the sum over its fleet. Allocation is local: assignedCU ≤ capacityCU, counted against live hosts only.

§3Minting & the invariant

§3.1

Every mint enforces the honesty invariant. A mint of cu units reverts unless sold capacity, including the new units, stays within the live-capacity safety bound. It is contract-enforced and fuzz-tested — an invariant, not a policy — so a perpetual right can never degrade into a queue.

Honesty invariant · checked at mint
totalSoldCU + cu   ≤   liveCU × safetyBps ÷ 10000
v1: safetyBps = 8000   →   sold CU never exceeds 80% of live capacity
§3.2

The mint price (pricePerCU × cu, in USD) is split atomically on settlement:

ShareDestinationPurpose
70%BondEscrowStreams to the assigned provider for served uptime
15%RolloverReserveHardware-refresh treasury
15%FeeVaultProtocol fee → $LOXLEY buyback
§3.3

The deed is an ERC-721 with fully on-chain SVG/JSON metadata— no external URI, no server that can revoke or rewrite it.

§3.4

Secondary sales carry a 2.5% ERC-2981 royalty routed to the FeeVault, where it fuels the $LOXLEY buyback. The royalty funds the protocol, not a treasury multisig.

§4Bond streaming

§4.1

The bond streams linearly against provider online-seconds, not wall-clock time. Vesting is measured across 1095 days of attested uptime.

Accrual · per stream
accrued = principal × vestedOnlineSeconds ÷ vestingSeconds
vestingSeconds = 1095 days of provider online-time  (≈ 3 years)
§4.2

Online-seconds accumulator. onlineSecondsOf(p) is a monotonic counter that advances only while the oracle attests the provider online. Each stream stores a snapshot; one oracle flip meters allof a provider’s streams at once — O(1) status updates regardless of stream count. Payment halts the same block a provider goes dark.

§4.3

Migration.On reassignment, amounts already accrued stay with the departing provider; only the unvested remainder follows the deed to its replacement. The holder’s entitlement is uninterrupted across the handover.

§4.4

Retirement. Retiring a deed returns its unvested bond to the Rollover Reserve. Retirement is blocked while the deed is encumbered by an active spot rental.

§5Slashing conditions

§5.1

These are the adverse conditions, stated plainly. When a provider breaches its SLA, staked $LOXLEY is slashed and the proceeds are routed largely to the holders it failed.

ParameterValue
Grace window300 s
Slash per incidentassignedCU × 1 LOXLEY × downtimeHours
Per-incident cap10% of collateral
To affected holders80%
Burned20%
Jail conditionstake < requiredStake
Unbonding period14 days · slashable throughout
Parameters governed by $LOXLEY · PARAM_ROLE at genesis, timelock at maturity
§5.2

Compensation reaches holders through a per-CU accumulator (compPerCUAcc). A deed snapshots the accumulator on mint and reassignment and claims the delta × its CU — no loops, O(1) per claim, regardless of how many deeds exist.

§5.3

Jailed providers, whose stake has fallen below the required collateral, are removed from allocation until they top up. The 14-day unbonding queue is slashable for its entire duration, so a provider cannot exit ahead of a pending breach.

§5.4

We state the limits honestly: the oracle committee is permissioned in v1. Permissionless challenge windows and on-chain dispute are on the roadmap — not yet live. Slashing is capped per incident and is not a full indemnity against loss.

§6Spot leasing

§6.1

Holders list idle CU on the SpotMarket at a price per CU-hour. Renters prepay for a bounded term (minHours … maxHours); capacity is reserved for the duration of the rental.

§6.2

A 5% protocol fee is split between the FeeVault and the Rollover Reserve; the net accrues to the current PCR owner. Cashflow follows title — selling the deed transfers accrued and future lease income with it.

§6.3

Settlement is permissionless. Anyone may settle an expired rental; released capacity returns to the holder or is re-listed. No privileged operator sits between a lease and its payout.

§7Rollover Reserve

§7.1

Inflows. 15% of every primary sale, a share of protocol fees and royalties, and the unvested bond of any retired deed.

§7.2

Purpose. The Reserve finances hardware refresh — the replacement of aged accelerators — so perpetual rights outlive the silicon that first served them. Disbursement is timelock-gated and governed by $LOXLEY.

§7.3

Every disbursement is an on-chain, event-logged transaction. The Reserve is a program, not a promise; its balance and every outflow are public.

§8$LOXLEY

§8.1

$LOXLEY is an ERC-20 with Permit and Votes (timestamp clock) and a fixed supply of 1,000,000,000. There is no mint function beyond genesis; supply cannot inflate.

§8.2

Utility is threefold: provider collateral (staked and slashable), governance (protocol parameters and the Reserve), and buyback target (protocol fees purchase LOXLEY, distributed to provider stakes via the RewardsDistributor).

§8.3

The full token page — supply, staking, buyback trail and governance thresholds — is at /token.

§9Proof of compute

§9.1

Proof-of-compute honesty in v1 rests on oracle-attested heartbeats and challenge sampling, with TEE attestation where the hardware supports it. Fully verifiable execution is on the roadmap, and named as such here rather than implied.

§9.2

Online-seconds are metered against block timestamps. On Arbitrum-stack chains (Nitro), block.timestamp tracks the sequencer clock and advances monotonically; the accumulator is written to tolerate this by only ever moving forward, never rewinding on a timestamp anomaly.

§9.3

The oracle holds ORACLE_ROLE: it records online/offline transitions and files SLA breaches. It cannot mint deeds, move bonds, or seize collateral outside the slashing rules in §5.

§10Contract registry

§10.1

Every address is read live from the deployment artifact for the active chain. Switching testnet → mainnet is config-only; no chain constant is hardcoded in this document.

Fetching the registry…

§11REST endpoints

§11.1

The indexer’s REST API is the single source of truth for every figure the frontend shows — landing, registry and dashboard read the same numbers.

MethodEndpointReturns
GET/api/statsNetwork capacity, money and token aggregates
GET/api/providersProviders: capacity, stake, uptime, streams
GET/api/pcrsAll deeds: CU, provider, bond accrual, listing
GET/api/market/listingsOpen spot listings and their rentals
GET/api/activityChronological protocol event feed
GET/api/portfolio/:addressDeeds, spot income, compensation, provider role
POST/api/heartbeatProvider uptime heartbeat for the oracle service

§12Risk disclosures

§12.1

A PCR is a utility right to compute capacity. It is not a security, not a deposit, and not a guaranteed-income product. Spot income depends on demand and served uptime and may be zero.

§12.2

Hardware obsolescence is handled by the Rollover Reserve program, not by magic. Refresh depends on the Reserve balance and on governance executing disbursements; it is a best-effort treasury, not an insurance guarantee.

§12.3

Slashing protects holders but is capped per incident(§5) and depends on the oracle committee, permissioned in v1. Compensation may not cover the full value of a prolonged outage.

§12.4

Regulatory positioning. Locksley is infrastructure for purchasing and transferring rights to compute. Nothing in this Charter is an offer of securities or investment advice; deed holders are responsible for their own legal and tax compliance in their jurisdiction.

End of instrument · LP-09 · Rev 1

The terms are the contract.
The contract is on-chain.