Privacy as Protocol

The conventional model treats privacy as a contractual layer placed on top of an architecture fully capable of surveillance. The provider retains an administrative interface that can read any session, a logging system that records inputs, and a training pipeline that ingests submissions. Privacy, in that model, is the provider's decision to refrain from using capabilities it possesses. ArxCode removes the capability rather than restraining its use. This is the difference between a promise and a property.

Sealed Execution

Work submitted to the network runs inside a sealed execution environment — inputs enter and finished output returns, but nothing in between is observable by the operator, the network, or any third party. A unit of work is called a build.

Four Properties of Sealed Execution

(i)Input confidentiality. The input is decrypted only inside the environment and is never accessible to the operator, the host, or the network.
(ii)Non-retention. Neither the input nor any intermediate state survives the build. When the environment terminates, the data is gone.
(iii)Output integrity. The output is returned only to the holder of the originating wallet key, and its correctness can be attested without revealing the input.
(iv)No training surface. Because the input is never persisted, it cannot enter any training corpus.

Proof of Compute

Correctness is enforced by attestation and redundancy rather than by inspection. An operator cannot earn rewards by claiming compute it did not perform. Rewards are conditioned on a verifiable attestation that the work was carried out inside a properly sealed environment.

The Cost of Tampering

An operator that breaks the seal to read data forfeits the ability to produce valid attestations and earns no reward. The economic incentive is explicit: reading one build costs the operator all future revenue from all builds.

Tokenomics ($ARX)

$ARX is an SPL token on Solana that functions as the metering unit of the network. It is not a governance token with speculative future utility — it is consumed by every build.

Burn-to-Build

Every build permanently removes a quantity of $ARX from circulation proportional to the compute consumed. Usage is deflationary by construction. The act of using the network for its intended purpose reduces supply.

Mint-on-Compute

New $ARX enters circulation through exactly one channel: a node operator delivers verified compute and is rewarded. There is no liquidity mining, no farming airdrop, no emission to bootstrap mercenary capital.

Hold-for-Discount

The per-build rate declines as a user's $ARX balance increases. The same compute costs less to a larger holder — aligning incentives toward accumulation rather than disposal.

Supply Tracks Usage

S(t) = S₀ + M(t) − B(t). Both mint and burn are driven by the same underlying activity. As adoption grows, aggregate burns from many users outpace mint events tied to marginal capacity additions.