Welcome

The EdgeORE handbook

EdgeORE brings a native Android workspace, a Solana wallet review path, an owned-host AI client, a local encrypted vault, scoped node access and portable receipt verification into one product direction. The name is a brand. It does not identify a token, a Solana mining protocol or a guaranteed source of earnings. The recorded review candidate is a debug build for devnet. This handbook explains how to inspect that candidate, reproduce its gates and qualify its behavior without confusing a working screen with a completed service.

Choose a learning path

If you are evaluating the project, begin with the evidence ledger, hosted preview and receipt chapters. Those explain what can be inspected today and which results are still missing. If you are building the Android app, read environment setup, source identity, wallet authorization, exact-message review and durable recovery in that order. If you operate an owned host, continue to endpoint policy, Ollama, node pairing and revocation. If you are designing a contribution network, read the roadmap chapters after the current implementation; those chapters do not describe a deployed marketplace.

A browser preview is useful because it removes the need for local virtualization just to inspect the interface. It does not automatically supply a compatible wallet, prove Android hardware behavior or establish that a transaction was confirmed. This website's interactive phone uses sample data. The linked Appetize session runs an Android APK, while the concept phone is a React presentation. Their labels deliberately differ. A customer should understand that difference before clicking either experience.

Understand the candidate

The recorded APK is version 0.2.8-review, versionCode 10, package com.edgeore.app, stamped d675002bd701. Its preserved Android gate reports 164 tests: 163 passed and one skipped, with the live node-agent integration run recorded separately. The JVM receipt checker reports seven tests in its own suite. These are historical results associated with a specific source revision and artifact. They are not a claim that every later branch, every Android device or every wallet has passed the same checks.

Hosted launch and navigation are recorded in the Android repository. Wallet authorization was attempted, and a later diagnostic branch improves previously silent failures. The latest session notes leave disconnect, reconnect after restart, a small devnet transfer, interrupted-submit recovery and a real-transfer receipt incomplete. Do not promote those rows to PASS because a fixture verifies or because an authorization sheet opens. The conditions for passing each row are explained in dedicated chapters.

Follow the evidence vocabulary

Implemented in source means a code path exists. Test passed means a named automated test produced a preserved result. Recorded means an artifact captures a runtime observation. ATTEMPTED means the action began but did not establish its acceptance criteria. NOT_RUN means the relevant observation has not been completed. NOT_IMPLEMENTED means there is no released code path. Unavailable means a runtime could not supply a value or capability. None of those statuses can be substituted for another to make a page look more complete.

Work through a first exercise

Open the Android repository and locate its qualification report, evidence directory and Appetize session note. Write down the APK source stamp, the environment of the screenshots, the two separate test totals and one remaining runtime gate. Then compare those facts with the website status page. If the website says more than the artifacts support, correct the website. This exercise is the simplest contribution a reviewer can make, and it catches errors that another feature does not solve.

The handbook is maintained as Markdown with a GitBook summary and configuration. Its website reader and GitBook import use the same chapter text. Publishing this collection to a GitBook account is a separate owner operation; the files themselves are not a hosted GitBook space. Treat links, source pins and commands as versioned material that should be reviewed when the Android candidate changes.

---

Wiki home · Qualification updates · Sources and credits