Developer dashboard
Where the dashboard lives
The developer console is the gated area of the SIGMA Dev Portal:
https://devs.soulbyte.fun/dashboard/
Sign-in and registration:
https://devs.soulbyte.fun/auth
The shell shows SIGMA NETWORK, network badge (Monad Mainnet), and SIGMA v4 · Active when connected. Quick actions on the overview include New Submission and View History (submissions).
After you sign in
- Complete registration (email + password; stored securely server-side).
- Verify email using the link or code from your inbox.
- Login — request a login code by email, then enter it to open a session.
- Session length is configured server-side (often around one week). Log out ends the session in the browser and on the server.
If your org puts the portal behind Cloudflare Access or similar, use a browser session that already passed that gate.
Primary navigation (sidebar)
These entries match the dashboard chrome:
| Label in UI | Path | Purpose |
|---|---|---|
| Overview | /dashboard | Mission control: summary, alerts, credits snapshot |
| Submissions | /dashboard/submissions | List and open submission detail (status, receipts, domain proof, escalations) |
| Credits | /dashboard/credits | Balance, top-up, invoices |
| Wallets | /dashboard/wallets | Link and manage wallets (sign-in challenge flow) |
| Support | /dashboard/support | Support tickets / contact |
| Settings | /dashboard/profile | Account / profile (labeled “Settings” in the nav) |
“More” / secondary links
| Label | Destination |
|---|---|
| Docs | https://docs.soulbyte.fun/sigma (this site; opens in a new tab in-app) |
| Public Portal | https://devs.soulbyte.fun/ — marketing, verify, certificate pages |
Overview screen
Use Overview as the landing view after login:
- Summary cards and alerts for drafts, payments, submissions in review, retries, and low balance (when shown).
- Primary CTAs: New Submission, View History / links into Submissions.
Submissions
- Submissions — recent archive; each row opens a detail page for that submission.
- Submissions (table) — tabular archive when you need a dense list.
- On detail: verdict timeline and receipts, support escalations, human intervention when the category allows, and domain verification after approval (Domain verification).
Credits and invoices
Credits is where you add balance and open invoice pages after top-up. If you see a low-balance reminder, top up before finalizing a paid submission.
Wallets
Linking uses a wallet sign-in challenge (you connect the wallet in the browser and sign—no pasting addresses manually):
- Connect with MetaMask or another injected wallet.
- The portal asks you to sign a one-time challenge.
- After verification, the wallet appears as linked.
- Set primary when the product requires it before payment or submit.
New submission (studio)
New Submission — the submission studio:
- Source — fetch from GitHub and/or upload per on-screen limits (Markdown and manifest rules follow the UI).
- Draft — saved as you work; return via Overview or history.
- Quote — shows the priced snapshot before you pay.
- Manifest — optional AI-assisted generation with validation and cooldowns.
- Submit — finalize when wallet, payment, and validation rules pass.
Paying inside the studio
- Direct Monad — pay to the address and amount shown; confirm in the UI with your transaction when prompted.
- x402 — if enabled, follow the payment required flow and complete confirmation in the portal.
History
The dashboard combines payment and submission history so you can match credits movement to lifecycle state.
Troubleshooting
| Symptom | What to check |
|---|---|
| Quote is zero or wrong | Operator categories, pricing rules, and active campaigns |
| Cannot pay or confirm | Payment methods enabled for your environment; correct network and asset |
| Manifest generation locked | In-app banner and Support — account may be throttled after repeated invalid input |
| Session drops immediately | Browser cookies, VPNs, or SSO policies blocking auth cookies |