# DEPROOF-
A contribution workspace for Solana Mobile × SKR.
Run supported jobs on infrastructure you own. Verify the result. Review the payment. Keep the receipt.
Get started · Qualification · Threat model · Source
Built by CodesbyFebin
---
DePIN participation creates scattered records: node logs, job results, bandwidth measurements, wallet transactions and provider dashboards.
A payment alone does not explain the contribution. A signed record alone does not prove the work was independently verified.
Deproof connects those records so contributors can inspect:
- What ran — the job, runtime and inputs.
- What was verified — the result and verification method.
- What was approved — the exact transaction message.
- What was paid — observed settlement, when available.
- What can be exported — portable contribution evidence.
| Stage | Action | Record |
|---|---|---|
| 01 · Contribute | Run a supported job on an owned node | Job identity, input digest and operation history |
| 02 · Verify | Check the result using a separate verifier | Verification outcome and stated assumptions |
| 03 · Review & pay | Inspect and authorize a supported SKR payment | Exact-message review and transaction reference |
| 04 · Keep the receipt | Link evidence to observed settlement | Exportable contribution receipt |
The SKR payment journey is proposed functionality until its end-to-end implementation and qualification are recorded.
Deproof’s Android workspace connects to a user-owned node agent.
Compatible workloads run on the paired host. The phone provides the control and evidence interface; it does not automatically run every DePIN project.
- Scoped pairing and authorization
- Supported workload discovery
- Hardware and capability observations
- Operation controls and health information
- Resource limits and revocation
- Contribution history and receipt export
Each adapter defines its own:
- Supported operating systems and hardware
- Installation artifacts and pinned versions
- Required permissions and credentials
- Available runtime operations
- Measurement sources and verification rules
- Qualification status
A catalog entry is not proof of compatibility. External project support must be qualified individually.
Deproof distinguishes four evidence levels:
| Evidence level | What it establishes |
|---|---|
| Local observation | A particular measurement source reported a value |
| Node-signed record | A node identity signed the recorded data |
| Independently verified result | A separate verifier checked a defined result |
| Provider-acknowledged contribution | An external provider acknowledged the contribution |
These levels are not interchangeable.
A file hash checks integrity, not physical truth. A computation proof covers its defined computation and assumptions. A node signature does not independently establish bandwidth delivery. A contribution receipt does not automatically establish payment.
The proposed SKR workflow connects a useful service to a reviewable payment:
Select a job → execute → verify → review payment → authorize → observe settlement.
The initial design uses explicit requester-approved payment. It does not imply escrow, automatic rewards or guaranteed earnings.
Implementation requirements include:
- Official mint and token-program validation
- Exact integer amount handling
- Network and recipient checks
- Complete serialized-message review binding
- Validation of wallet-returned signed transactions
- Separate verification and payment states
- Duplicate-payment protection and recovery
- Unavailable observations shown explicitly
Wallet private keys remain in the wallet.
SKR is separate from DEPR.
DEPR is Deproof’s ecosystem brand; $DEPR is a brand concept only.
This project does not define a DEPR token issuance, supply or launch.
| Surface | Purpose |
|---|---|
| Now | Account context, recent activity and contribution controls |
| Review | Inspect transaction details and enforce signing gates |
| Receipts | Inspect records, observations and exports |
| Nodes | Pair and monitor owned infrastructure |
| Projects | Explore supported adapters and compatibility |
| Proof jobs | Discover jobs, match capabilities and inspect verification |
Deproof is under active development.
The repository includes Android, node-agent, proof and portable-verification source, documentation and qualification tooling.
Historical local qualification reports cover their recorded source and environment. They do not automatically qualify another branch, operating system, device or external provider.
Production readiness is not claimed.
Consult:
Planned integrations are not partnerships. Mock fixtures must remain separate from production behavior.
Follow the setup guide for the project’s pinned toolchain.
git clone https://github.com/CodesbyFebin/DEPROOF-.git
cd DEPROOF-
bash scripts/setup-android.sh
bash ./gradlew :app:testDebugUnitTest --stacktrace
bash ./gradlew :app:lintDebug --stacktrace
bash ./gradlew :app:assembleDebug --stacktraceRun broader qualification after installing its prerequisites:
bash scripts/qualify.shRecord actual outcomes. These commands are not a promise that every revision or environment passes.
| Component | Responsibility |
|---|---|
| Android app | Wallet interaction, node controls, review and receipts |
| Node agent | Scoped operations and observed runtime state |
| Project adapters | Project-specific compatibility and interfaces |
| Prover / verifier | Supported computation execution and verification |
| Evidence tools | Manifest validation and portable inspection |
| Website / docs | Setup, project scope and qualification boundaries |
- Reliable mobile core — exact-message review and persistent receipts.
- Evidence workflows — tasks, import, backup and recovery.
- Owned-node operations — supported hosting, bandwidth and proof jobs.
- Multi-project adapters — independently qualified workloads.
- SKR contribution payments — explicit authorization and settlement linkage.
- Broader qualification — devices, providers, accessibility and release.
The authoritative blueprint contains 336 overlapping registry records: 120 features, 100 checks, 30 ecosystem requirements and 86 function contracts.
These describe scope—not a count of completed capabilities.
Our target demonstration is one complete contribution journey:
- Pair an owned node from Android.
- Select and execute a supported bounded job.
- Independently verify the result.
- Inspect the contribution evidence.
- Demonstrate the qualified payment flow, if available.
- Export the receipt and verify its supported contents separately.
Show failures too: changed messages, tampered evidence, revoked permissions and unavailable providers.
We welcome reproducible bug reports, contract-specific tests, device qualification, accessibility improvements and adapter reviews.
Include your source revision, environment, commands and observed results. Do not replace missing integration with fabricated signatures, balances, measurements or rewards.
See LICENSE and licensing notes for source licensing and imported-asset boundaries.
DEPROOF / DEPR — Built by CodesbyFebin
Deproof / DEPR — Built by CodesbyFebin. $DEPR is a brand concept only; no token issuance.
Native Android source, domain tests, schemas, portable verifier, user-owned Go node agent and local documentation website are now present. Android node controls use authenticated real API operations, durable operation recovery and signed contribution receipts. Local qualification covers Android assembly/JVM tests/lint, a fixed isolated hosting profile on the tested Docker VM, educational Groth16 proofs, read-only public RPC observations and automated browser accessibility checks. The project remains incomplete: physical-wallet/hardware, broader host support, production proof setup, external providers, manual accessibility and release gates remain unresolved. Consult the qualification report for exact outcomes and uncovered requirements.
./scripts/setup-android.sh
./gradlew assembleDebug testDebugUnitTest lintDebug
./scripts/qualify.shSee setup, qualification report, machine-readable status, threat model and privacy. Proposed MIT applies to new source; imported asset rights remain unresolved in licensing. Original README assets above are preserved.