Repository navigation
Home
EdgeORE is a non-custodial Android ORE v3 client for Solana Mobile, built in Kotlin and Jetpack Compose by CodesbyFebin.
- Screens: Home · AI · ZK Proof · Settings. Settings holds Receipts, Storage and Nodes.
- Networks: one network selector drives the wallet, balances and ORE card. Devnet is the default.
- ORE v3 deploy: pick squares, then review the exact message, sign in your Mobile Wallet Adapter wallet, and submit once, with no resend. Mainnet is opt-in: each deploy is capped at 0.01 SOL and needs the real-SOL risk tick.
- Receipts: each action gets a receipt signed with an Android Keystore key. The receipt checker verifies the integrity of signed receipt contents.
- AI: no model is bundled. It shows "Model not loaded" until you connect a host you own or download an allowlisted model.
- ZK Proof: "Prover not configured".
-
Signing: release APKs are signed with certificate SHA-256
c2279fb0357bd3b78e577d57b93d5d9af273fb03191264811b6e3696165e62d2(see Release verification).
EdgeORE does not promise rewards or income, and deployed SOL may be lost. It's a hackathon build, provided as is, and not affiliated with Regolith Labs or Solana Mobile.
Links: Website · User docs · Releases · Source · Repository docs
Wiki pages: FAQ · Architecture · Build & test · Release verification
Some handbook chapters below describe earlier review candidates. Each one says which build it covers.
- 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
- 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