◒Singularity Protocol

Technical whitepaper / Research draft

Singularity Protocol

Verifiable AI compute with Solana settlement

Research draft · v0.1

Abstract

A buyer outsourcing inference cannot infer from a response alone which model ran, which inputs were used, or whether the provider followed the agreed computation. Singularity Protocol proposes a job protocol in which a buyer commits to execution terms, a worker returns output with independently checkable evidence, and a Solana program settles according to a policy pinned when the job was opened.

1. Job commitments

A job binds an identifier, model and runtime digests, an input commitment, a deadline and an evidence policy. The runtime digest includes the quantization and rounding rules. Where a job requires deterministic generation, the terms also fix the decoding procedure and randomness. Encode and domain-separate those fields before hashing so that receipts cannot be reused across jobs or deployments.

2. Admission and execution

Eligible workers post collateral and complete a challenge against a specified reference computation. Challenge inputs should change between rounds and include an expiry. Passing establishes knowledge of a valid result for that challenge. It gives no direct evidence of physical hardware ownership, throughput or prompt confidentiality. For the first prototype, constrain execution to a small, deterministic model with reproducible test vectors.

3. Evidence and committee decisions

A worker publishes a receipt binding the job commitment to the output digest. A proof-based policy should verify that the committed runtime transformed the agreed input into the committed output. Benchmark proof generation, verification and data movement separately. A stake-weighted committee can attest to receipt validation under a separate policy. Use a fixed snapshot, signed job identifiers and an explicit quorum rule. Committee signatures provide a statement about what the committee accepted. Their reliability depends on the committee assumptions and available evidence.

4. Settlement and failure

The proposed Solana state machine moves an escrowed job through open, accepted, submitted and settled states. Expiration releases the escrow under published rules. Receipt validation and terminal state updates must prevent double payment. Specify evidence for objectively attributable violations before implementing penalties. If a quorum fails to form, allow a defined timeout path. The website simulator illustrates quorum arithmetic only.

5. Privacy and availability

Public commitments can reveal timing, prices and repeated activity. Keep raw prompts out of public state. A proof can establish correctness without proving that the execution host kept a prompt private. Any future confidential execution mode needs its own attestation, key release and threat model. Output delivery and evidence availability also need separate checks so a buyer can actually retrieve what they paid for.

6. Validation milestones

First reproduce deterministic inference and measure the full evidence pipeline on documented hardware. Next test worker admission, timeout refunds, repeated receipts and conflicting committee decisions on a local validator. Publish the implementation, measurements and deployment addresses before presenting the system as live. This release consists of a research website, a whitepaper and an illustrative quorum simulator.

Download Markdown

Solana wallet · ARC

ARC mint reference B7hdpigsryz4oFq963EaWZXDBxcitNGJ3cj7ECn9parc

Staking, rewards and yield figures on this site are simulated.