Roadmap
From relaunch to the community
The Oracle is what makes SaTT trustworthy — it measures real performance and signs the attestation the contract pays on. This roadmap removes trust from it one layer at a time, until the project belongs to the community as full open source. It starts, deliberately, small.
Month 1 is a public test — testnet first, capped pilot, in the open.
The arc, in one line
Team signs → code opens → many sign → community owns. Trust is removed one layer at a time, and the tokenomics fee keeps flowing to the treasury the whole way.
The five phases
- Live nowT0 — relaunch
Relaunch baseline
One Oracle signer, run by the team. It reads real metrics, runs anti-fraud, and signs an EIP-712 attestation — it never holds funds. Non-custodial, fee-capped and replay-protected from day one, with the tokenomics fee flowing to the treasury on every payout.
- Test monthFirst ~30 days
The test month
A full month of public testing before anything scales. Free testnet campaigns end-to-end, plus a capped mainnet pilot with hard budget limits so any worst case stays bounded. Bug and fraud bounties tune the anti-fraud against real traffic. We advance on exit criteria, not the calendar.
- NextMonths 2–3
Open the code & prove every payout
The whole stack goes open source. We publish the signer address and a verifiable attestation feed — for every payout, the exact data that was signed, so anyone can recompute and check it. First independent audit, published in full.
- PlannedMonths 3–9
Decentralize the signer
Remove the single-operator trust: several independent operators each read the metrics and sign, and the contract requires an M-of-N threshold. Then trust-minimized sources — creator-authenticated reads and zkTLS web proofs — so the Oracle verifies a proof instead of trusting a fetch.
- PlannedMonth 9+
Community handover
The team stops being special. Governance owns the parameters, independent operators run the Oracle, and the project is fully open source. The preserved tokenomics fee funds operators, audits and bounties — so the network pays for its own trust after we step back.
What the test month actually is
Small, real, and in the open — this is where bugs and fraud surface cheaply, before any scale-up.
- Public testnet AdPools with faucet SaTT — create, post and claim end-to-end, for free.
- A capped mainnet pilot: a small allowlist with hard per-campaign and per-day budget limits, so a worst-case loss is bounded and survivable.
- Every attestation logged with its inputs — source, raw metrics, fraud verdict, cooldown — so decisions are reviewable after the fact.
- Bug + fraud bounties: reproducible exploits and escaped engagement-fraud are paid for. Fraud found here is thresholds tuned for free.
Given to the community — with the tokenomics intact
“Full open source” and “keep the tokenomics fee” aren’t in tension. We split the license by layer, so the community gets everything it needs to run and improve the project, while the protocol’s value accrual survives forks.
The web app, backend, indexers, Oracle pipeline and SDKs go out under a permissive license (MIT / Apache-2.0). Run it, fork it, build a business on it — no strings.
Anyone can read, audit and fork the contracts for research or testnet. A commercial deployment is allowed only if it keeps routing the protocol fee to the SaTT treasury — so value accrual can’t simply be forked away.
The invariant, in one sentence: you may take everything, but a commercial deployment of the contracts keeps paying the tokenomics fee to the treasury.
The exact licensing (BUSL-1.1 with a fee-preserving grant, versus a permanent non-commercial license) is a governance decision, and the license text is being finalized with legal review.
How the Oracle works today
Every phase above builds on the same mechanism that is live now: the Oracle signs, the contract verifies and pays, and you stay in custody the whole time.