Repository navigation
Contributor Guide
A useful Kotlin dApp workspace curates dependencies, examples and provenance. It does not need to merge hundreds of unrelated repository files into one build. Such a merge can introduce incompatible licenses, duplicate packages, stale tools and unsafe examples. EdgeORE's product benefits more from a small reviewed integration than from a large source snapshot that no one can qualify.
Before copying source, read the upstream license, notices and compatibility requirements. A repository without a license is not automatically free to reuse. Give credit where required and preserve relevant notices. Naming yourself as the integration author does not replace attribution for upstream code. If only documentation links are needed, a curated reference entry may be better than vendoring an entire project.
Treat Android tools, wallet implementations, storage clients and security research as different categories. A rooting utility or reverse-engineering project is not a required dependency for a wallet review app. A web wallet SDK is not automatically compatible with native Kotlin MWA. Select the smallest library or reference that solves a concrete problem and review the exact version used.
An agent prompt should identify the repository, target revision, task scope, prohibited shortcuts, required checks and acceptance artifacts. For a wallet error fix, ask it to inspect result handling, preserve exact-message review and durable operations, add meaningful regressions and return a build identity. Do not ask it to mark runtime checks PASS when it has no runtime. The instruction should make missing observations an explicit output.
For a storage adapter, begin with a feature branch and a written trust model. For an AI runtime, keep model licensing and download consent visible. For a contribution program, start with an escrow specification and tests rather than an earnings screen. Narrow instructions help an agent complete a reviewable unit without bundling experiments into the candidate that users are testing.
Read the diff, dependency changes, tests and limitations. Compare the branch's claims with preserved outputs. A gate failure should remain a failure until a real rerun passes; another person's successful run is useful context, not a substitute. An agent can prepare code and documentation, while the environment that owns the wallet must perform approvals. Keep that division explicit in session attribution.
Never place private wallet material, API tokens, release passwords or unrelated personal files in an agent-facing workspace archive. Use secure credential mechanisms when an authorized service needs access. A public repository should contain examples, public keys where appropriate and redacted manifests, not the values that allow an attacker to repeat privileged actions.
Submit a focused patch with a concrete problem, resulting behavior, validation and material limitations. Update documentation when a user-visible boundary changes. If the patch adds a new artifact, preserve its hash and source stamp. If it adds only evidence, keep the tested source identity distinct. This approach produces a single coherent EdgeORE project while crediting the ecosystem it builds on, without pretending all upstream work was created by one maintainer.
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