06Content: Home page and FAQ
Headline (the last word is set in the accent serif), intro text, search description, and the FAQ shown on the home and pricing pages (blocks separated by a blank line, first line = question; empty = the built-in FAQ).
● Set up · Every screen
Admin console
set up everything.
The operator console at /admin is the MIKODES Admin Kit 0.3.0: settings with hard caps, encrypted secrets, team, audit, history and a revenue centre that shows realised money only. The marketplace's own records (payments, providers, members, signals) open inside it. This page follows its sidebar. Screenshots come from the public demo.
01Roles and sign-in
| Role | Can do |
|---|---|
owner | Everything, including team, export and import, and the database backup. |
manager | Change settings and act on records (approve payments, verify providers, end access). |
viewer | Read only. Money fields show "manager only". |
The console has its own sign-in (password of at least 12 characters), separate from the site accounts. The first owner is created with the one-time setup code from the log, the same one that claims the site (how). Security & alerts adds TOTP two-factor with recovery codes, "require two-factor" for owners and managers, sessions and "sign out everywhere". Every change is written to the audit log; secrets are write-only and never appear in a response, an export or the log.
Day-one order
- Get started and Brand.
- Marketplace fees and Payment methods.
- Publishing and Measurement: decide before providers start.
- Integrations: Stripe, Telegram.
- Legal and Access: terms, risk notice, blocked countries.
- Security: two-factor on.
02Overview
Today's net, events, failing blockers, a configuration health score, KPI tiles (net revenue 30 days, members, active providers, paying members, MRR, subscription volume, signals sealed, results computed), 30 days of net revenue, Needs you and recent activity.
03Setup: Get started, Brand, Legal
- Get started: the setup wizard. It refuses to finish while a blocker check fails.
- Brand: site name, tagline, accent colour (dark theme) and light-theme accent, logo, support email, custom CSS (Rebranding). The console also offers a Website field; Receipts does not show it on the public site.
- Legal: terms and privacy URLs, or the text shown at
/termsand/privacy; the disclaimer.
04Money
| Screen | What you set |
|---|---|
| Marketplace fees | Currency (USD, EUR, GBP), commission on subscriptions (hard cap 50 %), Provider Pro per month, verification fee, performance billing switch, provider price range, exchange trade links, sponsored provider slugs. |
| Payment methods | Bank transfer with your instructions; stablecoins to your own wallets (8 networks); extra crypto instructions. |
| Referrals | Referral programme on/off, tier 1 and tier 2 share of your fee, payout threshold, disclosure text. |
| Plans, trials and referrals | Months a referral keeps earning, the longest free trial providers may offer, plan lengths providers may sell (1, 3, 6, 12 months). |
| Payments to confirm | Bank and crypto payments waiting for you: approve, reject, refund. |
| Payouts | Provider and referrer payout requests. Mark paid with a reference after you send the money yourself, or reject. |
| Ledger | Every payment, refund and adjustment with the split. CSV export (owner only). |
| Coupons | Create and switch coupons for bank and crypto payments. |
Details and caps: Earnings.
05Product
| Screen | What you set |
|---|---|
| Access | Open sign-up, maintenance mode and message (reading and verifying stay open), announcement banner, blocked countries, the country header (default cf-ipcountry). |
| Publishing | Price sources, default visibility for new providers, open signals per provider (20), signals per 24 h (30), longest expiry (30 days), webhook and Telegram publishing, the embeddable badge, provider approval. |
| Measurement | Reaction window (30 s), venue fee and slippage per side (5 + 5 bps), closed signals and days to rank (30 / 60), shrink k (20), anchor interval (10 minutes, 5–60). Saving recalculates every result, closed ones included. |
| Delivery | Web push, Discord channels, Telegram DMs and VIP group posts, the Telegram footer, the risk notice shown on every page. |
| Providers | Search, verify or unverify, decline a verification request, give 30 days of Pro, suspend or restore. Sealed history is never deleted. |
| Members | Make someone an operator or a member, suspend or restore. |
| Subscriptions | Every subscription with its type (Stripe, bank, crypto, performance, demo, free access). Give free access for 1–365 days; end access now. |
| Signals | Every signal, filtered by status, provider or symbol. Nothing can be edited or deleted here, or anywhere. |
07System: Integrations, Notifications, Security, Export / Import
- Integrations: Stripe secret key, Stripe webhook signing secret, Telegram bot token, each with a connection test. A value set in
.envlocks the field. Restart after changing them. - Notifications: HMAC-signed alert webhooks when a blocker fails or net revenue stays at zero, with a test button.
- Security & alerts: two-factor, sessions.
- Export / Import (owner only): the whole configuration as a file; import with a preview. Secrets are never exported.
08Monitor: Operations, Anchors, Revenue, Status, Audit, History
- Operations queue: payments to confirm, provider and referral payouts, verification requests; members, providers, open signals and seals waiting for an anchor.
- Anchors and Bitcoin proofs: every batch with its Merkle root, seals, OpenTimestamps status and, once confirmed, the Bitcoin block. Seal a batch now skips the wait; optionally store your own on-chain memo reference per batch.
- Revenue: realised events only (commission, Provider Pro, verification fees, refunds and disputes, referral rewards), daily chart, sources, CSV. Demo payments never count.
- Status: members have a way to pay, wallet addresses match their network, Stripe keys complete, open signals priced, seals batched on schedule, Telegram bot answers, OpenTimestamps accepts batches, batches confirm in Bitcoin.
- Audit log and History: every change with who and when; configuration versions with diff and rollback.
- Team: invite members with a role.
09Operations pages and backup
The marketplace records also live at /ops, which the console frames as its product pages. /ops is gated by the console session; writes need a manager. Every action is written to the console audit log as product.*.
Data backup (owner only) downloads a snapshot of the database from the Operations page. For scheduled backups see Deployment → Backups.
