Skip to content

Digitalia Marketplace Developer Submission Guide

Version: 1.0
Last updated: 2026-05-15 (UTC)
Audience: Developers submitting apps to Digitalia Marketplace

1. Overview

This guide explains how to submit your DApp to the Digitalia Marketplace, how approval works, and what happens if your submission is rejected.

For Digitalia-controlled networks, publication requires Digitalia approval before listing goes live.

2. Before You Submit

Prepare the following:
1. DApp name, category, and clear description
2. Public application URL (reachable and stable)
3. Supported network details
4. Commercial agreement selection
1% self-build, 30% Digitalia-build, or Joint Venture 5. Acceptance of marketplace terms (captured as a terms hash)

Tips: 1. Ensure your app URL is publicly accessible without auth errors. 2. Keep descriptions factual and specific. 3. Ensure legal, branding, and ownership claims are accurate.

3. Submission Flow

In the Developer Portal:

  1. Complete the submission form (basic info, technical details, assets).
  2. Select one agreement option:
  3. 1% self-build
  4. 30% Digitalia-build
  5. Joint Venture
  6. Accept Marketplace Terms.
  7. Submit.

System behavior: 1. A terms acceptance hash is generated and stored with your submission. 2. On Digitalia-controlled networks, your submission enters an approval queue. 3. On other networks, standard registration is applied.

4. Approval States You Will See

Your submission status progresses through:

  1. SUBMITTED_FOR_DIGITALIA_APPROVAL
    Submitted successfully and waiting in Digitalia queue
  2. UNDER_DIGITALIA_REVIEW
    Assigned to reviewer and currently evaluated
  3. APPROVED_BY_DIGITALIA
    Approved for listing/publication
  4. REJECTED_BY_DIGITALIA
    Not approved, requires corrections and resubmission

5. What Reviewers Check

Digitalia reviewers validate: 1. DApp accessibility and functionality 2. Policy compliance and safety 3. Consistency of network/contract claims 4. Agreement model clarity 5. Terms acceptance evidence integrity

6. If Your Submission Is Rejected

A rejection includes: 1. Reason code(s) 2. Plain-language explanation 3. Required remediation steps

Typical rejection reasons: 1. Invalid or incomplete metadata 2. Application URL unreachable 3. Policy non-compliance 4. Security risk findings 5. Invalid terms hash or agreement mismatch

How to resubmit: 1. Apply all requested corrections. 2. Re-run your internal checks. 3. Submit again from Developer Portal.

Use this checklist before pressing submit: 1. Metadata complete and accurate 2. App URL reachable from public internet 3. Category/tags reflect real functionality 4. Agreement option selected correctly 5. Terms accepted and hash captured 6. Security scan completed internally 7. Support contact and docs links valid

8. SLA Expectations

Typical review windows:
1. Acknowledgement: minutes
2. Initial triage: same day
3. Decision:
standard risk within 2 business days
higher-risk submissions may require up to 5 business days

9. Best Practices For Faster Approval

  1. Provide deterministic release artifacts and version notes.
  2. Avoid placeholder or broken links.
  3. Keep permission requests minimal and justified.
  4. Include concise security notes in your project docs.
  5. Respond quickly to reviewer clarification requests.

10. Support and Escalation

If review appears stalled or unclear: 1. Contact Marketplace support with your submission ID. 2. Include the latest state and timestamps. 3. If needed, request governance escalation through official support channels.

11. FAQ

Q: Why do I need approval on Digitalia Mainnet? A: Mainnet is Digitalia-controlled and requires governance review before publication.

Q: Does selecting an agreement option affect review? A: Yes. The selected agreement model is part of compliance and commercial validation.

Q: Can I edit a pending submission? A: Follow rejection/remediation instructions or submit an updated package where supported by the portal workflow.