SoulbyteSigmaSchoolChangelogs
Dev portal

Public surface and routes

Production host

The SIGMA Dev Portal is https://devs.soulbyte.tech. After you sign in, the developer dashboard is https://devs.soulbyte.tech/dashboard/.

The portal is a web app backed by Soulbyte’s SIGMA APIs. All URLs in this section are production unless stated otherwise.

Public routes (no login)

Examples:

  • Marketing home — stats, categories, and protocol copy (with sensible fallbacks if a data call fails).
  • Docs in marketing nav may point to https://docs.soulbyte.tech/sigma.
  • Verify, Marketplace, Leaderboard, FAQ, Transparency, Why verify, Certificate pages, and discovery assets (llms.txt, sitemap, robots, .well-known endpoints, badge routes).

Landing payload (abbrev.)

Typical bundled fields include:

  • stats — approved certificates, active validators, actor count, starting USD price
  • categories — active submission catalog with optional campaign pricing
  • protocol — minimum deposit, auditors per round, yield label, manifest model label, network name (e.g. Monad)

Authenticated routes (dashboard)

PathRole
https://devs.soulbyte.tech/authRegister, verify email, login code
https://devs.soulbyte.tech/dashboardOverview
https://devs.soulbyte.tech/dashboard/submissionsSubmissions list / archive
https://devs.soulbyte.tech/dashboard/submissions/tableTabular submissions view
https://devs.soulbyte.tech/dashboard/submissions/<id>Submission detail
https://devs.soulbyte.tech/dashboard/creditsCredits / top-up
https://devs.soulbyte.tech/dashboard/invoice/<id>Invoice after purchase
https://devs.soulbyte.tech/dashboard/walletsWallets
https://devs.soulbyte.tech/dashboard/supportSupport
https://devs.soulbyte.tech/dashboard/profileSettings (profile) in sidebar
https://devs.soulbyte.tech/dashboard/newNew Submission studio

Design: dark auth shell; dense dashboard chrome with sidebar labels.

Submission lanes

The studio now supports two intake lanes:

  • Public — default lane. Uses a public GitHub source, can appear on public verify surfaces, and can emit off-chain and on-chain SIGMA certificates when approved.
  • Private — internal review lane. Uses the same Sigma review infrastructure, but it does not emit certificate pages, verify endpoints, browse listings, domain verification proofs, off-chain certificates, or on-chain commits.

Private code-bearing submissions may use either:

  • Private GitHub intake
  • Direct upload intake using loose files or supported archives

Supported private archives:

  • .zip
  • .tar.gz
  • .tar.bz2

Private uploads are screened before review. SIGMA rejects unsafe archives, including path traversal attempts, symlinks, oversized decompression, duplicate normalized paths, and deeply nested trees.

API family

Authenticated browser calls use the developer API under /api/v1/sigma/dev/* with your portal session. See API surface.

SEO

Canonical URLs use devs.soulbyte.tech in production.

Next

Step-by-step usage: Developer dashboard.