Frontend Trust and Verification

How Arkeo Marketplace evaluates and lists frontends. No governance gatekeeping, just open-source accountability.

No Governance Gatekeeping

Arkeo Marketplace does not use on-chain governance to approve frontends. Listings are curated by the community using open-source review, not token voting or centralized approval. Anyone can build and submit. Quality is maintained through transparency, not bureaucracy.

How Trust Works

🔍

Open Source, Auditable

Every listed frontend must publish its source code publicly. You can read exactly what the app does before using it.

👥

Community Review

Submissions are reviewed by community members on GitHub. Issues, PRs, and discussion are all public and traceable.

🏛️

Curated, Not Governed

Maintainers apply consistent listing criteria. No token vote required, no political process. Just the published requirements.

🔌

Provider Choice

Frontends route through Arkeo providers, but users can configure which provider they use. No single provider lock-in.

🚨

Community Reporting

Anyone can flag a frontend that violates listing requirements. Maintainers review and remove listings that no longer meet standards.

🔄

Versioned and Traceable

Listing decisions are made in public Git history. You can see when a frontend was added, changed, or removed and by whom.

What the Review Checks

Criterion What Reviewers Look For
Source available Public repository, readable code, no obfuscated bundles without source maps
Arkeo integration Data requests genuinely route through Arkeo protocol, not just re-branded centralized endpoints
No malicious code No key loggers, no unauthorized token approvals, no hidden tracking pixels or analytics calls to unknown servers
Functional App is live and its core feature works. Broken or incomplete apps are not listed.
Distinct purpose Offers something meaningfully different from other listed frontends. Duplicate clones not listed.
Maintainer reachable Someone responds to GitHub issues or Discord questions. Ghost projects are flagged for removal.

Provider Choice: Your Control

Frontends route requests through Arkeo providers, but you are never locked in. Every Arkeo-compatible frontend allows you to:

  • Choose any provider from the directory
  • Open your own PAYG contract with any provider
  • Switch providers without losing data or account history
  • Self-host a frontend and point it at your preferred provider
No vendor lock-in. If you dislike a frontend or provider, you switch. Your contracts are on-chain, not held by any company.

Frequently Asked Questions

Does Arkeo endorse every listed frontend?
No. A listing means the frontend passed the open-source review criteria at the time it was submitted. It does not mean the Arkeo Foundation or any community member vouches for the frontend's financial advice, UI choices, or ongoing maintenance. Always review the source yourself before depositing funds.
Can a frontend be delisted?
Yes. If a frontend becomes unmaintained, moves its code closed-source, adds malicious behavior, or stops routing through Arkeo, the community can open a GitHub issue requesting removal. Maintainers review and act.
Is token voting used for listing decisions?
No. Token voting introduces plutocracy risks. Listings use open published criteria and community review, not token-weighted governance. This keeps the process accessible to small builders and prevents whale capture.
What if I find a problem with a listed frontend?
Open a GitHub issue on arkeo-data-engine-v2 describing the issue. For urgent security concerns, also post in the #security channel on Discord. If the issue is confirmed, the listing will be suspended pending resolution.
Can I fork a listed frontend and submit my version?
Yes, if your fork offers meaningful improvements or specialization. A copy with just a logo swap will not be listed. Show what your version adds and why users would prefer it.
How do I know a frontend is not stealing my keys?
Read the source code. All listed frontends are open source. You can also use a hardware wallet (Ledger, Trezor) for signing, which means your private key never touches the frontend code. Never paste a private key or seed phrase into any web app.
What does "routes through Arkeo" mean exactly?
It means the frontend connects to the Arkeo sentinel network to serve blockchain data. Requests include valid PAYG or subscription authentication headers. The frontend is not just a wrapper around Infura or another centralized API with Arkeo branding.
🚀

Ready to submit your frontend?

Fill out the submission form and open a GitHub issue. The community will review it.

Submit a Frontend Browse Frontends