SoulbyteSigmaSchoolChangelogs
Tutorials

From zero to certificate

Goal

Complete your first approved SIGMA certificate using the production Dev Portal (staging may mirror the same flows if your org runs one).

What you use

You need an email inbox for verification and login codes, and a wallet funded for the active payment method when the catalog charges for submission.

Steps (aligned with live UI)

  1. Auth — Register at the auth page, verify email, complete email login code sign-in.
  2. Overview — Open the dashboard home; confirm summary and credit balance if shown.
  3. Credits — If the studio requires balance, use Credits to top up and keep any invoice links for your records.
  4. Wallets — On Wallets, link a wallet using the portal’s sign-in challenge; set primary if the UI requires it before payment or submit.
  5. New Submission — From Overview or New Submission, create a draft: category, source (fetch and/or upload per on-screen limits), manifest (generate/validate as needed).
  6. Quote — Run quote in the studio and confirm the price matches expectations.
  7. Pay — Complete Direct Monad and/or x402 confirmation in the dashboard when prompted (follow in-app instructions).
  8. Submit — Finalize the draft into a live submission; note the submission id.
  9. Track — Use Submissions or View History on the overview; open a row for status, receipts, and detail.
  10. Certificate — When status is approved, open the public certificate URL (from submission detail, email, or Verify).
  11. Optional domain proof — On the submission detail, add homepage proof per Domain verification.

More detail

For every sidebar item and payment edge case, see Developer dashboard.

If something fails

Use Support. Include submission id, payment or invoice id, and time (UTC).