Repository navigation
Build and Test
Febin Francis edited this page Oct 13, 2026
·
1 revision
Requirements: JDK 17, Android SDK (compile SDK per app/build.gradle.kts). Dependency versions are pinned (Kotlin 2.0.21, AGP 8.7.3, MWA clientlib-ktx 2.0.3); do not bump them without re-testing.
./gradlew :app:assembleDebug
./gradlew :app:testDebugUnitTest
./gradlew :app:lintDebug
Each suite is recorded on its own; counts are never added together.
| Suite | Commit | Ran | Passed | Skipped | Failed |
|---|---|---|---|---|---|
Android unit tests (:app:testDebugUnitTest) |
main 4f6e207
|
391 | 382 | 9 | 0 |
Android unit tests (:app:testDebugUnitTest) |
PR #30 head | 396 | 387 | 9 | 0 |
Other suites (receipt checker, edgeore-kit Python tests, screenshot verification, release R8 build) run in GitHub Actions; see each workflow run for its own counts. Lint passes against committed baselines (config/detekt, config/ktlint).
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