In one line
SkoopoS serves real ads from real campaigns through a real browser extension and settles the spend — off chain today, with the on-chain pallets wired and waiting.
Done
- Backend: campaign management, delivery, analytics, publisher spaces. Ad matching upgraded from highest-bid-wins to Ad Rank (
bid × (1 + category-overlap)) — the same shape as bid × quality score, using category overlap as the only relevance signal the platform has at this scale. Frequency capping (default 3/day per user per campaign, advertiser-overridable). Creative A/B rotation with real click-through measurement. A real brand account type. - The circuit (30 July 2026): a campaign created in the Console's real UI → the real extension loaded in a real Chrome via Playwright → served on a test page → a real click → spend reflected in the Console and the platform data. Four extension bugs found that had made ad serving fail silently forever (a missing
alarmspermission that crashed initialisation before the API client existed; a CSP that blocked the real backend host; two more). None had been found before because nothing had run the real extension against a real campaign. - Consoles: admin (12 pages) and advertiser console with real authentication; the unified platform had never had a public URL until July 2026 and now does (Vercel).
- Aephoron integration: the browser's native ads crate connected to the SkoopoS backend, verified.
- App (
com.skoopos.skoopos): brand-impersonation and seed-loss paths closed in August; 56/56 tests. - On chain:
SkooposCampaign(escrow for bids),SkooposPov(proof-of-view, 70 % viewer / 30 % treasury),SkooposSponsor(brand–creator offers with level-based fees),SkooposBlocks(daily slot auction),SkooposReputation— runtime indexes 111–115 (the ads group is 116–122 in the architecture map; the on-chain flow document lists the settlement pallets above).
Compliance model
SkoopoS is structured like a platform-ads business relative to GnoosiS and PhoonoS: advertiser money flows through the web consoles or the API, never through in-app purchases in a store-distributed app. Advertising is a B2B service outside app-store billing — verified against the store's payments policy. Two obligations remain regardless: the financial-features declaration for apps that credit DMS, and marketing copy that never frames earning DMS as income. One open question — whether earning DMS by watching an ad inside an app touches billing rules — is flagged for confirmation before shipping to real users.
Not done
skoopos.comreturns 404, as does its hosting fallback — a known hosting-corruption issue with the provider.- On-chain settlement of a real campaign: pallets wired, app writes to a local store and queues chain intents; no campaign has settled on the public testnet.
- Publisher embed client: the portal accepts an optional viewer id for one; none exists yet.
- Proof-of-view antifraud beyond the current model: in development.
Why it is in the ecosystem
Because GnoosiS, PhoonoS and Aephoron need an ad system that pays viewers and creators in DMS and can prove a view happened — and because a chain with escrow, PoV settlement and reputation as pallets can make "verified" mean something. The circuit works; the chain leg is next.
Based on the SkoopoS extension circuit (2026-07-30), Ads Engine v2, the app audit (2026-08-22), the payments compliance document and SKOOPOS_ADS_ONCHAIN.md.