Repository navigation
Settlement Status
Program: onchain/programs/receipt-settlement/ — devnet-only prototype, unaudited. Canonical reference: docs/SETTLEMENT-SPEC.md (v2: create_job / accept_job / submit_proof / verify_and_settle / refund_after_deadline).
Merged into main: PR #8, merge commit 38fb71d5c25e (38fb71d5c25ef944152edecfd128ab12e0fce2e0), which brought in feature/settlement-spec-v2 @ 305f1e7 via the integration branch.
Tested source 047657f89b48 (evidence-only head 305f1e7).
| Environment | Result |
|---|---|
| LiteSVM | 25/25 passed, exit 0 |
| Local solana-test-validator, Agave 4.3.0 | 25/25 passed, exit 0 |
Program artifact: SBPF v3, receipt_settlement.so 274,352 bytes, sha256 9ce9addf14b1b432305bbcdfaabe25c174b32f00f27e18534e0b996009bf78a7.
Preserved logs (pinned to the merge commit):
- Branch evidence for
047657f89b48:evidence/anchor-receipt-settlement/047657f89b48/— SUMMARY.md, commands-and-exit-codes.txt, anchor-test-litesvm.log, anchor-test-validator.log, validator-transactions.log, per-test-results.txt. - Re-run on the integration merge
250be029b35c(same .so sha256; LiteSVM 25/25, exit 0; local validator 25/25, exit 0):evidence/integration-0.2.9/gate-250be029b35c/anchor/.
Passing tests in LiteSVM and on a local validator do not establish:
-
Deployment. The program has not been deployed to devnet or mainnet. The J-4 deploy gate (
docs/DEPLOY-DEVNET.md,scripts/deploy-devnet.sh) is prepared and NOT RUN. Once deployed on devnet, the program will be upgradeable. - Android integration. The EdgeORE app has no client for this program; no program ID is embedded and nothing in the app calls it.
- A real SOL payout. All SOL in the tests came from LiteSVM or the local test faucet. No settlement has paid anyone on any public cluster.
Deployment, Android integration and real SOL payout remain unqualified until demonstrated with saved evidence. No token, reward, yield or mining is involved, and no ORE integration is claimed.
Built by CodesbyFebin · Devnet review candidate · Trust boundaries · Qualification
EdgeORE
- The EdgeORE handbook
- Read the evidence ledger
- Clone and pin the Android source
- Prepare the Android build environment
- Run and preserve qualification gates
- Install and identify the candidate APK
- Choose a runtime without tool shopping
- Authorize through Mobile Wallet Adapter
- Use the official mock wallet safely
- Test disconnect and reconnect after restart
- Read balance and obtain devnet funding
- Review the exact transaction message
- Submit once and observe confirmation
- Recover after an interrupted submission
- Understand budgets and spend reservations
- Read a receipt without overclaiming it
- Verify an export on the JVM
- Change signed lamports and observe rejection
- Separate integrity, provenance and completeness
- Use an Ollama-compatible owned host
- Understand endpoint and transport policy
- Evaluate the experimental on-device AI branch
- Evaluate AI quality and privacy claims
- Use the device-local encrypted vault
- Design an owned-node IPFS adapter
- Design backup and restore acceptance
- Pair an owned node with a pinned identity
- Observe health and revoke node access
- Interpret controls and device readings
- Threat model and production boundaries
- Collect diagnostics without leaking secrets
- Design customer-funded SOL contribution jobs
- Specify escrow before writing a program
- Settlement program status
- Use attestation for the claim it can support
- Evaluate federated learning and data contribution
- Bound mesh networking and agent hosting
- Write marketing copy that survives inspection
- Build the website and publish the GitBook handbook
- Contribute without merging every upstream repository